APPMgmtPack for Ora EBS

8/7/2019 APPMgmtPack for Ora EBS

1/38

Oracle Application Management Pack for OracleE-Business SuiteInstallation Guide

Release 2.0.2Part No. E12177-03

August 2008


2/38

Oracle Application Management Pack for Oracle E-Business Suite Installation Guide, Release 2.0.2

Part No. E12177-03

Copyright 2007, 2008, Oracle and/or its affiliates. All rights reserved.

Primary Author: Biju Mohan, Mildred Wang

Contributor: John Aedo, Max Arderius, Srikrishna Bandi, Nipun Goel, Ritanshu Jaiswal, Mike Smith

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarksof their respective owners.

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalfof the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTSPrograms, software, databases, and related documentation and technical data delivered to U.S. Governmentcustomers are "commercial computer software" or "commercial technical data" pursuant to the applicableFederal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication,disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in theapplicable Government contract, and, to the extent applicable by the terms of the Government contract, theadditional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). OracleUSA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is notdeveloped or intended for use in any inherently dangerous applications, including applications which maycreate a risk of personal injury. If you use this software in dangerous applications, then you shall beresponsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use ofthis software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this

software in dangerous applications.This software and documentation may provide access to or information on content, products and servicesfrom third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim allwarranties of any kind with respect to third party content, products and services. Oracle Corporation and itsaffiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of thirdparty content, products or services.


3/38

iii

Contents

Send Us Your Comments

Preface

1 Installing the Oracle Application Management Pack for Oracle E-BusinessSuite

Introduction ............................................................................................................................... 1-1System Requirements ................................................................................................................1-1

2 Installation Procedures

Before You Begin....................................................................................................................... 2-1

Running Oracle Universal Installer ..........................................................................................2-1Install Grid Control Extensions for Enterprise Manager Repository and Management Service.................................................................................................................................................... 2-2

Installing the Management Agent Plug-in ............................................................................... 2-9Patching the Oracle Application Management Pack for Oracle E-Business Suite ................ 2-15

A Installation in a Shared Agent Environment

Installation in a Shared Agent Environment ........................................................................... A-1

Index


4/38


5/38

v

Send Us Your Comments

Oracle Application Management Pack for Oracle E-Business Suite Installation Guide, Release 2.0.2

Part No. E12177-03

Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.Your feedback is important, and helps us to best meet your needs as a user of our products. For example:

Are the implementation steps correct and complete? Did you understand the context of the procedures? Did you find any errors in the information? Does the structure of the information help you with your tasks? Do you need different information or graphics? If so, where, and in what format? Are the examples correct? Do you need more examples?

If you find any errors or have any other suggestions for improvement, then please tell us your name, the

name of the company who has licensed our products, the title and part number of the documentation andthe chapter, section, and page number (if available).

Note: Before sending us your comments, you might like to check that you have the latest version of thedocument and if any concerns are already addressed. To do this, access the new Applications ReleaseOnline Documentation CD available on Oracle MetaLink and www.oracle.com. It contains the mostcurrent Documentation Library plus all documents revised or released recently.

Send your comments to us using the electronic mail address: [email protected]

Please give your name, address, electronic mail address, and telephone number (optional).

If you need assistance with Oracle software, then please contact your support representative or OracleSupport Services.

If you require training or instruction in using Oracle software, then please contact your Oracle local officeand inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site atwww.oracle.com.


6/38


7/38

vii

Preface

Intended AudienceWelcome to Release 2.0.2 of the Oracle Application Management Pack for Oracle E-BusinessSuite Installation Guide.

This book is intended for use by anyone who is responsible for installing or upgradingthe Oracle Application Management Pack for Oracle E-Business Suite.

See Related Information Sources on page viii for more Oracle Applications productinformation.

TTY Relay Access to Oracle Support ServicesTo reach AT&T Customer Assistants, dial 711 or 1.800.855.2880. An AT&T CustomerAssistant will relay information between the customer and Oracle Support Services at1.800.223.1711. Complete instructions for using the AT&T relay services are available athttp://www.consumer.att.com/relay/tty/standard2.html. After the AT&T CustomerAssistant contacts Oracle Support Services, an Oracle Support Services engineer willhandle technical issues and provide customer support according to the Oracle servicerequest process.

Documentation AccessibilityOur goal is to make Oracle products, services, and supporting documentation accessibleto all users, including users that are disabled. To that end, our documentation includesfeatures that make information available to users of assistive technology. Thisdocumentation is available in HTML format, and contains markup to facilitate access bythe disabled community. Accessibility standards will continue to evolve over time, andOracle is actively engaged with other market-leading technology vendors to addresstechnical obstacles so that our documentation can be accessible to all of our customers.For more information, visit the Oracle Accessibility Program Web site at


8/38

viii

http://www.oracle.com/accessibility/.

Accessibility of Code Examples in DocumentationScreen readers may not always correctly read the code examples in this document. The

conventions for writing code require that closing braces should appear on an otherwiseempty line; however, some screen readers may not always read a line of text thatconsists solely of a bracket or brace.

Accessibility of Links to External Web Sites in DocumentationThis documentation may contain links to Web sites of other companies or organizationsthat Oracle does not own or control. Oracle neither evaluates nor makes anyrepresentations regarding the accessibility of these Web sites.

Structure1 Installing the Oracle Application Management Pack for Oracle E-Business Suite2 Installation ProceduresA Installation in a Shared Agent Environment

Related Information SourcesOracle Application Management Pack for Oracle E-Business Suite User's Guide

This guide describes how to manage and monitor an Oracle E-Business Suite systemwith the Oracle Application Management Pack for Oracle E-Business Suite.

Do Not Use Database Tools to Modify Oracle Applications DataOracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle DataBrowser, database triggers, or any other tool to modify Oracle Applications data unlessotherwise instructed.

Oracle provides powerful tools you can use to create, store, change, retrieve, andmaintain information in an Oracle database. But if you use Oracle tools such asSQL*Plus to modify Oracle Applications data, you risk destroying the integrity of yourdata and you lose the ability to audit changes to your data.

Because Oracle Applications tables are interrelated, any change you make using an

Oracle Applications form can update many tables at once. But when you modify OracleApplications data using anything other than Oracle Applications, you may change arow in one table without making corresponding changes in related tables. If your tablesget out of synchronization with each other, you risk retrieving erroneous informationand you risk unpredictable results throughout Oracle Applications.

When you use Oracle Applications to modify your data, Oracle Applications


9/38

ix

automatically checks that your changes are valid. Oracle Applications also keeps trackof who changes information. If you enter information into database tables usingdatabase tools, you may store invalid information. You also lose the ability to track whohas changed your information because SQL*Plus and other database tools do not keep arecord of changes.


10/38


11/38

Installing the Oracle Application Management Pack for Oracle E-Business Suite 1-1

1Installing the Oracle Application

Management Pack for Oracle E-BusinessSuite

IntroductionOracle Application Management Pack for Oracle E-Business Suite extends EnterpriseManager (EM) 10 g Grid Control to help monitor and manage an Oracle E-Business Suitesystem more effectively. The pack integrates Oracle Applications Manager with GridControl to provide a consolidated, end-to-end E-Business Suite management solution.

This pack supersedes the Oracle Grid Control Plug-in version 1.2. The pack can be usedto manage both Oracle E-Business Suite Release 12 as well as Release 11 i systems.

This document describes the system requirements and installation of this new pack forGrid Control.

Note: This document typically uses UNIX syntax. If using MSWindows, substitute the appropriate Windows syntax.

System Requirements

OS/User Group RequirementPlease ensure that the ORACLE and APPLMGR OS user groups that own the OracleApplications System nodes file system are added to the EM Agent user group list thatmonitors the machine on which the node exists.

For example:

If the Applications System node being monitored by the EM Agent has a user"applmgr" and primary group "appsdba", and an "oracle" user with a primary group of


12/38

1-2 Oracle Application Management Pack for Oracle E-Business Suite Installation Guide

"oradba", the EM Agent user "emagent" must have secondary and tertiary groups"appsdba" and "oradba" added to it such that cloning and certain monitoring tasks canbe properly executed. If you are adding these now, the agent must be bounced beforeproper command execution can begin.

Before continuing with the installation as outlined below, please read and become familiar with

the known limitations as described in the Oracle Application Management Pack for OracleE-Business Suite User's Guide. These limitations are typically minor to most E-Business SuiteR12 and 11i administrators; however, they might be of concern to longtime users of EnterpriseManager who are new to using the Application Management Pack plug-in for EnterpriseManager.

Preparing Oracle E-Business Suite SystemsThe Oracle Application Management Pack for Oracle E-Business Suite can be used tomanage Oracle E-Business Suite systems, Releases 12 and 11 i.ATG_PF.H RUP4 orhigher. However, certain features will be disabled unless the managed Oracle

E-Business Suite system meets certain prerequisites.1. Apply Interoperability Patches.

For enabling advanced features to manage Oracle E-Business Suite Release 11i orRelease 12, the following patch(es) should be applied to the Oracle E-Business Suitesystem:

Patch 6874932 - 11i Interoperability Patch for AMP 2.0.2

This patch (which supersedes the previous Release 11 i interoperability patch)enables the collection of additional metrics for the Oracle E-Business Suitesystem target. It will also enable extended features in Grid Control, includinglinks to Oracle Applications Manager.

Please note that if you apply this patch to an Oracle E-Business Suite Systemthat is already being monitored by Grid Control, then you will need to restartthe Management Agent that is monitoring the system before the additionalfeatures and metrics will be enabled for the corresponding Oracle E-BusinessSuite System target in Grid Control.

Patch 6874927 - R12 Interoperability Patch for AMP 2.0.2

This patch provides the following additional fixes on top of base Release 12.0:

Provides an out-of-box "em_monitor" database user with restricted accessto the Oracle Applications database objects required by the managementpack for monitoring.

Provides numerous fixes for Rapid Clone required for proper cloning fromthe Oracle Application Management Pack environment.

2. Enable and Update AutoConfig on All Nodes.


13/38


In order for Oracle E-Business Suite systems to be properly recognized by theOracle Application Management Pack, AutoConfig must be enabled and updatedon all nodes.

Please refer to the applicable FAQs on Oracle MetaLink:

Article-ID: Note 165195.1

Title: Using AutoConfig to Manage System Configurations with OracleApplications 11i

Article-ID: Note 387859.1

Title: Using AutoConfig to Manage System Configurations in OracleE-Business Suite Release 12

3. Update Rapid Clone Code.

To successfully utilize the cloning features of the Oracle Application Management

Pack, it is required to apply the latest Oracle E-Business Suite cloning patch(es) andall required prerequisites as documented in the applicable Oracle MetaLink Note:230672.1 (for Release 11 i) or 406982.1 (for Release 12). Because the OracleApplication Management Pack cloning features use the underlying executable codepresent on the target system applications node and database nodes, this softwaremust be current before attempting to use the Oracle Application Management PackUI for cloning. In order to clone from EM, you must be able to successfully clonefrom the command line.

Preparing Oracle Enterprise Manager 10 g Grid Control 10.2.0.3 and Applying Oracle

Application Management Pack for Oracle E-Business SuiteFollow these steps for installing Oracle Enterprise Manager 10 g Grid Control 10.2.0.3

1. Install Oracle Enterprise Manager Grid Control 10 g 10.2.0.3.

The Oracle Application Management Pack for Oracle E-Business Suite installs intothe Enterprise Manager 10 g Grid Control management service, repository, andagent. Before installing this pack, you must first have Enterprise Manager 10 g GridControl 10.2.0.3. Installation instructions may vary for each platform, so please referto the Grid Control installation instructions available from the Oracle TechnologyNetwork, under Documentation -> Enterprise Manager.

2. Apply Required Oracle Enterprise Manager Grid Control Patches.

The following patches are required on top of Grid Control 10.2.0.3:

6342108 - Timezone parsing issues that cause Dashboard Reports to fail (Applyon the OMS ORACLE_HOME)

5997301 - Placeholder patch for Grid Control patches (apply on the agent


14/38


ORACLE_HOME)

5890474 - Spurious "MissingResourceException" errors in logs (apply on theOMS ORACLE_HOME)

6117528 - OJMX fetchlet fails to retrieve AJP port for 10.1.3 application server onAIX (for AIX only, apply on the agent ORACLE_HOME))

6670069 - Getting Initialization Error when Running File Transfer CommandIteratively (Apply on the agent ORACLE_HOME)

Preparing Oracle Enterprise Manager 10 g Grid Control 10.2.0.4 and Applying OracleApplication Management Pack for Oracle E-Business Suite

Perform this step for installing Oracle Enterprise Manager 10 g Grid Control 10.2.0.4 andthe Oracle Application Management Pack for Oracle E-Business Suite.

1. Apply Patch 6670069 - Getting Initialization Error when Running File TransferCommand Iteratively (Released for Oracle Enterprise Manager 10.2.0.4) (Apply onthe agent ORACLE_HOME)

2. Apply Patch 6342108 - Oracle E-Business Suite Dashboards fail to render; generateStack in OC4J Log (Released for Oracle Enterprise Manager 10.2.0.4). Note that youmust apply this patch for 10.2.0.4 even if it had been previously applied under10.2.0.3. (Apply on the OMS ORACLE_HOME)

3. (Microsoft Windows platforms only) Apply Patch 5983040 - Target Property ValueNot Being Returned Correctly (Released for Oracle Enterprise Manager 10.2.0.4)

(Apply on the OMS ORACLE_HOME)

Applying Oracle Application Pack for Oracle E-Business SuiteFollow these steps to install the management pack.

1. Install Oracle Application Management Pack for Oracle E-Business Suite Version2.0.0.

Once Grid Control is installed and patched, it is ready for the installation of the baseversion of the Oracle Application Management Pack. The pack can be obtainedfrom Oracle MetaLink under

Patch 5489352 - EM PLUGIN V2 FOR ORACLE APPLICATIONS

Important: On Windows platforms, this patch can be applied onEM 10.2.0.4 only.

See the next chapter for installation instructions.


15/38


2. Apply the Oracle Application Management Pack for Oracle E-Business SuiteVersion 2.0.2 Patchset.

The base version of the management pack is required for the full functionalitydescribed in this document. The 2.0.2 patchset may also be obtained from OracleMetaLink under:

Patch 6809246 : APPLICATIONS MANAGEMENT PACK V2.0.2 UPDATE FORE-BUSINESS SUITE

See Chapter 2 for additional details on patching the Oracle ApplicationManagement Pack for Oracle E-Business Suite.

Upgrading from Oracle Enterprise Manager Grid Control 10.2.0.3 to 10.2.0.4If you are upgrading from Oracle Enterprise Manager Grid Control 10.2.0.3 that hasalready had Application Management Pack 2.0.x installed to 10.2.0.4, you will need toedit the list of valid discover scripts that are registered with Oracle Grid Control.

The 10.2.0.4 upgrade process overwrites the$ORACLE_HOME/sysman/admin/scripts/discover/discover.lst with a default file.

You need to add in the entry that is added as part of the Oracle ApplicationManagement Pack Agent-side installation for oracle_apps.pl.

Manually edit the file to add:

ORACLE_APPS|oracle_apps.pl|TRUE


16/38


17/38

Installation Procedures 2-1

2Installation Procedures

Before You BeginDownload the Oracle Application Management Pack for Oracle E-Business Suite Patch5489352 from Oracle MetaLink to the Enterprise Manager Oracle Management Server.

The Oracle Application Management Pack for Oracle E-Business Suite is installed usingOracle Universal Installer. To install this pack, you must have an existing Grid Controlinstallation. The pack must be installed into each existing Grid Control ManagementService and Management Agent that will be used for Oracle E-Business Suite.

Note: When Installing Patch 5489352, the oraInst.loc must point to anoraInventory with correct permissions for the user that is running theinstaller.

Running Oracle Universal Installer Please follow these steps to run Oracle Universal Installer.

1. First stop all the Management Services before installing the pack to a ManagementService. Management Services will be restarted automatically after the pack hasbeen installed.

Note: If your EM Repository (EM Database) is on the samemachine, it must be left running. Only OMS and Agent servicesneed to be taken down.

2. Set the environment variable ORACLE_HOME to ORACLE_HOME ofManagement Service 10.2.0.3 or 10.2.0.4 as shown here:

export ORACLE_HOME=/d1/oracle/em10g/oms10g


18/38


3. Unzip the p_R12_LINUX.zip and run the runInstaller command as shownhere. (Please check the appropriate plugin patch numbers for the other platformswhen available.)

/Disk1/runInstaller

The installer will then run a series of tests. If all of the tests succeed, then theinstallation will open a new window.

From this window, you can choose to install the Grid Control extensions forEnterprise Manager Repository and Management Service or the ManagementAgent extensions for managing Oracle E-Business Suite. Press Next to continuewith the installation.

Install Grid Control Extensions for Enterprise Manager Repository andManagement Service

Please follow these steps to install Grid Control Extensions for Enterprise ManagerRepository and Management Service.

1. Specify the product to install.


19/38


Choose Grid Control Plug-in for Oracle Applications 2.0.0.0.0 and click Next tocontinue.

2. Specify Oracle Home (of Management Service) details.


20/38


The Application Management Pack must be installed into each existing GridControl Management Service and Repository. To perform this installation, begin bychoosing the name and location of the Oracle Home of the Management Service intowhich you want to install the plug-in.

Once you have properly chosen the name and location of the Management Service'sOracle Home, click Next to continue.

3. Specify Repository Database Connection details.


21/38


You will be prompted to enter the password for the SYS user account in theEnterprise Manager Repository database. After you enter the password, click Next to continue.

Note: When installing the management pack in a Grid Control

environment in which the Management Repository was not a newdatabase created by the Grid Control installer, you may see theconnect string blanked out in the Universal Installer. This is aknown display-only limitation and does not prevent successfulinstallation of the management pack.

4. View the Install Summary.


22/38


23/38


You can then view the progress of the installation in the Install window. Once all ofthe installation steps have completed, the Configuration Assistants window willdisplay automatically.

6. View the Configuration Assistants (Upgrade and Restart Service).


24/38


The configuration assistants will complete the upgrade of the Grid ControlRepository and restart the Management Service. You can view the progress of theconfiguration assistants in this window.

7. End of Installation.


25/38


Once the installation is complete, click Exit to end your session.

Installing the Management Agent Plug-in

Download patch 5489352 to your Oracle Enterprise Manager (EM) Agent host.Please follow these instructions to install the Management Agent Plug-in.

Running Oracle Universal Installer:Please follow these steps to run Oracle Universal Installer.

1. First set the environment variable ORACLE_HOME to the ORACLE_HOME of theEM Agent 10.2.0.3 or 10.2.0.4.

export ORACLE_HOME=/d1/oracle/em10g/agent10g

2. Unzip the p5489352_R12_LINUX.zip and run the runInstaller.

/Disk1/runInstaller

(Please check the appropriate plug-in patch numbers for the other platforms whenavailable.)

3. The installer will then run a series of tests. If all of the tests succeed, then theinstallation will open a new window. Next, follow the steps described in the next


26/38


section.

Installing the Management Agent Plug-in:Please follow these steps to install Management Agent Plug-in.

1. Specify the product to install.

Begin the installation of the Management Agent Plug-in by running the OracleUniversal Installer (as described in Running Oracle Universal Installer, page 2-1) onthe respective host. Choose the Management Agent Plug-In for Oracle Applicationsoption to install the Management Agent plug-in. Click Next to continue.

2. Specify the Agent's Oracle Home details.


27/38


Next choose the correct name and location of the Oracle Home of the EM Agent intowhere you want to install the plug-in. Click Next to continue with the installation.

3. View the Install Summary.


28/38


29/38


You can then view the progress of the installation in the Install window. Once all ofthe installation steps have completed, the Configuration Assistants window willdisplay automatically.

5. View the Configuration Assistant (Stop and Start Agent).


30/38


The configuration assistants will stop and restart the agent for you. You canmonitor their progress in this window.

6. End of Installation.


31/38


Once the installation is complete, click Exit to end your installation.

Patching the Oracle Application Management Pack for Oracle E-Business

SuitePatching the Oracle Application Management Pack for Oracle E-Business Suite isaccomplished through the use of a utility called OPatch which is delivered in all Oracle10g ORACLE_HOMEs.

Before applying any patch with OPatch, verify the oraInst.loc points to the oraInventorywhere the AGENT or OMS HOMES are registered. This file defines the location of theGlobal Inventory and is located under /etc for Linux and AIX and /var/opt/oracle onSolaris and HP-UX Platforms.

Note: After applying patches using OPatch, the Opatch lsinventoryversion does not change; for example, after applying the 2.0.2 patch, the

Opatch lsinventory will still show 2.0.0.0.0.0. To find the version forversion 2.0.2, refer to these files:

ebs_oms/sysman/admin/scripts/ebs/version.txtebs_agent/sysman/admin/scripts/ebs/version.txt

You can also determine the management pack version by logging in to


32/38


the Oracle Management Server console, navigate to the OracleApplications target tab, and select "About the ApplicationsManagement Pack" in the "Related Links" section.

Applying Patches to the Application Management Pack:1. Unzip the patch:

unzip p.zip

2. Applying a patch on the OMS HOME:

1. Set the ORACLE_HOME environment variable:

ORACLE_HOME=export ORACLE_HOME

2. Include /OPatch in the $PATH environment variable:

PATH=:.:$PATH:$ORACLE_HOME/OPatchexport PATH

3. Shut down the OMS Server.

4. Navigate to the directory where the patch is located and run OPatch:

$ cd /ebs_oms$ opatch apply

At the end of the OPatch session, you will be presented with details asking that thepost-install script ebs_postinstall.sh be run. Run the script and provide the requiredconnection details.

If prompted by OPatch to "Rollback" an existing fix, hit "y" and continue.

3. Applying a patch on the AGENT HOME:

1. Set the ORACLE_HOME environment variable:

ORACLE_HOME=export ORACLE_HOME

2. Include /OPatch in the $PATH environment variable:

PATH=:.:$PATH:$ORACLE_HOME/OPatchexport PATH

3. Shut down the agent.

4. Navigate to the directory where the patch is located and run OPatch:

$ cd /ebs_agent$ opatch apply

If prompted by OPatch to "Rollback" existing patch, hit "y" and continue.


33/38


Patch Deinstallation Instructions:Use the following command:

cd /opatch rollback -id


34/38


35/38

Installation in a Shared Agent Environment A-1

AInstallation in a Shared Agent Environment

Installation in a Shared Agent EnvironmentNote: Shared Agent configurations are currently not supported withthe Application Management Pack on Windows platforms.

1. Read the official documentation to become familiar with this process.

Read "Sharing the Agent Oracle Home Using the nfsagentinstall Script", OracleEnterprise Manager Grid Control Installation and Basic Configuration 10g Release 3(10.2.0.3.0) (or 10g Release 4, or 10.2.0.4).

What follows in this guide is an expansion and clarification of the documentationlisted above. There are a few points in the above document that warrant specialattention.

2. Perform the installation.

Install a 10.2.0.3 (or 10.2.0.4) agent to the master system. This installation is verystraightforward, but please be mindful of the following: The ORACLE_HOME mustbe mounted on the shared hosts on the exact same path. Example: AgentORACLE_HOME is /u01/oracle/agent10g on the master, therefore it must also bemounted as /u01/oracle/agent10g on the slaves. Secondly, make sure that your usersand groups are consistent between master and slaves; and that ultimately, the agentbelongs in the same group as the Oracle Applications instances to be monitored. Asan example, the target Oracle Applications instances run under a user called "applrt" with a group of "g680" the uid was 20001 and the gid 680. Therefore, on the masteragent system, there should be a user called "applrt" with a group of "g680" anduid/gid of 20001/680. This replication of UNIX username and group associationsisn't strictly necessary as long as, ultimately, the agent on the slaves runs under thesame group and has appropriate permissions to read, write, and execute files underthe Oracle E-Business Suite.


36/38

A-2 Oracle Application Management Pack for Oracle E-Business Suite Installation Guide

3. Apply the Oracle Application Management Pack patch (patch 5489352) to themaster.

4. Apply the latest Oracle Application Management Pack patchset to the master.

See Chapter 1, "Installing Oracle Application Management Pack for Oracle

E-Business Suite" for details on the latest patchset available on Oracle MetaLink.

5. Share out the Agent $ORACLE_HOME as read-only.

This assumes that your Master agent server already has the NFS server installed andrunning.

In /etc/exportfs on the Master agent server, add a line similar to the following:

/u01/oracle/agent10g *(ro)

This is only an example. In fact, this configuration is not very secure, despite settingthe read-only ("ro") flag. Please set your export options as appropriate for yoursecurity requirements.

You should now re-export your shares:

/usr/sbin/exportfs -r

6. Mount the Agent $ORACLE_HOME on each slave.

7. On the master AND slaves, create the EM states directory.

The states directory is the local directory to which configuration files and logs arewritten. For example, if your remote agent home is mounted as/u01/oracle/agent10g, you could create a directory /u01/oracle/emstate on the slave.

mkdir /u01/oracle/emstate

8. On the Master, run the $ORACLE_HOME/sysman/install/nfsagentinstall scriptIN the states directory:

cd /u01/oracle/emstate$ORACLE_HOME/sysman/install/nfsagentinstall -s /u01/oracle/emstate

Important: It is absolutely critical that the nfsagentinstall script isNOT executed from the remote home (in our example,/u01/oracle/agent10g). This will cause the script to fail because itcannot write out its log, which is always written to the currentworking directory.

9. Repeat Step 8 for each slave.


37/38

Index-1

Index

A

AutoConfig, 1-1

E

Enterprise Manager 10g Grid Control 10.2.0.3, 1-3Enterprise Manager 10g Grid Control 10.2.0.4, 1-4

G

Grid Control Extensionsinstallation, 2-2

I

Installationshared agent environment, A-1

Interoperability patches, 1-1

M

Management agent plug-ininstallation, 2-9

O

Oracle Universal Installer, 2-1

OS/User Group Requirement, 1-1

R

Rapid Clone, 1-1

S

Shared agent environment, A-1

System requirements, 1-1


38/38

APPMgmtPack for Ora EBS

Documents

Transcript of APPMgmtPack for Ora EBS