Configuring an Oracle Application server

The discovery of an Oracle Application server uses JAR files that are included with the Oracle Application server. These JAR files are not included in the TADDM server installation.

There is a property in the $COLLATION_HOME/etc/ file for pointing to an existing installation of the Oracle Application server. The following text is in the $COLLATION_HOME/etc/ file:
# Location of the root directory for Oracle Application Server on 
the Tivoli Application Dependency Discovery Manager 
# 1. An example is /home/oracle/product/10.1.3/OracleAS_1 
# 2. A relative directory is relative to com.collation.home  
# 3. This directory (and its subdirectories) must be accessible 
     for the user under which the server runs, usually the collation user.
# 4. Ignore if you do not intend to discover an Oracle Application server. 
To point to an existing installation of the Oracle Application server, edit the following line in the $COLLATION_HOME /etc/ file:
In an Oracle Application server installation, the directories that contain the required JAR files are owned by the oracle user with permissions: rwx------. This means no user other than from the owner (usually, an Oracle application) can access these directories. If the TADDM server is run using the oracle user, these directories are accessible. However, if this is not the case, you must change the directory permissions of the following directories to 711 so that all users can access the them:
  • OracleAppServerHome
  • OracleAppServerHome/j2ee
  • OracleAppServerHome/j2ee/home
  • OracleAppServerHome/opmn
  • OracleAppServerHome/opmn/lib, where an example of OracleAppServerHome is /home/oracle/product/10.1.3/OracleAS_1
For discovery of an Oracle Application server, the com.collation.platform.os.ignoreLoopbackProcesses property in the $COLLATION_HOME/etc/ file must be set to true:

To configure the access list, complete the following steps:

  1. From the Discovery Management Console, create a discovery scope set that contains your Oracle Application server, or use an existing scope that contains your Oracle Application Server.
  2. To create an access list, click the Access List icon.
  3. In the Access List window, click Add.
  4. In the Component Type field of the Access Details window, click Application Servers.
  5. In the Vendor field, click Oracle Application Server.
  6. Type the credentials for the Oracle Application server.