You are on page 1of 36

OAM Usage and Navigation Page 1 of 36

Oracle Application Manager (OAM)


Use, Navigate, and Understand
December 2005

This article is written to assist in using, understanding, and to determine what technology is being manipulated through OAM. It will be
constantly updated with the latest solutions to OAM issues from Core OAM Specialists. Currently the latest release is OAM 2.3.1, the
information in this note is based on the documentation in Metalink Note: 258330.1.

This document contains the following sections:

 OAM Dashboard

 Setup ICON: Dashboard Collection, Metalink Credentials, Business Flows, and Knowledge Base

 Diagnostics and Repair Launch

 Manage Security Options

 SiteMap: System Configuration, AutoConfig, Manage Custom Parameters,Configuration Wizards

 SiteMap: Administration > Application Services, Generic Services, Status Overview, Activity Monitors

 SiteMap: Administration > Concurrent Requests, Submit New, Schedule Requests

 SiteMap: Administration > Others, OAM Log, USER|SUPPORT|DEV Mode, Support Cart, Applications Signature

 SiteMap: Monitoring > Performance, Jserv Usage, Forms Session Monitoring

 SiteMap: Maintenance > Patching and Utilities, Download and Analyze, Advisor and Impact Analysis

 SiteMap: Maintenance > Manage Downtime Schedules, Apache Restricted Mode

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 2 of 36

 Requirements for OAM

OAM Dashboard

Application Dashboard > Overview

 Applications System Status


Lists the Hosts/Nodes of the Application Instance that are registered in the FND_NODES table.
Host Status reflects the value of the Node_Mode from FND_NODES table.
Components of the instance ( admin, database, concurrent manager, forms, web ) are represented here and correspond to
the Support_<comp> column in the FND_NODES table.

Hint: If there are any Red Components or Xs, issue goes to CCMGR team to investigate GSM, FND_NODES and
FND_CONCURRENT_QUEUES tables.

 Configuration Changes (last 24 hours)


Reflects changes within the last 24 hours: Patches, Profile Option Changes & Context File.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 3 of 36

 System Alerts
Search Alerts, Search Occurrences, Setup Notifications

Alerts are classified as Security Alerts (ie: Form, Function, Service, Program)
Warnings are classified as System Generated Alerts (runaway process, failures)
Navigation: Click on any option in this area > Notification Setup > Create
or Sitemap > Monitoring > Current Activity > System Alerts > Notification > Setup

Hint: Periodically purge the alert information by running the "Purge Debug Log and System Alerts" program. Before
running this program, Close all alerts by clicking on any option in this area > select system alert and change state
from Open to Close.

 Web Components Status


Reflects the status for PL/SQL Agent, Servlet Agent, JSP Agent, Discoverer, PHP, TCF.
Can be checked retrieving the value of the %AGENT% profile option in the FND_PROFILE_OPTIONS and
FND_PROFILE_OPTION_VALUES tables.

The status of the Web Components will show "Up" if the following URLs execute successfully:

PL/SQL Agent:

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 4 of 36

http://hostname.domain:port/pls/PTCH/fnd_web.ping

Servlet Agent:
http://hostname.domain:port/oa_servlets/oracle.apps.fnd.test.HelloWorldServlet

TCF:
http://hostname.domain:port/oa_servlets/oracle.apps.fnd.tcf.SocketServer

JSP Agent:
http://hostname.domain:port/OA_HTML/jsp/fnd/fndping.jsp?dbc=<database id>

Substitute the <database_id> with the value from the following sql statement:
SQL> select lower(host_name)||'_'||lower(instance_name)
from v$instance;

JTF:
http://hostname.domain:port/OA_HTML/jtflogin.jsp

Personal Home Page:


http://hostname.domain:port/OA_HTML/US/ICXINDEX.htm

Hint: If all URL test pass successfully but still show down or Red Xs in OAM,

refresh Apache Cache by shutting down the services

$ cd $OA_HTML

$ mv _pages backup_pages

Restart the services

 User Initiated Alerts


Same as Security / System Alerts but is user defined through
Application Dashboard Setup Icon > Dashboard Setup > Metric Setup >
Enable Alert > Update Specific Metric > Set Threshold

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 5 of 36

Setup ICON

 Dashboard Collection Metrics

 All components seen in the Application Dashboard are collected from metrics that are monitored and updated by the
background concurrent program "OAM Application Dashboard Collection". To manipulate the frequency Navigate:
Setup Icon (upper right hand corner)/Dashboard Setup > Update

Default Metric Collection > OAM Dashboard Collection Interval is every 30 minutes.

Hint: FNDOAMCOL is a JAVA Concurrent Program, it depends on the AF% environment variables settings
to use the JDK 1.3 or 1.4. To test if the is a problem is with FNDOAMCOL only or all Java Concurrent
Programs, run the "CP JAVA Regression Test" if that fails too, issue goes to CPREQ.

If issue with only FNDOAMCOL: There is a Dashboard Collection Wizard under Diagnostics that can be run
to determine a problem. Navigation: Sitemap > Diagnostics and Repair > Troubleshooting Wizard >
Dashboard Collection Signature compare versions to ARU.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 6 of 36

 Metalink Credentials
Metalink Credentials > Supply Metalink Userid, Password, Email Address
Needed for OAM to interface with Metalink. The Metalink information supplied here is stored in the
FND_OAM_METALINK_CRED table.

.
Additional Requirements: Site Level %WEB_PROXY% Profile Options Settings must be provided to
establish authentication with the proxy server. These settings are stored in the FND_PROFILE_OPTIONS and
FND_PROFILE_OPTION_VALUES tables.

Errors during the setup of Web_Proxy profile options stay with OAM, if errors persists see Bug: 4113087.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 7 of 36

 Business Flows

They help to understand the effects that system component issues and availability have on your
business. You can monitor system components within the context of the business flows that those
components enable. These components include WorkFlow item types, concurrent programs,
forms, Oracle Applications Framework functions, and services.

Navigation: Business Flows > Create


Refresh BusinessFlows by running OAM:KBF Metrics Rollup Program, NEXT through all
scheduling wizard steps.

If the Concurrent Program OAM:KBF Metrics Rollup "FNDOAMKBFRU" fails, it is also a


JAVA Concurrent Program, determine if it is the only JAVA Program failing first, if so then it
stays with OAM, investigate the Java Error error by checking JDK 1.3 or 1.4 requirements and
research error.

 Knowledge Base
Collects current Metalink documents on the preseeded Category Types.
Load Docs by running OAM: Knowledge Base Catalog Refresher Program.
It searches Metalink for documents depending on Category specified.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 8 of 36

Refresh Knowledge Base by invoking the JAVA Concurrent Program "FNDOAMKBCRP".


Determine if it is the only JAVA Program failing first, if so then it stays with OAM, investigate
the Java Error error by checking JDK 1.3 or 1.4 requirements and research error.

Diagnostics and Repair Launch

 Diagnostic Dashboard > Test Statistics


Launch Diagnostics uses the code from Oracle Diagnostics Pack from Note: 262006.1

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 9 of 36

Hint: To test Diagnostics outside of OAM, supply the following in browser


http://hostname.domain:port/OA_HTML/jtfqalgn.htm
Supply "HTML Platform" as the Tag > GO.

Each product area should support it's diagnostic report. It is an OAM issue only if all Diagnostics are

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 10 of 36

running successful from jtfqalgn.htm and not running in OAM.

 Troubleshooting Wizards from Diagnostics

Additional diagnostics scripts for major components such as Concurrent Managers, FNDSM, OAM
Generic Collection Service and Forms Monitoring, CP Signature, Dashboard Collection, Stat Pack
Report. Wizard gives Profile Options, pls files versions, package and package body information, class

file used, and tables that are updated.

Manage Security

 Manage Security Options

OAM > Application Dashboard > Security > Manage Security Options > Enable Restricted Access > Run
Wizard > Register

Enables SQL*Net access to the database by restricted clients.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 11 of 36

Under the default view will list the current hosts that have sqlnet access to the database. The same hosts are
registered in the FND_NODES table. Enabling restricted access gives a standalone server or client pc access to the
database.

Requirements after adding hosts: Run AutoConfig on 9i ORACLE_HOME/appsutil/admin/scripts and Bounce the
database. The changes will get incorporated into the 9i $TNS_ADMIN/sqlnet.ora file, which then needs adds a
parameter

tcp.validnode_checking = yes
tcp.invited_nodes=(SYJONES-PC.US.ORACLE.COM, SYSADMIN-SUN.us.oracle.com)

Errors during this setup stay with OAM and steps can be checked against Note: 291897.1.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 12 of 36

SiteMap > System Configuration

 AutoConfig
Lists the current xml files for the instance. Each xml file corresponds to the
$APPL_TOP/admin/<context>_<host>.xml.

Updates in OAM only writes to the xml file, but the environment change is not populated until
$APPLCSF/scripts/adautocfg.sh is run.

AutoConfig > Context Files are retained FND_OAM_CONTEXT_FILES.


There is a Context File present for each tier.
Ex.
Applications Context File - /u01/oracle/prodappl/admin/PROD_sysadmin-sun.xml
Database Context File - /u01/oracle/proddb/9.2.0/appsutil/PROD_sysadmin-sun.xml
2nd Node Application Context File - /u00/oracle/prodappl/admin/PROD_syjones- sun.xml

In the Edit Parameters Function, OAM uses the Web Report Review Agent (FNDWRR.exe) to write back to
file server after an update is made. In a Multiple Node environment FNDWRR.exe errors are common.

Hint: Make sure Patch is 3042652 is applied, if so and problem still exists, See Bugs: 4297933 and 4170879.

 Manage Custom Parameters

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 13 of 36

The Custom Environment Variable is added to the Context File and the File System is updated creating the
new PROD_TOP the next time AutoConfig is run.

1) Manage Custom Parameters > Add


2) Choose Application Tier or Database Tier > Next
3) Create custom variable name – prefixed with “c_”
4) Give environment value and fill out the rest > Next
5) Confirmation >Next and Save

 Configuration Wizard

Invokes the launch of Advance Configuration steps such as Enabling HTTP Load Balancing, SSL
Configuration, Forms Listener Servlet, and Apache Load Balancing.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 14 of 36

Hint: Each Advanced Configuration task requires the OAM Generic Collection Service (OAMGCS) to be
enabled on all nodes in the environment. The OAMGCS manager are dependent on GSM/FNDSM to be
running on all nodes first. An issue with starting the OAMGCS can be worked by OAM team only after
CP/GSM teams has resolved FNDSM to run all nodes.

To see if what managers are running Navigate: SiteMap > Application Services > Generic Services > View All

If there are errors associated only to starting the OAMGCS, issue stays in OAM team and the "Verify
Configuration Wizard Infrastructure Wizard" can be run.

SiteMap > Application Services > Generic Services

 View All

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 15 of 36

Reflects a grouping for all the Concurrent Managers in the environment.


***In this frame, Internal Manager capability to Stop, Abort or Verify.
Request Processing Managers - Managers that process requests
Transaction Managers - Managers for specific Transactions (INV, PO, RCTM)

Hint: All issues reported here ( Red Xs) are CCMGR/GSM issue except specific OAM usage problems. This
information is stored in the FND_CONCURRENT_QUEUES table.

 Activity Monitors

Activity Monitors breaks down Database Sessions: Logins, Forms, Services, Concurrent Requests: Running,
pending, waiting on lock, inactive.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 16 of 36

Hint: The $DISPLAY setting is a requirement for OAM, several issues arise when the $DISPLAY is not set
correctly on server and xhost not enabled by root prior to starting the services.

Key error words are: XServer, Xlib, BIB-7000, MIT-MAGIC-COOKIE - all lead to a DISPLAY problem.
Issue stays in OAM group. Use steps from Note: 351839.1

See Notes: 181244.1 and 210323.1 if customer is using VNC, Xvfb, Xseed

SiteMap > Concurrent Requests

 Submit New
Submit New uses the same Request Submit and Monitor Menu Functions as SSWA

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 17 of 36

Pending: queries on FND_CONCURRENT_REQUESTS table Phase_code='P'


Running: queries on FND_CONCURRENT_REQUEST PHASE_CODE='R'
Completed Last Hour: queries on FND_CONCURRENT_REQUESTS table

Hint: Test all issues outside of OAM, from the System Administration Web Application Responsibility >
Monitor and Schedule functions first, if unable to submit request there, issue goes to CCREQ. If able to submit
there and not in OAM then investigate class files.

SiteMap > Others > Application Manager Log

 Oracle Applications Manager Log


OAM log modes are USER|SUPPORT|DEV.
Weboam log is stored in $APPLRGF/oam location on the Web Server (middle tier).
$APPLRGF location is set in the jserv.properties file and can be changed.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 18 of 36

Hint: DEV mode should be used as preliminary troubleshooting step, see Note: 268837.1 for manual steps to
turn on logging.

For all OAM Login Issues: On the Web/Apache Tier get the following files for configuration settings and
errors:

$APACHE_TOP/Jserv/etc/jserv.properties
$APACHE_TOP/Jserv/etc/zone.properties
$APACHE_TOP/Jserv/etc/jserv.conf
$APACHE_TOP/Jserv/logs/mod_jserv.log
$APACHE_TOP/Apache/logs/error_log
$APACHE_TOP/Apache/logs/access_log

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 19 of 36

 Adding to Support Cart


Each frame in OAM has a "Add to Support Cart" button at the bottom right corner.

This allows customer to capture the error as a screen print in an xml file format which can then be uploaded to
tar.

Give description of Pages to Save > OK


Associate saved pages to Tar# and give Details > Update
Save Cart downloads compressed pages in the support.zip file
To Desktop > Upload to tar through Metalink.

 Applications Signature

Navigation: Application Signature > Collect. This area gives Patche Information - all Application patches
applied.
Database version - database version details, Database Parameters - database configuration parameters (settings
from init.ora).

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 20 of 36

Product Information - current product information (ie: 11i.AD.1.2), Topology report - topology information
from application system

SiteMap > Monitoring

 Performance

SQL Activity: SQL_Hash, Physical Reads, Logical Reads, Total Sorts, Execs, Loads

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 21 of 36

Hint: Any error when run the Execution Plan on a SQL_HASH should be addressed by OAM team.

Make sure customer has applied Patch 3882116 or 4090504 "REHOST ORACLE 9iR2 JDBC DRIVERS
(v9.2.0.5) FOR USE WITH ORACLE APPLICATIONS 11i".

If still errors within OAM, see Bug: 4329362

 Jserv Usage
Jserv Usage: is beneficial to Web Server analysis for AM Pool, JVM Memory Consumption

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 22 of 36

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 23 of 36

Hint: Typically this is an informational area driven by the Jserv setup, any issues here are referred to
WEBSRV team.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 24 of 36

 Forms Session Monitoring


Forms Monitoring is setup through OAM and is used to Audit Forms usage.

Session Details reveals Database Session Information


Session Summary: Username, Formname, Responsibility
Instance Attribute: Logon Time, Serial #, OS PID, Status
Client Attributes: OS User, Machine, Process, Terminal
Application Attributes: Module, Module Hash, Action
Session Wait Information: Event, Wait time, Timeouts
Tracing Options: Normal, Trace with waits, Trace with waits and binds
***Forms Session can be Terminated from this area.

Hint: To use the Forms Management feature, complete the following steps:

1) Ensure that your installation includes Oracle Forms Patchset 11 or higher.


2) Ensure that FNDFS is setup and running on the Forms node.
3) Set FORMS60_OAM_FRD to "ON" in OAM and run AutoConfig.
4) Set profile option "'Sign-on: Audit Level" to "FORM".
5) Start OAM Generic Collection Service from OAM.
6) Start a Forms listener service instance from OAM
- Navigate to Site Map > Status Overview > Application Services > Generic Service >Forms Listener > click
"Edit" button.
- Check the "Enabled" check box.

 Custom Reporting Utilities

SQL Extension
Custom scripts are automatically discovered by OAM and available to run from the SQL Extensions page.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 25 of 36

Hint:
1) Create a new SQL script. Multiple SQL statements are allowed within the same file.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 26 of 36

2) Create a directory called /custom/sql for your custom SQL files under <APPL_TOP>/admin on Web Tier.
3) Copy your SQL files to <APPL_TOP>/admin/custom/sql directory.
4) Now log in to OAM and navigate to Site Map > SQL Extensions.
5) The discovered SQL files will be under the "Custom Extension" group.
6) After the files are discovered, you can customize the grouping, protection, and execution method of these
scripts.

Any error in this section stays with the OAM team.

SiteMap > Maintenance

 Patching and Utilities

Applied Patches queries on the following AD Tables:


AD_PATCH_DRIVERSAD_PATCH_RUNS , AD_PATCH_DRIVER_LANGS, AD_BUGS,
AD_PATCHED_APPLIED.
Querying for a specific patch will return all patches that contain that specific patch.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 27 of 36

Hint: Patches applied to an instance before OAM implementation will not show in OAM UI.

AD_BUGS is a lookup table. When a patch number is listed in AD_BUGS, it means a patch that was applied
referenced
that bug fix. Normally any bug fix referenced by a patch is also applied by that patch. However, there are
corner cases where this is not true. AD_APPLIED_PATCHES lists the actual patches successfully applied
using AutoPatch.

Patch Detail gives Timing Report, Files Copied, Bug Fixes, Action Summary

 Patch Wizard Tasks

Allows OAM to interrogate patches before applying them, also patches are downloaded to the CCM server by
interface with Metalink and can be merged into a unified driver.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 28 of 36

Preferences: Defining a Staging Area on the Concurrent Manager Tier


Ie: /u01/oracle/patches/oampatchwiz
Specify Merging Options: One, Two or Multiple Patches
NLS_LANG is used as the Default Download, choose additional LANGS
For Multi-Lang environments.
***Multi-Platform downloads cannot be done.

Creating Patch Filter to stipulate the analysis run can be done for
New Code, Recommended Patches or Create Custom Filter

 InfoBundle11i.zip
Prior to running a Download or Analyze on specific patches OAM requires the Meta Data information of all patches
or a Patch Manifest to be uploaded to the CCM server. The Manifest is called the "InfoBundle11i.zip" it is refreshed
in Metalink daily with new patch information and prerequisite patch information.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 29 of 36

Hint: The InfoBundle11i.zip must stay in a .zip format in the staging area.

ie:
/u01/oracle/patches/oampatchwiz

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 30 of 36

$ ls -lrt InfoBundle*
-rw-r--r-- 1 appl1159 dba 31900208 Nov 15 16:53 InfoBundle11i.zip

 Analyzing a Specific Patch

Patch analysis runs a JAVA Concurrent Program which is actually a Request_Set. The Parent Request is

Hint: These are where the Impact Analysis and Analyze information get generated. If request complete in
Error or Warning this is an OAM issue regardless of what the error is.

Make sure patch 4443965 "Integrate Recommended Patch List data into Patch Wizard (11.5.10 or OAM.H)" or
See Bugs: 3158506, 3897709, 3584462

 Downloading Patches
Downloading and Merging patches submits a request set for Download and saves .zip files to the Staging Areas

-rw-r--r-- 1 appl1159 dba 2806664 Dec 12 22:16 p3130740_11i_GENERIC.zip


-rw-r--r-- 1 appl1159 dba 1008512 Dec 12 22:16 p3410599_11i_GENERIC.zip

A Merged Directory is created with the unified driver file to be used by adpatch.

drwxr-xr-x 2 appl1159 dba 512 Dec 12 22:22 merged_20050112222217

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 31 of 36

-rw-r--r-- 1 appl1159 dba 135 Dec12 22:22 merged_2005011222225.lst


drwxr-xr-x 5 appl1159 dba 512 Dec12 22:22 mrgsrc_20050112222217
drwxr-x--- 10 appl1159 dba 512 Dec 12 22:22 merged_2005011222225_US
-rw-r--r-- 1 appl1159 dba 432313 Dec12 22:22 merged_2005011222225.log

Driver merged_2005011222225_US/u_merged_2005011222225_US.drv
Located under merge director with suffix <Default Lang>

 Impact Analysis

Manage Downtime Schedules

 Downtime Schedules

Downtime schedules sets a pre-defined time to notify users of when the system will not be available for access.

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 32 of 36

 Start Apache in Restricted Mode for OAM access

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 33 of 36

In OAM Restricted Mode, you can now access utilities on the Maintenance tab of the
Site Map. You can monitor progress of your patching utilities here. After patch completion, bring down the
Apache Server in Restricted Mode using the script 'adaprstctl stop'. If the patch requires AutoConfig be run,
run AutoConfig.
Start the system using the script 'adstrtal.sh'.. Apache and items such as concurrent managers, forms will be
started.

Hint: How to Implement Restricted Mode

1) Shutdown the services with the adstpall.sh

2) Enabled Maintenance Mode in ADADMIN

3) Unlock the ad_monitor/lizard user in sqlplus and change password

4) Restart the Apache Server in Restricted Mode using the script 'adaprstctl'.

ie: $APPLCSF/admin/scripts/<context name>/ adaprstctl.sh start

5) Launch OAM Restricted Mode using the OAM Restricted Mode

URL: http://[host]:[port]/servlets/weboamLogin/oam/oamLogin

Login as ad_monitor with the new password.

Requirements for OAM

 Apache 1.0.2.2.2 or Greater


 Self Service Framework 5.7 or Greater
 JDK 1.3 or Greater - Note: 130091.1
 OAM.H uses SSO AppsLocalLogin.jsp, customer must be able to access PHP before investigating OAM Login

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 34 of 36

 Valid Account with the System Administration (SSWA) responsibility


 OAM parameters setting in $IAS_ORACLE_HOME/Apache/Jserv/etc/ zone.properties file

# ----- Oracle Applications Manager (OAM) ------


servlet.weboam.code=oracle.apps.fnd.oam.servlet.ui.OAMServlet
servlet.weboamLocal.code=oracle.apps.fnd.oam.servlet.ui.OAMServlet

# Manadatory Cabo settings; do not modify these!


servlet.weboam.initArgs=oracle.cabo.servlet.pageBroker=oracle.apps.fnd.oam.servlet.ui.oamUIXPageBroker
servlet.weboam.initArgs=oracle.cabo.servlet.loginPage=oam/oamLogin
servlet.weboam.initArgs=oracle.cabo.servlet.loggedInKey=oracle.apps.oam.oamUserData
servlet.weboam.initArgs=oracle.apps.oam.servletName=weboam

servlet.weboamLocal.initArgs=oracle.cabo.servlet.pageBroker=oracle.apps.fnd.oam.servlet.ui.oamUIXPageBroker
servlet.weboamLocal.initArgs=oracle.cabo.servlet.loginPage=oam/oamLogin
servlet.weboamLocal.initArgs=oracle.cabo.servlet.loggedInKey=oracle.apps.oam.oamUserData
servlet.weboamLocal.initArgs=oracle.apps.oam.servletName=weboamLocal
# End of mandatory settings.
servlet.weboam.initArgs=oracle.cabo.servlet.xml.UIXPATH=/u00/oracle/prodcomn/html
servlet.weboam.initArgs=oracle.apps.oam.logger.path=/u00/oracle/prodcomn/html/oam
servlet.weboam.initArgs=oracle.apps.oam.logger.filename=weboam.log

servlet.weboamLocal.initArgs=oracle.cabo.servlet.xml.UIXPATH=/u00/oracle/prodcomn/html
servlet.weboamLocal.initArgs=oracle.apps.oam.logger.path=/u00/oracle/prodcomn/html/oam
servlet.weboamLocal.initArgs=oracle.apps.oam.logger.filename=weboamLocal.log
#
# Possible logger levels: USER, SUPPORT, DEV. Default is USER
#servlet.weboam.initArgs=oracle.apps.oam.logger.level=USER
#
# Possible trace settings: on, true, off, false. Default is off
servlet.weboam.initArgs=oracle.apps.oam.trace=off
servlet.weboam.initArgs=oracle.apps.oam.logger.history=on
servlet.weboam.initArgs=oracle.apps.oam.dbInitParams.path=/u00/oracle/prodcomn/html/oam/config
servlet.weboam.initArgs=oracle.apps.oam.dbInitParams.filename=dbInitParams.xml
servlet.weboam.initArgs=oracle.apps.oam.standalone=on

servlet.weboamLocal.initArgs=oracle.apps.oam.trace=off

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 35 of 36

servlet.weboamLocal.initArgs=oracle.apps.oam.logger.history=on
servlet.weboamLocal.initArgs=oracle.apps.oam.dbInitParams.path=/u00/oracle/prodcomn/html/oam/config
servlet.weboamLocal.initArgs=oracle.apps.oam.dbInitParams.filename=dbInitParams.xml
servlet.weboamLocal.initArgs=oracle.apps.oam.standalone=on
#
# dbcfilename defaults to listing .dbc files from $FND_TOP/secure
#servlet.weboam.initArgs=oracle.apps.oam.dbcfilename=
#
servlet.weboam.initArgs=oracle.apps.oam.sqlplus_home=/u00/oracle/prodora/iAS
servlet.weboam.initArgs=oracle.apps.oam.tns_admin=/u00/oracle/prodora/iAS/network/admin/PROD_syjones-
sun

servlet.weboamLocal.initArgs=oracle.apps.oam.sqlplus_home=/u00/oracle/prodora/iAS
servlet.weboamLocal.initArgs=oracle.apps.oam.tns_admin=/u00/oracle/prodora/iAS/network/admin/PROD_syjones
-sun

# initArgs for restricted mode configuration


servlet.weboam.initArgs=oracle.apps.oam.apacheRunInfo=NORMAL
servlet.weboamLocal.initArgs=oracle.apps.oam.apacheRunInfo=NORMAL

 Patches

If earlier than release 11.5.10 make sure the following patches are applied:

3258830 - OAM.H

4038964 - Oracle AD Mini-pack 11i.AD.I

2864765 - Technology Stack Advanced Configuration Scripts

2949264 - Concurrent Processing Rollup Patch F

3594604 - Technology Stack AutoConfig Template Rollup Patch I (August 2004)

3671463 - Oracle Applications Framework Rollup Patch 5.7H - V6+

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006
OAM Usage and Navigation Page 36 of 36

3764779 - SSO Prerequisite Patch for Application Products - Rollup F

3882116 - Technology Stack - Rehost Oracle 9iR2 JDBC Drivers (v. 9.2.0.5) for Use with Oracle Applications 11i

2655277 - Mini-pack 11i.FND.G

2878058 - JTT-UIX (CABO) 2.1.14 Compatibility Patch

2420923 - Mini-pack 11i.JTT.D

Last updated: December 2005

file://D:\selina_oam\OAM_Under_Tech.html 1/10/2006