<Insert Picture Here>

EM Installation for FMW Management

Agenda

Components & Architecture Overview EM Grid Control Install JVM Diagnostics Application Dependency and Performance Q&A

Components and Architecture

OVERVIEW

Key Components
EM Grid Control 11.1 OMS
Installer creates a GC domain, OMS is a managed server in the domain

EM Repository (Database) JVM Diagnostics Manager

Installed OMS contains binaries and script to add EMAD4JMANAGER managed server to GC domain Depends on EM Repository for DB

Application Dependency and Performance Manager

Installed OMS contains install binaries to install standalone Java server Uses any Oracle DB (dedicated schema recommended)

Grid Control Architecture

JVM Diagnostics Architecture

Additional Components Relative to OMS

ADP Architecture
Additional Components Relative to OMS

OMS

WEBLOGIC DOMAIN
Application Servers

RMI

JMX ADP Manager JMX RMI

App Components

OMS ADF Pages

ADP Agent Admin Server

ADP Database

Installation

GRID CONTROL

EM Grid Control Install

Main OMS Install Documentation
http://www.oracle.com/technology/documentation/oem.html Navigate through View Library Overview (tab) Basic Installation Guide Deep links may not be stable as doc IDs change

EM Install and Upgrade EM Components Forum

http://myforums.oracle.com/jive3/forum.jspa?forumID=4137 Help on topics specific for install (reach more install experts)

helpsmp_us mailing list forum

http://myforums.oracle.com/jive3/forum.jspa?forumID=3320 Search past questions and answers General help across all EM products (higher traffic)

EM Grid Control Install Tips

Setting up prerequisites is usually the most challenging part
EMGC is a very large codebase, more akin to a packaged app like EBS Happy path is fairly easy stick to it

While secure SSL/HTTPS (locked OMS) is the recommended configuration, un-checking the Secure Oracle Management Server options in the install wizard can get you to completion sooner
Then add back SSL options, if necessary, after getting your initial infrastructure and first remote agent operational

10

EM Grid Control Install Tips

Use DNS names, make sure that that they point to real (e.g. not localhost, 127.0.0.1) and static IP addresses
Changing IPs is supported so long as DNS names are used Changing DNS names is not supported Use names that refer to your logical service (e.g. gridcontrol.us.oracle.com) and not those that are tied to your hardware (e.g. node3-rack1.austin-dmz.corp.net)

Installer uses OUI, thus X (or at least VNC) is required

11

EM Grid Control Prerequisites Key Highlights

Start with DB 11.2 + patches (9002336, 9067282) DB install will take you through all the OS requirements WLS 10.3.2 + patch WDJ7 (via SmartUpdate) Must be 10.3.2 only! Must be Sun JDK, known issues on JRockit Use 1.6.0_18 on 64-bit Linux (download separately) Database Setup Prereqs DBControl deconfigured via DBCA (see deconfigdbcontrol.sh) Dont drop the schema manually! System parameters (see emgc_system_parms.sql) Undo tablespace (see emgc_undo_tbs.sql)

12

FMW Cumulative Patch

Should be considered to be REQUIRED for all FMW Management (WLS, SOA, OSB, etc) Contains cumulative fixes for all components (Grid Control, JVM Diagnostics, and ADP) Two parts OMS side and Agent side
MOS bug/patch IDs: 9901141 (OMS), 9930117 (Agent) ARU URLs: http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/pro cess_form?aru=13191668 http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/pro cess_form?aru=13123302

13

Installation

JVM DIAGNOSTICS

14

JVM Diagnostics Install

Main JVM Diagnostics Install Documentation
http://www.oracle.com/technology/documentation/oem.html Navigate through View Library Overview (tab) Administrators Guide 11 Setting Up the JVM Diagnostics Manager Deep links may not be stable as doc IDs change

Dev Help Wiki

http://dbdev.us.oracle.com/twiki/bin/view/Smpdev/AllYouWant edToKnowAboutAD4J%28new%29

helpad4j_us mailing list forum

http://myforums.oracle.com/jive3/forum.jspa?forumID=2736 Search past questions and answers

15

JVM Diagnostics Install Tips

Install scripts are in ORACLE_MIDDLEWARE_HOME/oms11g/ad4j Make sure your environment is clean of any database ORACLE_* variables before you run DeployAD4JManager.sh JVMD Manager only supports Linux, Solaris, and Windows JVMD Manager must run on 32-bit JVM
If rest of OMS is installed on 64-bit, a separate 32-bit JVM should be installed and the JVMD Managers managed server startup script should be pointed at it see dbdev wiki for details

16

JVM Diagnostics Deployment Tips

OMS contains all of the UI (JSP) pages, which are populated with data from the JVMD manager OMS talks to JVMD Manager via T3 EJB calls for real-time data operations
If this is broken, historical metrics may work, but exceptions will occur whenever you try to update configuration or perform real-time operations

JVMD Manager writes to EM Repository DB which OMS reads from for historical data pages JVMD agent calls back to JVMD Manager on port 3600 (raw socket, custom protocol)

17

JVM Diagnostics Deployment Tips

JVMD Agent logs are intermixed with the monitored JVMs stdout Log level changes for both JVMD manager and agents are controlled via the UI and take effect immediately Use JVM Diagnostics Threads Real-time Analysis (at the domain level) to determine agent connectivity status

18

Installation

APPLICATION DEPENDENCY & PERFORMANCE

19

ADP Install

Main ADP Install Documentation

http://www.oracle.com/technology/documentation/oem.html Navigate through View Library Management (tab) Getting Started with Oracle Fusion Middleware Management 6 Enabling ADP Within Enterprise Manager Grid Control Take note of the Installation Quick Steps Deep links may not be stable as doc IDs change

camm_field_us mailing list forum

http://myforums.oracle.com/jive3/forum.jspa?forumID=3577 Search past questions and answers

20

ADP Install Tips

The ADP Manager install is basically identical to the 10g CAMM manager, except that there is no direct web UI Install by running install.bin or el5install.bin Ignore any popup windows that may occur when running config.sh and do everything from the Application Dependency and Performance related link from Grid Controls Middleware tab Create a database schema in advance via:
create user adp identified by adp; grant connect,resource to adp;

ADP Manager must be restarted whenever Resource configuration is changed

21

ADP Deployment Tips

OMS contains all of the UI (JSP) pages, which are populated with data from the JVMD manager OMS talks to ADP Manager via Sun RMI (ports 51099 and 55003 by default) to populate data for every ADP page ADP Manager calls to every WLS server in the domain (admin & managed) via T3 ADP Agent calls back to ADP Manager via Sun RMI (ports 51099 and 55003 by default)

22

ADP Deployment Tips

ADP Agent contains 3 parts
HTTPDeployer Servlet that is deployed only to Admin server, allows ADP Manager to download T3/EJB/JMX client libraries specifically to the version/SP of WLS installed (provider jars) Deployer EJB EJB ear that is deployed to all servers (admin & managed) in the domain, used to perform discovery and configure the agent Agent Bytecode instrumentation libraries loaded by startup args (classpath, -Xbootclasspath/p, -javaagent) that collects core metrics

23

ADP Deployment Tips

ADP Manager tracks agent status in the CAMM or Status node (name varies depending on version, its always the last node in the navtree click on it, dont unfold it)
EJB Installed = False Deployer EJB is not deployed, no further status is available Agent Status = DEPLOYED Deployer EJB is reachable, but Agent is not able to connect back to the ADP manager this is an acceptable state for the admin server Agent Status = CONNECTED Agent is able to connect to the manager but has not started delivering metrics (this state is usually transient and should last for < 5 mins) Agent Status = REPORTING Agent is reporting metrics, this is the desired normal state for managed servers

24

QUESTIONS

25