Perform the Prerequisite Tasks

Configure MBeans on Oracle WebLogic Servers

Follow the instructions in this section if you're setting up the environment to use Oracle Management Cloud with Oracle E-Business Suite Release 12.2.

To collect the JVM performance metrics from platform MBeans, the MBeans must be made accessible through the runtime MBeanServer. Activate MBeans by logging in to your Oracle WebLogic Server and verify the activation by running the WLST script:

Activate MBeans on Oracle WebLogic Servers

Activate MBeans by acessing each Oracle WebLogic Server by logging into it or from the WebLogic console as follows:

Log in to your Oracle WebLogic Server:

Follow the user actions in the WebLogic Scripting Tool session demostration at Activating Platform MBeans on WebLogic Server 9.x to 10.3.2 versions in Enterprise Manager Cloud Control Middleware Management Guide.
Access your WebLogic console:

Navigate to Domain > Configuration > General page > Advanced options. Select the Platform MBean Server Used check box.

If MBeans are not registered after you’ve followed the above steps, then start the Oracle WebLogic Servers with the following system property:

-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder

Verify the Activation of MBeans

To verify if MBeans is successfully activated, run the WLST script that’s available at Using the Platform MBean Server in Fusion Middleware Developing Custom Management Utilities With JMX for Oracle WebLogic Server. The WLST script demonstrates how to use the Platform MXBeans to monitor the resources of a running Oracle WebLogic Server domain.

Ensure that MBeans are registered under java.lang.

Verify Collection of Forms Sessions Data

Verify the collection of forms sessions data to view it later in the Forms System Health Dashboard by performing the following task. This is in addition to the steps performed in the section Configure MBeans on Oracle WebLogic Servers. If this step is not configured, then some of the Forms System metrics will not be collected.

When you log in to Oracle E-Business Suite, the system creates a user session in the database identified by a unique session ID (SID) by using the APPS schema credential. Each database session is associated with an Oracle E-Business Suite application user. This enables linking the database session with the application user for troubleshooting purposes. Using a Forms session, you can determine how the Oracle E-Business Suite user opened a database session.

Log in to your Oracle E-Business Suite.
From the user interface, navigate to System Administrator > Profile > System.
Ensure that the value of Sign-On: Audit Level is set to FORM. Set this at the site level.
Ensure that the value of AuditTrail: Activate is set to YES.

Save the changes.

Set Up DNS in an Oracle E-Business Suite Environment

The Oracle E-Business Suite hosts must be able to detect one another on the network. For example, in the UNIX environment, the DNS servers are configured in the file /etc/resolv.conf on each host.

To verify that the DNS servers are configured correctly, run the command:

nslookup any_publicDomain_hostname

Install a Cloud Agent

You must perform the following tasks to install a cloud agent.

Required Role: To complete these tasks, you must have the Cloud Account Administrator role. If this role isn’t assigned to you or you’re not sure, then ask your system administrator to ensure that the role is assigned to you in Oracle Cloud.

An operating system user who is the owner of the database tier must install the cloud agent, typically, the oracle user.

Task	Description
Task 1: Understand the agent deployment topology.	Review and understand the deployment topology of Oracle Management Cloud agents. See Understand the Architecture of Oracle Management Cloud in Installing and Managing Oracle Management Cloud Agents.
Task 2: Review the prerequisites for deploying Oracle Management Cloud agents.	Review the hardware and software requirements for deploying Oracle Management Cloud agents. See Generic Prerequisites for Deploying Oracle Management Cloud Agents in Installing and Managing Oracle Management Cloud Agents.
Task 3: Download the agent software.	Download the agent software that contains the script required to install the Oracle Management Cloud agents. See Download the Oracle Management Cloud Agent Software in Installing and Managing Oracle Management Cloud Agents.
Task 4: Install the cloud agent on each of the application tier hosts and database hosts.	Install the cloud agent on each host in the Oracle E-Business Suite topology. See Install Cloud Agents in Installing and Managing Oracle Management Cloud Agents.
Task 5: Verify the deployment.	See Verify the Cloud Agent Installation in Installing and Managing Oracle Management Cloud Agents.

Apply Grants to an EBS Database for Monitoring

To monitor the database instance using Oracle Infrastructure Monitoring, create a special database user and provide the requisite privileges to the user. Typically, in the UNIX environment, the database is located at <EBS_home>/VISION/11.2.0 in the Oracle E-Business Suite directory structure for release 12.2. You can log in to the database instance as any user or with any SYSDBA role.

For steps to apply grants for monitoring CDB or PDB, see Monitor CDB and PDB.

The example code below uses the schema name APPS. If the schema name is different in your setup, then replace APPS with it accordingly in the following code.

Run the SQL script grantPrivileges.sql to automatically perform the following tasks that are required for monitoring the database instance. See Oracle Database in Using Oracle Infrastructure Monitoring.
- Create a monitoring role.
- Create a special database user and provide the requisite privileges to the user.
- Grant the monitoring role to the user.
- To the monitoring user, grant access to the database.
- Allow the monitoring user to create sessions.
- To use the Oracle Infrastructure Monitoring, provide generic grants to the monitoring user.

Provide the Oracle E-Business Suite specific grants to the user:

GRANT SELECT ON APPS.FND_OAM_CONTEXT_FILES TO MONCS;
GRANT SELECT ON APPS.FND_PRODUCT_GROUPS TO MONCS;
GRANT SELECT ON APPS.FND_CONC_PROG_ONSITE_INFO TO MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_PROGRAMS_VL TO MONCS;
GRANT EXECUTE ON APPS.FND_OAM_EM TO MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_REQUESTS TO MONCS;
GRANT SELECT ON APPS.FND_APPLICATION_VL TO MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_QUEUES TO MONCS;
GRANT SELECT ON APPS.FND_LOOKUPS TO MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_WORKER_REQUESTS TO MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_QUEUES_VL TO MONCS;
GRANT SELECT ON APPS.FND_OAM_FNDUSER_VL TO MONCS;
GRANT SELECT ON APPS.FND_FORM_SESSIONS_V TO MONCS;
GRANT SELECT ON APPS.FND_CP_SERVICES TO MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_PROCESSES TO MONCS;
GRANT SELECT ON APPS.FND_SVC_COMPONENTS TO MONCS;
GRANT SELECT ON APPS.FND_LOG_MESSAGES TO MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_PROGRAMS TO MONCS; 
GRANT SELECT ON APPS.FND_CONFLICTS_DOMAIN TO MONCS; 
GRANT SELECT ON APPS.FND_ORACLE_USERID TO MONCS; 
GRANT SELECT ON APPS.FND_APP_SERVERS TO MONCS; 
GRANT SELECT ON APPS.FND_NODES TO MONCS;
GRANT SELECT ON APPS.ICX_SESSIONS TO MONCS;
GRANT SELECT ON APPS.FND_USER TO MONCS;
GRANT SELECT ON APPS.FND_RESPONSIBILITY TO MONCS;
GRANT EXECUTE ON APPS.FND_PROFILE TO MONCS;
GRANT SELECT ON APPS.WF_DEFERRED TO MONCS;
GRANT SELECT ON APPS.WF_NOTIFICATION_IN TO MONCS;
GRANT SELECT ON APPS.WF_NOTIFICATION_OUT TO MONCS;

Monitor CDB and PDB

If you're deploying the Oracle E-Business Suite application to monitor the pluggable database (PDB) or multitenant container database (CDB), then follow these steps for providing grants to the monitoring user:

Verify that the database is CDB or PDB:
```
select cdb,name from v$database;
```
Check the value of the CDB parameter _common_user_prefix. C## is the default value in the CDB root. Use it as the prefix for the MONCS user. So the resultant user is C##MONCS.
Log in to the database node and create OMC monitoring user and grant the privileges:
```
sqlplus / as sysdba
show con_name
@grantPrivileges.sql C##MONCS <password> Y
```
Note:

The script is found under <Agent_Home>/plugins/oracle.em.sgfm.zip/<agent_version>/ scripts/ directory.

This will create C##MONCS database user in the CDB with privileges which can used as a credential when discovering Oracle Management Cloud database entity.

Log in to the database node and obtain the PDB name of the Oracle E-Business Suite instance:

sqlplus / as sysdba
SELECT PDB_ID, PDB_NAME, STATUS FROM DBA_PDBS ORDER BY PDB_ID;
alter session set container=<EBSPDB>;
grant connect to C##MONCS;

Provide the Oracle E-Business Suite specific grants to the C##MONCS user:

GRANT SELECT ON APPS.FND_OAM_CONTEXT_FILES TO C##MONCS;
GRANT SELECT ON APPS.FND_PRODUCT_GROUPS TO C##MONCS;
GRANT SELECT ON APPS.FND_CONC_PROG_ONSITE_INFO TO C##MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_PROGRAMS_VL TO C##MONCS;
GRANT EXECUTE ON APPS.FND_OAM_EM TO C##MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_REQUESTS TO C##MONCS;
GRANT SELECT ON APPS.FND_APPLICATION_VL TO C##MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_QUEUES TO C##MONCS;
GRANT SELECT ON APPS.FND_LOOKUPS TO C##MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_WORKER_REQUESTS TO C##MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_QUEUES_VL TO C##MONCS;
GRANT SELECT ON APPS.FND_OAM_FNDUSER_VL TO C##MONCS;
GRANT SELECT ON APPS.FND_FORM_SESSIONS_V TO C##MONCS;
GRANT SELECT ON APPS.FND_CP_SERVICES TO C##MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_PROCESSES TO C##MONCS;
GRANT SELECT ON APPS.FND_SVC_COMPONENTS TO C##MONCS;
GRANT SELECT ON APPS.FND_LOG_MESSAGES TO C##MONCS;
GRANT SELECT ON APPS.FND_CONCURRENT_PROGRAMS TO C##MONCS;
GRANT SELECT ON APPS.FND_CONFLICTS_DOMAIN TO C##MONCS;
GRANT SELECT ON APPS.FND_ORACLE_USERID TO C##MONCS;
GRANT SELECT ON APPS.FND_APP_SERVERS TO C##MONCS;
GRANT SELECT ON APPS.FND_NODES TO C##MONCS;
GRANT SELECT ON APPS.ICX_SESSIONS TO C##MONCS;
GRANT SELECT ON APPS.FND_USER TO C##MONCS;
GRANT SELECT ON APPS.FND_RESPONSIBILITY TO C##MONCS;
GRANT EXECUTE ON APPS.FND_PROFILE TO C##MONCS;
GRANT SELECT ON APPS.WF_DEFERRED TO C##MONCS;
GRANT SELECT ON APPS.WF_NOTIFICATION_IN TO C##MONCS;
GRANT SELECT ON APPS.WF_NOTIFICATION_OUT TO C##MONCS;

Grant additional privilege to the C##MONCS user:

GRANT INHERIT PRIVILEGES ON USER C##MONCS TO APPS;

Verify the grants for C##MONCS user.

Log in to the database node and run the below SELECT statements to verify the grants:

sqlplus / as sysdba
alter session set container=<EBSPDB>;
SELECT GRANTEE, TABLE_NAME, PRIVILEGE FROM DBA_TAB_PRIVS WHERE GRANTEE='C##MONCS';

Add EBS Database

Discover the Oracle E-Business Suite database entity before you discover the Oracle E-Business Suite composite entity.

To complete this task:

Set up monitoring credentials for database system discovery
Add a database system using Oracle Management Cloud Console or Command Line Interface (OMCLI) via JSON files

After the database entity is discovered, it is automatically reconciled with Oracle E-Business Suite application during the discovery of the Oracle E-Business Suite composite.

For the steps and detailed instructions, see Discover Oracle Database Systems in Using Oracle Infrastructure Monitoring.

Configure Oracle Application Performance Monitoring for EBS

Follow the instructions in this section if you're setting up the environment to use Oracle Management Cloud with Oracle E-Business Suite Release 12.2.

If you also want to monitor the performance of Oracle E-Business Suite applications using Oracle Application Performance Monitoring, then perform the following tasks:

Install the APM agent on the managed servers oacore, oafm, and forms clusters. A user who is the owner of the application tier must install the APM agent, typically, the ApplMgr user.

After you install the agent, you get an output that instructs you to execute more steps. Ignore the instructions in the output, and proceed to the step below. For details about the installation, see Install and Configure APM Java Agent on Oracle E-Business Suite in Installing and Configuring Oracle Application Performance Monitoring.
Enable the APM Java Agent in the WebLogic Managed Servers: To enable the access to Oracle E-Business Suite from Oracle Application Performance Monitoring, JVM configuration changes must be made to the WebLogic Managed Servers. Perform the required steps on each of the managed servers of the oacore, oafm, and forms clusters services. See Install and Configure APM Java Agent on Oracle E-Business Suite in Installing and Configuring Oracle Application Performance Monitoring.
Deploy the APM Java Agent with Oracle Forms monitoring: Ensure that Oracle Forms server is configured in servlet mode. For the steps to verify that Oracle Forms server is running in servlet mode and the APM agent is deployed with Oracle Forms monitoring, see Install and Configure APM Java Agent on Oracle E-Business Suite in Installing and Configuring Oracle Application Performance Monitoring.

If Oracle Forms monitoring is not working after deploying APM Java Agent, then troubleshoot the errors by using the tips at Troubleshoot APM Java Agent Deployment in Installing and Configuring Oracle Application Performance Monitoring.
Configure the browser agent on oacore managed servers. See Enable and Configure End User Monitoring in Installing and Configuring Oracle Application Performance Monitoring.

When you enable End User Monitoring, you may also want to configure User Name Reporting for Oracle E-Business Suite.

Insert JavaScript code in the Oracle E-Business Suite environment to all the used home pages for extracting the user name:
1. Log into Oracle E-Business Suite as the SYSADMIN user > In the left navigation pane, expand Functional Administrator option > Click Home.
2. Navigate to Personalization tab > Enter the path /oracle/apps/fnd/framework/navigate/webui/ in the Document Path field > Click Go to retrieve the document.
3. Click the Personalize Page icon for the home page document, for example, NewHomePG.
  
  The default home page for Oracle E-Business Suite version 12.2.10 is /oracle/apps/fnd/framework/navigate/webui/NewHomePG. It is possible that one or more other home pages are configured. You can identify the home page name from the URL when logging in to Oracle E-Business Suite using the OAFunc parameter. For example, in the log in URL http://ebs12210.example.com:8000/OA_HTML/OA.jsp?OAFunc=OANEWHOMEPAGE, the home page is OANEWHOMEPAGE.
4. Accept the defaults on the Choose Personalization Context screen and click Apply.
5. Select the Complete View option > Click on the Create Item icon for the Page Layout row.
6. In the Create Item page:
  
  Description of the illustration ebs_javascript.png
  - From the Item Style menu, select Raw text.
  - Enter a name for the ID.
  - In the Text field, enter the following script:
```
<script type='text/javascript' charset='UTF-8'>
 var spanList2 = document.getElementsByClassName("x2u");
 apmeum.username = spanList2[0].innerHTML;
</script>
```
    Note: You may need to adjust the above script for it to work with the specific page that you are using.
    
    To verify that the script works as expected, you can optionally add console.log('user name is:' + spanList2[0].innerHTML); to the script.
    
    For example patterns to identify the user name, see step 4 > a, step 4 > b, and step 4 > c in Configure User Name Reporting in Installing and Configuring Oracle Application Performance Monitoring.
  - Click Apply to save the changes.