4 Provisioning Oracle BPEL Processes

Besides discovery and monitoring capabilities, Enterprise Manager Grid Control also offers provisioning capabilities using deployment procedures that help you deploy BPEL processes on Oracle BPEL Process Managers (BPEL Process Manager).

A deployment procedure is a procedure that contains a hierarchal sequence of provisioning or patching steps, where each step may contain a sequence of other steps. In other words, the workflow of all tasks that need to be performed for a particular lifecycle management activity is encapsulated in a deployment procedure.

The deployment procedure used for provisioning BPEL processes on BPEL Process Managers is BPEL Process Provisioning. This chapter describes how you can use this deployment Procedure to provision BPEL processes on BPEL Process Managers.

In particular, this chapter covers the following:

• Prerequisites

• Provisioning Procedure

Prerequisites

Before running the Deployment Procedure to provision BPEL processes, meet the following prerequisites:

• Ensure that BPEL Process Manager on which the process suitcase files have to be deployed is already discovered and monitored in Enterprise Manager Grid Control.

• Ensure that Oracle Management Agent 10g Release 5 (or higher) is installed on the host where the target BPEL Process Manager is running.

• Register the credentials of application server instances on which the target BPEL Process Managers are running. Also register the BPEL administrator credentials (and RMI credentials for 10.1.2 BPEL targets) for the target BPEL Process Managers.

• Ensure that Oracle Software Library (Software Library) is set up. For instructions to set up the Software Library, see Setting Up Oracle Software Library. For more information, refer to the Enterprise Manager Advanced Configuration Guide available at the following URL:

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

• Store the BPEL process suitcase files as generic components in the Software Library. For instructions to create generic components, refer to the Enterprise Manager Advanced Configuration Guide available at the following URL:

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

  Note:

  While adding a generic component for BPEL processes, on the Create Component: Describe page of the Software Library Wizard, select Generic Component from the Type list, provide a name for the parent folder, and navigate to the Upload File page to upload the files. You DO NOT have to provide details for Customize and Set Directives page.

• If you want to use a deployment plan that can be associated with a BPEL process suitcase file (JAR file), then store this deployment file as a generic component in the Software Library. For instructions to create generic components, refer to the Enterprise Manager Advanced Configuration Guide available at the following URL.

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

Provisioning Procedure

To provision BPEL processes to a target BPEL Process Manager, follow these steps:

1. In Grid Control, click Deployments. Enterprise Manager Grid Control displays the Deployments page.

2. On the Deployments page, in the Deployment Procedure Manager, click Deployment Procedures. Enterprise Manager Grid Control displays the Deployment Procedure Manager page.

3. On the Deployment Procedure Manager page, in the Procedures tab, from the table, select BPEL Process Provisioning. Then click Schedule Deployment. Enterprise Manager Grid Control displays the Source Selection page.

4. On the Source Selection page, do the following:

   1. In the Source section, click Add and select the BPEL Process suitcase files that you want to deploy to a target BPEL Process Manager. The table is populated based on the selection made.

      If you have selected multiple suitcase files, then from the table, select the BPEL process suitcase file and use Move Up and Move Down to order the components the way they should be deployed by the Deployment Procedure.

   2. In the Select Deployment Plan, select a deployment plan that can be associated with a BPEL process suitcase file (JAR file).

      The deployment plan helps you modify the configuration details and partner link binding properties, which have been set for a particular environment, at run time. You can also use it to search and replace strings and URLs that have been set for a particular environment. This way, you can deploy the same BPEL processes on BPEL Process Managers that are in development, test, and production environments; without having to reconfigure your settings across these environments.

   3. Click Next. Enterprise Manager Grid Control displays Target Selection page.

5. On the Target Selection page, in the Target section, click Add and select the BPEL Process Managers on which you want to deploy the BPEL processes. If there are multiple domains available for a BPEL target, then you can select an appropriate domain from the BPEL Domain list, on which the suitcase files can be deployed. Click Next.

   Note:

   When you click Next, Enterprise Manager Grid Control internally checks to see if the Context Provider URL is captured. If this URL is not captured, then you may see some errors. To resolve this issue, set the URL in the Monitoring Configuration page of the BPEL target.

6. On the Credentials page, specify the following:

   1. Credentials of application server instances on which the selected BPEL Process Managers are running.

   2. BPEL administrator credentials (and RMI credentials for 10.1.2 BPEL targets) for the selected Oracle BPEL Process Managers.

      The credentials required for BPEL Process Managers vary according to the supported BPEL Process Manager version. For BPEL 10.1.3 targets, you need to provide only one set of credentials that will be used for accessing the BPEL Process Manager. However, for BPEL 10.1.2 targets, you need to provide the BPEL administrator password and another set of OC4J RMI Access credentials for remote access.

      If the preferred credentials are already set and stored in the Management Repository, then by default, they are prefilled on this page. You can choose to either use these prefilled preferred credentials or edit them to use the changed credentials. If the preferred credentials are not stored, then the fields are blank. In this case, you have to specify the credentials. The credentials specified here apply only to the current deployment procedure session and do not get stored in the Management Repository for future use.

      Note that if you change the credentials, the change applies only to the current deployment procedure session and does not override the preferred credentials stored in the Management Repository.

   3. Click Next. Enterprise Manager Grid Control displays the Schedule page.

7. On the Schedule page, schedule the deployment procedure to run immediately or later, and specify a unique name for the deployment procedure so that it can be tracked. Click Next. Enterprise Manager Grid Control displays the Review page.

8. On the Review page, review the details you have provided for provisioning BPEL processes, and click Submit.