WebSphere Application Server Network Deployment provides a configurable
default deployment manager profile.
About this task
After you install WebSphere Application Server Network Deployment,
you can start, configure and run the default deployment manager profile.
Procedure
- Start the default deployment manager.
- On the Control Language (CL) command line, run the Start Qshell
(STRQSH) command.
- At the Qshell prompt, run the following commands:
The startServer command
starts the QWAS61 subsystem if it is not already started.
- Verify that the deployment manager is running
Use
the Work with Active Jobs (WRKACTJOB) command to determine
when the deployment manager is ready to accept administrative requests through
the administrative console.
- Add a node to the network deployment profile, as described in Adding a node to the deployment manager profile.
Run the addNode command
from the Qshell command shell to federate the default application server profile
into the Network Deployment cell.
- Verify that the node agent is running, as described in Verifying that the node agent is running.
Use the Work with Active Jobs (WRKACTJOB)
command to determine when the node agent is ready to accept administrative
requests through the administrative console.
- Start the administrative console for the deployment manager.
Open the administrative console in a Web browser, as described in Starting the administrative console for the deployment manager.
- Verify that the node exists, as described in Verifying that the node exists.
Use the administrative console to verify
that the WebSphere Application Server node was successfully added to the deployment
manager domain.
Results
The addNode command creates a new server, the
node agent, under the application server profile being added to the Network
Deployment domain. The node agent server is started as a side effect of adding
the node to the domain.
What to do next
Repeat the previous steps for each node (or application server
profile) that you want to manage using your deployment manager profile.
Next: Go
to Verifying that the deployment manager is running to verify that the
deployment manager is running.