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

ProcedureHow to Configure the Master Server for the WebSphere Plug-in

The WebSphere plug-in requires some minor modifications of the basic provisioning system configuration to allow communication between applications and to allow sufficient time for plans to run.

Steps
  1. Import the plug-in.

    See Acquiring the WebSphere Plug-In.

  2. Set the WebSphere 5.1 session variables: WS_DEFAULT_USER and WS_DEFAULT_PASSWORD.

    These variables are used during standalone application server installation, deployment manager installation, and node federation.

  3. Create a virtual host to represent the provisioning system's command-line interface (CLI).

    Use the following attributes to define the virtual host.

    • host: cliHost

    • host type: com.sun.was#cliHT

    • cliLoc: the absolute path to the CLI.

      For example, InstallPath/cli/bin/cr_cli

    • parent host: The remote agent located on the Master Server.

  4. Install the CLI on the machine running the Master Server.

  5. Install and start the Remote Agent software on the machine running the Master Server.

  6. Go to the Master Server's Host Edit page and select the Include Remote Agent On This Physical Host option.

  7. Modify the Master Server's config.properties file.

    The allowSessionIDOnHosts value enables the plug-in communicate with the Master Server through the CLI and Remote Agent interface.

    The defaultPlanTimeout value enables you to increase the amount of time that a plan can run. The value is represented in seconds. Add this line if you need to increase the default plan run time from the 30–minute (1800 second) default value. The above example is an arbitrary value of 100 minutes (6000 seconds).

    Add the following lines to the file.


    config.allowSessionIDOnHosts=masterserver
    pe.defaultPlanTimeout=6000

    The config.properties file's default location is /opt/SUNWn1sps/N1_Grid_Service_Provisioning_System_5.0/server/config.

  8. Restart the Master Server.