Oracle Enterprise Manager uses Dynamic Monitoring Service (DMS) metrics service to allow you to easily monitor the performance metrics and Reports Server information:
Log in to Oracle Enterprise Manager.
Navigate to the component's home page (see Section 6.3, "Viewing the Component Topology").
Examine the Reports Engines statistics table for detailed information about the engines that are running in Reports Server. This table provides information about the number of jobs that are running in that engine, process ID, running and idle time, and remaining life of the engine. The Reports Engines statistics table is shown on the Reports Server Home page and the Reports Application Home page.
Examine the Response and Load chart for an overall picture of the load.
To view scheduled jobs status:
From the Reports menu, select Reports Jobs > Jobs Page.
In the Show list, select Scheduled Jobs.
Examine the page for additional information about the scheduled jobs.
To view Oracle Reports performance:
From the Reports menu, select Monitoring > Performance Summary.
The Performance Summary page displays, showing metrics such as Average Response Time, Job Load, and Failed Jobs Ratio.
Click Show Metric Palette to display all metrics available.
Additionally, many new metrics are available in Oracle Reports 11g Release 2 (11.1.2). Refer to the online help for detailed descriptions of each of the available metrics.
When you use Oracle Enterprise Manager to monitor an instance of Oracle Reports that has been configured to use Secure Sockets Layer (SSL), some performance metrics for Oracle Reports may not display.
To correct this problem, you must allow Oracle Enterprise Manager to recognize the Certificate Authority that was used by the website to support HTTPS. You must add the Certificate of that Certificate Authority to the list of Certificate Authorities recognized by Oracle Enterprise Manager.
To configure Oracle Enterprise Manager to recognize the Certificate Authority:
Obtain the Certificate of the Web Site's Certificate Authority, as follows:
In Microsoft Internet Explorer, connect to the HTTPS URL of the application server you are attempting to monitor.
Double-click the lock icon at the bottom of the browser screen, which indicates that you have connected to a secure website.
The browser displays the Certificate dialog box, which describes the Certificate used for this website. Other browsers offer a similar mechanism to view the Certificate detail of a web Site.
Click the Certificate Path tab and select the first entry in the list of certificates.
Click View Certificate to display a second Certificate dialog box.
Click the Details tab on the Certificate window.
Click Copy to File to display the Certificate Manager Export wizard.
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 reports_certificate.cer.
Open the certificate file using your favorite text editor.
The content of the certificate file will look similar to the content shown in Example 6-2.
Update the list of Certificate Authorities, as follows:
Locate the b64InternetCertificate.txt file in the following directory:
ORACLE_INSTANCE/EMAGENT/<emagent_name>/sysman/config/b64InternetCertificate.txt
This file contains a list of Base64 Certificates.
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.
Copy the text file that contains the certificate to any location. You must specify this location when running the orapki utility.
Use the orapki utility to update the monwallet Oracle wallet by using the following command:
ORACLE_HOME/bin/orapki wallet add
-pwd <password>
-wallet ORACLE_INSTANCE/EMAGENT/<emagent_name>/sysman/config/monwallet
-trusted_cert
-cert certificate_location
When you are prompted for a password, enter the password for the monwallet wallet. The default password is welcome.
In the example, replace certificate_location with the full path to the text file that contains the certificate you saved earlier in this procedure. For example:
/dua0/oracle/reports_certificate.cer
In the ORACLE_INSTANCE/EMAGENT/emagent_name/sysman/emd/targets.xml file, for oracle_repapp, oracle_repserv targets, change http references to https and http port references to https port, as in Example 6-1.
Example 6-1 Changing HTTP References
Change:
<Property NAME="HTTPPort" VALUE="<http port>"/><Property NAME="HTTPProtocol" VALUE="http"/><Property NAME="Servlet" VALUE="http://host.domain.com:<httpport>/reports/rwservlet"/>
to the following:
<Property NAME="HTTPPort" VALUE="<https port>"/><Property NAME="HTTPProtocol" VALUE="https"/><Property NAME="Servlet" VALUE="https://host.domain.com:<httpsport>/reports/rwservlet"/>
Bounce Enterprise Manager Agent by running the following commands:
./opmnctl stopproc ias-component=emagent_name
./opmnctl startproc ias-component=emagent_name
Restart Enterprise Manager.
After you restart Oracle Enterprise Manager, it detects your addition to the list of Certificate Authorities, and you can successfully monitor the Oracle Reports metrics using the secure Oracle Enterprise Manager Console.