How to Install a Deployment Manager

When your configuration contains multiple standalone application servers you can manage them with a deployment manager. The deployment manager tracks which applications are being deployed to which application server instance.

You can use this procedure to create a deployment manager or you use this procedure to register an existing deployment manager within the provisioning system.

This task is performed as root.

Steps

1. Ensure that your WebSphere session variables, WS_DEFAULT_USER and WS_DEFAULT_PASSWORD, are set.

   For more information about session variables, see Chapter 5, Session Variables, in N1 Grid Service Provisioning System 5.0 Plan and Component Developer’s Guide.

2. In the Common Tasks section in the browser interface, click WebSphere 5.1.

3. Click the Network Deployment Manager: Install link.

   The plan's Details page displays.

4. Click Run.

   The plan's Run page displays.

5. In the Plan Parameters area, select the variable settings for the NetworkDeploymentInstall component that you plan to deploy.

   • If the variable settings have been established for this component, select the appropriate settings from the menu.

   • If the settings are not available from the menu, click Select From List.

     The Select Variable Settings From List window displays.

     • To create a new set of variable settings, select Create Set.

       The NetworkDeploymentInstall variable settings rely primarily on the standalone application server's variable setting values.

       ---

       Note –

       If you change the default port values for the deployment manager, ensure that they do not conflict with the standalone application server's port values.

       ---

       variable set name

       Required. A name for the new variable set you create.

       installPath

       Required. The location where you plan to install the WebSphere deployment manager.

       The default value for installPath is /opt/was51nd.

       installerHome

       Required. The location of the deployment manager installer

       ---

       Note –

       Do not include extra spaces after the path name.

       ---

       name

       Required. The name of the deployment manager's virtual host.

       httpServerPort

       Required for regular web access. The web server port number.

       httpsTrnsprtPort

       Required for secure web access. The secure web server port number.

       bootstrap

       Required. The bootstrap port. You must change the port number if you install a standalone application server and a deployment manager on the same remote agent.

   • To use variable components from another component, click Import Set.

     For more information about importing variable sets, see How to Run a Plan in N1 Grid Service Provisioning System 5.0 Operation and Provisioning Guide.

6. Select the target host.

   Install the deployment manager on a remote agent.

   ---

   Note –

   The target host must be a member of the com.sun.was#InstallTargetHS host set.

   ---

7. Deselect the Target Host Set checkbox.

8. If you are capturing an existing standalone application server within the provisioning system, select the markOnly Install option.

   This option enables you to create a component that represents an existing WebSphere 5.1object and then manage the object through the provisioning system.

9. Click Run Plan (Includes Preflight).

10. Verify that the new deployment manager virtual host was created by viewing the Hosts page.