InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.46: Administering WebSphere administrative servers (overview) >
6.6.46.5: Having administrative servers start automatically

6.6.46.5: Having administrative servers start automatically

By default, the administrative server does not start automatically when a machine is started (or rebooted). This article provides information about starting the server automatically on Windows NT, triggered by system reboots and other events.

Starting the server when Windows NT starts

On Windows NT, you can use the Services panel to configure the administrative server service to start automatically.

You might also create batch files to run the service. Note than when started from a command line on Windows NT, for example:

net start IBM WS AdminServer 4.0
the administrative server falsely indicates that it has failed to start. Use the NT Services Panel to verify whether it actually started.

Starting the server when IBM DB2 starts

To have the WebSphere administrative server start automatically after DB2 starts on Windows NT, use the following procedure.

  Take great care in modifying registry entries. The procedure is straightforward, but could cause unintended consequences if you make a mistake while entering data. Use this procedure at your own risk. If possible, try the procedure on a test machine first.

  1. Open the Windows NT Services Panel.
  2. Verify that the DB2 and WebSphere administrative server services are set to start automatically.
  3. Start regedt32 (not regedit).
    1. Locate HKEY_LOCAL_MACHINE\Current Control Set\Services\IBM WS AdminServer 4.0
    2. If this value name and type does not exist, create it:
      • Value Name: DependOnService
      • Value Type: REG_MULTI_SZ

      To create it, use the Edit -> Add Value menu option. When creating it, you will be prompted to specify data...

    3. Assign two pieces of data to the value:
      • DB2
      • DB2DAS00 (last two digits are zeroes)

      List one piece of data on each line.

  4. Save the changes and close regedt32.
  5. Reboot the machine. Verify that the administrative server started automatically after the DB2 service started.

Go to previous article: Administrative server configuration file properties Go to next article: Using administrative server agents

 

 
Go to previous article: Administrative server configuration file properties Go to next article: Using administrative server agents