|Oracle® Enterprise Manager Advanced Configuration
10g Release 5 (10.2.0.5)
Part Number E10954-03
|PDF · Mobi · ePub|
This appendix suggests solutions to issues that have been identified for components of Oracle Enterprise Manager.
BPEL (Business Process Execution Language) is an XML-based language for enabling task sharing across multiple enterprises using a combination of Web services. BPEL is based on the XML schema, simple object access protocol (SOAP), and Web services description language (WSDL). BPEL provides enterprises with an industry standard for business process orchestration and execution. Using BPEL, you can design a business process that integrates a series of discrete services into an end-to-end process flow. This integration reduces process cost and complexity. The BPEL language enables you to define how to:
Send XML messages to, and asynchronously receive XML messages from, remote services
Manipulate XML data structures
Manage events and exceptions
Design parallel flows of process execution
Undo portions of processes when exceptions occur
Oracle BPEL Process Manager enables enterprises to model, deploy, and manage BPEL processes. It includes a BPEL business process modeler, a scalable BPEL runtime engine, an extensible WSDL binding framework, and a monitoring console.
BPEL targets can be discovered in Oracle Enterprise Manager. After the discovery of the BPEL target, the BPEL process may occasionally not be listed in the Enterprise Manager BPEL Process Manager Processes tab. There are two causes for this and two ways to ensure they display on the Processes tab. The sections below discuss these scenarios in detail.
The credentials required for monitoring the BPEL target are not provided in Enterprise Manager Grid Control. To address this, you can provide the credentials using Enterprise Manager Grid Control using the following steps.
On the BPEL Process Manager home page, click on the Monitoring Configuration link
On the 'Monitoring Configuration' page, check the following four fields:
BPEL Admin Username -- Provide the BPEL administrator user ID
BPEL Password - Provide the BPEL admin password
When adding the credentials validate the following two criteria:
BPEL Admin User ID and password should have BPEL Admin role
The same credentials should succeed for the BPEL console login operation
Initial Context Factory - In case this field is empty, please copy the string value 'com.evermind.server.rmi.RMIInitialContextFactory'
Context Provider URL - In case this field is empty, please copy the following highlighted string given below.
Note:Replace the <host>,<opmn port> with the correct host address and opmn port number details for the Oracle Application Server where the BPEL Process Manager is deployed. (Steps to retrieve <opmn port> are described in Retrieving the OPMN Port.)
Click the OK button to save the settings.
The required BPEL jar files (storage containers) are not added to agent CLASSPATH. To add the jars, follow these steps.
Log in to the host machine where SOA is installed.
Go to the ORACLE_HOME of the EM Agent installed on the same host.
Open file '$AGENT_ORACLE_HOME/sysman/config/emd.properties' as shown in figure.
Check whether the following jar files have been added to the CLASSPATH property in the file. The property must manually update with the BPEL-specific jar file names to get the process listing.
Note:The $BPEL_SERVER_ORACLE_HOME should be replaced with the absolute path of the ORACLE_HOME path of the application server where the SOA is installed.
Add the JAR filenames to CLASSPATH property. When adding the jar files to CLASSPATH, ensure that the BPEL home
optic.jar property is the first value in the classpath.
Restart the EM Agent.
To retrieve SOA Applications Server OPMN PORT details, follow these steps.
Open the configuration file
$SOA_ORACLE_HOME corresponds to SOA Application server home location.
Identify the value of the request port attribute in the configuration file.