Have you tried using Oracle AMP for EBS Suite?

The Oracle Application Management Pack for Oracle E-Business Suite extends Oracle Enterprise Manager 12c Cloud Control to help monitor and manage Oracle E-Business Suite systems more effectively. The pack integrates Oracle Applications Manager with Cloud Control to provide a consolidated, end-to-end Oracle E-Business Suite management solution. The pack can be used to manage both Oracle E-Business Suite Release 11i systems and Release 12 systems.

This document describes the features and usage of this new pack for Cloud Control. Oracle Enterprise Manager Cloud Control provides a complete view of your enterprise so that you can manage all of your Oracle E-Business Suite systems from a single console. This pack provides new pages within Cloud Control that help you to monitor the performance, availability and configuration changes of your Oracle E-Business Suite system and also help you to provision your Oracle E-Business Suite applications. You can take advantage of advanced Cloud Control features such as the provisioning framework.

 
 

 Enterprise Manager itself allows you to monitor multiple Oracle E-Business systems (both Release 11i and Release 12) from the outside.

The Oracle Application Management Pack for Oracle E-Business Suite provides advanced features to monitor and manage Oracle E-Business Suite Release 12 systems as well as Release 11i systems that meet a standard interoperability patch level. These advanced features include Oracle E-Business Suite provisioning, Application Service Level Management, extended performance metrics, and links from Cloud Control to Oracle Applications Manager.

System Management for Oracle E-Business Suite
Oracle Application Management Pack for Oracle E-Business Suite extends Enterprise Manager Cloud Control to monitor and manage Oracle E-Business Suite systems. This new release of this management pack offers the following key capabilities:

General:

• Oracle Enterprise Manager 12c Base Platform uptake: All components of the management suite are certified with Oracle Enterprise Manager 12c Cloud Control.
  

Client System Analyzer

 

Issues with Performance can arise if your computer is not optimally configured. You can enable the diagnosis of such problems, the Client System Analyzer allows you to collect client configuration data about the hardware and software of your computer.

How to check Client System Analyzer:
From Forms-based applications, navigate to Help > Diagnostics Menu > Client System Analyzer.

The Client System Analyzer runs on demand when you launch it. However, before data can be collected, you may be prompted to do the following:

• Accept the Client System Analyzer applet.
  
• Download and install a compatible Java Virtual Machine.
  

Viewing Data Collected by the Client System Analyzer

The Client System Analyzer collects information about a your computer’s configuration, such as:

• Hard drive size
  
• CPU speed
  
• Memory
  
• Installed software
  

It also performs some network performance measurements.

Every time you run the Client System Analyzer, the results are saved for future reference. You can work with the data through Oracle Applications Manager; go to Site Map > Diagnostics and Repair (tab) > Client Configurations. In addition, you can work with the data through Oracle Enterprise Manager 10g Grid Control. See Section 3 of this document for the relevant configuration procedure.

Data Collection Details

The default set of collected data is organized into categories as follows.

• Client Identification Information
  
  • OS user name
    
  • Host name
    
  • Domain
    
  • IP address
    
• Network Configuration and Performance Information
  
  • Latency
    
  • Bandwidth
    
  • Subnet
    
• Browser and Java Information
  
  • Browser type
    
  • JVM vendor
    
  • JVM version
    
  • Proxy information
    
• Hardware Information
  
• CPU Information
  
• OS Information
  
  • OS name
    
  • OS vendor
    
  • Base version
    
  • Update level
    
• OS Components
  
• OS Properties
  
• OS-Registered Software
  

Configuring Oracle Enterprise Manager 10g Grid Control to Collect E-Business Suite Client Configurations

Set up Enterprise Manager to retrieve the client configuration data from the Web server and upload it to the Oracle Management Repository. When the data has been moved to the Oracle Management Repository, you can use Enterprise Manager to view it. This procedure assumes that Enterprise Manager 10g Grid Control has been installed and configured in your enterprise, and that a Management Agent has been installed and configured on each Oracle Applications Web Server host.

Required Patch Level
Oracle Enterprise Manager 10g Grid Control release 10.1.0.3 or later is required.

Procedure

Follow the steps below:

1. In Enterprise Manager, click Management System, then click Agents. The Agents Home Page displays.

2. In the Agents table, click the link for a Management Agent that has read/write access to the Web server directory to which client configuration data is being written. The person who configures the client configuration collection applet for your site chooses the directory into which the applet writes client configurations.

The Agent Home Page for the Management Agent displays.

3. In the Add list for the Monitored Targets table, choose CSA Collector, then click Go.

The Add CSA Collector page displays.

4. On the Add CSA Collector page, click Help for more information about configuring Enterprise Manager to collect and upload client configuration data to the Management Repository.

Configuration Manager

The Oracle Configuration Manager (OCM) is a tool to proactively monitor your Oracle environment to provide this information to Global Customer Services (GSC formerly known as OSS). It uploads this information to Oracle Customer Configuration Repository and replicates this to My Oracle Support so that you can view it and it informs you about alerts and lets you perform health checks against your Oracle database. The Configuration Manager a different product from Oracle Enterprise Manager Agent.

• The ability to define configurations and organize projects

• A view of System details and changes

• Create, track, and status Service Requests

• Advanced Knowledge Management capabilities

• Proactive problem avoidance with Health Checks

• Proactive Product and Security Alerts

• Service Request Priority Handling

What is collected

• Captures information about:

– Host

– Oracle Software and Patches

• E-Business Suite Patches

• Database and iAS Patches

– Third party software inventory

• Access to this data is limited by:

– Hardware

– System Software

– Oracle Product Information

Configurations Data Security and Privacy

• Customers see the same data as Oracle

• Primary access is by Oracle Product Support

• Data is used by Product Support to improve the customer level of service

• Data collected is hardware, system software, and Oracle product information

• Data does not include business transactions, passwords, or control sensitive information

Apache Server Monitoring and Troubleshooting

Monitoring the Web Node involves monitoring the Apache server provided with iAS and monitoring the Java servlets. Troubleshooting tasks consist of configuration validation steps and log file research.

Apache Log Files

When troubleshooting Apache, the Applications DBA should monitor the various log files for Apache and the JServs. The $APACHE_TOP/Apache/logs directory contains files such as error_log and error_log_pls. The JServ log files are located in the $APACHE_TOP/Apache/Jserv/logs and $APACHE_TOP/ Apache/Jserv/logs/jvm directories. Apache and JServ log files should be monitored for potential error messages.

To enable additional logging for Apache when you’re troubleshooting, you can modify the level of debug messaging in the jserv.log file. The location of the jserv.log file is defined by the log.file parameter in the jserv.properties file. These are the steps for enabling the additional logging:

1. Set LogLevel to DEBUG in $APACHE_TOP/Apache/conf/httpd.conf.
2. Set ApJservLogLevel to DEBUG in $APACHE_TOP/Jserv/etc/jserv.conf.
3. Make the following changes to $APACHE_TOP/Jserv/etc/jserv.properties:
                             • Add wrapper.bin.parameters=-Djbo.debugoutput=console
                             • Set log=true
                             • Set log.channel=true
                             • Set log.channel.info=true
                             • Set log.channel.debug=true

Once these changes are made, review the log files for information to assist with troubleshooting the underlying issue. Use the information from the log files to search MetaLink for issue resolution. If MetaLink does not provide you with solutions, you should open an SR with Oracle Support.
Apache Availability

cd $COMMON_TOP/admin/scripts/

$ adapcctl.sh status

adapcctl.sh version 115.54

Apache Web Server Listener :httpd ( pid 12459 ) is running.
Apache Web Server Listener (PLSQL) :httpd ( pid 12558 ) is running.

adapcctl.sh: exiting with status 0

 How to Stop and Start (Bounce) the Apache Server

$ adapcctl.sh stop

adapcctl.sh version 115.54

Apache Web Server Listener :httpd ( pid 12459 ) is running.
Stopping Apache Web Server Listener (dedicated HTTP) …
Apache Web Server Listener (PLSQL) :httpd ( pid 12558 ) is running.
Stopping Apache Web Server Listener (dedicated PLSQL) …

adapcctl.sh: exiting with status 0

Wait for 30 seconds

$ ps -ef|grep http |grep applvis
 applvis 18735 12076  1 16:24:05 pts/1     0:00 grep http

$ adapcctl.sh start

adapcctl.sh version 115.54

Apache Web Server Listener is not running.
Starting Apache Web Server Listener (dedicated HTTP) …
Apache Web Server Listener (PLSQL) is not running.
Starting Apache Web Server Listener (dedicated PLSQL) …

adapcctl.sh: exiting with status 0

$ ps -ef|grep http |grep applvis
 applvis 18842 18809  0 16:24:16 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 19032 12076  1 16:26:15 pts/1     0:00 grep http
 applvis 18876 18809  0 16:24:49 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18880 18809  0 16:24:50 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18929 18899  0 16:24:57 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18919 18899  0 16:24:56 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18927 18899  0 16:24:57 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18881 18809  0 16:24:50 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18926 18899  0 16:24:57 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18809     1  0 16:24:15 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18825 18809  0 16:24:15 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18841 18809  0 16:24:16 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18899     1  0 16:24:53 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18844 18809  0 16:24:16 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18826 18809  0 16:24:15 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18843 18809  0 16:24:16 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18925 18899  0 16:24:57 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18845 18809  0 16:24:16 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18917 18899  0 16:24:55 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle
 applvis 18928 18899  0 16:24:57 ?         0:00 /d01/oracle/vis10ora/iAS/Apache/Apache/bin/httpd -d /d01/oracle