Sun Java System Access Manager Policy Agent 2.2 Guide for Oracle Application Server 10g

Previous: Installation Related Information About Agent for Oracle Application Server 10g
Next: Launching the Installation Program of Agent for Oracle Application Server 10g

Preparing to Install Agent for Oracle Application Server 10g

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 Oracle Application Server 10g

SJS_Oracle_1012_agent_2.2.tar.gz
SJS_Oracle_1012_agent_2.2.zip
SJS_Oracle_1012_agent_2.2_SUNWamoc4j.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 Oracle Application Server 10g

# gzip -dc SJS_Oracle_1012_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 Oracle Application Server 10g

# gzip -dc SJS_Oracle_1012_agent_2.2_SUNWamoc4j.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 Oracle Application Server 10g

unzip SJS_Oracle_1012_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 Oracle Application Server 10g

Perform the following pre-installation tasks:

Ensure that Policy Agent 2.2 for Oracle Application Server 10g is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for Oracle Application Server 10g.

(CONDITIONAL) Install the Oracle Application Server 10g instance, if not already installed.

Visit the following link to learn more about installing Oracle Application Server 10g: http://www.oracle.com/technology/software/products/ias/index.html. Refer to the appropriate documentation as necessary. If you install the Oracle Application Server 10g instance at this time, ensure that you use the fully qualified host name as described in the following step.

Ensure that the Oracle Application Server 10g instance is installed with the fully qualified host name.

The Oracle Application Server 10g instance gets installed with the fully qualified host name when the installation program is started with the following command-line parameter:
```
./runInstaller OUI_HOSTNAME=fully-qualified-host-name
```
Caution –
If a fully qualified host name was not provided during installation, the front-end Apache web server will be configured with the wrong host name in the httpd.conf file. This file contains the variable ServerName. For this file is to be configured correctly, the value associated with the variable ServerName must be a fully qualified host name. If a fully qualified host name is not used, a problem can arise where the agent issues an unlimited self-direct.

Perform steps such as the following substeps to ensure that the Oracle Application Server 10g instance is configured with a fully qualified host name.
1. Using the text editor of your choice, access the following file:
```
DeployContainer-base/Apache/Apache/conf/httpd.conf
```
  where DeployContainer-base represents the directory within which the Oracle Application Server 10g instance was installed.
2. (CONDITIONAL) If the value for ServerName is not the fully qualified host name, change the value to the fully qualified host name.

Ensure that the Oracle Application Server 10g instance is shut down.

Since the J2EE agent installer changes some of the configuration files in the Oracle Application Server 10g instance, the server should not be running during the agent installation process.

The following substeps, which include the issuance of two commands, serve as an example of how to shut down an Oracle Application Server 10g instance, where DeployContainer-base represents the directory within which the Oracle Application Server 10g instance was installed.
1. Change directories to the following:
```
DeployContainer-base/opmn/bin
```
2. Issue the following command:
```
./opmnctl stopall
```
3. Change directories to the following:
```
DeployContainer-base/bin
```
4. Issue the following command:
```
./emctl stop em
```

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 console. A valid password file can have only one line that contains the agent profile password.

Ensure that the ownership and group settings for the files in the am_oracle_1012_agent directory are correct.

Therefore, if necessary, change the ownership of all the files in the am_oracle_1012_agent directory to the Oracle Application Server 10g installation user and change the group associated with these files to the same group associated with the Oracle Application Server 10g installation user.

The following is the full path to the am_oracle_1012_agent directory:
Agent-HomeDirectory/j2ee_agents/am_oracle_1012_agent
where Agent-HomeDirectory is the directory you choose in which to unpack the J2EE agent binaries. For more information about J2EE agent directory structure, including Agent-HomeDirectory, see J2EE Agent Directory Structure in Policy Agent 2.2.

The following list provides default values for the Oracle Application Server 10g installation user.

Default Oracle Application Server 10g installation user:

oracle

Default group of the Oracle Application Server 10g installation user:

oinstall

Caution –
For the agent installation to be successful, the Oracle Application Server 10g installation user must have ownership of the files in the am_oracle_1012_agent directory and this same user must issue the agent installation command, as described subsequently. Otherwise, the installation can appear successful, but when end users access a protected resource, the browser might issue the following error: NoClassDefFoundError.

This step is necessary since you cannot install this agent as user root. As indicated, instead, install this agent as the Oracle Application Server 10g installation user.