test

Sun N1 Service Provisioning System User's Guide for WebSphere Plug-In 3.0

Chapter 3 Installing and Configuring the WebSphere Plug-In

This chapter explains how to install and configure the WebSphere plug-in. The chapter contains the following information:

Acquiring the WebSphere Plug-In

Acquiring the WebSphere 5.1 plug-in is a two-step process. First, you must add the package file that contains the WebSphere 5.1 plug-in JAR file to your system. Then you must import the WebSphere 5.1 plug-in JAR file.

The IBM WebSphere Application Server 5.1 solution is packaged as a plug-in to the Sun N1 Service Provisioning System software. Plug-ins are packaged in JavaTM Archive (JAR) files. The plug-in files for the WebSphere Application Server solution are available from the Sun N1 Service Provisioning System Supplement CD or from the Sun Download Center.

Once the package file is added to your system, the WebSphere Plug-In is available for import from two different JAR files. Choose the correct file depending on your situation.

  1. Add the package containing the JAR file.

  2. Import the JAR file – Importing the WebSphere Plug-In to the Sun N1 Service Provisioning System

Adding the WebSphere Plug-In for Solaris

The WebSphere 5.1 plug-in is contained in the SUNWspswas package.

ProcedureTo Add the WebSphere Plug-In for Solaris

Steps

  1. In a terminal window, become superuser.

  2. Move to the directory containing the plug–in package.

  3. Type the following command and press Return.

    # pkgadd -d . SUNWspswas

    The standalone JAR file is in the /opt/SUNWn1sps/plugins/com.sun.was/ directory. The upgrade JAR file is in the /opt/SUNWn1sps/plugins/com.sun.was/Upgrade directory.

Adding the WebSphere Plug-In for Linux

The WebSphere 5.1 plug-in is contained in the sun-spswas-3.0-1.noarch.rpm file.

ProcedureTo Add the WebSphere Plug-In for Linux

Steps

  1. In a terminal window, become superuser.

  2. Move to the directory containing the sun-spswas-3.0-1.noarch.rpm file.

  3. Type the following command and press Return.

    # rpm –i sun-spswas-3.0-1.noarch.rpm

    The standalone JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.was/ directory. The upgrade JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.was/Upgrade directory.

Adding the WebSphere Plug-In for Windows

The WebSphere 5.1 plug-in is contained in the SUNWspswas.msi file.

ProcedureTo Add the WebSphere Plug-In for Windows

Steps

  1. Move to the directory containing the sun-spswas-3.0.msi file.

  2. Double-click the sun-spswas-3.0.msi file.

    The Installer GUI start. The JAR file is copies to the C:\Program Files\N1 Service Provisioning System\plugins\com.sun.was directory. The upgrade JAR file is in the C:\Program Files\N1 Service Provisioning System\plugins\com.sun.was/Upgrade directory.

Importing the WebSphere Plug-In to the Sun N1 Service Provisioning System

To make a given plug-in known to the Sun N1 Service Provisioning System, you need to import the plug-in to the Master Server. If you have already imported a previous version of the WebSphere Plug-In you need to upgrade to the new plug-in.

ProcedureHow to Import the WebSphere Plug-In Using the Browser Interface

To import or upgrade a plug-in, follow these steps as explained in detail in Chapter 5, Plug-In Administration, in Sun N1 Service Provisioning System 5.2 System Administration Guide

Steps

  1. In the Administrative section of the browser interface main window, click Plug-ins.

  2. In the Action column of the Plug-ins page, click Import.

  3. Navigate to the location of the JAR file.

    • If you are importing the WebSphere Plug-In for the first time, select the com.sun.was_3.0.jar file.

    • If you have already imported a previous version of the WebSphere Plug-In, select the com.sun.was_2.0_3.0.jar file.

  4. Click the Continue to Import button.

    When the import complete successfully, a plug-in details page appears and shows you the objects that the plug-in provides.

ProcedureHow to Import the WebSphere Plug-In using the CLI

You can also import a plug-in by using the command line.

Step

    To import a plug-in file from the CLI, type:


    % cr_cli -cmd plg.p.add -path plugin-filename -u username -p password

    • If you are importing the WebSphere Plug-In for the first time, plugin-filename is com.sun.was_3.0.jar.

    • If you have already imported the previous version of the WebSphere Plug-In, plugin-filename is com.sun.was_2.0_3.0.jar.

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 .

  2. Set the WebSphere 3.0 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. Install the CLI on the machine running the Master Server.

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

    Note –

    If virtual host cliHost exists and the host type is com.sun.sap#cliHT, do not create another cliHost.

    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.

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

    The pe.nonPlanExecNativeTimeout value is in seconds. Add this line if your site needs to increase the time for execNative timeouts.


    pe.nonPlanExecNativeTimeout=2400

    Add the following lines to the file.


    config.allowSessionIDOnHosts=masterserver
pe.defaultPlanTimeout=6000

    The config.properties file's default location is /opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/server/config.

  8. Restart the Master Server.

Upgrading Considerations

The following information is related to viewing previous versions of components after upgrading.

ProcedureHow to Access Previous Versions of a Component

When you upgrade to a new version of a plug-in, the Common Tasks page for the plug-in is updated to provide links to components that are installed with the new plug-in version. This feature enables you to easily view components that contain the most current features and improvements. Components that rely on old functionality are not linked to from the Common Tasks page.

If you have trouble finding a component that you previously installed, the component was likely created from the previous version of the plug-in.

Follow these steps to view or work with a previous version of the component:

Steps

  1. Click the appropriate component procedure on the Common Tasks page.

    The Component Detail page appears.

  2. On the Component Details page, click Version History.

    A list of components and versions appears.

  3. Click the appropriate link.

    1. To perform a task with a component, click the version number or the details link that applies to the component that you want to use.

    2. To view where a component is installed, click Where Installed.

Patching the WebSphere Plug-In

Check the SunSolve site for available patches for the WebSphere 3.0 plug-in. To apply the patch, follow the instructions in the patch README file.