Oracle Applications Manager (OAM) - Introduction

 


Oracle Applications Manager (OAM) 


Oracle Applications Manager (OAM) allows administrators to manage Oracle E-Business Suite systems from an HTML console. Utilities available from OAM include Oracle Workflow Manager, Patch Wizard, and Concurrent Processing monitoring tools. 


With Oracle Applications Manager, system administrators can view information on general system activity including the statuses of the database, concurrent managers and other services, concurrent requests, and Oracle Workflow processes. OAM provides a summary of configuration changes, infrastructure usage, performance, required maintenance activities, potential security issues, status of business flows, and diagnostic test results. In addition, they can manage downtime and patching. System administrators can also start or stop services, and submit concurrent requests. 


Using Oracle Workflow Manager, administrators can control Workflow system services, such background engines, the Notification Mailer, agent listeners, queue propagation, and purging obsolete Workflow data. 

  

These Oracle Applications responsibilities are as follows: 


  • System Administrator - This responsibility has access to all functionality in OAM.

  •  

  • OAM Read Only Mode - This responsibility provides administrators with view only access to most of the data in OAM. This responsibility does not provide access to critical actions such as Stop Services and Edit Configuration Parameters. 


  • OAM Patch History – This responsibility is used to view the Applications Dashboard and Patch History pages. 


The OAM is also used in conjunction with autoconfig for making changes to the application and DB tier context files. 


OAM also provides advanced configuration wizards like SSL /SSL Accelerator conversion, Forms Listener servlet configuration and Apache Jserv load balancing. 


OAM is used to monitor of our Oracle Applications environment. AM is also used to monitor forms listener servlet if forms listener is configured to run as a servlet. Additionally OAM is also used to monitor your concurrent manager and concurrent requests. 


If generic service management is implemented, we can monitor and control our different Oracle Applications services through OAM. 


Using Oracle Workflow Manager, administrators can control Workflow system services, such background engines, the Notification Mailer, agent listeners, queue propagation, and purging obsolete Workflow data. OAM utilities are generally available from two main screens: the Applications Dashboard and Site Map. 


Oracle Applications Manager uses with Oracle Application Object Library's function security model. We can create custom responsibilities and menus to control access to specific OAM features. 


Oracle Diagnostics can also be run from OAM. Oracle Diagnostics enables testing, identifying and reporting functional problems through a web-interface. This tool allows invoking test cases interactively using custom input values or through batch mode using pre-registered input values. 


We can also extend the functionality of OAM by using custom SQL scripts to run with Oracle Applications Manager. 


OAM: 


OAM provides an HTML-based administration console (or dashboard) through which Apps administrators can perform a wide variety of tasks. While it does not yet have OEM's full library of self-fixes, script scheduling, and automated notification of trouble spots, it does bring with it many features that an Apps administrator will find useful. Further than this, however, there are certain tasks, depending on which modules that you have implemented, that you can now perform only through this interface. 


Through OAM, you can, in one simple interface, monitor the status of your applications system, including the database, the Apps tier, Concurrent Managers and Concurrent Programs, and Oracle's Workflow process. Further, you can control system processes on the Applications tier and submit concurrent requests directly through the interface. Charts and graphs provide an at-a-glance summary of the state of your system, while allowing for further drill down to detailed information. It includes diagnostic tools for many of your Applications specific components and displays for errors reported by Transaction Managers and concurrent requests. Monitoring tools include the ability to monitor currently running forms and sql queries and through these assists in helping to determine problems areas in the system and poorly running sql statements via an explain plan. 


OAM can help you to: 


Configure and administer your system: 


System Administrators can check the status of an EBS instance’s database, concurrent managers and other services, concurrent requests, and Workflow processes.

 

  • Diagnose and correct problems 

  • Manage patches – available free from OAM 

  • Monitor and tune performance 

  • Monitor system security 

  • You can also manage initialization parameters and profile options 

  • Recommended tool for making changes to Auto Config 


OAM utilities are generally available from two main screens:  


The Applications Dashboard and Site Map 


Oracle Applications Manager Dashboard 


The Applications Dashboard provides an overview of the key features of an Oracle E-Business Suite installation, including summaries of current status, performance, critical activities, diagnostics, business flows, and security.  

Oracle Applications Manager Sitemap 


Oracle E-Business Suite system is offered by the Site Map, which provides easy access to the numerous features and options that exist in the areas of administration, monitoring, maintenance, and diagnostics and repair. 


Administration 


Oracle Applications Manager provides a comprehensive system configuration editor, for use in conjunction with the Auto Config configuration management tool. Previous configuration settings can easily be compared with the current settings, allowing changed settings to be identified and rolled back as necessary. 


OAM helps you track configuration changes, such as recently altered site-level profile option settings.  


It can also helps you detect potential configuration problems, such as database initialization parameters that do not meet Oracle requirements or recommendations. 

 

OAM can be used to configure and control critical application tier services such as concurrent processing, Forms listeners, and Web servers. For example, you can monitor and administer concurrent requests, and easily analyze the concurrent request workload to make informed configuration changes for concurrent processing. monitor and analyze Oracle Workflow system activity, suspend and resume processes, retry activities that end in error. 


Oracle Applications Manager enables you to manage all aspects of licensing your products and related features. 


You can extend Oracle Applications Manager using your own custom SQL scripts. Not only can SQL scripts be organized and accessed from within the OAM console, but drilldowns can be enabled from script output to standard Oracle Applications Manager interfaces.  


For example, if you obtain concurrent request IDs from an SQL script, you can then drill down into the standard Oracle Applications Manager interface to obtain details of the concurrent requests. 


Monitoring 


Oracle Applications Manager provides extensive monitoring features for Oracle E-Business Suite.  


Charts and graphs provide high-level summaries, and you can drill down for more detailed information as required. 


The Monitoring tab provides key performance metrics related to online, batch, and workflow activity. Additionally, system administrators can now subscribe to receive automated alerts when concurrent requests run longer or wait longer than specified thresholds. 


Monitoring support is provided for application tier services such as concurrent managers and web services. for currently running processes such as forms or concurrent requests, you can examine both application tier and database session details, right down to the currently executing SQL. 


OAM can alert you when certain errors occur within the EBS system, and will provide detailed context information to help in diagnosing those errors. Information from system components, including performance details, availability, configuration, diagnostic data, and security concerns can all be presented in the context of affected business flows, so that you can better understand any impact on your business. 


Maintenance 


You can easily determine which patches have been applied to a system, including the individual patches included in mini-packs, maintenance packs, and merged patches.  

OAM also enables you to examine the patched files on a system, and identify all the patches that altered a given file. For each patch applied, you can see the actions taken by each patch driver. 


The Patch Wizard tool built into OAM can recommend patches for your Oracle EBS system. The wizard takes patch data downloaded from Oracle, analyzes that data against the Oracle EBS system, and recommends patches based on criteria you specify. The wizard can also analyze individual patches, identify any prerequisites missing on the system, and show the impact that the patches would have on the system in terms of affected applications, files, and other areas. Additionally, the wizard can download multiple patches from Oracle and merge them into a single patch. 


Administrators can use the manage downtime feature to schedule downtimes. When a downtime is scheduled, a message on the home page notifies users of the period when the system will not be available. The user has to log in, or return to the Home Page to see this message. If the downtime is in progress, an appropriate warning page will replace the login page. 


During the scheduled downtime period, administrators with suitable database privileges are able to log into OAM to monitor the progress of Auto Patch and other Applications DBA (AD) utilities: access to other parts of Oracle EBS is not allowed. 


Diagnostics and Repair 


OAM for Oracle EBS Release 12 provides troubleshooting wizards that automate complex recovery steps. Tools such as Concurrent Manager Recovery help you diagnose problems and take corrective action from the same screen. The Service Infrastructure Troubleshooting wizard ensures that the Generic Service Management (GSM) infrastructure is running normally, and if not, guides the administrator through the steps needed to bring GSM back up. 


Support Cart 


The OAM Support Cart automates the collection of detailed node-specific information that can be sent to Oracle Support to assist with problem diagnosis. 


The information collected includes details of products installed, patches applied, database version, current database parameters, and system topology. Other pages from OAM can be added to the Support Cart if desired. 

 

Comments

Popular posts from this blog

Oracle Database Server Architecture: Overview

Oracle E-Business Suite (EBS) - Introduction

Why enterprises must not ignore Azure DevOps Server