Preparing to Install Agent for IBM WebSphere Application Server 6.0

Detailed information about unpacking the distribution files for J2EE agents in Policy Agent 2.2 is covered in Chapter 2, Vital Installation Information for a J2EE Agent in Policy Agent 2.2. The best practice is to follow the detailed steps outlined in that chapter before you implement any steps outlined in this chapter.

The following examples provide quick details about the unpacking process. Furthermore, this section provides the opportunity to present again the cautionary note that follows about the GNU_tar program.

For .tar.gz archives, do not use a program other than GNU_tar to untar the contents of the J2EE agent deliverables. Using a different program, such as another tar program, can result in some files not being extracted properly. To learn more about the GNU_tar program, visit the following web site:

http://www.gnu.org/software/tar/tar.html

Example 3–1 Format of the Distribution Files of Agent for IBM WebSphere Application Server 6.0

SJS_WebSphere_60_agent_2.2.tar.gz
SJS_WebSphere_60_agent_2.2.zip
SJS_WebSphere_60_agent_2.2_SUNWamwas.tar.gz

For detailed information on the format of the distribution files, see Format of the Distribution Files for a J2EE Agent Installation in Policy Agent 2.2.

Example 3–2 Unpacking Non-Package Formatted Deliverables of Agent for IBM WebSphere Application Server 6.0

# gzip -dc SJS_WebSphere_60_agent_2.2.tar.gz | tar xvf -

For detailed information about this command, see To Unpack Non-Package Formatted Deliverables of a J2EE Agent in Policy Agent 2.2.

Example 3–3 Unpacking Package Formatted Deliverables of Agent for IBM WebSphere Application Server 6.0

# gzip -dc SJS_WebSphere_60_agent_2.2_SUNWamwas.tar.gz | tar xvf -

For detailed information about this command, see To Unpack Package Formatted Deliverables of a J2EE Agent in Policy Agent 2.2.

Example 3–4 Unpacking a .zip Compressed file of Agent for IBM WebSphere Application Server 6.0

unzip SJS_WebSphere_60_agent_2.2.zip

For detailed information about this command, see To Unpack a .zip Compressed file of a J2EE Agent in Policy Agent 2.2.

Follow the specific steps outlined in the following section before you install the agent to reduce the chance of complications occurring during and after the installation.

To Prepare to Install Agent for IBM WebSphere Application Server 6.0

Perform the following pre-installation tasks:

1. Ensure that the Policy Agent 2.2 for IBM WebSphere Application Server 6.0 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for IBM WebSphere Application Server 6.0.

2. Install IBM WebSphere Application Server 6.0 if not already installed.

   You can visit http://www.ibm.com to download the IBM WebSphere Application Server 6.0 software.

3. Ensure that the IBM WebSphere Application Server 6.0 instance that will be protected by the agent is shut down.

   The following is an example command for shutting down this server:

   DeployContainer-base/WebSphere/Appserver/bin/stopServer.bat instanceName
   

   DeployContainer-base

   represents the directory within which the IBM WebSphere Application Server 6.0 instance was installed.

   instanceName

   represents the IBM WebSphere Application Server 6.0 instance the agent will protect.

4. Create a valid agent profile in Access Manager Console if one has not already been created.

   For information on how to create an agent profile, see Creating a J2EE Agent Profile.

   To avoid a misconfiguration of the agent, ensure that you know the exact ID and password used to create the agent profile. You must enter the agent profile password correctly in the next step and you must enter the agent profile ID correctly when installing the agent.

5. Create a text file and add the agent profile password to that file.

   Ensure that this file is located in a secure directory of your choice. You will refer to this file during the agent installation process.

   With the agent profile password in this file, stored in a secure location, you are not required to enter sensitive information in the console. A valid password file can have only one line that contains the agent profile password.