Perform Oracle E-Business Suite Specific Tasks

Configure MBeans on Oracle WebLogic Servers

To collect the JVM performance metrics from platform MBeans, you must make the MBeans accessible using the runtime MBeanServer.

Activate MBeans by acessing each Oracle WebLogic Server in your Oracle E-Business Suite setup by logging into it or from the WebLogic console as follows:

Log in to your Oracle WebLogic Server.
Access your WebLogic console.
Navigate to Domain > Configuration > General page > Advanced options. Select the Platform MBean Server Used check box.

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.

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

nslookup any_publicDomain_hostname

Apply Grants to Databases for Monitoring

To monitor the database instance on Oracle E-Business Suite, 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 directory structure for release 12.2. You can log in to the database instance as APPS user or with any SYSDBA role.

Create a database user, MONCS, and grant the required rights to the created user. A script, grantPrivilegesMonSvc.sh, is available that automates the creation of the monitoring database user and grants the requisite monitoring privileges.
1. Download and save the grantPrivilegesMonSvc.sh script on the same host where the database is located.
  This script needs to be run locally from the host where the database is located.
  
  When the script is run, it prompts you for the following:
  - ORACLE_HOME [ Oracle database home ] .
  - SID [ Oracle database SID ].
  - SYSDBA USER [ Any database user with SYSDBA privileges to connect to the database.].
  - SYSDBA PASSWORD.
  - Monitoring USER; enter MONCS.
    
    If the monitoring user already exists, the user creation step is skipped and the existing user is granted privileges. If the monitoring user does not exist, the user is created and then granted privileges.
  - Monitoring USER PASSWORD.

Provide the Oracle E-Business Suite specific grants to the MONCS user.

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.

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_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 additional privileges required for Oracle IT Analytics data collection.
1. Run <AGENT_HOME>/plugins/oracle.em.sgfm.zip/<AGENT_VERSION>/scripts/grantPrivilegesITA.sh
  This script needs to be run locally from the machine where the database is located. When you run this script, it prompts you for the following:
  - ORACLE_HOME [ Oracle database home ] .
  - SID [ Oracle database SID ].
  - SYSDBA USER [ Any database user with SYSDBA privileges to connect to the database.].
  - SYSDBA PASSWORD.
  - Monitoring USER; enter MONCS.
  - Monitoring USER PASSWORD.
  - Output File Name [Complete path of the text file]
The grantPrivilegesITA.sh script grants the permissions needed for both monitoring and data collections. If the role exists (created by the monitoring script), the script appends the permissions needed for Oracle IT Analytics data collection to the same role.
Grant additional privileges from the command line if necessary. For example:
```
GRANT SELECT ON APPS.ICX_SESSIONS to moncsrole;
```

Configure Oracle Application Performance Monitoring for Oracle E-Business Suite

To monitor the performance of Oracle E-Business Suite applications using Oracle Application Performance Monitoring, you need to perform a set of tasks.

Install the Oracle Application Performance Monitoring agent on the oacore managed server:
1. Log into the Oracle Management Cloud console as an Oracle Management Cloud Administrator.
  If the Management Cloud navigation pane isn’t displayed, then click the OMC Navigation icon on the top-left corner.
2. From the Oracle Management Cloud console navigation pane, click Administration and then click Agents.
3. Click the menu on the right and select Download Agents.
4. Click Agent Type and then select APM Agent.
5. Download the APM Java Agent zip file on your Linux host and extract it in an empty directory. (For example: /stage/apm_staging).
6. Make the installation script an executable using chmod:
```
chmod +x ProvisionAPMJavaAsAgent.sh
```
7. Run ProvisionApmJavaAsAgent with the following parameters:
```
$ ./ProvisionApmJavaAsAgent.sh -d <PATH_TO_FMW_HOME>/user_projects/domains/<EBS_DOMAIN> -no-wallet
```
  - -d is the absolute path of the home directory of the WebLogic Server domain. The APM Java Agent will be installed under this directory.
  - -no-wallet means that you will not use Oracle Wallet for this installation.
  Note that this setup does not use a proxy or a gateway.
8. Locate the registration key that you created when you installed the cloud agents. Copy and paste the registration key value on the command line when prompted.
9. Press y to confirm and install the agent.
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 step 2 below.
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 following steps on the oacore managed servers:
1. Log in to the WebLogic Server Administration Console as a user with admin security role. By default, it’s the user weblogic.
2. Click Servers. The WebLogic Administration Server and Managed Servers summary page is displayed.
3. Click the managed server oacore.
  A page containing various tabs for the settings of the managed server appears.
4. Click Server Start.
5. In the Change Center, click Lock and Edit. Update the Arguments field with the parameters required for Oracle Application Performance Monitoring. Ensure that the existing arguments are not altered.
6. Click Save.
7. In the Change Center, click Activate Changes to activate the changes.
8. Restart the managed servers using the script available at $ADMIN_SCRIPTS_HOME in the Oracle E-Business Suite environment for stopping and starting the managed servers.
Configure the browser agent on oacore managed servers and enable end user monitoring.
1. On the Oracle Management Cloud console, click the Global Navigation Menu on the top-left corner and navigate to APM, select APM Admin, and select Browser Agent.
2. In the Configure End User Monitoring Injection Type Property section, select the application server to modify, and click the Edit icon in the Injection Type column, and select the required injection type.

Discover Oracle E-Business Suite Entities

To monitor the different entities in Oracle E-Business Suite, you must add them using the Add Entities page in Oracle Management Cloud.

Note:

After you install a cloud agent, agent configuration information must first be collected before you can add it. Wait for five minutes after a cloud agent installation before trying to add it.

To complete these tasks, you must have the Oracle Management Cloud Administrator role.

Log into the Oracle Management Cloud console as an Oracle Management Cloud Administrator.
If the Management Cloud navigation pane isn’t displayed, then click the OMC Navigation icon on the top-left corner.
From the Oracle Management Cloud main menu, click Administration, Discover, and then Add Entity. The Add Entity page is displayed.
In the Entity Type list, select EBS.
Enter the Entity Name.
From the Database Host Name list, select the host name of the database that contains the Oracle E-Business Suite schema. Enter the Database Service Name. The default database port is automatically available in the Database Port field. You can change it, if required.
In the Cloud Agent list, select the cloud agent from which the discovery must be run. It is recommended to run the discovery from the cloud agent that’s installed on the WebLogic Administration Server host.
Under Monitoring Credentials section, select EBS 12.2, enter the Database Credentials, and enter the WebLogic Server Credentials.
Under Entity Attributes, select Enterprise from the License Edition list.
To automatically associate Oracle E-Business Suite logs during log collection, enable Associate Logs.
Click Add Entity. You are returned to the Entity Addition Job Status page. The entity addition job name appears in the table of entities on the page.
Return to the Oracle Management Cloud console. Click Administration, Entity Configuration, and then click Licensing. Make sure that Log Collection toggle is ENABLED for EBS.

Verify the Oracle E-Business Suite Setup

After you’ve set up the environment for using Oracle Management Cloud with Oracle E-Business Suite, verify the setup with a few tests.

You can validate your environment with the following checks to start using it:

Topology viewer renders Oracle E-Business Suite hierarchy correctly.
All the metrics are collected without delay. Metric tables and charts are correlated and the data is accurate.
Dashboards reflect the right Oracle E-Business Suite hosts, entities, host metrics, Oracle WebLogic Server metrics, and log widgets.
In the Log Explorer, when the EBS composite is selected, the logs pertaining to Oracle WebLogic Server, database instance, and Oracle E-Business Suite application hosts are included.