D Setting up a Connection to the Enterprise Manager Repository

This appendix describes how you can set up a connection to the Oracle Enterprise Manager Repository. This is necessary when you want KPIs defined for the applications, suites, and services that comprise your business applications to be reported as events in Incident Manager. The use of Incident Manager is described in Oracle Enterprise Manager Cloud Control Administrator's Guide. The use of the business application facility is described in Oracle Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management.

D.1 Introduction

Oracle Enterprise Manager supports the monitoring of business applications. These represent logical services or applications, and unify the dedicated performance monitoring, diagnostics, and reporting capabilities available through RUEI with that available through Oracle Enterprise Manager. The alerts generated by KPIs defined for the applications, suites, and services that comprise your business applications are reported as events in Incident Manager.

The required procedure consists of two parts: establishing a connection to the Oracle Enterprise Manager repository, and setting up the authentication to this repository. These are described in the following sections.

D.2 Setting up the Connection Data

Two files, sqlnet.ora and tnsnames.ora, require to be set up in the RUEI data directory (RUEI_DATA) on the Reporter system. Do the following:

Ensure that the sqlnet.ora file contains the following:

NAMES.DIRECTORY_PATH = (TNSNAMES)
SQLNET.WALLET_OVERRIDE = TRUE
WALLET_LOCATION = (SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=RUEI_DATA)))
DIAG_SIGHANDLER_ENABLED = FALSE

where RUEI_DATA specifies the RUEI data files directory (see Table 2-2).

Edit the tnsnames.ora files on the Reporter and Processing Engine systems. You should add the following:
```
RUEI_DB_TNSNAME_EM =(DESCRIPTION=
  (ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=EM_database_server) 
     (PORT=1521)))
  (CONNECT_DATA=(SERVICE_NAME=RUEI_DB_INST_EM)))
```
where:
- EM_database_server specifies the network address (host name or IP address) of the Enterprise Manager database server.
- RUEI_DB_TNSNAME_EM specifies the Enterprise Manager database connect string. For more information, see Section 2.4.1, "The RUEI Configuration File".
- RUEI_DB_INST_EM specifies the Enterprise Manager database instance name.
Ensure that the HOST setting specifies the Enterprise Manager database. If you use a host name, ensure that it is also specified in the /etc/hosts setup. However, you can also specify an IP address.

D.3 Setting up the Oracle Wallet

The Reporter system requires non-interactive access to the Enterprise Manager database. In order to achieve this, the Oracle autologin wallet is used to store passwords securely. A wallet should already exist to connect to the Reporter database. Do the following:

Use the following command to add the new credentials to the existing wallet files ewallet.p12 and cwallet.sso files:
```
mkstore -wrl RUEI_DATA -createCredential RUEI_DB_TNSNAME_EM RUEI_DB_USER_EM
```
where:
- RUEI_DB_TNSNAME_EM specifies the Enterprise Manager database connect string.
- RUEI_DB_USER_EM specifies the user of the Enterprise Manager database.
Note that you are prompted for the wallet password and the database password for RUEI_DB_USER_EM.
Use the following command to change the permissions of the cwallet.sso wallet file:
```
chmod 640 cwallet.sso
```
Ensure that the permissions for these files are set correctly. Both files should have the ownership of RUEI_USER and RUEI_GROUP. The ewallet.p12 file only needs to be readable by the RUEI_USER, but both files need to be readable by RUEI_GROUP.
If the database connection has been set up correctly, it should now be possible to access the Enterprise Manager database without being prompted for the password. Issue the following command as the RUEI_USER on the Reporter system:
```
sqlplus /@RUEI_DB_TNSNAME_EM
```