1.5 Upgrading the J2EE Agents

This section describes how to upgrade the following agents on Linux and Windows:

1.5.1 Upgrading the WebSphere or JBoss Agent on Linux

  1. (JBoss only) Stop the JBoss server.

  2. Download the Access Manager Agent file for Linux from Novell and extract the file.

  3. After downloading the file, unpack the tar.gz file by using the following command:

    tar -xzvf [filename]

  4. Change to the Access Manager Agent directory.

  5. At the command prompt of the Access Manager Agent directory, enter the following:

    ./install.sh

  6. When prompted, enter Y to perform an upgrade.

  7. Review and accept the License Agreement.

  8. At the prompt to enter the Administration Server IP address, enter the IP address of the Administration Console machine.

  9. Enter the name of the administrator for the Administration Console.

  10. Enter and confirm the password for this administrator.

    This starts the installation of some components.

  11. Enter the base directory for the J2EE server.

  12. (WebSphere only) Make sure that the server is running, then confirm that it is.

  13. (WebSphere only) Enter the information required for modifying the WebSphere server:

    WebSphere administrator username: Specify the name of the WebSphere administrator.

    WebSphere administrator password: Specify the password of the WebSphere administrator. Confirm the password by re-entering it.

    A few more modules are installed and then configured.

  14. (JBoss only) Enter the JBoss server configuration set. Standard values are default, all, or minimal. If you have created a custom configuration, enter its name.

    Verify that the JBoss server is stopped, then press Enter.

    A few more modules are installed and then configured.

  15. Restart the J2EE server.

  16. (Optional) Verify the upgrade:

    1. Log in to the Administration Console.

    2. Click Access Manager > J2EE Agents > [Name of Agent].

    3. Verify that the Server Version field contains the correct information.

1.5.2 Upgrading the WebSphere or JBoss Agent on Windows

  1. Download the Access Manager Agent file for Windows from Novell.

  2. Execute the file.

  3. Select to upgrade the agent.

  4. Read the welcome information, then click Next.

  5. Note where additional information can be found, then click Next.

  6. Review the License Agreement, accept it, then click Next.

  7. Select the current communication server directory where the device manager directory is located, then click Next.

  8. Select the type of agent you are upgrading, then click Next.

  9. (WebSphere only) Confirm that the WebSphere server is running, then enter the information required for modifying the WebSphere server:

    WAS Administrator ID: Specify the name of the WebSphere administrator.

    WAS Administrator Password: Specify the password of the WebSphere administrator. Confirm the password by re-entering it.

  10. (JBoss only) Complete the following steps:

    1. Stop the JBoss server.

    2. Select the directory where you have installed the J2EE server, then click Next.

    3. Select the server configuration folder, then click Next.

  11. (WebLogic only) Confirm that you understand that the WebLogic configuration is manual.

  12. Click Next, then review the installation summary.

  13. To upgrade the agent, click Install.

  14. If you are prompted to overwrite existing file, select to overwrite all files.

  15. (WebSphere only) Select to restart the server, then click Next.

  16. Review the log information, then click Next.

  17. To exit the installer, click Done.

  18. (JBoss only) When the installation finishes, restart the J2EE server.

  19. (Optional) Verify the upgrade:

    1. Log in to the Administration Console.

    2. Click Access Manager > J2EE Agents > [Name of Agent].

    3. Verify that the Server Version field contains the correct information.

1.5.3 Upgrading the WebLogic Agent

Because the install and configuration of the J2EE Agent for WebLogic is manual, the upgrade process is also manual. To upgrade the WebLogic Agent, you need to stop the embedded service provider of the agent and stop the WebLogic server. Select a time when users do not need access to the WebLogic applications.

  1. Undeploy the embedded service provider:

    1. In the WebLogic Administration console, click Deployments in the Domain Structure list.

    2. Click Lock and Edit.

    3. Select the name of the embedded service provider application.

      The default name is AccessManagerEmbeddedServiceProvider. If you deployed it manually, the name is nesp.

    4. Click Stop, then select Force Stop Now.

    5. To stop the deployment, click Yes.

    6. Select the name of the embedded service provider application, click Delete, then confirm the action.

    7. Click Activate Changes.

  2. Stop the WebLogic server.

  3. Delete the nesp directory.

    On Linux, the directory is WL_DOMAIN/nesp.

    On Windows, the directory is c:\Novell\nesp.ear.

  4. Run the standard agent upgrade program for your platform.

  5. Copy the NidsWebLogicAgentMbeans.jar file from AGENT_HOME/lib to WL_HOME/server/lib/mbeantypes, replacing the existing file.

  6. Start the WebLogic server.

  7. Execute the WebLogic scripting tool with the parameters required to run the weblogic_nesp_deploy.jy script. This script needs the following parameters:

    • The location of the script

    • The name of the WebLogic admin user

    • The admin’s password

    • The server name

    • The local host with port (usually localhost:7001)

    • The path to the nesp.ear file

    Linux Example: /root/bea/weblogic92/common/bin/wlst.sh /opt/novell/nids_agents/bin/weblogic_nesp_deploy.jy username password AdminServer localhost:7001 /root/bea/weblogic92/nesp/nesp.ear

    Windows Example: C:\bea\weblogic92\common\bin\wlst.cmd C:\Novell\bin\weblogic_nesp_deploy.jy username password AdminServer localhost:7001 C:\Novell\nesp.ear

  8. (Optional) Verify the upgrade:

    1. Log in to the Administration Console.

    2. Click Access Manager > J2EE Agents > [Name of Agent].

    3. Verify that the Server Version field contains the correct information.