test

N1 Grid Service Provisioning System User's Guide and Release Notes for the WebSphere Plug-In 1.0

Creating WebSphere Infrastructure Components

Before you can deploy applications to WebSphere application servers, you must either install the WebSphere components by using the provisioning system or capture the existing WebSphere configuration.

ProcedureHow to Install a Standalone WebSphere Application Server

You must install a standalone application server before you can set up application server instances to service your applications. A standalone application server can hold a set of application server instances. The standalone application server can be managed as a single entity or by a deployment manager. All information about the application server is contained both on the application server and, if used, on the deployment manager.

When you create a new standalone application server by installing the component, you also:

You can use this procedure to create a standalone WebSphere application server or you can use this procedure to register an existing standalone application server within the provisioning system.

Note –

This task is performed as root.

Before You Begin

To create a standalone application server, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.

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 WebSphere Application Server for Standalone Systems: 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 StandaloneInstall 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 following list provides commonly updated variables for the StandaloneInstall component. You can keep the default values for most variables.

        Note –

        If you change the default port values for the standalone application server, ensure that they do not conflict with the deployment manager'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 WebSphere 5.1. The default value for installPath is the install path that was used during the most recent installation of a WebSphere component.

        installerHome

        Required. The location of the standalone application server installer.

        Note –

        Do not include extra spaces after the path name.

        name

        Required. The name of the standalone application server virtual host.

    • 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. In the Plan Parameters area, select the Default variable set for the AppInstance component that you plan to deploy.

    Note –

    If you decide to create a new variable set, do not change the application server instance name. The name must be server1, otherwise the installation will fail.

  7. Select the target host.

    The standalone application server is installed on the remote agent that you select as target host.

    Note –

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

  8. Deselect the Target Host Set checkbox.

  9. 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.1 object and then manage the object through the provisioning system.

  10. Click Run Plan (Includes Preflight).

  11. View the Hosts page to verify that the standalone application server and application server instance virtual hosts were created.

ProcedureHow to Create an Application Server Instance

When you create a standalone application server, you automatically create one application server instance, server1. If you must create additional application server instances, use this procedure.

You can use this procedure to create an application server instance or you can use this procedure to capture an existing application server instance within the provisioning system.

Note –

This task is performed as root.

Before You Begin

Before you create an application server instance, you must create a standalone application server. For more information, see How to Install a Standalone WebSphere Application Server.

Steps

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

  2. Click the Application Server Instances: Install link.

    The plan's Details page displays.

  3. Click Run.

    The plan's Run page displays.

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

    Each new application server instance needs a unique name. You must create a new variable set to indicate the name for each new application server instance.

    • 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 following list provides commonly-updated variables for the AppInstance component. The AppInstance variable settings rely primarily on the standalone application server's variable setting values. You can keep the default values for most variables.

        variable set name

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

        name

        Required. The name of the application server instance.

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

  5. Select the target host.

    Install the application server instance on the virtual host of a standalone application server.

  6. Deselect the Target Host Set checkbox.

  7. 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.1 object and then manage the object through the provisioning system.

  8. Click Run Plan (Includes Preflight).

  9. View the Hosts page to verify that the new application server instance virtual host was created.

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

Note –

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.

ProcedureHow to Add Nodes to the Deployment Manager

For a deployment manager to track which applications are deployed to different standalone application servers, you must add the standalone application servers to the deployment manager. The process of adding nodes to the deployment manager is also called federation.

Note –

This task is performed as root.

Before You Begin

Before you can add nodes to a deployment manager, the deployment manager must be installed. For information on installing a deployment manager, see How to Install a Deployment Manager.

Steps

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

  2. Click the Network Deployment Manager: Federate link.

    The plan's Details page displays.

  3. Click Run.

    The plan's Run page displays.

  4. Select the target host.

    Select the standalone application server virtual host that you plan to federate.

  5. Deselect the Target Host Set checkbox.

  6. Type the name of the deployment manager virtual host with which you plan to federate the standalone application server.

  7. If you want to copy applications from the federated node to the deployment manager, ensure that the includeApps option is set to true.

  8. If you are creating a representation of an existing, federated standalone application server, select the markOnly Install field.

    This option enables you to represent an existing WebSphere 5.1 object and then manage through the provisioning system.

  9. Click Run Plan (Includes Preflight).

    After federation, the standalone application server virtual host's host type attributes, cellName and dmHost, are updated with the appropriate information.

ProcedureHow to Create a WebSphere Cluster

When you create a WebSphere cluster through the provisioning system, you create an empty container that can hold cluster members. To add cluster members to a cluster, see How to Add Cluster Members.

Note –

This task is performed as root.

Steps

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

  2. Click the Cluster Management: Create link.

    The plan's Details page displays.

  3. Click Run.

    The plan's Run page displays.

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

    Each new cluster needs a unique name. You must create a new variable set to indicate the new name for each cluster.

    • 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 following list provides commonly updated variables for the Cluster component. You can keep the default values for most variables.

        variable set name

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

        name

        Required. The name of the cluster.

        clusterSPSName

        Required. The name of the cluster virtual host.

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

  5. Select the target host.

    Target the virtual host of the deployment manager that will manage the cluster.

  6. Deselect the Target Host Set checkbox.

  7. If you are creating a representation of an existing cluster, select the markOnly Install option.

    This option enables you to represent an existing WebSphere 5.1 object and then manage through the provisioning system.

  8. Click Run Plan (Includes Preflight).

  9. View the Hosts page to verify that the cluster virtual host was created.

ProcedureHow to Add Cluster Members

The procedure creates new cluster members in selected clusters.

Note –

This task is performed as root.

Steps

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

  2. Click the Cluster Member Management: Join link.

    The plan's Details page displays.

  3. Click Run.

    The plan's Run page displays.

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

    Each new cluster member needs a unique name. You must create a new variable set to indicate the name for each new cluster member.

    • 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 following list provides commonly-updated variables for the ClusterMember component. You can keep the default values for most variables.

        variable set name

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

        name

        Required. The name of the cluster member.

        cmemberSPSName

        Required. The name of the cluster member virtual host.

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

  5. Select the target host.

    You target the cluster virtual host where you plan to add the cluster member.

  6. Deselect the Target Host Set checkbox.

  7. If you are creating a representation of an existing cluster member, select the markOnly Install option.

    This option enables you to represent an existing WebSphere 5.1 object and then manage through the provisioning system.

  8. Click Run Plan (Includes Preflight).

  9. Click the View Cluster Members link on the WebSphere 5.1 Common Tasks page to verify that the cluster members were created.