Sun Java System Access Manager Policy Agent 2.2 Guide for BEA WebLogic Server/Portal 9.2

Previous: Installation Related Information About Agent for BEA WebLogic Server/Portal 9.2
Next: Launching the Installation Program of Agent for BEA WebLogic Server/Portal 9.2

Preparing to Install Agent for BEA WebLogic Server/Portal 9.2

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.

Caution –

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 BEA WebLogic Server/Portal 9.2

SJS_Weblogic_92_agent_2.2_SUNWamwl.tar.gz
SJS_Weblogic_92_agent_2.2.tar.gz
SJS_Weblogic_92_agent_2.2.zip

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 BEA WebLogic Server/Portal 9.2

# gzip -dc SJS_Weblogic_92_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 BEA WebLogic Server/Portal 9.2

# gzip -dc SJS_Weblogic_92_agent_2.2_SUNWamwl.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 BEA WebLogic Server/Portal 9.2

unzip SJS_Weblogic_92_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 BEA WebLogic Server/Portal 9.2

Perform the following pre-installation tasks:

Ensure that the Policy Agent 2.2 for BEA WebLogic Server/Portal 9.2 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for BEA WebLogic Server/Portal 9.2.

Install BEA WebLogic Server/Portal 9.2 if not already installed.

For more information about BEA WebLogic Server/Portal 9.2, see the product documentation available at the following web site: http://www.bea.com/.

Create a server or portal domain

Using the configuration or domain wizard appropriate for your server version and operating system, create a new stand-alone server domain. Typically, the configuration wizard launch script or program is located in the respective directory as follows:

UNIX—based systems (including Linux systems)

DeployContainer-base/weblogic92/common/bin/config.sh

Windows systems

DeployContainer-base\weblogic92\common\bin\config.cmd

where DeployContainer-base represents the directory in which BEA WebLogic Server/Portal 9.2 was installed.

Shut down the BEA WebLogic Server/Portal 9.2 instance that will be protected by the agent.

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.

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 do not need to enter sensitive information in the command line. A valid password file can have only one line that contains the agent profile password.

You must decide what to do with this password file after the installation process is complete. You might choose to remove the file or provide restricted permissions to it. However, certain deployment-related tasks, such as installing multiple instances, require a password file. If you do remove the password file, create a new one if a future situation requires it.

Ensure that the ownership and group settings for the files in the Policy Agent base directory are correct.

Note –
The Policy Agent base directory is explained in more detail in J2EE Agent Directory Structure in Policy Agent 2.2 and Example 3–5. In summary, for this agent, Agent for BEA WebLogic Server/Portal 9.2, the Policy Agent base directory is named am_wl92_agent.

Often, such installations are performed by a user with root permissions. In these cases, the potential problems discussed subsequently in this step would not apply.

Therefore, if necessary, change the ownership of all the files in the Policy Agent base directory to the BEA WebLogic Server/Portal 9.2 installation user and change the group associated with these files to the same group associated with the BEA WebLogic Server/Portal 9.2 installation user.

Caution –
For the agent installation to be successful, the BEA WebLogic Server/Portal 9.2 installation user must have write permissions to the files in the Policy Agent base directory. Furthermore, to help prevent permission problems, the ownership of all the files in the Policy Agent base directory should be changed to the BEA WebLogic Server/Portal 9.2 installation user. Otherwise, permission-related issues might occur, which can be as serious as BEA WebLogic Server/Portal 9.2 not starting.