Monitoring Oracle E-Business Suite

This chapter covers the following topics:

Navigation and Overview

Once discovered, an Oracle E-Business Suite instance will appear in the Oracle E-Business Suite Instances section in the Oracle E-Business Suite Management page. You can click on the name of the instance to go to the home page of that instance.

Oracle E-Business Suite System

Oracle E-Business Suite is discovered as a system. The members of the system include all the nodes and the targets that run on each node. To see the members select Members/Show All from the target menu.

the picture is described in the document text

Topology of the Oracle E-Business Suite

The Configuration Topology Viewer provides a visual layout of Oracle E-Business Suite with its child targets. To access the Configuration Topology Viewer, select Members/Topology from the target menu.

the picture is described in the document text

Upon service failure, the potential causes of failure, as identified by root cause analysis, are highlighted in the topology view. You can view dependent relationships between services and systems from the Topology tab.

Using the viewer, you can:

Metrics

Once discovered, metrics are collected for Oracle E-Business Suite System as well as its individual members. To see the metrics collected for any target, select Monitoring > All Metrics from the Target menu.

the picture is described in the document text

For more information on metrics, see: Oracle Application Management Pack for Oracle E-Business Suite Metric Reference Manual.

Setting Thresholds for Metrics

Metrics collected can be compared to predefined values to check if they are exceeding a critical threshold or a warning threshold. Incidents are generated once the threshold is exceeded. To see the thresholds defined for metrics of any target, select Monitoring/Metric and Collection Settings from the Target menu. Here you can set the Critical/Warning thresholds used to generate incidents. You can also change the collection schedule of the metrics here.

For more information on incidents, see: Incidents for an Oracle E-Business Suite Target.

the picture is described in the document text

Home Page of an Oracle E-Business Suite System

General Section

The general section gives the following basic details of the Oracle E-Business Suite instance.

Configured Components

The count of member targets that fall into the status categories of Up, Down, or Other. You can drill down on a status category to view the targets that currently fall into that category.

System Name

The name of the Oracle E-Business Suite instance.

Version

The version of the Oracle E-Business Suite instance.

Products Installed

The number of products installed in the Oracle E-Business Suite system. You can drill down into Oracle Applications Manager to see the details.

New Internal System Alerts

The number of new System Alerts generated in the Oracle E-Business Suite instance. You can drill down on this number to view the details in Oracle Applications Manager. Note that these System Alerts originate from the alerting infrastructure of Oracle E-Business Suite. These are complementary to the Oracle Enterprise Manager incidents.

Patches Applied

The number of patches applied to the system in the last 24 hours. You can drill down to view the patches in Oracle Applications Manager.

Site Level Profile Options Changed

The number of site level profile options that have changed on the system in the last 24 hours. You can drill down to view the site level profile options in Oracle Applications Manager.

Context Files Edited

The number of AutoConfig context files that was changed on the system in the last 24 hours. You can drill down to view the context files in Oracle Applications Manager.

Monitoring Host

The host of the agent which is monitoring the Oracle E-Business Suite system. This will be the host where the database is running.

Note: The New Internal System Alerts, Patches Applied, Site Level Profile Options Changed, and Context Files Edited metrics are based on information periodically summarized in the Oracle E-Business Suite database by the Oracle Applications Manager Dashboard Collection concurrent program. This program is controlled through the Preferences global link in Oracle Applications Manager. If this program has been disabled in the Oracle E-Business Suite system for any reason, then these metrics will not be updated.

Availability Status Charts

This section has three charts:

the picture is described in the document text

Services

Oracle E-Business Suite and its member targets provide four major services to its customers. They are:

All these services are registered with Cloud Control once the successful discovery of the Oracle E-Business Suite target is completed . The services section in the home page of the Oracle E-Business Suite instance has the details of services. Each service has a set of critical components without which the service cannot be provided. The following table lists the critical component of each service.

Critical Components of Services
Service Critical components
Concurrent Processing

  • Internal Concurrent Manager

  • Concurrent Manager

  • Database

  • Apps Listener

Workflow Service

  • Concurrent Processing Service

  • Oracle Workflow Background Engine

  • Oracle Workflow Agent Listener

  • Oracle Workflow Notification Mailer

Forms Applications Service

  • Forms server (OC4J/WLS)

  • HTTP Server

  • Database

Self Service Applications Service

  • OACORE Server (OC4J/WLS)

  • HTTP Server

  • Database

Performance of Services

The metrics collected from a service's critical components are used to evaluate the performance of each service. The following table lists the performance metrics for each service.

Performance Metrics for Services
Service Metric Description
Concurrent Processing Service Concurrent Requests Success Rate Successfully completed requests per hour
Concurrent Processing Service Concurrent Requests Error Rate Failed requests per hour
Forms Service Forms Response Time Average response time of forms in milliseconds
Forms Service Forms Requests per Second Average of number of requests processed by the Forms server per second
Forms Service HTTP Server Request Throughput Average of number of requests processed by the HTTP server per second
Workflow Service Pending Agent Listener Events Count of pending agent listener events
Workflow Service Pending Mailer Notification Events Count of pending mailer notification events
Workflow Service Pending Mailer Notifications Count of pending mailer notifications
Self Service Applications Service OACore requests per second Average of number of requests processed by the oacore server per second
Self Service Applications Service HTTP Server Request Throughput Average of number of requests processed by the HTTP server per second

Usage by Services

The metrics collected from a service's critical components are used to evaluate the resources used by each service. The following table lists the the usage metrics for each service.

Usage Metrics for Services
Service Metric Description
Concurrent Processing Service Running Requests per Hour Number of requests running per hour
Concurrent Processing Service Active Service Processes Number of active services running per hour
Forms Service Forms server CPU usage Percentage of CPU used by the Forms server
Forms Service HTTP server CPU usage Percentage of CPU used by the HTTP server
Forms Service (Socket Mode) Total Memory Utilization Percentage of the total memory used by the Forms process
Forms Service (Socket Mode) Total CPU Utilization Percentage of CPU used by the Forms process
Forms Service (Socket Mode) Number of Forms Processes Total number of Forms processes that are running
Workflow Service Background Engine Deferred Items Number of items deferred by the background engine yet to be processed
Self Service Applications Service OACore CPU usage Percentage of CPU used by the oacore server
Self Service Applications Service HTTP server CPU usage Percentage of CPU used by the HTTP server

Charts for services

You can see charts based on the above performance and usage metrics. Go to the home page of each service and click on the tab Charts.

the picture is described in the document text

Incidents for Services

You can set thresholds for tracking the performance and usage of services. Incidents are generated once the metrics exceeds the threshold. To set the threshold, go to the home page of the service and click on the tab Monitoring Configuration. Click on the link Performance Metrics or Usage Metrics. You can set the warning and critical threshold for performance and usage metrics in the respective pages.

the picture is described in the document text

The services section in the Oracle E-Business Suite home page shows the details described in the following table:

Service Status Information on the Home Page
Status Whether the status is up or down
System The Oracle E-Business Suite system whose members are providing this service.
Performance Incidents Number of performance incidents which are Critical or Warning. You can drill down from here to get the details of the incident.
Usage Incidents Number of performance incidents which are Critical or Warning. You can drill down from here to get the details of the incident.
Key Components Status The status of the key components. The service will be down if any of the key components is down. You can drill down from here.
Key Components Incidents Incidents (Critical and Warning) raised against key components of the service. You can drill down from here.

Services Dashboard

Extending the service dashboard feature provided by Cloud Control, Oracle E-Business Suite also has a service dashboard which provides a brief summary of all service-related information. You can access it by selecting Service Level Reports > Oracle Application Services from the target menu.

the picture is described in the document text

Targets Running on Nodes

This section shows the targets running on each node in which the Oracle E-Business Suite is deployed. The data is shown in a hierarchical way with the host as the topmost parent. The nodes running on that host appear as the immediate children. The individual targets running on each node will appear as the child of each node. If the Oracle E-Business Suite instance features Online Patching, only run edition targets will be shown.

the picture is described in the document text

Tip: Use the Detach button to view the table in a separate page. This feature is useful if your table has more rows than can be shown in the default display.

Configuration of Oracle E-Business Suite

You can get the details of how the Oracle E-Business Suite instance is configured by looking at the configuration metrics collected for the Oracle E-Business Suite target. Select Configuration > Last Collected from the target menu.

the picture is described in the document text

Configuration of all members

To see the configuration of each member target of Oracle E-Business Suite you would have to go to the home page of each target and follow the navigation path mentioned above. As this would be inconvenient, the Configuration of all members page simplifies this task. You will get a link to see configuration of all members in one place. Select Configuration of all members from the Oracle E-Business Suite target menu.

the picture is described in the document text

Here you can see the links to see the last collected configuration of all member targets grouped as nodes, host, services etc. You can search for any context variable by clicking the Search Context Variable button. You can also search for patches applied and patch set information.

Comparing Configurations

Comparing configurations is very important while managing Oracle E-Business Suite targets. Benefits include:

You can compare the configuration of one Oracle E-Business Suite instance with another or the configuration of the same Oracle E-Business Suite instance collected at different times. The same applies to any member target of Oracle E-Business Suite as well. To compare configurations select Configuration > Compare from the target menu.

the picture is described in the document text

Configuration Comparison Templates

In Enterprise Manager, a comparison template is an exemplar for fine-tuning a comparison of like configurations. A template is associated with a specific target type, which determines the configuration item types, items, and properties to be compared. A set of default templates ships out of box to support certain target types. A template enables you to establish specific settings to take into account when comparing configurations of the given target type; for example, which property differences to ignore, and which property differences trigger an alert. For more information on comparison templates, see the Oracle Enterprise Manager Lifecycle Management Administrator's Guide.

The Oracle E-Business Suite plug-in includes a set of comparison templates for the following target types:

These templates will be available once the Oracle E-Business Suite plug-in is deployed. You can use these templates to compare the configurations of similar target types without creating new comparison templates.

You can use these templates as-is, or as a guideline. For example, you might decide that an existing comparison template, with just a few changes, can meet your requirements. Perhaps a shipped template ignores property differences that you are concerned about. In this case, you can use the "Create Like" feature to make the adjustments to the existing template and save the new template under a different name.

Using a configuration comparison template

Click on Enterprise > Configuration > Compare.

In the Search region, select one of the above target types in the Target Type List. Click on the Search button.

Select the configuration against which other configurations will be compared. Click Next.

Click Add Configuration to select a single or multiple configurations to compare with the first. Click Next.

Select the template with the same name as the target type. In the same page you can view the template settings and member settings of the comparison template.

Click Submit.

Check the comparison result. The comparison report should adhere to the selected template rules. That is, if there are any ignored members or properties present from comparison , the same properties/members should not be present in the result report.

Creating a copy of an existing comparison template

Click on Enterprise > Configuration > Comparison Templates. Select an existing template's row and click Create Like. Give the new template a name and edit the copy of the template.

Incidents for an Oracle E-Business Suite Target

Incidents will be raised if any member of the Oracle E-Business Suite system is down or if any metric exceeded its threshold. The incidents region in the Oracle E-Business Suite instance home page gives an overview of the incidents raised for that instance. You can get the number of incidents grouped by severity. In addition, you can filter incidents based on the type of the incident, such as availability, performance, security, and so on. You can drill down to the details of each incident by clicking on the summary column which takes you to the Incident Manager. Here you can see more details of the event. You can also track and manage the incident from here.

Compliance Standards for Oracle E-Business Suite

Compliance evaluation generates a score for a target which indicates how much the target is compliant with the standard. Violation of a standard can be classified as critical, warning or minor warning.

The management pack includes a set of compliance standards for Oracle E-Business Suite security which will be associated to every Oracle E-Business Suite instance once it is discovered. Evaluation will happen periodically which will ensure that the Oracle E-Business Suite is configured in a secure way.

The following table lists details of the compliance standards shipped along with the compliance rules associated with them.

Compliance Standards
Compliance Standard Rules mapped to the standard Severity
Profile Settings Check if all critical profiles are set correctly. Critical
Profile Settings Check if other profiles are set correctly. Warning
Profile Settings Check if no profile is missing. Critical
Change Default Passwords Checks if any database user with a default password exists. Critical
Change Default Passwords Checks if any application user with a default password exists. Critical
Secure APPLSYSPUB Checks if there is any unwanted privilege in the APPLSYSPUB account. Warning
Use Secure Flag on DBC File Checks if server security is on. Warning
Migrate to Password Hash Checks if the setting for hashed passwords are on. Warning
Enable Application Tier Secure Socket Layer (SSL) Checks if Oracle E-Business Suite is configured for HTTPS. Warning
Turn on ModSecurity Checks if mod security is on. Warning
Encrypt Credit Card Data Checks for the encryption of credit card data. Warning
Encrypt Credit Card Data Checks if supplemental credit card data is encrypted or not. Warning
Encrypt Credit Card Data Checks if enhanced hashing is on or not. Warning
Database Configuration Standards Checks if the parameter work area size policy is set to the default recommendation Critical
Database Configuration Standards Checks if the use of bitmap plans optimizer parameter is set to the default recommendation Critical
Database Configuration Standards Checks if NLS date default format is set for Oracle E-Business Suite Critical
Database Configuration Standards Checks if block size for Oracle E-Business Suite is 8K Critical
Database Configuration Standards Checks if the create columns semantics is using byte by default for Oracle E-Business Suite Critical
Database Configuration Standards Checks if the total size of the SGA is configured set to the default recommendation for Oracle E-Business Suite Critical
Database Configuration Standards Checks if version 7 dictionary accessibility support for Oracle E-Business Suite is set to False Critical
Database Configuration Standards Checks if the Cost Based Optimizer is set to FALSE for Oracle E-Business Suite Critical
Database Configuration Standards Checks if the treat LIKE predicate with bind as an equality predicate optimizer parameter is set to suggested value Critical
Database Configuration Standards Checks if the index fast full scan configuration set to the default recommendation Critical
Database Configuration Standards Checks for cursor sharing mode in Oracle E-Business Suite Critical
Database Configuration Standards Checks if the system management undo parameter is set for Oracle E-Business Suite Critical
Database Configuration Standards Checks if the cost ratio for sort elimination optimizer parameter is set to suggested value for Oracle E-Business Suite Critical
Database Configuration Standards Checks if optimizer parameters used to turn off automatic statistics is set for Oracle E-Business Suite Critical
Database Configuration Standards Checks if the database system triggers has been enabled for Oracle E-Business Suite Critical
Cluster Database Configuration Standards Checks if the Real Application Clusters parameter is set to TRUE startup in cluster Critical

The compliance standards region in the home page of the Oracle E-Business Suite instance has the details of the evaluations performed on that instance and how many violations are there. You can click on each standard which will give further details of evaluations per rule. Each standard comes with a recommendation on how to fix the violations for that standard.

Note: Compliance standards will not be set for Oracle E-Business Suite instances discovered using the previous releases of the management pack. You must rediscover an instance to attach compliance standards to it.

Monitoring Online Patching to Detect Cutover

If the Oracle E-Business Suite Target features online patching, false incidents will be raised for the patch edition targets being down or the whole Oracle E-Business Suite being down during cutover. To prevent this the system keeps checking the patching activities to see if any cutover is in progress. Corrective actions are triggered once it detects a cutover. If there is any cutover in progress the whole Oracle E-Business Suite target will be blacked out. This is true if the patching is done either from Patch Manager or Oracle E-Business Suite console. Once the cutover is complete (success or failure) the corrective actions will end the blackout of the Oracle E-Business Suite target and black out the correct patch edition.

Important points to note

Monitoring Current Activity

Activity metrics are collected for the Oracle E-Business Suite target. These metrics provide details of current activities going on the Oracle E-Business Suite instance. Select Monitoring/All Metrics from the target menu. Expand the metric named Activity. You can see the trends for service processes, concurrent processing, and Forms.

the picture is described in the document text

Monitoring User Sessions

When a user logs in to Oracle E-Business Suite, the system creates sessions in the database identified by a unique session ID, or SID. All of these user sessions are created using the APPS schema credential. Each database session is associated with an Oracle E-Business Suite application user. This feature enables linking the database session with the corresponding application user for monitoring and troubleshooting purposes. You will be able to pinpoint how the Oracle E-Business Suite user opened a database session and whether it is with a concurrent processing, Forms, or Self-Service application.

For information on diagnostic tests for this feature, see: Diagnostic Tests for User Monitoring.

Mandatory Settings

The following settings are mandatory:

Settings in the OMS

Set the preferred credentials of the "Oracle E-Business Suite" target type for the credential set AppsUserCredsSet. You must provide the Oracle E-Business Suite user login credentials.

For information on setting preferred credentials, see: Setting Oracle E-Business Suite Preferred Credentials.

Settings on the Oracle E-Business Suite

Top Sessions

This page will show four bar charts of database sessions triggered by APPS database user.

The level of detail shown in the bar graphs is controlled by properties set in the Preferences page. See: Setting Preferences.

You can drill down from the legend to see the details of the session. If the Oracle E-Business Suite user information is available, the Oracle E-Business Suite session details is shown with further drilling down available to the database session details. If the Oracle E-Business Suite user information is not available (that is, the database sessions was triggered by a background process and not by a user), you can drill down to the database session details directly.

To navigate to the Top Sessions page, select User Monitoring > Top Sessions from the target menu of the Oracle E-Business Suite target.

the picture is described in the document text

Searching for User Sessions

You can search for Oracle E-Business Suite user sessions using:

Database Session ID - Provide the database session ID and if a match is found with a concurrent program, form, or Oracle Application Framework page, the details will be shown with a drilldown facility to the database session details.

Oracle E-Business Suite user name - This search shows all the active concurrent programs, Forms, and Oracle Application Framework pages accessed by the user. It will also show the associated database session ID with drilldown capability.

To navigate to user sessions search, select User Monitoring > Search E-Business Suite User from the target menu of the Oracle E-Business Suite target.

the picture is described in the document text

Monitoring JVM Usage

Note: This feature is not supported for Oracle E-Business Suite Release 12.2 in this release. Starting from AMP 12.1.0.3.0, this feature is disabled by default. You must enable it by following the steps mentioned below.

You can monitor JVM usage parameters which are specific for Oracle E-Business Suite. You can review the following parameters for each of the oacore J2EE containers in which a given Oracle E-Business Suite instance is deployed.

Setup Steps

For Release 12 systems, ensure that you have set up the monitoring configuration for each "oacore" OC4J target as follows:

  1. In the section Targets Running on Nodes in the Oracle E-Business Suite instance home page, click on the "oacore" OC4J target. This will take you to the home page of the target.

  2. On the home page of the oacore OC4J target, Select Target Setup > Monitoring Configuration in the target menu.

  3. Enter the OC4J administrator username and password for the "oacore" OC4J in the "Username for Basic authorization" and the "Password for Basic authorization" fields, respectively.

    Note: The OC4J administrator username by default is "oc4jadmin" and is specified in the system-jazn-data.xml file under the $INST_TOP/ora/10.1.3/j2ee/oacore/config directory. The oc4jadmin password by default is set to a randomized value during installation and will need to be reset as in the following example:

    In the $INST_TOP/ora/10.1.3/j2ee/oacore/config/system-jazn-data.xml file, set the value of the "credentials" element for oc4jadmin user to your chosen password preceded by a ! character. For example:

    <user>
<name>oc4jadmin</name>
<display-name>OC4J Administrator</display-name>
<description>OC4J Administrator</description>
<credentials>[new password]</credentials>
</user>

    After saving system-jazn-data.xml, restart the oacore OC4J. This step encrypts the updated password in system-jazn-data.xml.

  4. Click OK to save the information.

For both Release 11i and Release 12, ensure that the Application Server passwords are set as well, because Oracle Enterprise Manager expects these passwords to be set for metrics collection for the JVM targets.

Command to enable the metric collection

./emcli modify_collection_schedule -force
-targetType="oracle_apps_jvm"
-targetNames="<targetName1>,<targetName2>"
-collectionName="LockedAOLJConn"
-collectionStatus="Enabled" -preview=N -freqType="Minute"
-freqValue="1"
./emcli modify_collection_schedule -force
-targetType="oracle_apps_jvm"
-targetNames="<targetName1>,<targetName2>"
-collectionName="AMPoolCount"
-collectionStatus="Enabled" -preview=N -freqType="Minute"
-freqValue="1"
./emcli modify_collection_schedule -force
-targetType="oracle_apps_jvm"
-targetNames="<targetName1>,<targetName2>"
-collectionName="CachedObjects"
-collectionStatus="Enabled" -preview=N -freqType="Minute"
-freqValue="1"

Command to disable the metric collection

emcli modify_collection_schedule
-targetType="oracle_apps_jvm"
-targetNames="<targetName1>,<targetName2>"
-collectionName="LockedAOLJConn"
-collectionStatus="Disabled" -preview=N emcli modify_collection_schedule
-targetType="oracle_apps_jvm"
-targetNames="<targetName1>,<targetName2>"
-collectionName="AMPoolCount"
-collectionStatus="Disabled" -preview=N emcli modify_collection_schedule
-targetType="oracle_apps_jvm"
-targetNames="<targetName1>,<targetName2>"
-collectionName="CachedObjects"
-collectionStatus="Disabled" -preview=N

To find out the oracle_apps_jvm target names associated with an Oracle E-Business Suite instance, go to the All Targets page and search for <ebs_instance_name>%oacore_jvm_1_apps.

Note: It is important to set the oc4j admin username and password at the EBS as per the mandatory setups mentioned above. If you enable this metric without doing that, it can result in flooding of metric collection errors at the OMS repository.

Monitoring Templates for Oracle E-Business Suite

Monitoring templates let you standardize monitoring settings across your Oracle E-Business Suite environments by allowing you to specify the monitoring settings once and apply those to your monitored targets. You can save, edit, and apply these templates across one or more targets. A monitoring template is specified for a particular target type and can only be applied to targets of the same type. For example, you can define one monitoring template for Oracle E-Business Suite test instances and another monitoring template for Oracle E-Business Suite production instances. For more descriptions of Oracle Certified Templates and Oracle Provided Templates please see the latest Oracle Enterprise Manager Cloud Control Administrator's Guide.

Note: Currently, Oracle delivered templates may not have many out-of-box metric values. However, you can set these metric values by observing the trend in your own environment over a period of time. You can view some of the trend information by examining Average value, Low value, and High value statistics for each metric that you are monitoring using the template.

Managing Out-of-Box Monitoring Templates for AMP Targets

Navigate to monitoring templates using the path Enterprise (menu) > Monitoring > Monitoring Templates.

the picture is described in the document text

Users must have the requisite privilege(s) to manage monitoring templates. The privilege(s) for the view/edit/create like/delete functions for managing out-of-box monitoring templates for AMP are the same as that for all out-of-box monitoring templates. See: Oracle Enterprise Manager Cloud Control Administrator's Guide for more information.

the picture is described in the document text

Viewing Out-of-Box Monitoring Templates

To view out-of-box monitoring templates, select “Display Oracle Certified Templates” and search for templates. All Oracle-certified templates are displayed.

Default Listing of the Monitoring Templates

Out-of-box monitoring templates are called ‘Oracle Certified Templates’, by default the ‘Oracle Certified Templates’ are not displayed.

Find Out-of-Box Monitoring Templates for Oracle Application Management Pack for Oracle E-Business Suite

Search for out-of-box monitoring templates for AMP targets by checking "Display Oracle Certified Templates" and selecting the AMP target type, or enter the Target Name search criteria. Currently, out-of-box monitoring templates is supported for following AMP targets:

the picture is described in the document text

Editing Out-of-Box Monitoring Templates

Editing an out-of-box monitoring template is not permitted in all Enterprise Manager versions. Please check Oracle Enterprise Manager Cloud Control Administrator's Guide for more information.

In addition, the Edit option is enabled only if the user has the required privilege to edit an out-of-box monitoring template through Enterprise Manager. AMP templates follow the same restrictions as all out-of-box monitoring templates.

The Monitoring Templates home page lists all viewable templates. To display out-of-box templates, search using the criterion ‘Oracle Certified Templates’.

To edit a template:

  1. From the Enterprise menu, select Monitoring, and then Monitoring Templates.

  2. Choose the desired out-of-box monitoring template from the table.

  3. Click Edit.

  4. Once you have finished making changes, click OK.

Copying an Out-of-Box Monitoring Template

To create a template based on an existing template, select the template, go to Actions and select ‘Create Like’.

the picture is described in the document text

Enter the inputs for ‘General’, ‘Metric Thresholds’, and ‘Other Collected Items’ and click OK.

the picture is described in the document text

Deleting an Out-of-Box Monitoring Templates

Out-of-box monitoring templates cannot be deleted.

Applying a Monitoring Template to an Oracle E-Business Suite Target

An out-of-box monitoring template can be applied to an AMP target based on the target type. To apply a template, you must have at least Manage Target Metrics target privileges on the destination target(s).

  1. From the Enterprise menu, select Monitoring and then Monitoring Templates.

  2. Select the desired template from the table.

  3. Click Apply.

  4. Select the desired apply options and the target(s) to which you want the templates applied. See Oracle Enterprise Manager Cloud Control Administrator’s Guide for more information.

  5. Click OK.

the picture is described in the document text

Other Features of Monitoring Templates

All other features of out-of-box monitoring templates such as ‘Compare Settings’ , ‘View Past Apply Operations’ are valid for out-of-box monitoring templates in AMP.

Defining or Modifying the Threshold Values in the Out-of-Box Monitoring Templates

Currently, the Oracle Application Management Pack for Oracle E-Business Suite supplies the out-of-box monitoring templates with default values. To define the threshold values in out-of-box monitoring templates, the following steps are involved:

  1. Observe the trend of the metrics for the targets.

  2. Determine the threshold values based on observation.

  3. Modify the threshold values by editing the template.

  4. Apply the modified template to the target.

To check the trend of the metrics for the target, navigate to [Target] > Monitoring > All Metrics. Select any metric, and check ‘Metric Value History’. Change the ‘View Data’ period based on the time of analysis.

the picture is described in the document text

Enabling Service Tests and Beacons Link

Administrators can define service tests for Oracle E-Business Suite services, and can also define their own ATS transactions to determine the health of an application (for example, whether the application is rendering the correct pages and functional flows are intact). All Oracle E-Business Suite service targets support the Service Test Types of ATS and HTTPPING. For more information on service tests, service test types, beacons, and Oracle Application Test Suite (OATS), see the section "Configuring and Using Services" in the Oracle Enterprise Manager Cloud Control Administrator's Guide.

Specifically, the following services have the 'Service Tests and Beacons' link enabled:

The basic steps to create such a test are as follows:

  1. Navigate to the Service target home page.

  2. Select the Service link.

  3. Click on the Monitoring Configurations tab.

  4. Select the “Service Tests and Beacons” link.

  5. Select ‘Test Type’ as ‘ATS Transaction’ and click Add.

  6. Enter an appropriate name.

  7. Click the Upload button and select the OATS script zip file.

  8. Add a Beacon to monitor the Service Test. The Enterprise Manager Management Beacon default is available.

  9. Enable the Service Test.

  10. Click OK.

Example - Creating an ATS transaction for a Concurrent Processing Service

  1. Navigate to the an Oracle E-Business Suite instance home page. Under Services, click on a concurrent processing service's name (link).

  2. Click on the Monitoring Configurations tab in the Concurrent Processing Service page.

    the picture is described in the document text

  3. Select the “Service Tests and Beacons” link.

    the picture is described in the document text

  4. Select 'ATS Transaction’ for the Test Type and click Add.

    the picture is described in the document text

  5. Enter an appropriate name for the test.

  6. Upload the OATS script ZIP file from the Local Machine or Test Repository.

    the picture is described in the document text

  7. Add a Beacon to monitor the Service Test. The Enterprise Manager Management Beacon default is available.

    the picture is described in the document text

  8. Enable the Service Test.

  9. Click OK.

Seeded ATS Test Transaction for Self Service Applications Service

A sample ATS test script is shipped out of the box for a login/logout test against Oracle E-Business Suite 12.1.X instances. This script will only work if the 12.1.X instance is not SSL configured. This ATS test transaction is configured during the discovery time of the 12.1.3 Oracle E-Business Suite instance against ‘Self Service Applications Service’. An end user needs to enable the ATS transaction and edit it with a correct Oracle E-Business Suite username and password.

  1. Click on the Monitoring Configuration tab from the Self Service Applications Service home page.

    the picture is described in the document text

  2. Click on the 'Service Tests and Beacons' link.

    the picture is described in the document text

  3. The default ATS service test is disabled. First mark the default beacon, ‘EM Management Beacon’ as ‘Key Beacon’ in the Beacons region. Then click on the Enable button for the Service Test.

    the picture is described in the document text

  4. Click on Edit.

    the picture is described in the document text

  5. Enter the Oracle E-Business Suite applications username and password under Variables, Sensitive Values. Click OK.

    the picture is described in the document text

  6. Again, click the OK button from the Service Tests and Beacons home page to ensure that the changes are saved.

    the picture is described in the document text

  7. You can verify service test as follows:

    Click the Verify Service Test button in the Service Tests region.

    the picture is described in the document text

    Click the Perform Test button.

    the picture is described in the document text

    Execution results are displayed in the results table.

    the picture is described in the document text

  8. You need to mark this service as ‘Key Service Test’ so that it starts contributing to the availability.

    Check the Key Service Test box and click the Change Key Tests button.

    the picture is described in the document text

For more details see the chapter "Configuring and Using Services" in the Oracle Enterprise Manager Cloud Control Administrator's Guide.

Configuring Monitoring of HTTPS/SSL Targets

To configure Cloud Control to monitor Oracle E-Business Suite middle tiers that are running in SSL, each Management Agent must be able to authenticate the middle tier's SSL certificate against its Certificate Authority (CA).

Assumed Prerequisites

The HTTP Server that ships with Oracle E-Business Suite is already configured and verified to be running in SSL mode.

Basic knowledge of SSL certificates and their configuration.

Obtaining the CA certificate(s)

  1. In Microsoft Internet Explorer, connect to the HTTPS URL of the Web site you are attempting to monitor.

  2. Double-click the lock icon at the bottom of the browser screen which indicates that you have connected to a secure Web site. The browser displays the Certificate dialog box, which describes the certificate used for this Web site. Other browsers offer a similar mechanism to view the certificate details of a Web site.

  3. Click the Certificate Path tab and select the first entry in the list of certificates.

  4. Click View Certificate to display a second Certificate dialog box.

  5. Click the Details tab on the Certificate window.

  6. Click Copy to File to display the Certificate Manager Export wizard.

  7. In the Certificate Manager Export wizard, select Base64 encoded X.509 (.CER) as the format you want to export and save the certificate to a text file with an easily identifiable name, such as beacon_certificate.cer.

  8. Open the certificate file using a text editor.

Add the Certificate to the Management Agent(s)

Each Management Agent that monitors an Oracle E-Business Suite middle-tier must have the CA certificate added to it as follows:

  1. Locate the b64InternetCertificate.txt file in the following directory of Agent Home of the Beacon host: $AGENT_ORACLE_HOME/sysman/config (This file contains a list of Base64 Certificates).

  2. Edit the b64InternetCertificate.txt file and add the contents of the certificate file you just exported to the end of the file, taking care to include all the Base64 text of the certificate including the BEGIN and END lines.

  3. Repeat for each Management Agent.

Restart Each Management Agent

Each Management Agent should be restarted: 

> $AGENT_ORACLE_HOME/bin/emctl stop agent
> $AGENT_ORACLE_HOME/bin/emctl start agent

Cloud Control may not immediately pick up the change. You may want to give it a few minutes for the agent to run a metrics collection and upload them to the Oracle Management Server (OMS). You can click on the Refresh icon in the upper right of the Oracle E-Business Suite home page (by the Page Refreshed time stamp) in the Cloud Control console to get updated information.

Importing an Oracle E-Business Suite SSL Certificate to the OMS

Oracle Application Management Pack for Oracle E-Business Suite invokes REST services deployed on Oracle E-Business Suite using java.net.HttpURLConnection. The User Monitoring and Diagnostics features use REST services. If the Oracle E-Business Suite instance is SSL-enabled, the SSL certificate must be exported from Oracle E-Business Suite and imported to the trust keystore of the Oracle WebLogic Server (WLS) that runs the OMS. Below are the steps to do this action:

  1. Find out the trust keystore of WebLogic Server.

  2. Open the WebLogic Server Administration Console by using the following steps.

    1. Go to the All Targets page of Enterprise Manager Grid Control.

    2. Select the target type Oracle WebLogic Server.

    3. Select the WebLogic Server instance that runs the OMS.

    4. The target home page will contain the link to open the Administration Console.

  3. From the Administration Console, select Servers.

  4. Select the server that runs the OMS.

  5. Click on the subtab Keystores under Configuration.

  6. Look for the Java Standard Trust Keystore which points to the location of the keystore.

  7. Run the command to import the certificate using the keytool utility. Use the JDK that comes with WebLogic Server.

    JDK_HOME/bin/keytool -importcert -alias oracle_ebs_<ebs instance name> -trustcacerts -file <location of EBS SSL certificate> -keystore <location of key store>

    Refer to the Java SE documentation on the command keytool for information on passwords.

  8. Restart the OMS.

For more information on configuring identity and trust for WebLogic Server, see the Oracle Fusion Middleware manual Securing Oracle WebLogic Server.

A Note on Oracle Forms 6i

Even though your Oracle Forms configuration may be running in SSL, Cloud Control does not require any additional configuration to monitor Forms. The reason for this is that it uses a different method for determining the Forms Server status which does not require SSL communications with the server.

Re-Configuring SSL for Oracle E-Business Suite

If you have implemented SSL or deactivated SSL after the initial discovery of that Oracle E-Business Suite instance in Cloud Control, you will have to re-configure Cloud Control to monitor the new URL with the new protocol. There are two ways to do this:

Re-configuring Release 11i Apache Targets

  1. Select the Release 11i instance in the Oracle Applications targets tab.

  2. Under Applications Nodes Status, expand the Context link that corresponds with your SSL middle tier.

  3. Select the Apache target (description: "HTTP Server for Oracle Applications 11i").

  4. From the Target menu, select Target Setup, then select Monitoring Configuration.

  5. Edit the Protocol and Port as appropriate.

  6. Click OK.

Re-configuring Release 12 Application Servers

  1. Select the Release 12 instance in the Oracle Applications targets tab.

  2. Under Applications Nodes Status, expand the Context link that corresponds with your SSL middle tier.

  3. Select the target described as "Oracle Application Server".

  4. Navigate to the Target menu (labeled "Application Server"), and select Change Application URL.

  5. Edit the "URL to measure application response" as appropriate.

  6. Click OK.

References

Drilling Down to Oracle Applications Manager

You can drill down to the Oracle Application Manager of each Oracle E-Business Suite instance from Oracle E-Business Suite plug-in. Select Oracle Applications Manager from the target menu.

the picture is described in the document text

You can go to the following sections and its subsections in Oracle Applications Manager:

Concurrent Processing Dashboard

The Concurrent Processing Dashboard provides you with details in concurrent processing in your Oracle E-Business Suite system. The dashboard gives you a complete picture of concurrent processing on your system, both current activities as well as usage statistics.

To navigate to the Concurrent Processing Dashboard, select E-Business Dashboard > CP Dashboard from the target menu of the Oracle E-Business Suite target.

the picture is described in the document text

You can add a user-defined concurrent program as a target to the Oracle E-Business Suite composite target. You can then monitor related activities of the registered individual concurrent programs for your own specified thresholds.

You can also add a user-defined concurrent manager as a target to the Oracle E-Business Suite composite target. You can then monitor related activities of the registered individual concurrent managers for your own specified thresholds.

Overview Tab

the picture is described in the document text

The General region includes details on the status of the Concurrent Processing Service:

The Hourly Completed Requests region shows a pie chart for requests by status (Successful, Warning, and Errored).

The Activity Summary graph illustrates active requests in the following statuses

The Components region lists components of the Concurrent Processing service. The table shows the following for each component:

The Incidents region lists any incidents that were triggered recently, with the following information for each:

At the bottom of the dashboard are Related Links:

The first three links provide metrics on requests and processes:

The last three links take you to Oracle Applications Manager pages for the Oracle E-Business Suite instance:

Current Activity Tab

the picture is described in the document text

The Concurrent Requests by Status region lists the number of requests for each status:

Click on the number for a status to find out more about the metric trend.

The Hourly Completed Requests region lists statistics for requests that have completed in the past hour, including:

Click on the number for each statistic to find out more details.

The Concurrent Managers by Requests lists all concurrent managers, in order of the number of requests it has in the specified status, either Running or Pending.

With "Running" selected, the following is shown for each concurrent manager:

With "Pending" selected, the following is shown for each concurrent manager:

The Top Concurrent Requests region shows the top ten (10) requests for the specified status of Running, Pending, or Scheduled.

The Top Applications region lists the top ten (10) applications for running requests or pending requests, as specified.

The Top Users region lists the top ten (10) users by number of running or pending requests, as specified.

Usage Tab

the picture is described in the document text

This tab provides a summary of how the concurrent programs and managers have been utilized over a period of time.

The top ten (10) concurrent requests for the following categories are listed:

the picture is described in the document text

The top ten (10) applications for the following categories are listed:

The top ten (10) users by total number of requests are also listed, in descending order of number of requests.

User-Defined Targets Tab

the picture is described in the document text

You can add concurrent managers and programs as targets to monitor. Use this tab to get details about these targets as well as add more custom targets.

Concurrent Programs

For custom concurrent program targets, the following columns are shown:

Click on "Show" in the Details column to see the following metrics for the given concurrent program target. (More details can be seen from the Target home page > All Metrics):

Use the Add button under Concurrent Programs to add a new program target.

Concurrent Managers

For concurrent manager targets, the following columns are shown:

Click on "Show" in the Details column to see the following for the given concurrent manager target:

Use the Add button under Concurrent Managers to add a new manager target.

Adding a Concurrent Program Target

You can add a concurrent program custom target so that the system will collect metrics on activity and usage for the concurrent program.

Note: You cannot add a custom concurrent program target using Internet Explorer 8. Please use a different version, or different browser such as Mozilla Firefox.

  1. To add a concurrent program custom target, navigate to the Concurrent Processing Dashboard, User Defined Targets tab, and click Add under Concurrent Programs.

    the picture is described in the document text

  2. For your new target, define the following:

    • Target Name Prefix - This value is determined by the system based on the instance name and cannot be updated.

    • Target Name - Enter in a target name "suffix". The actual target name will be composed of the Target Name Prefix (above) and the value of this field.

    • Target Type - The system automatically provides the value "Custom Oracle Concurrent Program".

    • Concurrent Program Short Name - Use the LOV icon to search for and select the program short name. In searching for the program name you can search by concurrent program short name, concurrent program name, or application.

    • Monitoring Host

    For the Basic Properties region, values for the following should default in. These values are used as credentials by the target for metrics collection:

    • SID

    • Machine

    • Port

    • (Database) User name

    • (Database) Password

    • ConnectString

  3. For metrics collection, you need to define the thresholds for several metrics. Define instance parameters that will be used to categorize requests for the following:

    A request will be termed Long Pending if it is in Pending status for longer than the "Long Pending Request Threshold In Minutes".

    A request will be considered Long Running if it runs for longer than the "Long Running Request Threshold In Minutes" and (1+0.1*"Long Running Tolerance Percentage")*Average Running Time of the Concurrent Program.

  4. When you are done, click Add to add the target.

Custom Concurrent Program Target Metrics

Once you have added a custom concurrent program target, you can monitor it. It should be listed on the User Defined Targets tab. Click on its name link to view details.

the picture is described in the document text

Click on the Show link under Details for links to drill down on the following:

From here, you can access the metrics collected for this target by navigating to Target menu > Monitoring > All Metrics. The collected metrics are listed below.

Metrics Collected

The following metrics are collected:

Basic Information

This page lists metrics for the following:

Concurrent Requests by Status

The numbers for requests in each status below are listed.

Hourly Completed Requests

Long Pending Requests

Long Running Requests

Pending Requests

Requests Completed with Error

Requests Completed with Warning

Running Requests

Adding a Concurrent Manager Target

You can add a concurrent manager custom target so that the system will collect metrics on activity and usage for requests run by the concurrent manager.

  1. To add a concurrent manager custom target, navigate to the Concurrent Processing Dashboard > User Defined Targets tab, and click Add under Concurrent Manager.

    the picture is described in the document text

  2. For your new target, define the following:

    • Target Name Prefix - This value is determined by the system based on the instance name and cannot be updated.

    • Target Name - Enter in a target name "suffix". The actual target name will be composed of the Target Name Prefix (above) and the value of this field.

    • Target Type - The system automatically provides the value "Custom Oracle Concurrent Manager".

    • Concurrent Manager Short Name - Use the LOV icon to search for and select the concurrent manager short name. In searching for the manager name you can search by concurrent manager short name, concurrent manager name, or application.

    • Monitoring Host

    For the Basic Properties region, values for the following should default in. These values are used as credentials by the target for metrics collection:

    • SID

    • Machine

    • Port

    • (Database) User name

    • (Database) Password

    • ConnectString

  3. For metrics collection, you need to specify values for three Instance Properties that will be used to categorize requests for the following:

    A request will be termed Long Pending if it is in Pending status for longer than the "Long Pending Request Threshold In Minutes".

    A request will be considered Long Running if it runs for longer than the "Long Running Request Threshold In Minutes" and (1+0.1*"Long Running Tolerance Percentage")*Average Running Time of the Concurrent Program.

    You can also change these properties by clicking the "Monitoring Configuration" link on the Target Home page.

  4. When you are done, click Add to add the target.

Monitoring a Custom Concurrent Manager Target

Once you have added a custom concurrent manager target, you can monitor for it. It should be listed on the User Defined Targets tab. Click on its name link to view details.

the picture is described in the document text

From here, you can also monitor the metrics for this target by navigating to Target menu > Monitoring > All Metrics.

Active Processes

Pending Requests

Running Requests

Concurrent Processing Metrics

the picture is described in the document text

This section lists the concurrent processing metrics available from the All Metrics page. Navigate to the All Metrics page by selecting Target menu > Monitoring > All Metrics.

For each type of metric below, the details listed for each record are shown.

Active Concurrent Requests by Application

Applications by Errored Executions

Applications by Executions

Applications by Pending Requests

Applications by Running Requests

Programs by Average Running Time

Programs by Errored Executions

Programs by Executions

Programs by Total Running Time

Top Pending Requests

Top Running Requests

Top Scheduled Requests

Top Users (Requests Submitted)

Users by Pending Requests

Users by Running Requests

Setting Long Running and Long Pending Requests Parameters for Metrics and Incidents

Oracle Application Management Pack for Oracle E-Business Suite allows you to define parameters for long running and long pending requests. Follow the procedure below to do so.

  1. From the Concurrent Processing Dashboard, add a custom concurrent program or concurrent manager target.

  2. For the custom target, enter in values for these fields:

    • Long Pending Request Threshold in Minutes

    • Long Running Request Threshold in Minutes

    • Long Running Tolerance Percentage

    The three parameters above are instance parameters for categorizing a request as long running or long pending.

    A request will be considered long pending if it is pending for more than the "Long Pending Threshold in Minutes" value.

    A request will be considered long running if it runs for more than the "Long Running Request Threshold in Minutes" value AND for longer than (1 + 0.01*[Long Running Tolerance Percentage]*[Average Running Time of the Concurrent Program]).

  3. After you have set these parameters, you can go to the All Metrics page to see these categories listed. Navigate to the All Metrics page by navigating to the Target Menu, selecting Monitoring, then selecting All Metrics.

    For Long Pending Requests, the following details are available through drilling down:

    • Request ID

    • Concurrent Program Short Name

    • Concurrent Program Name

    • Request Start Date

    • Username

    • Phase

    • Status

    • Pending Time

    • Concurrent Manager

    For Long Running Requests, the following are available through drilling down:

    • Request ID

    • Concurrent Program Short Name

    • Concurrent Program Name

    • Request Start Date

    • Username

    • Phase

    • Status

    • Running Time

    • Concurrent Manager

    For Long Running and Long Pending Requests, you can drill down to get a count for each.

  4. On the same All Metrics page, click on Metric and Policy Settings to edit the incident threshold for long pending and long running requests. Choose to view "All Metrics" from the View dropdown list and set the incidents count for Long Pending Requests and Long Running Requests.

Monitoring Concurrent Requests in a Blocked State

The metric Concurrent Requests in Blocked State for the target Oracle Concurrent Manager is used to collect information on requests that are in blocked state and raise incidents for requests where the requests are blocked for specified period of time. This metric is shipped without threshold time period; so to use this metric, you must provide the threshold time in minutes. This metric is also available for the target Custom Oracle Concurrent Manager which collect information of blocked concurrent requests which are specific to a Concurrent Manager.

the picture is described in the document text

Monitoring Capacity Utilization of Concurrent Managers

The metric Capacity Utilization of Concurrent Managers for the target Oracle Concurrent Manager is used to collect information on the utilized capacity for each manager type, and raise an incident when the utilized capacity is below a threshold value. This metric is shipped without a capacity threshold value, so to use this metric, you must provide a capacity utilization threshold in a percentage. This metric is also available for the target Custom Oracle Concurrent Manager which collect information about the capacity utilization of the specific concurrent manager.

the picture is described in the document text

Monitoring Unscheduled Requests

The metric Unscheduled Requests for the target Custom Oracle Concurrent Program is used to collect the number of the requests unscheduled for a concurrent program and raise an incident if there is any unscheduled request for a concurrent program that is recommended to be scheduled. This metric is shipped without a threshold. You must set it to 0 to get alerts.

the picture is described in the document text

Monitoring Schedules for Requests

The metric Monitor Schedule for Requests for the target Custom Oracle Concurrent Program is used to collect the frequency with which a concurrent program request is scheduled (minutes, hours, days, or months) and raise an incident if it is not scheduled as per best practices. This metric is shipped without a threshold time period, so you must provide the threshold time in minutes, hours, days, or months.

the picture is described in the document text

Oracle E-Business Suite Summary on the Exalogic Dashboard

You can add an Oracle E-Business Suite Summary region for instances running on Exalogic machines to enable monitoring for these instances.

This region contains:

the picture is described in the document text

To add an Oracle E-Business Suite summary region on the Exalogic dashboard, perform the following steps:

  1. Click on the global menu Targets > Exalogic. The landing page with all the discovered Exalogic instances should be displayed.

  2. Click on any instance. The Exalogic dashboard should be displayed.

  3. Click on the personalization page icon. The page should become editable.

    the picture is described in the document text

  4. Click on the Add Content button for a list of available regions. Click the Add icon for Oracle E-Business Suite Instances to add the region.

    the picture is described in the document text

  5. Click Close to exit the editable page.

To remove the Oracle E-Business Suite summary region from the Exalogic dashboard, click on the personalization page icon, and the page should become editable. Click on the cross icon (X) on the top right side of the region to remove the Oracle E-Business Suite summary region.

To change the location of the Oracle E-Business Suite summary region, click on the View Action Menu icon on the top right side of the region and click Move Up/Move Down to rearrange the region on the Exalogic dashboard.

End To End Performance Monitoring with RUEI and JVMD

AMP now integrates seamlessly with RUEI and JVMD for monitoring performance of transactions. Real User Experience Insight (RUEI) understands how users are interacting with your product. Using the measurements that RUEI collects, you can assess the effectiveness of user interface design, the responsiveness of web servers and the internet, and the success of user operations. Java Virtual Machine Diagnostics (JVMD) looks at the finest details of code execution and to identify problems like race conditions, blocked threads, and memory leaks. To learn more about RUEI and JVMD , see Part VI - Monitoring Application Performance of Oracle Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management Plug-in.

Supported Oracle E-Business Suite Versions

This feature works only for Oracle E-Business Suite Release 12.2 and above, where the middle tier is deployed on the WebLogic Server.

Prerequisites

Setting up End to End Monitoring

Configure Oracle E-Business Suite in RUEI

Real User Experience Insight can be configured to support drilling down to JVM Diagnostics. For example, if a page is taking too much time to load, RUEI will detect it. You can then drill down from RUEI to JVMD and find out the root cause of why the page is hanging.

  1. Log in to RUEI.

  2. Navigate to Configuration > Applications > Suites.

    the picture is described in the document text

  3. Click on New Suite. A "New Suite" window opens.

    the picture is described in the document text

  4. Enter a suite name. This is the name that can be used to uniquely identify an Oracle E-Business Suite in RUEI. Provide any name that uniquely defines the Oracle E-Business Suite instance being configured.

  5. Provide the domain name and port of the Oracle E-Business Suite applications URL in the Find Domain and Find Port fields. For instance, if http://domain.abc.com:8080/AppsLogin is your Oracle E-Business Suite applications URL, "domain.abc.com" will be the domain field value and 8080 will be the port field value.

  6. Enter '*' in the Find in URL field. This entry means that any request to the Oracle E-Business Suite applications URL will be monitored. Alternatively, you can provide some patterns so that only those URLs that match the given pattern will be monitored. Click Next.

  7. Enter "E-Business Suite" as the Suite Type and click Finish. The newly-created suite appears on the page.

  8. Click on the created suite name.

  9. Click on the Advanced tab.

  10. Click on Enterprise Manager subtab.

  11. Click on 'n/a' for Enterprise name. In the name field, provide the name of the Oracle E-Business Suite instance that is discovered in Enterprise Manager where you want to drill down to JVMD or the Oracle E-Business Suite search user sessions pages. For example, "tst1223_Oracle E-Business Suite".

    the picture is described in the document text

Configure Protocols

  1. Navigate to Configuration > Security > Protocols.

    the picture is described in the document text

  2. Based on the Oracle E-Business Suite instance protocol (http/https), click on the respective protocol and provide/add the respective port on which Oracle E-Business Suite is up and running. You can also provide the port on which forms are running in the respective protocols.

Configure Link for RUEI to EM

In diagnosing an issue in RUEI, it is possible to drill down to JVM Diagnostics in Enterprise Manager, if the EM instance is linked to RUEI. Use these steps to link RUEI to EM:

  1. Click on Configuration > General > Advanced settings > Clickout Settings. Click on Add new clickout setting.

    the picture is described in the document text

  2. Select the version of Enterprise Manager in the clickout tool list.

    the picture is described in the document text

  3. Provide host and port values of the Enterprise Manager instance.

  4. Click on Advanced. Provide the protocol (http/https).

    the picture is described in the document text

  5. Click on Save.

  6. After linking, you should be able to see the link "Inspect in Enterprise Manager" when right-mouse-clicking on any session activity in the Browse data tab.

Analyzing a Performance Issue

  1. Log in to RUEI screen and click on Browse data tab.

    the picture is described in the document text

  2. Select the date on the left hand side to filter the data accordingly. Select E-Business (Forms) from the dropdown list below Applications tab.

  3. Click on the Session diagnostics tab below the list mentioned in the above step.

  4. Select the EBS suite name configured in section "Configure Oracle E-Business Suite in RUEI" from the Application drop down. If you are trying to search for sessions of a specific user ID, EBS responsibility ID, or ECID, select the values accordingly from the respective drop down fields. Not all values need to be selected for each dropdown list to perform the search.

  5. Click on Search.

    the picture is described in the document text

  6. Click on a session link.

    the picture is described in the document text

  7. Multiple session activities are displayed. Check the Info column. A red-colored icon identifies that the session activity ended with some error or is hanging.

    the picture is described in the document text

  8. Right click on that session activity, click on Inspect in EM 12C > Trace JVM request.

    the picture is described in the document text

  9. This will take you to EM screen where after logging in, you will be taken to JVMD screen directly based on the failed session activity's ECID.

Drilling down from RUEI to AMP

You can drill down to AMP from RUEI to monitor user sessions.

Configure Link for RUEI to drill down to AMP

  1. Navigate to Configuration > General > Advanced settings > Clickout Settings.

    Click on Add New Clickout Setting.

  2. Select E-Business Suite Diagnostics in the click out tool list.

  3. Provide host and port values of the Enterprise Manager instance.

  4. Click on Advanced and provide the protocol (http/https).

  5. Click on Save.

  6. After creating this link, you should be able to see the link Inspect in EBS Diagnostics when you right-mouse-click on any session activity in Browse data.

Monitoring User Sessions by drilling down from RUEI

Once the Inspect in EBS Diagnostics link is available, select the child menu User Search to drill down to AMP. You will see the active sessions of the Oracle E-Business Suite user like Concurrent Processing (CP), Forms, and Oracle Application Framework (OAF) sessions. You can drill down to each session to get the details.

the picture is described in the document text

Custom Metrics

You can create custom metrics in case if it is not covered by the metrics shipped out of the box.

  1. Navigate to Enterprise > Monitoring > Metric Extensions.

  2. Click Create > Metric Extension.

  3. Select Applicable to as Oracle E-Business Suite.

  4. Select Adapter as SQL.

  5. Define the query. Define columns in next step.

  6. Add any target and test. Query will hit this EBS target.

  7. Submit.

  8. Select the metric you created, Actions > Save As Deployable Draft.

  9. Select the metric you created, Actions > Publish Metric Extension.

  10. Select the metric you created, Actions > Deploy to Targets.

  11. Select any target and deploy.

For more details, see "Using Metric Extensions" in Oracle Enterprise Manager Cloud Control Administrator's Guide.

Custom Compliance Rules

Follow these steps to create custom compliance rules.

  1. Navigate to Enterprise > Compliance > Library.

  2. Create > Repository Rule.

  3. In Applicable to, select Oracle E-Business Suite.

  4. Define Query, violation condition and other details.

  5. Make sure that query has target_guid as the first column.

  6. Click Test and Submit.

  7. Now you can map this rule to a custom standard and then the custom standard to a custom framework.

    Please note System defined compliance objects are non-editable. So you cannot map any compliance object to any System defined compliance object. However you can use Create Like to create a copy of System defined object and then edit that.

  8. You can always edit a custom compliance object and map rule to standard, standard to framework.

For more details, see "Managing Compliance" in Oracle Enterprise Manager Lifecycle Management Administrator's Guide.

Administration of Oracle E-Business Suite

Starting and Stopping Services

You can start and stop the components running on each node using the Administration menu. Select Administration > Start and Stop Services from the target menu. All the application nodes will be shown with the targets running in them. You can select individual target or a node (which means you are selecting all targets running on that node) and start or stop it. ICM does not show up under a specific node because we can start and stop it from any node where it is enabled. If the Oracle E-Business Suite instance features Online Patching, only run editions targets will be shown.

Jobs will be submitted to start and stop services. The details and status of these jobs can be tracked through standard Enterprise Manager Job screens.

Note: For Oracle E-Business Suite Release 12.2, you cannot perform any action if a cutover is detected.

the picture is described in the document text

Privileges need to start and stop services

An administrator must have the EM_ALL_ADMINISTRATOR role to run the jobs to start and stop components. In addition, an administrator must have the "Start and Stop Services" privilege to start and stop services.

For more information on privileges and roles, see: link : Privileges and Roles for Managing Oracle E-Business Suite.

Credentials that must be set to start and stop services

For more information on preferred credentials, see: Setting Oracle E-Business Suite Preferred Credentials.

Manual Synchronization of Editions

If the Oracle E-Business Suite instance features online patching, it is now possible to manually synchronize the edition details from UI. This comes handy if the corrective actions fail due to some reason resulting in the system considering the wrong edition as the run edition. Navigate to Administration > Synchronize Edition Details in the target menu.

the picture is described in the document text

This will submit a job equivalent to the corrective actions. This job will gracefully exit if the editions details are already in sync or if a corrective action is in progress. The same UI will also show the details of previous attempts to manually sync the edition details.

Privilege Propagation with Administration Groups

An administration group in Enterprise Manager is a special kind of group wherein the target members can be added automatically based on certain target properties of the members. If an administration group is defined with some specifications, and if some target's properties match those specifications, then the target is automatically added to the administration group without manual intervention. When a target is added to the group, Enterprise Manager applies settings using a template collection consisting of monitoring templates, compliance standards, and so on. This completely eliminates the need for administrator intervention. Administration groups are privilege propagating. A privilege defined for an aggregate target is also set for all the member targets of that aggregate. Thus, for a target to be part of any administration group, it must be privilege propagating; otherwise the privileges cannot be set for its members. Beginning with Release 12.1.0.3.0, the following targets are privilege propagating.

For more information on administration groups in Enterprise Manager, see the Oracle Enterprise Manager Cloud Control Administrator's Guide.

Important: To use this functionality, an administrator must have both Full Any Target and Create Privilege Propagating Group target privileges to be able to create an Administration Group.

Creating an administration group in Enterprise Manager

  1. From the Enterprise Manager console, navigate to Targets.

  2. From the list, choose Groups.

  3. Select Create on the left side.

  4. Select Administration Group from the list.

  5. Define the Administration Group's target properties. Choose one or more target properties by clicking on Add in Hierarchy Levels table.

  6. Specify the target property value(s) by adding in the Hierarchy Nodes table.

  7. Click Create to save your work and create the group.

Adding targets as members of an administration group

Once an administration group is created, members can be added by specifying member properties as that are of the group. For an Oracle E-Business Suite instance, the following steps are used to set the target properties.

  1. Navigate to Targets from the Enterprise Manager console.

  2. From the list, choose Oracle E-Business Suite.

  3. Select an instance by clicking on it.

  4. From the target menu, choose Target Setup.

  5. Select Properties.

  6. Set the target property value to one of the values specified in the Administration Group page by clicking on the Edit button.

  7. To save, click OK.

  8. To view the Administration group members, go back to Targets and then Groups.

You can now see the Oracle E-Business Suite instance and members added to the administration group created earlier and also in the corresponding subgroup based on the value of target property chosen.

Example

In this example, we have created an administration group with two subgroups corresponding to Production and Development lifecycle statuses.

the picture is described in the document text

We set the Lifecycle status of an Oracle E-Business Suite instance to Production.

the picture is described in the document text

The Oracle E-Business Suite target members are added to the group automatically and to the Production level as shown in the figure below.

the picture is described in the document text