WebSphere Application Server Network Deployment provides a configurable default deployment manager profile. Read about the Network Deployment deployment manager profile. The article describes the profile and how to change TCP/IP ports that it uses.
cd app_server_root/bin startServer dmgr
The startServer command starts the QWAS61 subsystem if it is not already started.
Use the Work with Active Jobs (WRKACTJOB) command to determine when the deployment manager is ready to accept administrative requests through the administrative console.
Run the addNode command from the Qshell command shell to federate the default application server profile into the Network Deployment cell.
Use the Work with Active Jobs (WRKACTJOB) command to determine when the node agent is ready to accept administrative requests through the administrative console.
Open the administrative console in a Web browser, as described in Starting the administrative console for the deployment manager.
Use the administrative console to verify that the WebSphere Application Server node was successfully added to the deployment manager domain.
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.
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.