This appendix describes the changes to the metrics of the following targets:
Changes to Oracle SOA Infrastructure Metrics in Enterprise Manager Cloud Control
Changes to Oracle SOA Composite Metrics in Enterprise Manager Cloud Control
Changes to Oracle Service Bus Metrics in Enterprise Manager Cloud Control
Changes to Oracle WebLogic Server Metrics in Enterprise Manager Cloud Control
Changes to JBoss Application Server Metrics in Enterprise Manager Cloud Control
Changes to Siebel Enterprise Metrics in Enterprise Manager Cloud Control
Changes to Siebel Server Metrics in Enterprise Manager Cloud Control
The following are the changes to the metrics related to Oracle SOA Infrastructure:
The old metric SOA Infrastructure - Service Engine Detail Metrics appears on the All Metrics page to show historical data. However, there is no further collection for this metric.
The new metric SOA Infrastructure - Service Engine Detail Metrics has now moved under the target component type SOA Infrastructure Engine.
In addition, the following metrics have been introduced:
Top SOA SQL Queries
Dehydration Store Tables
In the Preupgrade Console, when you generate a health report, you might see metric collection errors for the new metrics. You can ignore these errors and proceed further. However, ensure that you provide the database credentials for this target as described in Chapter 13.
The following are the changes to the metrics related to Oracle SOA Composite:
The old metrics SOA Composite - Component Detail Metrics and SOA Composite - Services/References Detail Metrics appear on the All Metrics page to show historical data. However, there is no further collection for this metric.
The new metric SOA Composite - Component Detail Metrics has now moved under the target component type SOA Composite Component.
The new metric SOA Composite - Services/References Detail Metrics has now been divided into the following metrics:
SOA Composite Service Metric that appears under the target component type SOA Composite Service.
SOA Composite Reference Metric that appears under the target component type SOA Composite Reference.
The old metric OSB Service Metrics appears on the All Metrics page to show historical data. However, there is no further collection for this metric.
The new metric OSB Service Metrics has now been divided into the following metrics:
OSB Proxy Service Metrics that appears under the target component type OSB Proxy Service.
OSB Business Service Metrics that appears under the target component type OSB Business Service.
The following configuration metrics are collected for the J2EE Application target, and not for the Oracle WebLogic Server target.
General
Web Services
Web Service Ports
JRF Web Services
JRF Web Services Ports
JRF Web Services Operations
JRF Web Services Policy References
Web Modules
EJB Modules
The following configuration metrics are available for Oracle WebLogic Server version 7, 8, and 9 and higher:
General
Web Modules
EJB Modules
The following configuration metrics are available for Oracle WebLogic Server version 9 and higher:
Web Services
Web Service Ports
The configuration metric JDBC Datasource is now available for all Oracle WebLogic Server targets.
The data for JDBC Multi Datasource was earlier collected by the metric JDBC Datasource. Now the data is collected by the metric JDBC Multi Datasource.
The data for JDBC Connection Pool was earlier collected by the metric JDBC Connection Pool. However, this metric is no longer available. All the data collected by that metric has now been moved to the metric JDBC Datasource.
These are configuration metrics, and therefore, they do not appear on the All Metrics page. Instead, they appear on the Last Collected page of the J2EE application.
In the earlier releases of Enterprise Manager, for monitoring JBoss Application Server, the Management Agent required some JAR files listed in the following file of the agent home:
$<AGENT_HOME>/sysman/config/classpath.lst
This file was populated during discovery, and the Management Agent had to restart to honor the JAR files location and append to its classpath.
In Enterprise Manager Cloud Control, the classpath.lst file is not used because there is a dynamic classloader that loads the classes specific to the target after discovery. So the Management Agent need not restart.
There is a new target instance property Library Path that is added to the target metadata. This property is needed by the monitoring logic to differentiate between the case of local and remote monitoring (target monitored by a local or remote agent).
In the case of local monitoring, this property is null.
In the case of remote monitoring, this property is set to the library path location you provide during discovery, which contains the JAR files required for discovering and monitoring JBoss.
During upgrade, ignore this error.
After upgrade, the monitored target status shows as down and no metrics are collected. So set the Library path instance property on the Monitoring Configuration page of the target. Set it to the JAR files location.
All the metrics available for Siebel Enterprise target have been moved to Siebel Gateway target in Enterprise Manager Cloud Control. As a result, to view the ECM metrics, access the Siebel Gateway target.
In the earlier releases of Enterprise Manager, for SARM reports, event log, server process control, and workflow processes, you were required to set only the preferred credentials of the hosts on which Siebel Server and Siebel Gateway Server were running. However, in Enterprise Manager Cloud Control, for these features, you must set several other credentials, besides the host credentials. This section describes the different credentials you must set for various Siebel target types.
This section covers the following:
For Siebel Server, set the following credentials:
| Host Preferred Credentials | To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, select Host and click Manage Preferred Credentials. On the Host Preferred Credentials page, set the operating system credentials of the host on which the Siebel Server is running. |
| Host Credentials for Siebel Server | To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, select Siebel Server and click Manage Preferred Credentials. On the Siebel Server Preferred Credentials page, in the Target Preferred Credentials section, select the credential set Host Credentials, and click Set to set the operating system credentials of the host on which the Siebel Server is running. |
| Server Manager Credentials for Siebel Server | To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, select Siebel Server and click Manage Preferred Credentials. On the Siebel Server Preferred Credentials page, in the Target Preferred Credentials section, select the credential set Server Manager Credentials, and click Set to set the server manager credentials. |
For Siebel Gateway Server, set the following credentials:
| Host Preferred Credentials | To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, select Host and click Manage Preferred Credentials. On the Host Preferred Credentials page, set the operating system credentials of the host on which the Siebel Gateway Server is running. |
| Host Credentials for Siebel Gateway Server | To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, select Siebel Gateway Server and click Manage Preferred Credentials. On the Siebel Gateway Server Preferred Credentials page, in the Target Preferred Credentials section, select the credential set Host Credentials, and click Set to set the operating system credentials of the host on which the Siebel Gateway Server is running. |
| Server Manager Credentials for Siebel Gateway Server | To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, select Siebel Gateway Server and click Manage Preferred Credentials. On the Siebel Gateway Server Preferred Credentials page, in the Target Preferred Credentials section, select the credential set Manage Preferred Credentials, and click Set to set the server manager credentials. |
For Siebel Database Repository, set the Siebel DBStore Credentials.
To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, select Siebel Database Repository and click Manage Preferred Credentials. On the Siebel Database Repository Preferred Credentials page, in the Target Preferred Credentials section, select the credential set Siebel DBStore Credentials, and click Set to set the credentials.