3.6.1 Starting a distributed server environment

An orderly procedure for starting a distributed server environment involves the following steps:

1.	On the deployment manager machine:

a. Change the directory to the <profile_home>/bin directory of the ND installation.

b. Use the startManager command to start the deployment manager.

If you are successful, you will see the process ID for the deployment manager process displayed on the window. See Example 3-6.

Example 3-6 Starting the deployment manager from the command line

C:\myWAS61Profiles\dmgrProfiles\DmgrProfile1\bin>startmanager
ADMU0116I: Tool information is being logged in file
C:\myWAS61Profiles\dmgrProfiles\DmgrProfile1\logs\dmgr\startServer.log
ADMU0128I: Starting tool with the DmgrProfile1 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 1120

If there are any errors, check the log file for the dmgr process:

<profile_home>/logs/dmgr/SystemOut.log

2.	On each node...

a. Change directory to the <profile_home>/bin directory for the appserver on that node.

b. Run the startNode command.

If successful, the node agent server process ID will be displayed on the window, as shown in this sample:

C:\myWAS61Profiles\appSrvrProfiles\AppSrvProfile1\bin>startnode

ADMU0116I: Tool information is being logged in file 
C:\myWAS61Profiles\appSrvrProfiles\AppSrvProfile1\logs\nodeagent\sta
rtServer.log

ADMU0128I: Starting tool with the AppSrvProfile1 profile

ADMU3100I: Reading configuration for server: nodeagent

ADMU3200I: Server launched. Waiting for initialization status.

ADMU3000I: Server nodeagent open for e-business; process id is 3356

If there are any errors, check the log file for the node agent process by typing this command:

<profile_home>/logs/nodeagent/SystemOut.log

c. Use the startServer command to start each of the appserver processes on the node.

d. Check the node status by running the serverStatus -all command.

3.	Repeat step 2 for each and every node associated with this deployment manager.