Skip Headers
Oracle® Enterprise Manager Getting Started with Oracle Fusion Middleware Management
11g Release 1 (11.1.0.1)

E17558-05
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

5 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 Grid 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 Grid Control.

Table 5-1 Supported Versions

Supported BPEL Process Manager Version Application Server Deployed To Supported Enterprise Manager Grid Control

Oracle BPEL Process Manager 10.1.2

Oracle Application Server 10g Release 1 (10.1.2)

Enterprise Manager 10g Grid Control Release 4 (10.2.0.4)

Enterprise Manager Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or higher

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 Grid Control Release 3 (10.2.0.3) or higher

Enterprise Manager Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or higher

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 Grid Control Release 5 (10.2.0.5)

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

Enterprise Manager Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or higher

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 Grid Control Release 5 (10.2.0.5)

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

Enterprise Manager Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or higher

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 Grid Control Release 5 (10.2.0.5) or higher

Enterprise Manager Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or higher

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 Grid Control Release 5 (10.2.0.5) or higher

Enterprise Manager Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or higher

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 Grid Control Release 5 (10.2.0.5) or higher

Enterprise Manager Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or higher


Understanding the Discovery Mechanism

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

Table 5-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 Grid Control.

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

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

For discovery procedures, see Discovering BPEL Process Manager 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 Grid Control.

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

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

For discovery procedures, see Discovering BPEL Process Manager 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 Discovering BPEL Process Manager 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 Discovering BPEL Process Manager Deployed to IBM WebSphere Application Server.


Understanding the Discovery Process

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

Table 5-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 Grid Control

  • If you want to monitor Oracle BPEL Process Manager 10.1.3.3 that is deployed to Oracle Application Server 10g Release 1 (10.1.3.3), then install Enterprise Manager 10g Grid Control Release 3 (10.2.0.3) or higher.

  • If you want to monitor Oracle BPEL Process Manager 10.1.2 that is deployed to Oracle Application Server 10g Release 1 (10.1.2), then install Enterprise Manager 10g Grid Control Release 4 (10.2.0.4).

  • If you want to monitor Oracle BPEL Process Manager 10.1.3.3 that is deployed to Oracle WebLogic Managed Server 9.2 or IBM WebSphere Application Server 6.1, then install Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) and apply the one-off patches.

  • If you want to monitor Oracle BPEL Process Manager 10.1.3.4 that is deployed to Oracle Application Server 10g Release 1 (10.1.3.1 or 10.1.3.3), Oracle WebLogic Managed Server 9.2, or IBM WebSphere Application Server 6.1, then install Enterprise Manager 10g Grid Control Release 5 (10.2.0.5).

Note that 10.2.0.3, 10.2.0.4, 10.2.0.5 are patch sets. Therefore, if you are installing Enterprise Manager Grid Control for the first time, then install the base release first and then apply the 10.2.0.3, 10.2.0.4, 10.2.0.5 patch set on it. For information about installing the base release of Enterprise Manager Grid Control, see the Enterprise Manager Grid Control Installation and Basic Configuration Guide available at:

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

Oracle recommends that you install the Enterprise Manager Grid 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 10g Release 3 (10.2.0.3) or higher on every host where BPEL Process Manager is installed.

If Oracle Application Server/BPEL Process Manager and Enterprise Manager Grid 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 Grid 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 Grid Control Installation and Basic Configuration Guide available at:

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

4

One-Off Patches

If you are using Enterprise Manager 10g Grid Control Release 4 (10.2.0.4), then you will be able to discover and monitor the BPEL Process Manager deployed to Oracle WebLogic Managed Server 9.2 and IBM WebSphere Application Server 6.1 only when the following one-off patches are applied.

OMS One-Off Patches: Apply these one-off patches to Oracle Management Service (OMS) in the order given below.

  • Patch 6678593 (Or ARU Patch 10024972)

  • Patch 6877335 (Or ARU Patch 10024974)

  • Patch 6850462 (Or ARU Patch 10024971) - Before applying this one-off patch, you must set up Oracle Software Library in Enterprise Manager Grid Control. For procedures to set up the library, see Setting Up Oracle Software Library.

Agent One-Off Patches: Apply these one-off patches to the Management Agent in the order given below.

  • Patch 6692284 (Or ARU Patch 10024969)

  • Patch 6877323 (Or ARU Patch 10024970)

For information about these patches, refer to the ReadMe.txt file that comes with the one-off patch. For procedures to download these one-off patches, see Downloading One-Off Patches.

5

Discovery in Enterprise Manager Grid Control

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

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


Setting Up Oracle Software Library

If you are using Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) to discover and monitor the BPEL Process Manager deployed to Oracle WebLogic Managed Server 9.2 and IBM WebSphere Application Server 6.1, then you must apply the one-off patches as described in Understanding the Discovery Process. However, before applying the one-off patch 6850462, you must set up Oracle Software Library (Software Library) in Enterprise Manager Grid Control.

If you do not set up the Software Library and if you try to apply the one-off patch, you might see the following error:

ERROR !
Software Library has not been setup !
Please configure Software Library and try again

Note:

This is a requirement only for patch 6850462. The other patches do not require the Software Library to be set up.

To set up the Software Library:

  1. Log in to Enterprise Manager Grid Control.

  2. Click Deployments and then Provisioning.

    Enterprise Manager Grid Control displays the Provisioning page.

  3. In the Provisioning page, Click Administration.

  4. In the Administration page, from the Software Library Configuration section, click Add. Enterprise Manager Grid Control displays the Add Software Library Location page.

  5. In the Add Software Library Location page, 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 Configuration Guide available at the following URL:

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

Downloading One-Off Patches

If you are using Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) for discovering and monitoring of BPEL Process Manager deployed to Oracle WebLogic Managed Server 9.2 or IBM WebSphere Application Server 6.1, then apply the following one-off patches.

Note:

You do not required these patches for Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or higher.

Table 5-4 One-Off Patches to Download

One-Off Patch Type One-Off Patches to Download

OMS One-Off Patches

Apply these one-off patches to Oracle Management Service (OMS) in the order given below:

  • Patch 6678593 (Or ARU Patch 10024972)

  • Patch 6877335 (Or ARU Patch 10024974)

  • Patch 6850462 (Or ARU Patch 10024971)

Agent One-Off Patches

Apply these one-off patches to Oracle Management Service (OMS) in the order given below:

  • Patch 6692284 (Or ARU Patch 10024969)

  • Patch 6877323 (Or ARU Patch 10024970)


To download these one-off patches:

  1. Log in to My Oracle Support at:

    https://support.oracle.com/

  2. Click Patches & Updates.

  3. In the Patches & Updates page, from the Quick Find list, select Patch Number, quote the one-off patch number you want to download, and click Go.

    My Oracle Support displays the Patch <patch_number> page that provides details about the one-off patch.

  4. In the Patch <patch_number> page, click Download to download the patch. Click View Readme to view the ReadMe file and learn more about the patch.

Discovering BPEL Process Manager

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

Discovering BPEL Process Manager Deployed to Oracle Application Server

A BPEL Process Manager deployed to Oracle Application Server is manually or automatically discovered in Enterprise Manager Grid 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 Grid Control.

  • If the Management Agent is installed after Oracle Application Server and BPEL Process Manager are installed, then Enterprise Manager Grid 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 Grid Control are all on the same host, then you need not install a separate Management Agent. The Management Agent that comes with Enterprise Manager Grid 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 Grid 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 Grid Control, then you must manually rediscover that Oracle Application Server.

To manually discover or rediscover Oracle Application Server:

  1. Log in to Enterprise Manager Grid Control.

  2. Click Targets and then Middleware.

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

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

  4. In the Middleware page, from the Add list, select Oracle Application Server and click Go.

    Enterprise Manager Grid Control displays the Add Oracle Application Server Target: Specify Host page.

  5. In the Add Oracle Application Server Target: Specify Host page, specify the name of the host where that Oracle Application Server is running, and click Continue.

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

Discovering 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 Grid 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 Grid Control:

  1. Log in to Enterprise Manager Grid Control (as a SYSMAN user).

  2. Click Targets and then Middleware.

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

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

    Enterprise Manager Grid 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.

  4. 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.

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

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

Discovering BPEL Process Manager Deployed to Oracle WebLogic Managed Server

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

  1. Log in to Enterprise Manager Grid Control (as a SYSMAN user).

  2. Click Targets and then All Targets.

    Enterprise Manager Grid Control displays the All Targets page that lists all the targets being monitored.

  3. In the All Targets page, from the Search menu, select Agent and click Go.

    Enterprise Manager Grid Control displays all the Agents that are being monitored.

  4. From the list of monitored agents, click the agent that monitors the Oracle WebLogic Managed Server.

    Enterprise Manager Grid Control displays the Agent home page that provides details about the selected agent.

  5. In the Agent home page, from the Add list, select Oracle BPEL Process Manager and click Go.

    Note:

    At this point, if you encounter an exception error (404 Not Found), then follow the workaround steps given in Table 5-9 and resolve the issue.

    Enterprise Manager Grid Control displays the Select Application Server page of the Add BPEL Process Manager wizard.

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

      Table 5-5 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 5-6 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 Grid 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 5-11 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 Grid Control.

      Enterprise Manager Grid 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 5-11 and resolve the issue.
  6. To verify whether the BPEL Process Manager has been added, click Targets and then Middleware.

    Enterprise Manager Grid 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. In Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or lower, the Middleware tab is Application Servers

Discovering BPEL Process Manager 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 Grid 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 Grid Control:

  1. Log in to Enterprise Manager Grid Control (as a SYSMAN user).

  2. Click Targets and then Middleware.

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

  3. In the Middleware page, from the Add list, select IBM WebSphere Application Server, and click Go.

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

  4. 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.

  5. 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 Grid Control for monitoring purposes.

    Enterprise Manager Grid 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.

Discovering BPEL Process Manager Deployed to IBM WebSphere Application Server

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

  1. Log in to Enterprise Manager Grid Control (as a SYSMAN user).

  2. Click Targets and then All Targets.

    Enterprise Manager Grid Control displays the All Targets page that lists all the targets being monitored.

  3. In the All Targets page, from the Search menu, select Agent and click Go.

    Enterprise Manager Grid Control displays all the Agents that are being monitored.

  4. From the list of monitored agents, click the agent that monitors the IBM WebSphere Application Server.

    Enterprise Manager Grid Control displays the Agent home page that provides details about the selected agent.

  5. In the Agent home page, from the Add list, select Oracle BPEL Process Manager and click Go.

    Enterprise Manager Grid Control displays the Select Application Server page of the Add BPEL Process Manager wizard.

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

      Table 5-7 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 5-8 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 Grid 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 Grid Control.

      Enterprise Manager Grid 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 5-12 and resolve the issue.
  6. To verify whether the BPEL Process Manager has been added, click Targets and then Middleware.

    Enterprise Manager Grid 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, from the Related Links section, click Monitoring Configuration.

  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.

Adding BPEL JAR Files To Agent CLASSPATH

Follow these steps to add the required BPEL JAR files (storage containers) to the Agent CLASSPATH:

  1. Log in to the host machine where SOA is installed.

  2. Go to the ORACLE_HOME of the EM Agent installed on the same host.

  3. Open file '$AGENT_ORACLE_HOME/sysman/config/emd.properties' as shown in figure.

  4. 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.

    • $BPEL_SERVER_ORACLE_HOME/opmn/lib/optic.jar

    • $BPEL_SERVER_ORACLE_HOME/bpel/lib/orabpel.jar

    • $BPEL_SERVER_ORACLE_HOME/bpel/lib/orabpel-common.jar

    • $BPEL_SERVER_ORACLE_HOME/bpel/lib/orabpel-thirdparty.jar

    • $BPEL_SERVER_ORACLE_HOME/j2ee/home/oc4jclient.jar

    • $BPEL_SERVER_ORACLE_HOME/j2ee/home/j2ee_1.3.01.jar

    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.
  5. 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.

  6. Restart the Agent.

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. In Grid Control, from the top-right corner of the page, click Preferences.

  2. On the General page, from the vertical menu bar, click Preferred Credentials.

  3. On the Preferences page, for the target type Oracle BPEL Process Manager, from the Set Credentials column, click the icon.

  4. On the Oracle BPEL Process Manager Preferred Credentials page, in the Target Credentials section, for the BPEL Process Manager target you discovered, specify the administrator credentials and host credentials. Then click Apply.

  5. Similarly, on the Preferences page, for the target type Host, from the Set Credentials column, click the icon.

  6. On the Host Preferred Credentials page, in the Target Credentials section, for the host on which the BPEL Process Manager is running, specify the normal credentials and privileged credentials. Then click Apply.

Troubleshooting

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:

404 Not Found Errors

The following exception error occurs when you try to access the Add BPEL Process Manager wizard to add a BPEL Process Manager installed on Oracle WebLogic Managed Server.

Table 5-9 Error Message: 404 Not Found - Workaround Steps

Error Message Workaround Steps
404 Not Found
OracleJSP:java.io.FileNotFoundException
Set the init-param debug_mode to "true"
to see the complete exception message
  1. Copy the following file:

    /opt/app/consola10g/oms10g/j2ee/OC4J_EM/config/global-web-application.xml

  2. Paste the file in the following location:

    /opt/app/consola10g/oms10g/sysman/j2ee/config/

  3. Ensure that the following parameter is uncommented in the file:

    <init-param>
    <param-name>main_mode</param-name>
    <param-value>justrun</param-value>
    </init-param>
    

Discovery Errors on Target Details Page (Adding BPEL Deployed to Oracle WebLogic Managed Server)

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 5-10 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 click Administration and Last Collected.


Discovery Errors on Review Page (Adding BPEL Deployed to Oracle WebLogic Managed Server)

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 Grid Control for monitoring purposes.

Table 5-11 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 Proess 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 Proess 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 (Adding BPEL Deployed to IBM WebSphere Application Server)

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 Grid Control for monitoring purposes.

Table 5-12 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 Proess 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 Grid 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, from the Related Links section, click Monitoring Configuration.

  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.

Required BPEL JAR Files Not Added To Agent CLASSPATH

Yo may not have added the required BPEL JAR files (storage containers) to the Agent CLASSPATH. To add the JAR files, do the following:

  1. Log in to the host machine where SOA is installed.

  2. Go to the ORACLE_HOME of the EM Agent installed on the same host.

  3. Open file '$AGENT_ORACLE_HOME/sysman/config/emd.properties' as shown in figure.

  4. 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.

    • $BPEL_SERVER_ORACLE_HOME/opmn/lib/optic.jar

    • $BPEL_SERVER_ORACLE_HOME/bpel/lib/orabpel.jar

    • $BPEL_SERVER_ORACLE_HOME/bpel/lib/orabpel-common.jar

    • $BPEL_SERVER_ORACLE_HOME/bpel/lib/orabpel-thirdparty.jar

    • $BPEL_SERVER_ORACLE_HOME/j2ee/home/oc4jclient.jar

    • $BPEL_SERVER_ORACLE_HOME/j2ee/home/j2ee_1.3.01.jar

    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.
  5. 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.

  6. Restart the Agent.

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.

java.lang.NoClassDefFoundError Error

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

Table 5-13 java.lang.NoClassDefFoundError Error - Workaround Steps

Error Message Workaround Steps
Error Type: Collection Failure
Message:
java.lang.NoClassDefFoundError:
com/oracle/bpel/client/auth/ServerAuth

(See Figure 5-1)

  1. Identify the BPEL JARs that must be added to the CLASSPATH:

    $BPEL_SERVER_ORACLE_HOME/opmn/lib/optic.jar
    $BPEL_SERVER_ORACLE_HOME/bpel/lib/orabpel.jar
    $BPEL_SERVER_ORACLE_HOME/bpel/lib/orabpel-common.jar
    $BPEL_SERVER_ORACLE_HOME/bpel/lib/orabpel-thirdparty.jar
    $BPEL_SERVER_ORACLE_HOME/j2ee/home/oc4jclient.jar
    $BPEL_SERVER_ORACLE_HOME/bpel/lib/j2ee_1.3.01.jar
    
  2. Verify the PATH for the JAR files to ensure that there are no errors in the path settings. If there are errors, then the Java classes in the JAR files will not be loaded.

  3. Restart the Agent to ensure that the new JAR files are loaded.


Figure 5-1 java.lang.NoClassDefFoundError Error

java.lang.NoClassDefFoundError Error

javax.naming.NameNotFoundException Error

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

Table 5-14 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 5-2)

  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 5-2 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 5-15 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 5-3)

  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 5-3 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 5-16 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 5-4)

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

    com.evermind.server.rmi.RMIInitialContextFactory


Figure 5-4 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 5-17 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 10g Release 5 (10.2.0.5):

Table 5-18 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 My Oracle Support note 735128.1.