OEM12c Install Mgmt

OEM 12c Installation and Mgmt with AMP |Jan, 2014

OEM12c Installation and Management with Application Management pack

Oracle® Enterprise ManagerCloud Control Advanced Installation and Configuration Guide12c Release 3 (12.1.0.3)

Platform Linux 5.x - 64 bit


Table of Contents

1. Installation of OMS …………………………………………………………………………… 3

2. Configuring OMS ………………………………………………………………………………. 10

3. Agent Installation ……………………………………………………………………………… 15

4. Discovery and Monitoring in Enterprise Manager Lifecycle ………………. 20

5. Application Management Pack Installation ………………………………………. 29

6. Discovering Oracle E-Business Suite Systems with Cloud Control ……… 35

[Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide 12c Release 3

(12.1.0.3)] Page 2


Introduction

Enterprise Manager Cloud Control is system manageP a g e | 3ment software that delivers centralized monitoring, administration, and life cycle management functionality for the complete IT infrastructure, including systems running Oracle and non-Oracle technologies.

1. Installation of OMS (Software only)

The Enterprise Manager Cloud Control Installation Wizard runs prerequisite checks to verify these packages. If the packages are not found or if the packages are found to be of a lower version than what is required at a minimum, then the wizard prompts you to install the required packages of the required version before proceeding with the installation or upgrade.

1.1)Packages Required

make-3.81 binutils-2.17.50.0.6 gcc -4.1.1 libaio-0.3.106 glibc-common-2.3.4 libstdc++ -4.1.1 setarch-1.6 sysstat-5.0.5 rng-utils-2.0 libXtst-1.0.1-3.1(x86_64) xorg-x11-utils (This package is required only for GUI-based interactive installation, and not

for silent installation)

1.2)Kernel Parametersset the kernel.shmmax parameter to a value 1 byte less than 4 GB or 4294967295

Oracle recommends this value to avoid lack of memory issues for other applications and to enable a complete and successful core file generation under any and all circumstances.

To verify the value assigned to kernel.shmmax parameter, run the following command:cat /proc/sys/kernel/shmmaxTo set the value for kernel.shmmax parameter, run the following command:sysctl -w kernel.shmmax=<new value>

1.3)Library Requirements for Oracle Management Service


(12.1.0.3)] Page 3


Oracle Linux 5.x Red Hat Enterprise Linux 5.x glibc-2.5-12

1.4)Creating the Operating System Groups and Users

1.5)As part of a new Enterprise Manager system, the installation wizard does the following:

Installs the following components in the Middleware home you enter in the installation wizard:

Java Development Kit (JDK) 1.6.0.43.0 Oracle WebLogic Server 11g Release 1 (10.3.6) Oracle Management Service 12c Release 3 (12.1.0.3) Oracle JRF 11g Release (11.1.1.6.0), which includes oracle_common directory Oracle Web Tier 11g Release (11.1.1.6.0), which includes Oracle_WT directory Oracle Plug-Ins

Oracle Database Plug-In Oracle Fusion Middleware Plug-In Oracle My Oracle Support Plug-In Oracle Exadata Plug-In

Installs Oracle Management Agent 12c Release 3 (12.1.0.3) in the agent base directory you specify (outside the Middleware home)

Creates an Oracle WebLogic domain called GCDomain. For this WebLogic Domain, a default user account, weblogic, is used as the administrative user. In advanced installation, you can choose to change this if you want

Creates a Node Manager user account called nodemanager. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements

Configures an Oracle Management Service Instance Base location (gc_inst) outside the Oracle Middleware home (Middleware home), for storing all configuration details related to Oracle Management Service 12c. In advanced installation, you can choose to change this location if you want

Configures Oracle Management Repository in the existing, certified Oracle Database. If the database instance is created using the database template offered by Oracle, then this step is skipped

1.6)In addition, install the 32-bit version as well as the 64-bit version of glibc-devel-2.5-49 to avoid any linking errors while installing the OMS. The installer checks for this package, so if this package is not installed, the installer displays an error.

1.7)Start the runinstaller from the software location

You must not set the ORACLE_HOME and ORACLE_SID environment variables. You must ensure that the Oracle directories do NOT appear in the PATH.


(12.1.0.3)] Page 4


1.8)


(12.1.0.3)] Page 5


1.9)

1.10)


(12.1.0.3)] Page 6


1.11)

1.12)


(12.1.0.3)] Page 7


1.13)

1.14)


(12.1.0.3)] Page 8


1.15)


(12.1.0.3)] Page 9


2. Configuring OMS

2.1)Run $OMS_HOME/sysman/install/ConfigureGC.sh

2.2)


(12.1.0.3)] Page 10


2.3)

2.4)


(12.1.0.3)] Page 11


2.5)

2.6)


(12.1.0.3)] Page 12


2.7)

2.8)


(12.1.0.3)] Page 13


2.9)

2.10)


(12.1.0.3)] Page 14


3. Agent Installation

3.1) Changes to Sudo files on remote server.

As part of the implementation the oracle user needs to be able to sudo to root and run scripts on the remote machine to do this add the following to the sudo file on the remote machine.

Sudo file located at /etc/sudoersThis work needs to be carried out as rootAdd Oracle, add this line to the bottom of the fileoracle ALL=(ALL) ALLcomment requiretty line as below:-#Defaults requirettyChange visiblepw, change entry to as below:-Defaults visiblepw

3.2) Package requirement on agent serversPackage required for 64 bit installation

Oracle Linux 5.x and Red Hat Enterprise Linux 5.x, where x <= 5 [for example, Oracle Linux 5.3] make-3.81 binutils-2.17.50.0.6 gcc -4.1.1 libstdc++ -4.1.1

Oracle Linux 5.x and Red Hat Enterprise Linux 5.x, where x > 5 [for example, Oracle Linux 5.6] make-3.81 binutils-2.17.50.0.6 gcc -4.1.1 libaio-0.3.106 glibc-common-2.3.4 libstdc++ -4.1.1 setarch-1.6 sysstat-5.0.5 rng-utils-2

3.3) Temporary Directory Space RequirementsEnsure that you allocate 400 MB of space for a temporary directory where the executables can be copied. By default, the temporary directory location set to the environment variable TMP or TEMP is honored. If both are set, then TEMP is honored. If none of them are set, then the following default values are honored: /tmp on UNIX hosts.


(12.1.0.3)] Page 15


3.4) Set the privilege delegation

For Privileged Delegation Setting, validate the Privilege Delegation setting to be used for running the root scripts. By default, it is set to the Privilege Delegation setting configured in Enterprise Manager Cloud Control. If you leave this field blank, the root scripts will not be run by the wizard; you will have to run them manually after the installation.

This setting will also be used for performing the installation as the user set in the Run As attribute of the selected Named Credential if you had set the user while creating that Named Credential.

Privilege delegation is required to set for the host which is selected as a source host to install the agents on other hosts.

Go to Setup -> Security -> Privilege Delegation

3.5) Acquiring the Management Agent Software in the Offline Mode

3.5.1) Ensure Cloud Control is set to the offline mode. From the Setup menu, choose Provisioning and Patching>Offline Patching, then change the setting for Connection to Offline.


(12.1.0.3)] Page 16


3.5.2) Click Check for Updates on the Self Update home page. A message is displayed that contains the URL to be accessed to download a catalog of all updates.

3.5.3) From an Internet-enabled computer, open a browser , download the catalog file using the aforementioned URL.

Example:

https://updates.oracle.com/Orion/Download/download_patch/p9348486_112000_Generic.zip

Copy the downloaded file to the Oracle Management Service host:

Run the emcli import_update command to import the file into the Oracle Management Service instance or the Management Agent you want to update.

Example:

[oracle@nagopise-lnx bin]$ ./emcli import_update_catalog -file=/home/oracle/Desktop/p9348486_112000_Generic.zip -omslocalProcessing catalog for Agent SoftwareProcessing update: Agent Software - Agent Software (12.1.0.1.0) for Linux x86Processing catalog for Management ConnectorProcessing update: Management Connector - BMC Remedy Change Management Connector - 12.1.0.1.0Processing catalog for Plug-in


(12.1.0.3)] Page 17


Operation completed successfully. Self Update catalog has been uploaded to Enterprise Manager. Please use the Self Update Home to view and manage updates.

3.5.4) From the Setup menu, choose Extensibility>Self Update.Select the entity type Agent Software and choose Open from the Action menu. The entity type page appears to show agent software for different platforms. Select an update from the list of available updates. All entries other than the one which matches the platform of the OMS host should show their status as Available, for example, linux x86

Click Download. A message is displayed with a URL and instructions.


(12.1.0.3)] Page 18


Example:

Select Agent software and select agent software that is not available in the oms:

3.5.5)

From an Internet-enabled computer, open a browser, download the file from the URL displayed in step

Example:

https://updates.oracle.com/Orion/Services/download/p12654265_112000_Generic.zip?aru=14155113&patch_file=p12654265_112000_Generic.zip

Copy the file to Oracle Management Service and follow the instructions displayed in step 4 (Run the command shown below from the OMS_HOME/bin directory).

Example:

./emcli import_update -omslocal -file=/DATA/p12654265_112000_Generic.zip

At this stage, the update will show up in downloaded state in the Self Update home page.

3.5.6) Once the download is complete, select the Management Agent, then click Apply. This step will stage the Management Agent software in the Software Library and make it available to the Add Targets wizard, which you will use to install the Management Agent on host machines.


(12.1.0.3)] Page 19


4) Discovery and Monitoring in Enterprise Manager Lifecycle

You can configure automatic discovery to set up a schedule for discovery, the target types to be discovered, and the hosts to scan for targets. Discovered hosts can then be promoted to managed target status, enabling Enterprise Manager Cloud Control to manage and monitor these targets. When new targets are added to your infrastructure, they can be found and brought under management on a regularly-scheduled basis.

4.1) Discovering Unmanaged Hosts Using Network Scan

4.1.1) To discover and configure hosts using IP scan, follow these steps:

From the Setup menu, select Add Target, then select Configure Auto Discovery.

On the Configure Auto Discovery page, click the Configure icon against Host and Oracle VM Manager in the Network Scan-based Auto Discovery table.


(12.1.0.3)] Page 20


4.1.2) On the Network Scan Discovery page, click Create. You will now create the discover job. By default, the Name field will be populated with a title including that date and time the job was created. Note that you can edit the discovery jobs and schedule discovery to run immediately or later.

4.1.3) On the Network Scan Discovery: Create page, click Add. You will now select the Management Agent that will perform the network scan. You can select the Management Agent that is installed by default on the Oracle Management Service host, or can select another Agent if desired.


(12.1.0.3)] Page 21


4.1.4) From the Setup menu, select Add Target, then select Auto Discovery Results

4.2) Converting Unmanaged Hosts to Managed Hosts

From the Setup menu, select Add Target, and then select Auto Discovery Results

On the Auto Discovery Results page, select the Network-scanned Targets tab. All discovered hosts are listed, with the open ports and identifiable service names shown. Based on your understanding of the Oracle components deployed on your network, you should be able to determine the types of potential targets that have been discovered.

Select a host from the table, then click Promote to promote the host to managed target status. The Add Host Targets wizard opens. You will use this wizard to install a Management Agent on the host.

OR

You can add a target manually as given below:


(12.1.0.3)] Page 22


4.3) Add Target Manually

4.3.1) Go to setup-> add target -> Add target manually

4.3.2)


(12.1.0.3)] Page 23


4.3.3)

4.3.4) Click add


(12.1.0.3)] Page 24


4.3.5)

4.3.6)

Click on Deploy Agent


(12.1.0.3)] Page 25


4.4) Discovering Targets on Managed Hosts

4.4.1) From the Setup menu, select Add Target, and then select Configure Auto Discovery.

On the Configure Auto Discovery page, click the Configure icon in the All Discovery Modules row in the Configure Auto Discovery table.


(12.1.0.3)] Page 26


4.4.2) On the Target Discovery (Agent-based) page, expand Search, then enter the hostname for the host you want to check for targets in the Agent Host Name field. The host must have a Management Agent installed on it.

To search for a specific Management Agent, click Search. The table lists all the Management Agents and filters the list based on what you search for.


(12.1.0.3)] Page 27


4.4.3) Promoting Targets

To promote discovered targets to managed status, follow these steps:

After the discovery job executes, you can check for discovered hosts that may contain potential targets. You can do this two ways:

Select the job in the Host Discovery page, then click View Discovered Targets;

or

From the Setup menu, select Add Target, then select Auto Discovery Results.

Select a target to promote, then click Promote. A wizard specific to the target type you are promoting opens. Supply the required values.


(12.1.0.3)] Page 28


5.) Application Management Pack Installation

5.1) System Requirements

Ensure that the following requirement has been met:

OS/User Group Requirement: It is recommended that the Oracle E-Business Suite OS user and the Enterprise Manager Agent OS user is the same. If they are different, then they must belong to the same OS group.

Oracle Application Management Pack for Oracle E-Business Suite 12.1.0.1.0 can be installed on Oracle Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1), 12c Release 2 (12.1.0.2), or 12c Release 3 (12.1.0.3)

Release 12.1+ with R12.ATG_PF.B.DELTA.3

5.2) Patches to be applied for R12.1.x

5.2.1)

AMP: Discovery NA AMP: Administration Patch 8919489 AMP: User Monitoring and Diagnostics Patch 10168359 AMP: Cloning Patch 9171651 ACMP: Setup Manager Patch 9444535 ACMP: Customization Manager Patch 9967338, Patch 7648894, Patch 16770159 ACMP: Patch Manager NA

5.2.2) Patch 14825718 - ORACLE FORMS BUNDLE PATCH 10.1.2.3.2 for product Developer Forms. Note: This patch conflicts with other existing patches in ORACLE_HOME 10.1.2.3, but conflict messages can be safely ignored. Please see Note 437878.1, "Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12" for more information.

5.3) Enable and update AutoConfig on All Nodes

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

Please refer to the applicable Knowledge Documents on My Oracle Support:

Note 387859.1, "Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12"


(12.1.0.3)] Page 29


5.4) Update Rapid Clone Code

To successfully utilize the cloning features of the Oracle Application Management Pack for Oracle E-Business Suite, you must apply the latest Oracle E-Business Suite cloning patch(es) as listed below.

Patch 9171651 - R12 RAPIDCLONE CONSOLIDATED FIXES JUL/2010 for Release R12

5.5) Create APPS_TS_TOOLS Tablespace. (Conditionally Required)

This step is required for using Customization Manager with Release 11i only.

The default initial size for the APPS_TS_TOOLS tablespace is 500 MB, with auto segment management enabled. If you create the APPS_TS_TOOLS tablespace through SQL*Plus, outside of the OATM utility, you can use the following statement:

CREATE TABLESPACE APPS_TS_TOOLS DATAFILE'datafile_name.dbf' SIZE 500MEXTENT MANAGEMENT LOCAL AUTOALLOCATE;

5.6) If EM 12c is deployed on a 11.2.0.3 Database, then you must perform the following setup steps:Log into the Enterprise Manager 12c WebLogic console.

Traverse through the GC Domain in the "Domain Structure".

Expand Environment. Click on Servers. Click on the name of the OMS server. Click on the "Server Start" subtab. Modify the "Arguments" text area by concatenating the parameter "-Doracle.jdbc.defaultLobPrefetchSize=1000000" at the end. Save the changes and then bounce the OMS server using these commands: "<Middleware Home>/oms/bin/emctl stop oms" "<Middleware Home>/oms/bin/emctl start oms"

5.7) The database plug-in must be deployed on the application nodes that have been configured to run the Applications listener so that metric collection can occur. The Applications listener target type is part of the database plug-in, so the database plug-in must be deployed on the same node(s).

5.8) Disk Requirements

For Oracle Management Service, the management pack requires a maximum of 1 GB.For the Agent, the management pack requires a maximum of 1 GB.


(12.1.0.3)] Page 30


5.9) Installing the Oracle Application Management Pack

5.9.1) Installing the Oracle Application Management Pack for Oracle E-Business Suite Deploy the Fusion Middleware plug-in on all application nodes that run the webtier. This step is necessary for Oracle E-Business Suite discovery to work correctly.

From the Enterprise Manager Cloud Control Setup menu, select Extensibility, then Plug-ins.

Select Oracle Fusion Middleware in the Plug-ins table. Select Deploy On and then select Management Agent.

5.9.2) If the RDBMS version of the OMS database is 11.2.0.2.0 or greater, then apply RDBMS Server patch 12965899 on the OMS database before installing the Oracle E-Business Suite plug-in.

5.10) Deploy E-business Suite Plug in

5.10.1) Go to Setup -> Extensibility -> Plugins


(12.1.0.3)] Page 31


5.10.2) Oracle E-business Suite -> Deploy on -> Management agents

5.10.3)


(12.1.0.3)] Page 32


5.10.4)

5.10.5)


(12.1.0.3)] Page 33


5.10.6)


(12.1.0.3)] Page 34


6) Discovering Oracle E-Business Suite Systems with Cloud Control

6.1) Prevalidating Discovery

6.1.1) To prevalidate discovery:

Navigate to the Discovery Wizard using Targets menu > Oracle E-Business Suite >Discovery Wizard (under "Related Links").Select an Application Database Target and click the Prevalidate button.

6.1.2) Enter the Monitoring Schema Username and the Monitoring Schema Password credentials for the database. Enter apps password :


(12.1.0.3)] Page 35


Click Prevalidate Discovery to start the job.

6.2) Discovery Wizard

6.2.1) Discovery Wizard also provides a way to prevalidate the system to ensure that the Oracle E-Business Suite context, OMS, and Agent are set up properly.

To access Discovery Wizard, navigate to the Targets menu > Oracle E-Business Suite > Discovery Wizard link (under "Related Links")


(12.1.0.3)] Page 36


6.2.2) The following are prerequisites to using Discovery Wizard:

An agent has been installed on the Oracle E-Business Suite system, on both the database tier and the application system tier

The Oracle E-Business Suite database host system has been discovered by Enterprise Manager Cloud Control. In the case of a Real Application Clusters (RAC) system, agents must be installed on all the nodes in the cluster

The Oracle E-Business Suite system database has been discovered by Cloud Control


(12.1.0.3)] Page 37


From the Discovery Wizard, you can add a database to the system using the Add Databases button

Select a database out of the above options.

On the main Discovery Wizard page, select the Application Database Targets you want to discover and click the Discover button to start a discovery process.

For Monitoring Schema and Monitoring Schema Password, enter the apps username and password for the Oracle E-Business Suite database that can be used by the management pack for monitoring.

To begin the discovery process, click the Start Discovery button.


(12.1.0.3)] Page 38