Before you can begin using the Management Pack, you must create an adapter instance to identify the host from which the Management Pack will retrieve data.

Procedure

  1. Log in to vRealize Operations as an admin user.
  2. Click the Administration administration_icon icon. In the right panel, the Solutions view will be displayed.
  3. Select Oracle EM Adapter from the Solutions list.
    Screen Shot 2018-12-06 at 11.39.24 AM
  4. Click the Configure configure_icon icon. The Manage Solution window will appear.
    Note: Click the Add add_icon icon above the Instance Name list on the left to create multiple adapter instances.

    Screen Shot 2018-12-06 at 11.40.48 AM
  5. In the Manage Solution window, enter the following information:
    1. Instance Settings:
      • Display Name: A name for this particular instance of the Management Pack.

      • Description: Optional, but it can be helpful to describe multiple adapter instances of the Management Pack.
    2. Basic Settings:
      • JDBC URL: Enter <host> and <SID> for the default JDBC URL provided; however, the entire URL can be altered if necessary for your environment.
      • Resource Kinds: See: Resource Kinds Options below.
      • Support Oracle DB Lifecycle MP: Default is False; if you select True for this option, you must have the appropriate license in place first.
      • Support AutoDiscovery: Should be True.
      • Credential: Select the credential you created when Creating a Credential (OEM).
    3. Advanced Settings:
      • Collectors/Groups: The collector you select determines which vRealize Operations Manager collector is used to manage the adapter processes. Default Collector/Group is automatically selected. Click the drop-down menu if you want to run the collection on a different node.
      • OEM Target Groups to Collect: Optional; to filter resources by OEM target groups, type the target group name(s), separated by commas. This will only return resources that are a member of one or more listed target groups.
      • Collect Incidents: True/False; default is True.
      • UI Hostname: Optional; allows you to set the OEM Hostname used to link from Alerts in vROps to the corresponding Alert in Enterprise Manager. If blank, the link defaults to using the OMR hostname.
      • Relationship Association Black List: Comma-separated list of relationship types to disable; if left blank, all relationships are enabled.
  6. Click Test Connection to test the configured connection information.
  7. Click Save Settings and Close to save your adapter instance.

Results

Resource Kinds Options

There are several options available from the Resource Kinds setting drop-down menu. Each selection predefines a set of target_types that the Management Pack imports into vROps from Oracle Enterprise Manager. See the Resource Kinds Selection Target Types table below.


Screen Shot 2018-12-06 at 11.44.12 AM

Resource Kinds Selection Target Types

target_type in Enterprise Manager Display Name in vRealize Operations
All Resource Kinds
Any target that is currently in the monitored EM box will be brought back as a resource in vRealize. Especially for large EM installs, this should usually only be used with additional filtering options.
Database, Host, Listener (Default)

host

OEM – Host

oracle_database

OEM – Database Instance

oracle_listener

OEM – Listener

oracle_emd

OEM – Oracle Management Agent

oracle_oms

OEM – Oracle Management Service

oracle_oms_console

OEM – OMS Console

oracle_oms_pbs

OEM – OMS Platform

Default + Oracle VM
host OEM – Host
oracle_database OEM – Database Instance
oracle_listener OEM – Listener
oracle_emd OEM – Oracle Management Agent
oracle_oms OEM – Oracle Management Service
oracle_oms_console OEM – OMS Console
oracle_oms_pbs OEM – OMS Platform
oracle_vm_server_pool OEM – VM Server Pool
oracle_vm_server OEM – VM Server
oracle_vm_guest OEM – VM Guest
Default + RAC, ASM Related

host

OEM – Host

oracle_database

OEM – Database Instance

oracle_listener

OEM – Listener

oracle_emd

OEM – Oracle Management Agent

oracle_oms

OEM – Oracle Management Service

oracle_oms_console

OEM – OMS Console

oracle_oms_pbs

OEM – OMS Platform

rac_database

OEM – Cluster Database

osm_cluster

OEM – Cluster ASM

osm_instance

OEM – Automatic Storage Management

osm_ioserver

OEM – ASM IO Server

osm_proxy

OEM – ASM Proxy

Default + Siebel Related

host

OEM – Host

oracle_database

OEM – Database Instance

oracle_listener

OEM – Listener

oracle_emd

OEM – Oracle Management Agent

oracle_oms

OEM – Oracle Management Service

oracle_oms_console

OEM – OMS Console

oracle_oms_pbs

OEM – OMS Platform

siebel_component

OEM – Siebel Component

siebel_component_group

OEM – Siebel Component Group

siebel_dbstore

OEM – Siebel Database Store

siebel_enterprise

OEM – Siebel Enterprise

siebel_gateway

OEM – Siebel Gateway

siebel_server

OEM – Siebel Server

host

OEM – Host

oracle_database

OEM – Database Instance

oracle_listener

OEM – Listener

oracle_emd

OEM – Oracle Management Agent

oracle_oms

OEM – Oracle Management Service

oracle_oms_console

OEM – OMS Console

oracle_oms_pbs

OEM – OMS Platform

weblogic_cluster

OEM – Oracle WebLogic Cluster

weblogic_domain

OEM – Oracle WebLogic Domain

weblogic_domain_group

OEM – Oracle WebLogic Domain Group

weblogic_j2eeserver

OEM – Oracle WebLogic Server

Default + WebLogic Related

host

OEM – Host

oracle_database

OEM – Database Instance

oracle_listener

OEM – Listener

oracle_emd

OEM – Oracle Management Agent

oracle_oms

OEM – Oracle Management Service

oracle_oms_console

OEM – OMS Console

oracle_oms_pbs

OEM – OMS Platform

weblogic_cluster

OEM – Oracle WebLogic Cluster

weblogic_domain

OEM – Oracle WebLogic Domain

weblogic_domain_group

OEM – Oracle WebLogic Domain Group

weblogic_j2eeserver

OEM – Oracle WebLogic Server

Default + WebLogic, RAC, ASM, Siebel Related
host

OEM – Host

oracle_database

OEM – Database Instance

oracle_listener

OEM – Listener

oracle_emd

OEM – Oracle Management Agent

oracle_oms

OEM – Oracle Management Service

oracle_oms_console

OEM – OMS Console

oracle_oms_pbs

OEM – OMS Platform

weblogic_cluster

OEM – Oracle WebLogic Cluster

weblogic_domain

OEM – Oracle WebLogic Domain

weblogic_domain_group OEM – Oracle WebLogic Domain Group
weblogic_j2eeserver OEM – Oracle WebLogic Server

rac_database

OEM – Cluster Database

osm_cluster

OEM – Cluster ASM

osm_instance

OEM – Automatic Storage Management

osm_ioserver

OEM – ASM IO Server

osm_proxy

OEM – ASM Proxy

siebel_component

OEM – Siebel Component

siebel_component_group

OEM – Siebel Component Group

siebel_dbstore

OEM – Siebel Database Store

siebel_enterprise

OEM – Siebel Enterprise

siebel_gateway

OEM – Siebel Gateway

siebel_server

OEM – Siebel Server

Use oem.properties

This will allow you to define a custom set of target types to bring in by creating a comma-separated list of EM target_types in the ‘allowedResourceKinds’ field of oem.properties. The available target types will vary depending on what a given EM system is monitoring.

To see a complete list for your system, connect to the OMR and run: select distinct target_type, type_display_name from mgmt$target;

What to do next