(iSeries)

Starting and configuring default deployment manager profiles on IBM i

WebSphere Application Server Network Deployment provides a configurable default deployment manager profile that we create using the manageprofiles command after installation.

Read the Network Deployment deployment manager profile article. The article describes the profile and how to change TCP/IP ports that it uses.

After installing WAS Network Deployment, we can start, configure and run the default deployment manager profile.

Tasks

1. Start the default deployment manager.

   1. On the Control Language (CL) command line, run the Start Qshell (STRQSH) command.

   2. At the Qshell prompt,s:

      cd app_server_root/bin
      startServer dmgr
      

      The startServer command starts the QWAS9 subsystem if it is not already started.

2. 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.

3. Add a node to the network deployment profile, as described in Add nodes to deployment manager profiles on IBM i.

   Run the addNode command from the Qshell command shell to federate the default application server profile into the Network Deployment cell.

4. Verify that the node agent is running, as described in Verifying that the node agent is running on IBM i.

   Use the Work with Active Jobs (WRKACTJOB) command to determine when the node agent is ready to accept administrative requests through the administrative console.

5. Start the administrative console for the deployment manager.

   Open the administrative console in a web browser, as described in Starting the administrative console for deployment managers on IBM i.

6. Verify that the node exists, as described in Verifying that nodes exist on IBM i.

   Use the administrative console to verify that the WAS 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.

What to do next

Repeat the previous steps for each node (or application server profile) to manage using the deployment manager profile.

Subtopics

• (iSeries) Verifying that the deployment manager is running on IBM i
  This article describes how to verify that the deployment manager is running before starting the administrative console.
• (iSeries) Add nodes to deployment manager profiles on IBM i
  We can add WAS nodes to the cell that the deployment manager profile is managing.
• (iSeries) Verifying that the node agent is running on IBM i
  Verify that the node agent is running before starting the administrative console.
• (iSeries) Starting the administrative console for deployment managers on IBM i
  The administrative console is a Web-based application that runs on any browser supported by WAS. This article describes how to start the administrative console for the deployment manager.
• (iSeries) Verifying that nodes exist on IBM i
  This article describes how to verify that the WAS node was successfully added to the deployment manager domain.

Starting WAS on IBM i

Add nodes to deployment manager profiles on IBM i

Verifying that the node agent is running on IBM i

Starting the administrative console for deployment managers on IBM i

Verifying that nodes exist on IBM i