This chapter describes how you can discover and configure the components of the SOA Suite 11g using Enterprise Manager Grid Control.
In particular, this document covers the following:
The new features that have been introduced in the 11.1 version of the SOA Suite are:
SOA Home Page: The SOA Home page provides a single view of all the SOA related artifacts being monitored by Enterprise Manager Grid Control. You can access this page by clicking on the SOA Home related link in the Middleware page.
Instance Tracing: This feature allows to trace the message flow across SOA Composites and SOA Infrastructure instances monitored by Enterprise Manager Grid Control. The message flow can be traced across servers, clusters, and WebLogic domains.
Historic Chart (Home Pages): The Home pages show real time and historic metric data. You can click on a specific metric value to view its historic trend.
The following are the versions of the SOA Suite 11g that are supported in Enterprise Manager Grid Control 11g Release1:
Oracle SOA Suite 11g PS1
Oracle SOA Suite 11g PS2
The following describes the overall process involved in discovering and monitoring SOA Suite 11g in Enterprise Manager Grid Control. Follow the instructions outlined against each step in this process to successfully discover and monitor the SOA Suite.
Table 7-1 Understanding the Discovery Process
| Oracle SOA Suite Version | Application Server Deployed To | Discovery Mechanism | Process |
|---|---|---|---|
|
Oracle SOA Suite 11.1 PS2 |
Oracle WebLogic Managed Server |
Manual Discovery |
|
This section describes the procedure for discovering the SOA Suite 11g. You can use a local or a remote Management Agent to perform the discovery process. In the case of discovery using a local agent, you need to use a Management Agent that is running on the same host as the Administration Server.
Login to Oracle Enterprise Manager Grid Control.
Click Targets and then Middleware.
Oracle Enterprise Manager Grid Control displays the Middleware page that lists all the middleware targets being monitored.
In the Middleware page, from the Add list, select Oracle Fusion Middleware / WebLogic Domain and click Go. Specify the Administration Server Host, Port, User Name, Password, Agent (local or remote) and the JMX Protocol and click Continue.
You will return to the Middleware page. You will see the SOA instances under the WebLogic Domain.
Note:
New SOA Composites are not displayed by default. To display all the SOA Composites, navigate to the Home page of the WebLogic Server target and select the Refresh Domain option from the menu.You can discover the SOA Suite 11.g using a remote agent which may be running on a host that is different from the host on which the Administration Server is running. In this case, you may not be able to perform certain operations like instance tracing and viewing recoverable instances. To ensure that all metrics are collected, you must copy the following jar files to the agent home path at $AGENT_HOME/sysman/jlib/extjlib (if the extjlib directory does not exist, it can be created)
soa-infra-mgmt.jar
oracle-soa-client-api.jar
After discovering the SOA Suite 11g, you must perform the following additional configuration steps:
Set the instance state in the Common Properties page:
Click Fusion Middleware Control on the SOA Infrastructure Home Page.
Navigate to the Home page of the SOA Infrastructure target.
Select Common Properties from the SOA-Infra drop-down menu.
On the Common Properties page, select the Capture Composite Instance State check box.
Set the SOA database details like the host name, port, and credentials.
Navigate to the Middleware page in Enterprise Manager Grid Control.
Select a SOA Infrastructure home from the list and click Configure.
The SOA Infrastructure Home page is displayed. Click Monitoring Configuration from the SOA-Infra drop-down menu.
Set the SOA database details in the Monitoring Configuration page.
Set preferred credentials for the WebLogic Domain.
Click the Preferences link in the top-right corner of the main page in Enterprise Manager Grid Control.
In the Preferences page, click Preferred Credentials on the right pane.
Select the Oracle WebLogic Domain target and click the Set Credentials icon.
On the Oracle WebLogic Domain Preferred Credentials page, in the Target Credentials section, specify the administrator credentials and host credentials and click Apply.
Similarly, on the Preferences page, select the Host target and click the Set Credentials icon.
On the Host Preferred Credentials page, in the Target Credentials section, specify the normal credentials and privileged credentials. Then click Apply.
To enable Instance Tracing for any SOA Infrastructure instances involved in executing composite instances:
Follow the sequence listed under Step 3 of the Post Discovery Steps section.
To view the state of the listed instances, enable the Capture Composite State flag by following the sequence listed Step 1 of the Post Discovery Steps section.
If the SOA instance is being monitored by the ADP Manager, additional metrics such as Arrival Rate, Minimum, Maximum, and Average Response Time will be collected.
Tip:
The ADP Manager must be registered before it can collect the metric data. For details on registering the ADP Manager, see Installing and Configuring Application Dependency and PerformanceThis section describe the procedure to create SOA Reports.
To access the reports wizard, click the Reports tab on the Enterprise Manager Console Home page.
On the Report Definitions tab, select the SOA Composite target type and click Go.
The out-of-box SOA reports are displayed under the SOA Performance Reports section.
Select a report from the section (for example, you can select Pending Instance Statistics) and click Create Like. The Create Report Definition page is displayed.
In the General page, enter the following details:
Enter the BPEL Process Name as the title.
Click the Set Time Period to set the time interval for the report.
Click the Run report using target privileges of the Report Owner (SYSMAN) checkbox in the Privileges section.
Click the Elements tab and click the Set Parameters icon for the Pending Instance Statistics Element in the table.
In the Set Parameters page, click the torch icon to select a Composite Name. The Result Set Size with default values for the Pending Instance Statistics report is displayed.
Select a Component Name from the list, enter the Result Set Size and click Continue to return to the Elements page.
The selected target name is displayed in the Elements table.
To schedule periodic report generation, click the Schedule tab.
Specify the schedule type and other details and click OK.
You will return to the Report Home page where the newly scheduled report is displayed in the table. Click the report name to view the details.
The SOA Artifacts Deployment Procedure allows you to:
Provision SOA Artifacts from a reference installation or from a gold image
Create a gold image of the SOA Artifacts
Provision SOA Composites either from the Software Library or from another accessible location.
For more details on the SOA Artifacts Deployment Procedure, see the Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching.
This section describes the errors you might encounter while discovering the SOA Suite 11g and the workaround steps you can follow to resolve each of them.
This section covers the following:
The following error occurs when the SOA instances are being discovered.
| Error Message | Workaround Steps |
|---|---|
New SOA Composite deployed on the SOA Server from JDeveloper are not displayed automatically in Enterprise Manager Grid Control. |
To discover the newly deployed SOA Composites in Enterprise Manager Grid Control, you must run the Refresh Farm menu option for the associated Weblogic Domain. |
The following error occurs when the collection frequency causes a delay in the collection of configuration data.
The following error occurs when the instance is traced.
Instance Search Fails - Same reason as BPEL first column. If Management Agent is down or unreachable.
| Error Message | Workaround Steps |
|---|---|
Instance Tracing Job Fails |
|
The following errors occur when:
All instances with faults are not displayed as only the last 10 values are collected.
The most recently collected fault instances do not appear in the Faults and Messages page.
| Error Description | Workaround Steps |
|---|---|
All instances with faults are not populated in Enterprise Manager Grid Control. |
By default, you can only view the latest 10 faults collected during the last 15 minutes. To view additional faults, navigate to Fusion Middleware by clicking the link in the General section on the target Homepage. |
When you click on the Application Dependency and Performance link in the SOA Instance Home page, you may see a blank page. This error may occur if:
Application Dependency and Performance is not being used to monitor the SOA instance.
Application Dependency and Performance has not been registered in Enterprise Manager Grid Control.
This section lists report related errors.
| Error Description | Workaround Steps |
|---|---|
Report generation fails due to invalid database details. |
|
No targets found message for Oracle SOA Composite Reports. |
You cannot use the out-of-box reports directly. You must use the Create Like option to generate custom reports based on the SOA Composite Target type. |
|
Report generation fails due to invalid host details. |
Set valid credentials for the host target on which the SOA Infrastructure instance is running. |
The following error occur when you try to refresh a service that has not been created.
| Error Message | Workaround Steps |
|---|---|
Create Service option does not work. |
System and service creation depends on the configuration collection of the SOA Infrastructure and related targets. Check the log file for details. |
Refresh Service option does not work. |
The Refresh Service function works for an existing Infrastructure service. In case the service does not exist, it should be created using the Create Service menu option. |
The following error occurs when invalid credentials are provided.
| Error Message | Workaround Steps |
|---|---|
Invalid Host and WebLogic Domain Credentials |
For the BPEL Recovery functionality to work, the host credentials and WebLogic Domain credentials must to be available in the preferred credential store. Set the valid credentials and try again. |
|
BPEL Processes disappear on the BPEL Process tab. |
This error may occur due to the missing parameter required for the DMS metric. To resolve this issue:
Example:
|