Upload
others
View
13
Download
0
Embed Size (px)
Citation preview
VMWARE VREALIZE OPERATIONS MANAGEMENT PACK FOR
Oracle Enterprise Manager
Installation & Configuration Guide
2 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
NOTE: This document supports the version of each product listed, as well as all subsequent versions, until a new edition replaces it.
You can find the most up-to-date technical documentation on the Blue Medora support site at: http://support.bluemedora.com.
The Blue Medora website also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected].
1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32. Installation and Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 Credential Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33. Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44. Installing the Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1 Uploading the Installation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64.2 Adding a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5. Configuring the Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1 Creating an Adapter Instance and Credential . . . . . . . . . . . . . . . . . . . . . . . . . . 95.2 Manually Discovering Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155.3 Configuring the Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175.4 Configuring the Resource Groups to Collect . . . . . . . . . . . . . . . . . . . . . . . . . .185.5 Validating Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
6. Appendix I: Management Pack Folders and Files . . . . . . . . . . . . . . . . . . . . . . . . . . .207. Appendix II: Revision Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
TABLE OF CONTENTS
3 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
1. Purpose
The Blue Medora VMware vRealize Operations (vROps) Management Pack for Oracle Enterprise Manager (OEM) Installation and Configuration Guide describes how to install and configure Blue Medora’s VMware vRealize Operations Management Pack for Oracle Enterprise Manager (OEM).
2. Installation and Configuration Requirements
Before installing and configuring the Management Pack for Oracle Enterprise Manager, ensure your system meets the following requirements:
Table 1: Management Pack Installation & Configuration Requirements
VREALIZE OPERATIONS (VROPS) REQUIREMENTS
ORACLE ENTERPRISE MANAGER (OEM) REQUIREMENTS
VERSION(S) vRealize Operations v6.2+(Enterprise edition only)
Oracle Enterprise Manager• 11g• 12c• 13c
CREDENTIALS N/A Oracle Enterprise Manager User Name/Password
NOTE: Refer to section “2.1 Credential Requirements” for information about granting the least amount of permissions for a user.
CONNECTION vROps hostname or IP address The Management Pack for Oracle Enterprise Manager requires a JDBC connection to the Oracle Enterprise Manager database.
The connection has the following requirements:• You must open an Oracle JDBC port on the
firewall. The default port number is 1521.• You must use a valid Oracle JDBC connection
URL (e.g., jdbc:oracle:thin:@<host>:port:<SID>).
2.1 Credential Requirements
The user account that the Management Pack uses to connect to the Oracle Enterprise Manager database must have read access to the following SYSMAN database views:
• MGMT$AVAILABILITY_CURRENT• MGMT$DB_ASSOC_DATA• MGMT$DB_CPU_USAGE• MGMT$DB_DATAFILES• MGMT$DB_DBNINSTANCEINFO• MGMT$DB_SGA• MGMT$GROUP_MEMBERS
• MGMT$HW_NIC• MGMT$INCIDENTS• MGMT$METRIC_CURRENT• MGMT$METRIC_DETAILS• MGMT$TARGET• MGMT$TARGET_ASSOCIATIONS
4 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
3. Licensing Requirements
When purchased individually, the Management Pack for Oracle Enterprise Manager is licensed per instance.
Alternatively, customers who have purchased Blue Medora’s True Visibility Suite (Standard, Advanced, or Enterprise) can access all management packs within that suite (and the edition below it, if applicable). The Management Pack for Oracle Enterprise Manager is part of Blue Medora’s Enterprise True Visibility Suite (TVS), which means a TVS Enterprise license is required to use it. For more information, visit http://www.bluemedora.com/true-visibility-suite-for-vmware/.
A license key will be provided by Blue Medora when the Management Pack or True Visibility Suite is purchased and must be added as an Oracle EM Adapter License within vRealize Operations before the Management Pack can be configured and used. Refer to section “4.2 Adding a License Key” for details.
This release of the vROps Management Pack for Oracle Enterprise Manager queries 13 distinct views (refer to Table 2) within the Oracle Enterprise Manager management repository in order to ingest metrics from OEM. Access to a subset of these management repository views require one or more Oracle Management Packs be licensed from Oracle in order to access the data within the views. A representative set of the most common Oracle Management Packs used in typical Enterprise Manager environments are:
• Database Lifecycle Management Pack for Oracle Database• Diagnostics Pack for Oracle Database• WebLogic Server Management Pack Enterprise Edition
Before installing the Blue Medora vRealize Operations Management Pack for Oracle Enterprise Manager, you must verify that appropriate Oracle Management Pack licenses are in place for each of the Oracle targets for which you wish to ingest data into vROps. Failure to do so will expose your organization to significant licensing risks.
Warning! Simply turning off access to Oracle Management Packs for each Oracle target from within the OEM user interface is not sufficient to prevent license exposure when directly querying the OMR via JDBC (as the vROps Management Pack for Oracle Enterprise Manager does). Per Oracle requirements, “Any and all methods of accessing Oracle Diagnostics Pack functionality, whether through Enterprise Manager Console, Desktop Widgets, command-line APIs, or direct access to the underlying data, requires an Oracle Diagnostics Pack license.”
Please refer to the Oracle Enterprise Manager Cloud Release 13.1 Licensing Information Guide for more information on Oracle Management Pack licensing requirements.
5 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
Table 2: List of OEM Management Repository (OMR) Views queried by the Management Pack for OEM
OMR VIEW QUERIED BY THE MANAGEMENT PACK
LICENSED ORACLE MPS REQUIRED TO QUERY VIEW
WHY IS THE VIEW QUERIED?
MGMT$AVAILABILITY_CURRENT
Diagnostics Pack for Oracle Database (if monitoring Databases or Oracle Hosts)
WebLogic Server Management Pack Enterprise Edition (if monitoring WebLogic)
Provides availability status information for each Oracle target
MGMT$DB_ASSOC_DATA None Provides metadata for Oracle databases
MGMT$DB_CPU_USAGE None Contains CPU utilization data for Oracle databases
MGMT$DB_DATAFILES Database Lifecycle Management Pack for Oracle Database
Provides details on Oracle database data files
MGMT$DB_DBNINSTANCEINFO Database Lifecycle Management Pack for Oracle Database
Contains configuration information for Oracle databases
MGMT$DB_SGA Database Lifecycle Management Pack for Oracle Database
Provides Oracle database SGA configuration settings for Oracle databases
MGMT$GROUP_MEMBERS None Used to determine membership in OEM groups
MGMT$HW_NIC None Provides IP addresses for EM monitored hosts
MGMT$INCIDENTS None Used to import EM incidents into vROps
MGMT$METRIC_CURRENT
Diagnostics Pack for Oracle Database (if monitoring Databases or Oracle Hosts)
WebLogic Server Management Pack Enterprise Edition (if monitoring WebLogic)
Contains the most recently collected metrics for Oracle targets
MGMT$METRIC_DETAILS
Diagnostics Pack for Oracle Database (if monitoring Databases or Oracle Hosts)
WebLogic Server Management Pack Enterprise Edition (if monitoring WebLogic)
Provides historical data for the metrics in MGMT$METRIC_CURRENT view
MGMT$TARGET NoneUsed to determine distinct Oracle targets to use as vROps ‘Resources’
MGMT$TARGET_ASSOCIATIONS NoneThis view contains data used to define relationships between Oracle ‘Resources’ in vROps
NOTE: This is not a complete list of possible required Oracle Management Packs. Please check the Oracle Enterprise Manager Cloud Release 13.1 Licensing Information Guide to verify the licensing requirements for your specific environment.
6 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
4. Installing the Management Pack
Installing the Management Pack in vRealize Operations involves completing the following tasks:• Uploading the Installation File• Adding a License Key
4.1 Uploading the Installation File
The Management Pack for Oracle Enterprise Manager is installed using a .pak file.
4.1.1 Prerequisites• Obtain the Management Pack installation file from http://www.bluemedora.com/true-visibility-suite-
for-vmware/.• Read the release notes that are included with the .pak file.
4.1.2 Procedure1. Save the .pak file in a temporary location.2. Log in to vRealize Operations as an admin user.3. Click the Home icon, then select the Administration navigation shortcut from the panel on the left.
Figure 2: Home > Administration
7 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
4. In the right panel, the Solutions tab will be displayed.
Figure 3: Solutions Tab
5. Click the Add icon ( ) to upload the .pak file to the vRealize Operations server. In the dialog that appears, browse to the location of the saved .pak file, then click Upload.
NOTE: The .pak file upload may take several minutes to complete. Status information appears in the Installation Details text box throughout the installation process.
Figure 4: Select the .pak file to upload
8 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
6. Click Next when the upload has finished. Read the End User License Agreement (EULA) and click the ‘I accept the terms of this agreement’ checkbox to accept, then click Next.
7. Click Finish when the installation process is complete.
NOTE: The installation utility creates the oem_adapter3 folder and oem_adapter3.jar file in the $VCOPS_BASE/user/plugins/inbound folder. Refer to section “6. Appendix I: Management Pack Folders and Files” for more information.
4.2 Adding a License Key
The Management Pack requires a valid license for full operation. Complete the following steps to license the Management Pack.
1. In vRealize Operations Manager, navigate to Administration > Licensing > License Keys.2. Click the Add icon ( ). In the dialog that appears, select ‘Oracle EM Adapter’.
Figure 5: Add License
3. Enter your Blue Medora license key, then click Validate. If successful, “License key validated successfully” will be displayed.
4. Click Save to finish adding your license key.
9 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
5. Configuring the Management Pack
Configuring the Management Pack for Oracle Enterprise Manager includes the following tasks:• Creating an Adapter Instance and Credential• Manually Discovering Resources (if necessary)• Configuring the Properties File• Configuring the Resource Groups to Collect• Validating Management Pack Data Collection
5.1 Creating an Adapter Instance and Credential
You must create an adapter instance and credential for the Management Pack in order to define the adapter type and identify the device(s) from which the adapter instance will retrieve data.
5.1.1 Prerequisites
Install the Management Pack for Oracle Enterprise Manager. Refer to section “4. Installing the Management Pack”.
5.1.2 Procedure1. Log in to vRealize Operations as an administrator.2. Click on the Administration navigation shortcut ( ). The Solutions view should automatically open.3. Select ‘Oracle EM Adapter’ from the Solutions list.
Figure 6: Solutions List
10 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
4. Click the Configure icon ( ). The Manage Solution window will appear.
Figure 7: Manage Solution Window
NOTE: If creating multiple adapter instances, click the Add icon ( ) above the list of Instance Names on the left.
5. In the Manage Solution window, enter the following information:
Instance Settings:• Display Name: A name for this particular instance of the Management Pack• Description: Optional; most helpful for describing multiple adapter instances of the Management
Pack
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: Refer to Figure 8 and Table 3 for more information on available selections• Support Oracle DB Lifecycle MP: Default is False; if you select True for this option, you must have
the appropriate license in place first. Refer to section “3. Licensing Requirements”, for details.• Support AutoDiscovery: Default setting is True, which enables the adapter instance to create
resources for you. If you select False, you must manually discover your Oracle Enterprise Manager resources.
• Credential: Click the Add icon ( ), then select the credential type (refer to Figure 9).
11 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
Figure 8: Resource Kinds Options
Table 3: Resource Kinds Selection Target Types
NOTE: Each selection predefines a set of target_types the Management Pack imports into vROps from Oracle Enterprise Manager.
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 + 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
12 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
target_type IN ENTERPRISE MANAGER DISPLAY NAME IN VREALIZE OPERATIONS
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
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
13 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
target_type IN ENTERPRISE MANAGER DISPLAY NAME IN VREALIZE OPERATIONS
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;
Advanced Settings:• Collectors/Groups: Automatically selected• 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
14 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
Figure 9: Manage Credential
• Credential Name: A name for this set of Management Pack credentials• User Name: Oracle Enterprise Manager User Name• Password: Oracle Enterprise Manager Password
NOTE: The following vRealize User Name/Password fields are shown only when the deprecated credential kind is selected. These fields are maintained for backward compatibility purposes only and are not necessary for proper operation of the Management Pack.
• vRealize User Name: User Name for your vRealize Operations user account• vRealize Password: Password for your vRealize Operations user account
6. Click OK to save your credential.7. Click Test Connection to ensure vRealize Operations can connect properly to the network device(s).8. Click Save Settings to save your adapter instance configuration.
15 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
5.2 Manually Discovering Resources
If AutoDiscovery was set to False when configuring the adapter instance, you will need to manually discover resources as described in this section. With manual discovery, the adapter sends a request to the Enterprise Manager to return resources, which you then manually select to import into vRealize Operations.
5.2.1 Prerequisites
Create an OEM adapter instance and credential. Refer to section “5.1 Creating an Adapter Instance and Credential”, for details.
5.2.2 Procedure1. Log in to vRealize Operations as an administrator.2. Click the Administration navigation shortcut ( ).3. Click Inventory Explorer in the navigator pane.
Figure 10: Inventory Explorer > Adapter Types
4. Under Adapter Types, select ‘OEM Adapter’.
16 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
5. Click the Discover Resources icon ( ) to open the Discover Objects window.
Figure 11: Discover Objects Window
6. In the Discover Objects window, select the following information:• The Collector to use
NOTE: Unless you added additional collectors, the only available collector is your vROps server.
• ‘OEM Adapter’ for Adapter Type• The applicable Adapter Instance• ‘Default Discovery’ for Discovery Info• Whether Only New Objects (select/de-select checkbox) should be collected
7. Click OK to start the discovery process.8. The discovery process can take several seconds to several minutes. When it has finished, the Discovery
Results window lists your resources.9. Double-click each resource kind that contains resources to add.10. Select options for each kind of resource. Refer to Table 4.
Table 4: Resource Options
OPTION DESCRIPTION
Import Import the resources but do not start collecting data. Resources appear in the resource list as Not Collecting; data is not stored; analysis is not performed.
Collect Import the resources and start collecting data. When you select the Collect check box, the Import check box is also selected.
11. Click OK. The Discovery Results window closes and the new resources appear.
5.2.3 What To Do Next
If you did not select the option to start metric collection when you defined a resource, you can start metric collection after the resource is defined. To start collecting metrics for a resource, choose the resources, then click the Start Collecting icon ( ).
17 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
5.3 Configuring the Properties File
The following settings can be found in the oem.properties file in the $VCOPS_BASE/user/plugins/inbound/oem_adapter3/conf/ folder. You can tune adapter operation by modifying the properties in the file and re-saving it. The modified properties will be read in during the next collection.
NOTE: If vROps is running in cluster mode, you must modify the oem.properties file on the collector node running the Management Pack for Oracle Enterprise Manager.
Table 5: Properties File Contents
PROPERTY DESCRIPTION DEFAULT VALUE
allowedResourceKindsComma-delimited list of allowed resource kinds. The values that you list must correspond to values in the TARGET_TYPE column in the database MGMT$TARGET view.
host, oracle_database, oracle_listener
discoverByHosts Filters by EM-monitored host(s) and returns only children of the listed host(s) blank
limitEventsToLastCollection Limits the events returned to only those created since the last collection false
mainFetchSizeNumber of records to process at a time during current metric collection. A higher value increases memory use during collection but improves data processing performance.
500
maxQueryWindow Maximum trailing time from the current time to query, in minutes. 15
minQueryWindow Minimum trailing time from the current time to query, in minutes. 1
openDataImporterHost Hostname of opendataimporter host localhost
openDataImporterPort Port to connect to on opendataimporter host 1100
resourceUpStatusesComma-delimited list of AVAILABILITY_STATUS column values that indicate a resource is available. This property determines resource availability.
Target Up
schema Schema that contains Oracle Enterprise Manager objects. SYSMAN
updateOEMHostToVMRelationshipsDetermines when Host to VM Relationships are updated. Allowed values are: {always, never, onFirstCollection}
onFirstCollection
18 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
5.4 Configuring the Resource Groups to Collect
The resourceGroups.conf file allows turning on and off resource groups. Turning off a resource group will cause it to not be collected from OEM or added into vROps. Limiting the number of resource groups results in higher performance both for OEM (faster query execution) and vROps (reduced processing and storage requirements).
This file is created when the first collection cycle starts for an adapter instance and will contain all resource groups and target types present in MGMT$METRIC_CURRENT. By default, only resource groups that are not instanced will be marked to collect (i.e., the value for the column_key value in MGMT$METRIC_CURRENT is null).
To change which resource groups are marked to collect, open the resourceGroups.conf file located in the $VCOPS_BASE/user/plugins/inbound/oem_adapter3/conf/ folder.
Each line has three fields, separated by a pipe (‘|’). The first line is the target_type, the second is the resource_group, and the third determines whether the resource group is marked to collect. To mark a resource group to collect, set the third column to ‘X’. For example, the following lines tell the adapter to collect resource_group_1, but not resource_group_2, for any resources of kind target_type_X.
target_type_X | resource_group_1 | X
target_type_X | resource_group_2 |
NOTE: If vROps is running in cluster mode, you must modify the resourceGroups.conf file on the collector node running the Management Pack for Oracle Enterprise Manager.
19 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
5.5 Validating Data Collection
After you add an OEM adapter instance, you will want to validate the data that it collects in vRealize Operations.
5.5.1 Prerequisites
Add an OEM adapter instance. Refer to section “5.1 Creating an Adapter Instance and Credential”, for details.
5.5.2 Procedure1. Select the Environment shortcut ( ).
NOTE: If you enabled AutoDiscovery for the adapter instance, it will create resources as soon as it begins collecting metrics. If you disabled AutoDiscovery for the adapter instance, you must go back and discover resources manually before you can validate data collection. Refer to section “5.2 Manually Discovering Resources”.
2. Under Inventory Trees, select All Objects, then expand the OEM Adapter objects list.3. Select a resource from the list, then click the Troubleshooting tab and All Metrics view to validate values
against the data source.
Figure 12: OEM Adapter Objects Troubleshooting
20 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
6. Appendix I: Management Pack Folders and Files
The installer places the Management Pack files in the oem_adapter3 folder under the $VCOPS_BASE/user/plugins/inbound folder as shown below.
Table 6: Management Pack Folders and Files
FOLDER FILE DESCRIPTION
conf OTN License Agreement.txt License agreement for Oracle Technology Network
dashboards (folder) Contains .json files for Management Pack Dashboards
db.properties Contains database properties
describe.xml Describes the Management Pack
historical.properties Used to enable historical mode. Allows the adapter to backfill data if collection is interrupted for any reason.
history.txt Contains the history of Management Pack changes
images (folder) Contains .png files for AdapterKind, ResourceKind, and TraversalSpec
license.properties Contains back-up copy of licenses used for this Management Pack
oem.properties Contains Management Pack configuration properties
oss_attribution.txt Describes open source libraries used by the Management Pack
reports (folder) Contains .xml files for Management Pack Reports
reskndmetrics (folder) Contains .xml files for Dashboard Metric configuration
resourceGroups.conf Controls which resource groups are collected for each Resource Kind
resources (folder) Contains resources.properties file
scripts (folder) Contains .sdm files consumed by the Management Pack
supermetrics (folder) Contains .xml files for Host and Oracle Database resources
version.txt Contains version information
views (folder) Contains .xml files for Management Pack Views
lib Refer to lib folder for entire list .jar files that contain the classes and resources used to implement the Management Pack
work install.log
lastcollection_#.properties Tracks when the last collection for each adapter instance was performed (used when historic mode is enabled)
21 Blue Medora VMware vRealize Operations Management Pack for Oracle Enterprise Manager Installation & Configuration Guide
7. Appendix II: Revision Notes
This installation guide is updated with each release of the product, or when necessary. The following table provides its revision history.
REVISION DATE DESCRIPTION
REV-16 22-FEB-2017 • Updated to fit newer organization scheme for all Management Pack docs• Updated “Table 1: Management Pack Installation & Configuration Requirements”
to reflect current Management Pack requirements• Removed “Upgrading the Management Pack” section• Updated “5.1 Creating an Adapter Instance and Credential” to include changes
made to Management Pack settings• Updated “6. Appendix I: Management Pack Folders and Files” to show current
Management Pack files• Updated screenshots throughout the document
REV-15 26-SEP-2016 • Added information regarding True Visibility Suite licensing to section “3. Licensing Requirements”
REV-14 06-JUL-2016 • Added compatibility for Oracle Enterprise Manager 13c and updated references to OEM 11g and 12c documentation to the latest release (13.1)
REV-13 17-JUN-2016 • Fixed path to /conf folder where oem.properties file is located in section “5.3 Configuring the Properties File” and to resourceGroups.conf file in section “5.4 Configuring the Resource Groups to Collect”
REV-12 30-JUL-2015 • Added “Upgrading the Management Pack” section
REV-11 30-JUN-2015 Optimized for vRealize Operations 6.0+
Copyright © 2017 Blue Medora Inc. All rights reserved. U.S. and international copyright and intellectual property laws protect this product. Blue Medora is a registered trademark or trademark of Blue Medora in the United States and/or other jurisdictions.
The Oracle name (including Oracle Enterprise Manager) and logo are trademarks or registered trademarks of Oracle Corporation in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
Blue Medora3225 N Evergreen Dr. NE Suite 103Grand Rapids, MI 49525
bluemedora.com
You can find the most up-to-date technical documentation on the Blue Medora support site at: http://support.bluemedora.com.
The Blue Medora website also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected].