Oracle Application Management Pack for Oracle E-Business Suite Installation Guide

Installation in a Shared Agent Environment

Note: Shared Agent configurations are currently not supported with the Application Management Pack on Windows platforms.

Read the official documentation to become familiar with this process.

Read "Installing Oracle Management Agent Using Shared Oracle Home Using nfsagentinstall Script," Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide.

What follows in this guide is an expansion and clarification of the documentation listed above. There are a few points in the above document that warrant special attention.
Perform the installation.

Install a Release 11.1.0.1 agent to the master system. This installation is very straightforward, but please be mindful of the following: The ORACLE_HOME must be mounted on the shared hosts on the exact same path. Example: Agent ORACLE_HOME is /u01/oracle/agent11g on the master, therefore it must also be mounted as /u01/oracle/agent11g on the slaves. Secondly, make sure that your users and groups are consistent between master and slaves; and that ultimately, the agent belongs in the same group as the Oracle E-Business Suite instances to be monitored. As an example, the target Oracle E-Business Suite instances run under a user called “applrt” with a group of “g680” the uid was 20001 and the gid 680. Therefore, on the master agent system, there should be a user called “applrt” with a group of “g680” and uid/gid of 20001/680. This replication of UNIX username and group associations isn't strictly necessary as long as, ultimately, the agent on the slaves runs under the same group and has appropriate permissions to read, write, and execute files under the Oracle E-Business Suite.
Apply the Oracle Application Management Pack patch (patch 8333939) to the master.
Apply the latest Oracle Application Management Pack patchset to the master.

See Chapter 1, "Installing Oracle Application Management Pack for Oracle E-Business Suite" for details on the latest patchset available on My Oracle Support.
Share out the Agent $ORACLE_HOME as read-only.

This assumes that your Master agent server already has the NFS server installed and running.

In /etc/exportfs on the Master agent server, add a line similar to the following:
```
/u01/oracle/agent11g   *(ro)
```
This is only an example. In fact, this configuration is not very secure, despite setting the read-only ("ro") flag. Please set your export options as appropriate for your security requirements.

You should now re-export your shares:
```
/usr/sbin/exportfs -r
```
Mount the Agent $ORACLE_HOME on each slave.
On the master AND slaves, create the EM states directory.

The states directory is the local directory to which configuration files and logs are written. For example, if your remote agent home is mounted as /u01/oracle/agent11g, you could create a directory /u01/oracle/emstate on the slave.
```
mkdir /u01/oracle/emstate
```
On the Master, run the $ORACLE_HOME/sysman/install/nfsagentinstall script IN the states directory:
```
cd /u01/oracle/emstate
$ORACLE_HOME/sysman/install/nfsagentinstall -s /u01/oracle/emstate
```
Important: It is absolutely critical that the nfsagentinstall script is NOT executed from the remote home (in our example, /u01/oracle/agent11g). This will cause the script to fail because it cannot write out its log, which is always written to the current working directory.
Repeat Step 8 for each slave.