5-10 Oracle Fusion Middleware Integration Guide for Oracle Enterprise Repository
MAXIMUM, STANDARD_DEVIATION, SAMPLE_COUNT, COLLECTION_ TIMESTAMP, ROLLUP_TIMESTAMP, NOW, DETAILS_URL}.
The CURRENT rollup period does not support columns AVERAGE, SUM, MINIMUM, MAXIMUM, STANDARD_DEVIATION, SAMPLE_COUNT,
or ROLLUP_TIMESTAMP.
The DAILY, WEEKLY and MONTHLY rollup periods doe not support columns VALUE or COLLECTION_TIMESTAMP.
NOW is a virtual column that contains the time of the query against EM.
DETAILS_URL is a virtual column that contains a URL to the detailed information in EM. This is constructed by the EM Integration code - its
not in the EM database views.
– oerField: The internal name of the custom data field in Oracle Enterprise
Repository where this data is stored.
– overwrite: Indicates whether to overwrite the custom data field in Oracle
Enterprise Repository if it already has data. It represents either true or false, by default the value is true, if not specified.
Figure 5–2 Metric Mappings
5.3.2.2 Target Finders
The logic for correlating targets in EM with assets in Oracle Enterprise Repository is different for each target type. EM Integration ships with target finders for the
following products: Oracle Service Bus, BPEL-PM, WebLogic.
If you are an advanced user, then you can create your own target finder classes. These must be configured in em-integration-settings.xml, as shown in
Figure 5–3 .
■
targetFinder: Mappings for a target type in EM to a target finder class. This element has the following attributes
– targetType: The EM target type from the EM database views.
– targetFinderClass: The fully-qualified classname of the finder class. This
must implement com.oracle.oer.integration.em.TargetFinder, which is found in em-integration.jar.
Enterprise Manager Integration Utility 5-11
Figure 5–3 Target Finders
5.3.2.3 Logging
EM Integration uses log4j for logging the detailed tasks performed and the log file is placed in the EM Integration Home. The logging options can be changed by
updating the log4fl.properties file located in the EM Integration folder.
5.4 Encrypting the Configuration File Passwords
To ensure security, the passwords in the configuration file must be encrypted before running the Enterprise Manager Integration utility. You can encrypt the configuration
file passwords in the EM using either of the following methods:
■
From the Command Prompt
■
From the Oracle Enterprise Repository Web Console
From the Command Prompt 1.
Navigate to the em_integration_home directory.
2. From a command prompt, run the password encryption tool as follows:
encrypt.bat em-integration-settings.xml em-integration-settings.xml
The password encryption tool, encrypt.batencrypt.sh, which is located in Oracle_hometoolssolutions11.1.1.x.x-OER-PasswordTools.zip, allows you to
encrypt the passwords that are stored in the configuration file, em-integration-settings.xml.
From the Oracle Enterprise Repository Web Console 1.
Navigate to the Oracle Enterprise Repository Web console at http:host:portdomaindiagencryptstrings.jsp replace host, port, and
domain to match to your computer credentials
2. Scroll down to the Tools section and click the Encrypt Strings for passwords link
to launch the Password encryption page.
3. Enter the clear text password into the String to Encrypt text box.
4. Click the Submit Query button.
5. Copy the resulting encrypted password string and paste it into the appropriate
context or properties files.
5.5 Known Issues
This section describes the following known Enterprise Manager Integration Utility issues:
5-12 Oracle Fusion Middleware Integration Guide for Oracle Enterprise Repository
5.5.1 Using Incorrect Encrypted Password
If you configure the em-integration-settings.xml file with incorrect encrypted password, then a very long stack trace is displayed. An extract from the very long
stack trace is as follows:
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElementUnk own Source
at org.apache.xerces.impl.XMLDocumentFragmentScannerImplFragmentConten Dispatcher.dispatchUnknown Source
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocumentU known Source
at org.apache.xerces.parsers.XML11Configuration.parseUnknown Source at org.apache.xerces.parsers.DTDConfiguration.parseUnknown Source
at org.apache.xerces.parsers.XMLParser.parseUnknown Source at org.apache.xerces.parsers.AbstractSAXParser.parseUnknown Source
at javax.xml.parsers.SAXParser.parseSAXParser.java:395 at org.apache.axis.encoding.DeserializationContext.parseDeserializatio
Context.java:227 at org.apache.axis.SOAPPart.getAsSOAPEnvelopeSOAPPart.java:696
at org.apache.axis.Message.getSOAPEnvelopeMessage.java:424 at org.apache.axis.handlers.soap.MustUnderstandChecker.invokeMustUnder
tandChecker.java:62 at org.apache.axis.client.AxisClient.invokeAxisClient.java:206
at org.apache.axis.client.Call.invokeEngineCall.java:2765 at org.apache.axis.client.Call.invokeCall.java:2748
at org.apache.axis.client.Call.invokeCall.java:2424 at org.apache.axis.client.Call.invokeCall.java:2347
at org.apache.axis.client.Call.invokeCall.java:1804 at com.flashline.registry.openapi.service.v300.FlashlineRegistryTrSoapB
ndingStub.authTokenCreateWithLicenseFlashlineRegistryTrSoapBindingStub.java:74 1
at com.oracle.oer.sync.plugin.writer.oer.ALERConnectionCache.getAuthTok nALERConnectionCache.java:128
at com.oracle.oer.sync.plugin.writer.oer.ALERAssetQueries.getTokenALER ssetQueries.java:82
at com.oracle.oer.sync.plugin.writer.oer.ALERAssetQueries.assetTypeQuer ByUUIDALERAssetQueries.java:159
at com.oracle.oer.sync.framework.MetadataManager.putAssetTypeMetadataM nager.java:204
at com.oracle.oer.sync.framework.impl.DefaultPluginManager.processIntro pectorDefaultPluginManager.java:104
... 5 more
6
Integration with Amberpoint 6-1
6
Integration with Amberpoint
This chapter describes how to get started with the integration of Oracle Enterprise Repository with Amberpoint.
Oracle Exchange Utility updates the endpoint asset with the performance metrics deposited by Amberpoint. The UDDIMappings.xml file contains the mapping
between the performance metrics t-models and the keys to Oracle Enterprise Repository custom fields where these metrics are populated. You can also customize
the UDDI Mapping file so that the metrics can appear on any tab mapped to any field in the tabs of any custom asset type. The following snippet describes the metrics part
in the UDDIMappings.xml file:
metrics keyedReference metricsName=DailyAvailability
alerName=availability---year---- tModelKey=uddi:amberpoint.com:management:metrics:availability keyName=Last 24
hours - Availability percentage value keyedReference metricsName=WeeklyAvailability
alerName=availability---week---- ModelKey=uddi:amberpoint.com:management:metrics:availability keyName=Last week
- Availability percentage value keyedReference metricsName=MonthlyAvailability
alerName=availability---month---- tModelKey=uddi:amberpoint.com:management:metrics:availability keyName=Last
month - Availability percentage value keyedReference metricsName=DailyAvgResponseTime
alerName=average-response-time--seconds- tModelKey=uddi:amberpoint.com:management:metrics:avgResponseTime keyName=Last
24 hours - Response Time average value in milliseconds keyedReference metricsName=WeeklyAvgResponseTime
alerName=weekly-average-response-time--milliseconds- ModelKey=uddi:amberpoint.com:management:metrics:avgResponseTime keyName=Last
week - Response Time average value in milliseconds keyedReference metricsName=MonthlyAvgResponseTime
alerName=monthly-average-response-time--milliseconds- tModelKey=uddi:amberpoint.com:management:metrics:avgResponseTime keyName=Last
month - Response Time average value in milliseconds keyedReference metricsName=DailyFaults alerName=daily-faults
Note: Integration of Oracle Enterprise Repository with Amberpoint,
which is now rebranded to Oracle Business Transaction ManagerOBTM, is supported only to product versions prior to
OBTM 11. This integration support with Oracle Enterprise Repository is not supported for OBTM 11.
