Skip Headers
Oracle® Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management
12c Release 2 (12.1.0.2)
Part Number E24215-03
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

9 Discovering and Monitoring Oracle BPEL Process Manager

This chapter describes how you can discover and monitor Oracle BPEL Process Manager (BPEL Process Manager) using Enterprise Manager Cloud Control.

In particular, this document covers the following:

Supported Versions

The following are the versions of BPEL Process Manager that are supported for monitoring in Enterprise Manager Cloud Control.

Table 9-1 Supported Versions

Supported BPEL Process Manager Version Application Server Deployed To Supported in Enterprise Manager

Oracle BPEL Process Manager 10.1.2

Oracle Application Server 10g Release 1 (10.1.2)

Enterprise Manager 10g Release 4 (10.2.0.4) or higher

Enterprise Manager 11g

Enterprise Manager 12c

Oracle BPEL Process Manager 10.1.3.1 and 10.1.3.3

(Part of Oracle SOA Suite 10.1.3.1 and 10.1.3.3)

Oracle Application Server 10g Release 1 (10.1.3.1) and (10.1.3.3)

Enterprise Manager 10g Release 3 (10.2.0.3) or higher

Enterprise Manager 11g

Enterprise Manager 12c

Oracle BPEL Process Manager 10.1.3.1 and 10.1.3.3

(Part of Oracle SOA Suite 10.1.3.1 and 10.1.3.3)

Oracle WebLogic Managed Server 9.2

Enterprise Manager 10g Release 5 (10.2.0.5) or higher

Enterprise Manager 10 g Release 4 (10.2.0.4) with one-off patches applied. For details, see Understanding the Discovery Process.

Enterprise Manager 11g

Enterprise Manager 12c

Oracle BPEL Process Manager 10.1.3.1 and 10.1.3.3

(Part of Oracle SOA Suite 10.1.3.1 and 10.1.3.3)

IBM WebSphere Application Server 6.1

Enterprise Manager 10g Release 5 (10.2.0.5) or higher

Enterprise Manager 10g Release 4 (10.2.0.4) with one-off patches applied. For details, see Understanding the Discovery Process.

Enterprise Manager 11g

Enterprise Manager 12c

Oracle BPEL Process Manager 10.1.3.4

(Part of Oracle SOA Suite 10.1.3.4)

Oracle Application Server 10g Release 1 (10.1.3.1) and (10.1.3.3)

Enterprise Manager 10g Release 5 (10.2.0.5) or higher

Enterprise Manager 11g Release 1 (11.1.0.1)

Enterprise Manager 12c

Oracle BPEL Process Manager 10.1.3.4

(Part of Oracle SOA Suite 10.1.3.4)

Oracle WebLogic Managed Server 9.2

Enterprise Manager 10g Release 5 (10.2.0.5) or higher

Enterprise Manager 11g

Enterprise Manager 12c

Oracle BPEL Process Manager 10.1.3.4

(Part of Oracle SOA Suite 10.1.3.4)

IBM WebSphere Application Server 6.1

Enterprise Manager 10g Release 5 (10.2.0.5) or higher

Enterprise Manager 11g

Enterprise Manager 12c

Understanding the Discovery Mechanism

The following describes the mechanism followed for discovering BPEL Process Managers in Enterprise Manager Cloud Control.

Table 9-2 Mechanism for Discovering BPEL Process Managers

BPEL Process Manager Version Application Server Deployed To Discovery Mechanism Process

Oracle BPEL Process Manager 10.1.2

Oracle Application Server 10g Release 1 (10.1.2)

Manual/Automatic Discovery

  • If the Management Agent is installed before Oracle Application Server and BPEL Process Manager are installed, then you must manually discover that Oracle Application Server and BPEL Process Manager in Enterprise Manager Cloud Control.

  • If the Management Agent is installed after Oracle Application Server and BPEL Process Manager are installed, then Enterprise Manager Cloud Control automatically discovers that Oracle Application Server and BPEL Process Manager

    The Management Agent can be installed along with Enterprise Manager Cloud Control or separately as a standalone product.

For discovery procedures, see Deployed to Oracle Application Server.

Oracle BPEL Process Manager 10.1.3.1, 10.1.3.3, 10.1.3.4

(Part of Oracle SOA Suite 10.1.3.1, 10.1.3.3, 10.1.3.4)

Oracle Application Server 10g Release 1 (10.1.3.1) and (10.1.3.3)

Manual/Automatic Discovery

  • If the Management Agent is installed before Oracle Application Server and BPEL Process Manager are installed, then you must manually discover that Oracle Application Server and BPEL Process Manager in Enterprise Manager Cloud Control.

  • If the Management Agent is installed after Oracle Application Server and BPEL Process Manager are installed, then Enterprise Manager Cloud Control automatically discovers that Oracle Application Server and BPEL Process Manager

    The Management Agent can be installed along with Enterprise Manager Cloud Control or separately as a standalone product.

For discovery procedures, see Deployed to Oracle Application Server.

Oracle BPEL Process Manager 10.1.3.1, 10.1.3.3, 10.1.3.4

(Part of Oracle SOA Suite 10.1.3.1, 10.1.3.3, 10.1.3.4)

Oracle WebLogic Managed Server 9.2

Manual Discovery

First, manually discover Oracle WebLogic Managed Server. For procedures, see Discovering Oracle WebLogic Managed Server.

Then, manually discover BPEL Process Manager. For procedures, see Deployed to Oracle WebLogic Managed Server.

Oracle BPEL Process Manager 10.1.3.1, 10.1.3.3, 10.1.3.4

(Part of Oracle SOA Suite 10.1.3.1, 10.1.3.3, 10.1.3.4)

IBM WebSphere Application Server 6.1

Manual Discovery

First, manually discover IBM WebSphere Application Server. For procedures, see Discovering IBM WebSphere Application Server.

Then, manually discover BPEL Process Manager. For procedures, see Deployed to IBM WebSphere Application Server.

Oracle BPEL Process Manager 10.1.3.5

Oracle WebLogic Managed Server 10.x

Manual Discovery

First, manually discover Oracle WebLogic Managed Server. For procedures, see Discovering Oracle WebLogic Managed Server.

Then, manually discover BPEL Process Manager. For procedures, see Deployed to Oracle WebLogic Managed Server.

Understanding the Discovery Process

The following describes the overall process involved in discovering and monitoring BPEL Process Manager in Enterprise Manager Cloud Control. Follow the instructions outlined against each step in this process to successfully discover and monitor your BPEL Process Manager.

Table 9-3 Discovery Process

Step Requirement Description

1

BPEL Process Manager

Install the BPEL Process Manager software in one of the following ways:

2

Enterprise Manager Cloud Control

To monitor BPEL Process Manager 10.x, install Enterprise Manager Cloud Control 12c. For information about installing the base release of Enterprise Manager Cloud Control, see the Enterprise Manager Cloud Control Installation and Basic Configuration Guide available at:

http://www.oracle.com/technology/documentation/oem.html

Oracle recommends that you install the Enterprise Manager Cloud Control components on a host that is different from the host where the BPEL Process Manager is installed. For example, if the BPEL Process Manager is installed on host1.xyz.com, then install and configure Oracle Management Service (OMS) and the Management Repository on host2.xyz.com.

3

Oracle Management Agent

(Management Agent)

Install Oracle Management Agent 12c or higher on every host where BPEL Process Manager is installed.

If Oracle Application Server/BPEL Process Manager and Enterprise Manager Cloud Control are all on the same host, then you do not have to install a separate Management Agent. The Management Agent that comes with Enterprise Manager Cloud Control is sufficient. However, if they are different hosts, then you must install a separate Management Agent on every host where BPEL Process Manager is installed.

You can install the Management Agent in one of the following ways:

For information about installing the Management Agent, see the Enterprise Manager Cloud Control Installation and Basic Configuration Guide available at:

http://www.oracle.com/technology/documentation/oem.html

4

Discovery in Enterprise Manager Cloud Control

BPEL Process Managers deployed to Oracle Application Servers are automatically discovered in Enterprise Manager Cloud Control.

BPEL Process Managers deployed to Oracle WebLogic Managed Servers and IBM WebSphere Application Servers must be manually discovered in Enterprise Manager Cloud Control. For procedures to discover them, see Discovering BPEL Process Manager.

Setting Up Oracle Software Library

If you are using Enterprise Manager 12c to discover and monitor the BPEL Process Manager deployed to Oracle WebLogic Managed Server 9.2 and IBM WebSphere Application Server 6.1, you must set up Oracle Software Library (Software Library) as described below:

To set up the Software Library:

  1. From the Enterprise menu, select Provisioning and Patching, then select Software Library.

  2. From the Actions menu, select Administration.

  3. In the Software Library: Administration page, select the Storage Type and click Add from the Actions menu.

  4. In the Add Software Library Location window, specify a valid directory path where you want to store the raw data for the components, and click OK.

Note:

For more information about setting up the Software Library, see the Enterprise Manager Advanced Installation and Configuration Guide available at the following URL:

http://www.oracle.com/technology/documentation/oem.html

Discovering BPEL Process Manager

This section describes the procedures for discovering BPEL Process Managers. In particular, this section covers the following:

Deployed to Oracle Application Server

A BPEL Process Manager deployed to Oracle Application Server is manually or automatically discovered in Enterprise Manager Cloud Control depending on when the Management Agent is installed.

  • If the Management Agent is installed before Oracle Application Server and BPEL Process Manager are installed, then you must manually discover that Oracle Application Server and BPEL Process Manager in Enterprise Manager Cloud Control.

  • If the Management Agent is installed after Oracle Application Server and BPEL Process Manager are installed, then Enterprise Manager Cloud Control automatically discovers that Oracle Application Server and BPEL Process Manager.

Note:

You must install a Management Agent on every host where BPEL Process Manager is installed. If Oracle Application Server/BPEL Process Manager and Enterprise Manager Cloud Control are all on the same host, then you need not install a separate Management Agent. The Management Agent that comes with Enterprise Manager Cloud Control is sufficient. However, if they are different hosts, then you must install a separate Management Agent on every host where BPEL Process Manager is installed. The Management Agent can be installed along with Enterprise Manager Cloud Control or separately as a standalone product.

Also note that if you have added a new BPEL Process Manager to an Oracle Application Server that is already discovered and monitored in Enterprise Manager Cloud Control, then you must manually rediscover that Oracle Application Server.

To manually discover or rediscover Oracle Application Server:

  1. From the Targets menu, select Middleware.

    The Middleware page that lists all the middleware targets being monitored is displayed. In Enterprise Manager 10g Cloud Control Release 4 (10.2.0.4) or lower, the Middleware tab is Application Servers.

  2. (Only for Rediscovering) In the Middleware page, select the Oracle Application Server that you want to rediscover and click Remove.

  3. In the Middleware page, from the Add list, select Oracle Application Server and click Go. The Add Oracle Application Server Target: Specify Host page is displayed.

  4. Enter the name of the host where that Oracle Application Server is running, and click Continue.

    Enterprise Manager Cloud Control rediscovers that Oracle Application Server along with its core components and the newly added BPEL Process Manager.

Deployed to Oracle WebLogic Managed Server

To discover the BPEL Process Manager deployed to Oracle WebLogic Managed Server, you have to first discover and add Oracle WebLogic Managed Server to Enterprise Manager Cloud Control.

This section describes the procedures for the following:

Discovering Oracle WebLogic Managed Server

To discover and add Oracle WebLogic Managed Server to Enterprise Manager Cloud Control:

  1. From the Targets menu, select Middleware.

    Enterprise Manager Cloud Control displays the Middleware page that lists all the middleware targets being monitored. In Enterprise Manager 10g Cloud Control Release 4 (10.2.0.4) or lower, the Middleware tab is Application Servers

  2. In the Middleware page, from the Add list, select Oracle Fusion Middleware / WebLogic Server Domain, and click Go.

    Enterprise Manager Cloud Control displays the Add Oracle Fusion Middleware / WebLogic Server Domain wizard that captures the details of the Oracle WebLogic Server Domain to be discovered and monitored.

  3. In the wizard, specify the required details and click Next on each page to reach the end of the wizard.

    For information about the details to be provided for each page of the wizard, click Help on each page.

  4. In the last page of the wizard, click Finish to complete the discovery process and add the target to Cloud Control for monitoring purposes.

    Enterprise Manager Cloud Control displays the Middleware page with a confirmation message that confirms that the Oracle WebLogic Manager Server has been successfully added to Cloud Control. In the Middleware page that shows all the middleware targets being monitored, you can see the Oracle WebLogic Managed Server you just added.

Deployed to Oracle WebLogic Managed Server

To discover and add the BPEL Process Manager deployed to Oracle WebLogic Managed Server:

  1. From the Setup menu, select Add Targets, then select Add Targets Manually. Now select the Add Non-Host Targets by Specifying Target Monitoring Properties option.

  2. Select the target type from the drop-down list and click the torch icon to select a Monitoring Agent. Click Add Manually. The Select Application Server page of the Add BPEL Process Manager wizard is displayed.

    1. In the Select Application Server page, provide the following details and click Next.

      Table 9-4 Select Application Server Page - Element Description

      UI Page Element Description

      Application Server Type

      Select the type of application server where the BPEL Process Manager to be discovered is running.

      Application Server Name

      Specify the name of the application server where the BPEL Process Manager to be discovered is running. If you are not sure about the name, click the each icon (torch icon) to view a list of application servers and select the appropriate one. The application server name must be suffixed with oracleBPELServer.

    2. In the Target Details page, provide the following details and click Next.

      Table 9-5 Target Details Page - Element Description

      UI Page Element Description

      Oracle Home

      Specify the full path to the Oracle Application Server home directory where the BPEL Process Manager is installed. For example, /opt/app/orabpel/product/10.1.3.1/OracleAS.

      Application Server Home

      Specify the full path to the directory where Oracle WebLogic Managed Server (to which the BPEL target is deployed) is running. For example, /opt/wls9.2/weblogic9.2.

      Note:

      • Enterprise Manager Cloud Control checks the configuration settings of the associated application server and prefills the values for fields such as BPEL Process Manager Name, Display Name, Context Provider URL, and Oracle BPEL PM Console URL.

      • At this point, if you encounter a discovery failure error, then follow the workaround steps given in Table 9-9 to resolve the issue.

    3. In the Host Credentials page, specify the operating system credentials of the host where BPEL Process Manager is running. By default, the fields are prefilled with preferred credentials that are stored in the Management Repository for the selected host. You can either use these prefilled values or edit them to override the preferred credentials with your new credentials.

    4. In the Review page, review the details and click Finish to complete the discovery process and add the target to Enterprise Manager Cloud Control.

      Enterprise Manager Cloud Control displays the Agent home page with a confirmation message that confirms that the BPEL Process Manager has been successfully added for monitoring.

  3. To verify whether the BPEL Process Manager has been added, click Targets and then Middleware.

    Enterprise Manager Cloud Control displays the Middleware page that shows all the middleware targets being monitored, including the Oracle WebLogic Managed Server and the BPEL Process Manager you just added.

Deployed to IBM WebSphere Application Server

To discover the BPEL Process Manager deployed to IBM WebSphere Application Server, you have to first discover and add IBM WebSphere Application Server to Enterprise Manager Cloud Control.

This section describes the procedures for the following:

Discovering IBM WebSphere Application Server

To discover and add IBM WebSphere Application Server to Enterprise Manager Cloud Control:

  1. From the Targets menu, select Middleware.

    Enterprise Manager Cloud Control displays the Middleware page that lists all the middleware targets being monitored.

  2. In the Middleware page, select IBM WebSphere Application Server from the Add drop-down list and click Go.

    Enterprise Manager Cloud Control displays the Add IBM WebSphere Application Server wizard that captures the details of the IBM WebSphere Application Server to be discovered and monitored.

  3. In the Add IBM WebSphere Application Server wizard, specify the required details and click Next on each page to reach the end of the wizard.

    For information about the details to be provided for each page of the wizard, click Help on each page.

  4. In the last page of the Add IBM WebSphere Application Server wizard, click Finish to complete the discovery process and add the target to Enterprise Manager Cloud Control for monitoring purposes.

    Enterprise Manager Cloud Control displays the Middleware page with a confirmation message that confirms that the IBM WebSphere Application Server has been successfully added for monitoring. In the Middleware page that shows all the application server being monitored, you can see the IBM WebSphere Application Server you just added.

Deployed to IBM WebSphere Application Server

To discover and add the BPEL Process Manager deployed to IBM WebSphere Application Server:

  1. From the Setup menu, select Add Targets, then select Add Targets Manually. Now select the Add Non-Host Targets by Specifying Target Monitoring Properties option.

  2. Select the target type from the drop-down list and click the torch icon to select a Monitoring Agent. Click Add Manually. The Select Application Server page of the Add BPEL Process Manager wizard is displayed.

    1. In the Select Application Server page, provide the following details and click Next.

      Table 9-6 Select Application Server Page - Element Description

      UI Page Element Description

      Application Server Type

      Select IBM WebSphere Application Server from the list.

      Application Server Name

      Specify the name of IBM WebSphere Application Server where the BPEL Process Manager to be discovered is running. If you are not sure about the name, click the search icon (torch icon) to view a list of application servers and select the appropriate one. The application server name must be suffixed with oracleBPELServer.

    2. In the Target Details page, provide the following details and click Next.

      Table 9-7 Target Details Page - Element Description

      UI Page Element Description

      Oracle Home

      Specify the full path to the Oracle Application Server home directory where the BPEL Process Manager is installed. For example, /opt/app/orabpel/product/10.1.3.1/OracleAS.

      Application Server Home

      Specify the full path to the directory where IBM WebSphere Application Server (to which the BPEL target is deployed) is running.

      BPEL Application Installation Location

      Specify the full path to the installation directory where the BPEL application is installed.For example, if the BPEL application is installed in <$WEBSPHERE_HOME>/profiles/AppSrv01/installedApps/sta00114Cell01/CollaxaWebApplications-sta00114Node01.ear, then specify the path as <$WEBSPHERE_HOME>/profiles/AppSrv01/installedApps. Here, replace $WEBSPHERE_HOME with the full path of the application home location.

      Note:

      Enterprise Manager Cloud Control checks the configuration settings of the associated application server and prefills the values for fields such as BPEL Process Manager Name, Display Name, Context Provider URL, and Oracle BPEL PM Console URL.

    3. In the Host Credentials page, specify the operating system credentials of the host where BPEL Process Manager is running. By default, the fields are prefilled with preferred credentials that are stored in the Management Repository for the selected host. You can either use these prefilled values or edit them to override the preferred credentials with your new credentials.

    4. In the Review page, review the details and click Finish to complete the discovery process and add the target to Enterprise Manager Cloud Control.

      Enterprise Manager Cloud Control displays the Agent home page with a confirmation message that confirms that the BPEL Process Manager has been successfully added for monitoring.

      Note:

      At this point, if you encounter a discovery failure error, then follow the workaround steps given in Table 9-10 and resolve the issue.

  3. To verify whether the BPEL Process Manager has been added, select Middleware from the Targets menu. /

    Enterprise Manager Cloud Control displays the Middleware page that shows all the middleware targets being monitored, including the IBM WebSphere Application Server and the BPEL Process Manager you just added.

Configuring BPEL Process Manager

After discovering BPEL Process Manager, you must perform the following configuration steps:

Specifying Details for Monitoring BPEL Process Manager

Follow these steps to specify the details required for monitoring BPEL Process Managers. If the values are prefilled, then validate them.

  1. In the BPEL Process Manager Home page, select Target Setup, then select Monitoring Configuration from the BPEL Process Manager menu.

  2. In the Monitoring Configuration page, specify the following details. If these values are prefilled, then validate them.

    • BPEL Admin Username - Specify the BPEL administrator user ID.

    • BPEL Password - Specify 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 - Specify the initial context factor. You can copy the following string value:

      com.evermind.server.rmi.RMIInitialContextFactory

    • Context Provider URL - Specify the context provider URL. You can copy the following string value:

      opmn:ormi://<host>:<opmn_port>:home/orabpel

      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.

      To retrieve SOA Applications Server OPMN PORT details, follow these steps:

      1. Open the configuration file $SOA_ORACLE_HOME/opmn/conf/opmn.xml. $SOA_ORACLE_HOME corresponds to SOA Application server home location.

      2. Identify the value of the request port attribute in the configuration file.

    • BPEL Repository Host Name - Specify the BPEL Dehydration store (database) host name.

    • BPEL Repository Port - Specify the BPEL Dehydration store (database) port.

    • BPEL Repository SID - Specify the BPEL Dehydration store (database) SID.

    • BPEL Repository User Name - Specify the BPEL Dehydration store (database) user name. By default, the user name is orabpel.

    • BPEL Repository Password - Specify the BPEL Dehydration store (database) password. By default, the password is welcome1.

    • Recoverable Instances Time Threshold (Days) - Specify the number of days for which the retryable instances must be shown.

    • Process Aggregate State - Specify 5, a numeric value that signifies the constant state of the BPEL target.

  3. Click OK to save the settings.

Registering BPEL Process Manager Credentials and Host Credentials

Follow these steps to register the credentials of the BPEL Process Manager, and the credentials of the host where BPEL Process Manager is running.

  1. From the Setup menu, select Security, then select Preferred Credentials.

  2. Select the Host target type and click Manage Preferred Credentials.

  3. Select Normal Host Credentials in the Credential Set column in the Default Preferred Credentials section and click Set.

  4. In the Select Named Credential window, enter the user name and password and click Save to return to the Preferred Credentials page.

  5. Select Oracle BPEL Process Manager target type and click Manage Preferred Credentials.

  6. Select Monitoring Administrator Credentials in the Credential Set column in the Default Preferred Credentials section and click Set.

  7. In the Select Named Credential window, enter the user name and password and click Save.

Troubleshooting BPEL Process Managers

This section describes the errors you might encounter while discovering BPEL Process Managers, and the workaround steps you can follow to resolve each of them.

This section covers the following:

Discovery Errors on Target Details Page

The following error occurs in the Target Details page of the Add BPEL Process Manager wizard where you provide details about the BPEL Process Manager installed on Oracle WebLogic Managed Server.

Table 9-8 Errors on Target Details Page While Adding BPEL Process Manager Deployed to Oracle WebLogic Managed Server

Error Message Workaround Steps 
Oracle BPEL Process Manager not found 
in the selected Application Server. 
Select another Application Server.

This error may occur if BPEL is not deployed on the selected Application Server or if the configuration data has not been collected.

To resolve this issue:

  1. Select another Application Server.

  2. Navigate to the Application Server Home page and select Configuration, then select Last Collected from the Application Server target menu.

Discovery Errors on Review Page

The following errors occur in the Review page of the Add BPEL Process Manager wizard when you are about to add a BPEL Process Manager installed on Oracle WebLogic Managed Server, to Enterprise Manager Cloud Control for monitoring purposes.

Table 9-9 Errors on Review Page While Adding BPEL Process Manager Deployed to Oracle WebLogic Managed Server

Error Message Workaround Steps 
Discovery Failure - Oracle BPEL
Process Manager target discovery
failed due to incorrect host
credentials.

  1. In the last page of the Add BPEL Process Manager wizard where you see this error message, click Previous to reach the Host Credentials page.

  2. In the Host Credentials page, specify the correct host credentials or set the preferred credentials for the specific host. Ensure that these are Agent user credentials.

 
Oracle BPEL Process Manager Discovery
Failed - Unable to connect to Oracle
BPEL Process Manager. The possible
reasons can be incorrect path or
insufficient permission to access
Oracle BPEL Process Manager home
location or inaccessible Oracle BPEL
Process Manager home location. Review
the specified value.

  1. In the last page of the Add BPEL Process Manager wizard, click Previous repeatedly to reach the Target Details page.

  2. In the Target Details page, verify the Oracle home location of the BPEL Process Manager.

  3. In the Target Details page, verify the installation location of the associated application server.

 
Oracle BPEL Process Manager Discovery
Failed - Unable to connect to Oracle
BPEL Process Manager. The possible
reasons can be incorrect path or
insufficient permission to access
Oracle BPEL Process Manager home
location or inaccessible Oracle BPEL
Process Manager home location. Review
the specified value.

Ensure that the BPEL directories have read permission for the Agent user.

Discovery Errors on Review Page

The following errors occur in the Review page of the Add BPEL Process Manager wizard when you are about to add a BPEL Process Manager installed on IBM WebSphere Application Server, to Enterprise Manager Cloud Control for monitoring purposes.

Table 9-10 Error on Review Page While Adding BPEL Process Manager Deployed to IBM WebSphere Application Server

Error Message Workaround Steps 
Discovery Failure - Oracle BPEL
Process Manager target discovery
failed due to incorrect host
credentials.

  1. In the last page of the Add BPEL Process Manager wizard where you see this error message, click Previous to reach the Host Credentials page.

  2. In the Host Credentials page, specify the correct host credentials or set the preferred credentials for the specific host. Ensure that these are Agent user credentials.

 
Oracle BPEL Process Manager Discovery
Failed - Unable to connect to Oracle
BPEL Process Manager. The possible
reasons can be incorrect path or
insufficient permission to access
Oracle BPEL Process Manager home
location or inaccessible Oracle BPEL
Process Manager home location. Review
the specified value.

  1. In the last page of the Add BPEL Process Manager wizard where you see this error message, click Previous repeatedly to reach the Target Details page.

  2. In the Target Details page, verify the BPEL application installation location.

    For example, the BPEL application may be installed at the following location:

    <$WEBSPHERE_HOME>/profiles/AppSrv01/installedApps/sta00114Cell01/CollaxaWebApplications-sta00114Node01.ear

    In this case, the path you specify must look like this:

    <$WEBSPHERE_HOME>/profiles/AppSrv01/installedApps

    Note: Replace $WEBSPHERE_HOME with the absolute application home location.

  3. In the Target Details page, verify the application server home location of the associated application server.

  4. In the Target Details page, verify the Oracle home location of the BPEL Process Manager.

Display Errors on Processes Page

Sometimes, after the discovery of a BPEL Process Manager, the BPEL process may occasionally not be listed in the BPEL Process Manager Processes page in Enterprise Manager Cloud Control.

There are two causes for this and two ways to ensure they display on the Processes page. The sections below discuss these causes and workaround steps to fix them.

No Credentials Specified for Monitoring BPEL Process Manager

You may not have specified the credentials required for monitoring BPEL Process Managers. To address this, do the following:

  1. In the BPEL Process Manager Home page, select Target Setup, then select Monitoring Configuration from the BPEL Process Manager menu.

  2. In the Monitoring Configuration page, check the following 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, copy the following string value:

      com.evermind.server.rmi.RMIInitialContextFactory

    • Context Provider URL - In case this field is empty, copy the following highlighted string value:

      opmn:ormi://<host>:<opmn_port>:home/orabpel

      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.

  3. Click OK to save the settings.

Retrieving the OPMN Port

To retrieve SOA Applications Server OPMN PORT details, follow these steps.

  1. Open the configuration file $SOA_ORACLE_HOME/opmn/conf/opmn.xml. $SOA_ORACLE_HOME corresponds to SOA Application server home location.

  2. Identify the value of the request port attribute in the configuration file.

javax.naming.NameNotFoundException Error

The following error occurs in the error details page when incorrect provider URL is specified.

Table 9-11 javax.naming.NameNotFoundException Error - Workaround Steps

Error Message Workaround Steps 
oracle.sysman.emSDK.emd.fetchlet.Fetchl
etException: java.lang.Exception:
Failed to create
"ejb/collaxa/system/ServerBean" bean;
exception reported is:
"javax.naming.NameNotFoundException:...

(See Figure 9-1)

  1. Validate the format of the string.

  2. Verify if the OPMN port is correct.

  3. Verify if the <oc4j_instance> name is properly substituted with the correct value, that is, the OC4J name value. The format must be like this:

    opmn:ormi://<host>:<opmn_port>:home/orabpel

Figure 9-1 javax.naming.NameNotFoundException Error

javax.naming.NameNotFoundException Error

javax.naming.NamingException Error

The following error occurs in the error details page when incorrect password is specified.

Table 9-12 javax.naming.NamingExceptionError - Workaround Steps

Error Message Workaround Steps 
oracle.sysman.emSDK.emd.fetchlet.Fetch
letException: java.lang.Exception: Failed
to create "ejb/collaxa/system/ServerBean" bean;
exception reported is:
"javax.naming.NamingException: Lookup
error:...

(See Figure 9-2)

  1. Validate the values specified for BPEL Admin username and BPEL Password fields in the Monitoring Configuration page. (Confirm the validity of credentials by using the same credentials to log in to the BPELConsole).

Figure 9-2 javax.naming.NamingException Error

javax.naming.NamingException Error

javax.naming.NoInitialContextException Error

The following error occurs in the error details page when incorrect Initial Context Factory value is specified.

Table 9-13 javax.naming.NoInitialContextException Error - Workaround Steps

Error Message Workaround Steps 
oracle.sysman.emSDK.emd.fetchlet.Fetchl
etException: java.lang.Exception:
Failed to create
"ejb/collaxa/system/ServerBean" bean;
exception reported is:
"javax.naming.NoInitialContextException
: Cannot instantiate class:...

(See Figure 9-3)

  1. Provide the following value for the Initial Context Factory field in the Monitoring Configuration page:

    com.evermind.server.rmi.RMIInitialContextFactory

Figure 9-3 javax.naming.NoInitialContextException Error

javax.naming.NoInitialContextException Error

Error While Creating BPEL Infrastructure Services

The following error occurs when you are creating a new BPEL infrastructure service.

Table 9-14 javax.naming.NoInitialContextException Error - Workaround Steps

Error Message Workaround Steps 
An error encountered while 
discovering the dependencies. Please 
try again.

  1. Apply patch 10849036 on the OMS and try creating the BPEL infrastructure service again:

    com.evermind.server.rmi.RMIInitialContextFactory

Metric Collection Errors for BPEL Process Manager Partner Link Metrics

The following metric collection error appears on the home page when you monitor BPEL 10.1.3.3 or 10.1.3.4 using Oracle Management Agent 12c:

Table 9-15 Metric Collection Errors for BPEL Process Manager Partner Link Metrics - Workaround Steps

Error Message Workaround Steps 
java.rmi.UnmarshalException: Error deserializing 
return-value: java.io.InvalidClassException: 
javax.xml.namespace.QName; local class incompatible: 
stream classdesc serialVersionUID = 
-916876369326528164, local class serialVersionUID = 
-9120448754896609940 at 
com.oracle.bpel.client.util.ExceptionUtils.handleServer
Exception(ExceptionUtils.java:82) at
com.oracle.bpel.client.BPELProcessHandle.getDescriptor
(BPELProcessHandle.java:207) at
oracle.sysman.emd.fetchlets.BPELPMFetchlet.getPartner
LinkMetrics(BPELPMFetchlet.java:873) at
oracle.sysman.emd.fetchlets.BPELPMFetchlet.getMetric
(BELPMFetchlet.java:235) at
oracle.sysman.emd.fetchlets.FetchletWrapper.getMetric
(FetchletWrapper.java:382)

Follow the workaround described in the My Oracle Support Note 735128.1. You can access My Oracle Support at the following URL:

https://support.oracle.com/CSP/ui/flash.html

Agent Monitoring Metric Errors

This error occurs if the same Agent is used to monitor the BPEL 10g and OSB, and BPEL 10g and SOA 11g targets.

Table 9-16 Metric Errors During Agent Monitoring

Error Message Workaround

The following exception has occurred:

Exception at getPartnerLinkMetrics: java.lang.NoClassDefFoundError: Could not initialize class javax.rmi.PortableRemoteObject

The same Management must not be used to monitor BPEL 10g and OSB, and BPEL 10g and SOA 11g targets.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us