Skip Headers
Oracle® BPEL Process Manager for Non-Oracle Application Servers Installation Guide
10g Release 3 (10.1.3.3) for UNIX and Microsoft Windows

Part Number E10538-01
Go to Documentation Home
Home
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
View PDF

2 Installing Oracle BPEL Process Manager with the BEA WebLogic Server

This chapter provides the requirements and procedures for installing Oracle BPEL Process Manager with BEA WebLogic Server.

This chapter contains these topics:

See Also:

The following documentation after completing installation:

2.1 Overview

You can install and use Oracle BPEL Process Manager with the BEA WebLogic Server.

The BEA WebLogic Server enables you to set up, operate, and integrate e-business applications across multiple computing platforms using Web technologies. The BEA WebLogic Server includes both the run-time components and the tools to develop and design applications.

Oracle BPEL Process Manager provides the infrastructure for creating standards-based business processes, which can span heterogenous environments, include human intervention, and exhibit efficient asynchronous and synchronous behavior. A key enabler of Service-Oriented Architecture it also provides services that can be used for integration and notifications.

Oracle BPEL Console is the monitoring environment for Oracle BPEL Process Manager. You can run, manage, and test your deployed BPEL process using the Oracle BPEL Console. Oracle BPEL Console provides a Web-based interface for management, administration, and debugging of processes deployed to Oracle BPEL Server.

The installation of Oracle BPEL Process Manager for WebLogic consists of the following high-level steps:

  1. Create the Oracle BPEL Process Manager Schema in the Oracle Database

    This step involves installing Oracle Database and creating the required Database schemas for the Dehydration store for BPELPM on Oracle Database.

  2. Installation of the Oracle BPELPM Standalone 10.1.3.1 for OC4J

    This is the standalone version of BPELPM, which comes with an embedded OC4J J2EE container. Further steps will configure this BPELPM to work on WebLogic Application Server.

  3. Apply SOA Suite Patchset 10.1.3.3 on BPELPM Standalone 10.1.3.1

    This patchset upgrades the existing 10.1.3.1.0 installation to 10.1.3.3.0

  4. Configure BPELPM Standalone on BEA WebLogic Server Version 9.2

    This step involves running a command-based script, which will configure the Oracle BPELPM Standalone installed earlier to run on BEA WebLogic 9.2 server. The script performs the following steps:

    • Create a Weblogic domain called BPELDomain

    • Create an application server called oracleBPELServer within BPELDomain

    • Configure the oracleBPELServer classpath with Oracle BPELPM Binaries

    • Create and configure required DataSources/JMS Resources etc.

    • Deploy the required Applications for BPEL Console, BPEL Admininstration etc.

    The above steps, which are further detailed in the "Installation and Configuration" section, summarize the installation and configuration of BPELPM on WebLogic 9.2 platform.

2.2 System and Database Requirements

Table 2-1 describes the system requirements for using Oracle BPEL Process Manager with the BEA WebLogic Server.

Table 2-1 Oracle BPEL Process Manager System Requirements

Element Requirement

BEA WebLogic Server

Version 9.2

Oracle BPEL Process Manager for OC4J

Version 10.1.3.1

Note: Refer to Step 2: Install Oracle BPEL Process Manager 10.1.3.1 for OC4J for installing Oracle BPEL Process Manager for OC4J. Apply SOA Suite patchset 10.1.3.3 on BPELPM Standalone 10.1.3.1.

Web browsers

Internet Explorer 6.0 or Mozilla Firefox 2.0

Operation systems

Microsoft Windows XP, Microsoft Windows 2003, Red Hat Enterprise Linux release 3, and Red Hat Enterprise Linux release 4

Dehydration store database

Oracle9i (9.2.0.8) or higher

Oracle Database 10g (10.1.0.5) or higher

Oracle Database 10g (10.2.0.2) or higher

Oracle Database 10g Express Edition 10.2.0.1

Oracle Database 10.1.2.2

Note: This certification matrix reflects the Oracle BPELPM certification on Oracle Application Server, and may vary with the application server being used. Confirm the certification matrix of the application server with Oracle Database version.


2.3 Installation and Configuration

This section describes the steps involved in installing and configuring the Oracle Database, creating a schema in the Database, and installing and configuring BEA WebLogic Server.

This section contains the following topics:

2.3.1 Step 1: Configure the Oracle Database

Follow these instructions to install Oracle Database 10g.

Note:

These instructions assume that you have obtained Oracle Database 10g version 10.1.0.2 and Oracle Database 10g Patch version 10.1.0.5.

For all other Database versions, refer to http://www.oracle.com/technology/documentation/index.html.

  1. Install Oracle Database 10g 10.1.0.2.

  2. Open SQL*Plus and log in as a user with the SYSDBA privilege.

  3. Shut down the database:

    SQL> SHUTDOWN IMMEDIATE
    
  4. Install the Oracle Database 10g 10.1.0.5 patch in the same Oracle home in which you installed Oracle Database 10g.

  5. If using Linux only, then log in as the root user and run the following command from the operating system command prompt:

    /etc/init.d/init.cssd stop
    
  6. Start the database in upgrade mode in SQL*Plus:

    SQL> STARTUP UPGRADE
    
  7. Run the following script:

    SQL> @ORACLE_HOME/rdbms/admin/catpatch.sql;
    
  8. Shut down the database:

    SQL> SHUTDOWN IMMEDIATE
    
  9. Restart the database:

    SQL> STARTUP
    
  10. Run the following script:

    SQL> @ORACLE_HOME/rdbms/admin/utlrp.sql;
    

2.3.2 Step 2: Install Oracle BPEL Process Manager 10.1.3.1 for OC4J

This is the standalone version of BPEL. Please note the basic SOA Suite installation cannot be used for this setup. You can download this standalone version of Oracle BPEL Process Manager 10.1.3.1 at

http://www.oracle.com/technology/software/products/ias/bpel/index.html

Note:

The file names start with soa although it really is a BPEL download file. For example, the name of the Windows download file for Oracle BPEL Process Manager 10.1.3.1 for OC4J appears as soa_windows_x86_bpel_101310.zip.

You need to install BPEL into it's own directory outside of WebLogic. The WebLogic installation will refer to binaries and property files from this installation. This external installation will need to be there permanently, it's not a temporary staging area. Even though it also contains OC4J, you will not be starting and stopping it. This is an important prerequisite prior to the WebLogic install.

2.3.3 Step 3: Create the Oracle BPEL Process Manager Schema in the Oracle Database

Note:

The scripts to configure Oracle BPEL Process Manager on the BEA WebLogic Server require that the JAVA_HOME environment parameter be set prior to running the script.
  1. Navigate to the Disk1\install\soa_schemas\irca folder in the BPEL Installation Setup files directory.

  2. Set ORACLE_HOME to point to the Oracle Database Installation location. For example,

    set ORACLE_HOME=c:\Oracle10g
    
  3. Enter irca bpel.

    This runs the irca script packaged with the Oracle BPEL Process Manager installation.

  4. Enter sys password when prompted.

    The orabpel schema is loaded on the Oracle Database.

2.3.4 Step 4: Apply SOA Suite Patchset 10.1.3.3 on Oracle BPELPM Standalone 10.1.3.1

You need to download the SOA Suite patchset 10.1.3.3 from MetaLink and then apply the patchset on BPELPM Standalone 10.1.3.1. Perform the following steps:

  1. Log in to OracleMetaLink at http://metalink.oracle.com. The OracleMetaLink home page is displayed.

  2. Click Patches & Updates. The Patches & Updates page is displayed.

  3. Click Simple Search.

  4. In the Search By field, enter 6148874. The details of the patchset 6148874 are displayed.

  5. Follow the instructions in the patchset to install the patchset on the BPELPM Standalone 10.1.3.1.

    Caution:

    You should not start/restart the BPELPM instance after applying the patch.

2.3.5 Step 5: Install BEA WebLogic Server Version 9.2 and Configure BPELPM Standalone for WebLogic

Note:

These instructions assume that you have obtained BEA WebLogic Server version 9.2.
  1. Install BEA WebLogic Server version 9.2.

    Note:

    If installing on Linux, then change the permissions using the command chmod a+x platform921_linux32.bin. Then, run the ./platform921_linux32.bin command.
  2. Download the Orabpel_10133_WebLogic.zip file, which enables you to port Oracle BPEL Process Manager in BEA WebLogic Server 9.2 at

    http://www.oracle.com/technology/software/products/ias/htdocs/101310.html and unzip to the Orabpel_10133_WebLogic folder.

    Note:

    • The directory to which you download the Oracle BPEL Process Manager should be the same host on which the BEA WebLogic Server is installed.

    • Unzip the orabpel_10133_WebLogic folder as a non-root user (same user as used to install Oracle BPEL Process Manager 10.1.3.1 for OC4J). For example, Oracle.

  3. Modify the following mandatory installation properties in the orabpel_10133_WebLogic\bpelDomain.properties file:

    Note:

    Mandatory properties cannot have a comment tag or contain blank values. Failure to follow this requirement results in errors during installation. Also, ensure that you enter the appropriate information for each of the fields. Any typo will cause errors during installation.
    Property Description
    BEA_HOME The directory path in which BEA WebLogic Server is installed.

    For example, BEA_HOME=C:\bea.

    BPEL_HOME The directory path in which Oracle BPEL Process Manager is installed.

    For example, BPEL_HOME=C:\product\10.1.3.1\OraBPEL_1\bpel

    JAVA_HOME JAVA path of WebLogic.

    For example, JAVA_HOME=C:\bea\jdk150_06

    DOMAIN_HOME The path for a new WebLogic domain called BPELDomain.

    For example, DOMAIN_HOME=C:\bea\user_projects\domains

    APPS_HOME The path where applications and adapters will be deployed from.

    For example, APPS_HOME=C:\bea\user_projects\apps

    DRIVER_TYPE The datasource class that the installable utilizes to create datasources for the oracleBPELServer manager server.

    For example, DRIVER_TYPE=oracle.jdbc.xa.client.OracleXADataSource

    DB_URL The is the URL to connect to ORABPEL schema.

    For example, DB_URL=jdbc:oracle:thin:@stbbn10.us.oracle.com:1521:orcl

    DB_USER The user Id for ORABPEL schema in database.

    For example, DB_USER=ORABPEL

    DB_PASSWORD The password for orabpel schema in database.

    For example, DB_PASSWORD=ORABPEL

    BPEL_SERVER_NAME The server which is created under BPELDomain.

    For example, BPEL_SERVER_NAME=oracleBPELServer

    PROXY_HOST The Host name of the proxy server.

    For example, PROXY_HOST=www-proxy.us.oracle.com

    PROXY_PORT The Port where the proxy server is running.

    For example, PROXY_PORT=80

    NON_PROXY_HOST The list of non proxy hosts that are divided by a | symbol.

    For example, NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|10.177.251.61|rajeshc-pc|rajeshc-pc.idc.oracle.com


  4. Run the following script from orabpel_10133_WebLogic folder at the operating system command prompt:

    For... Run...
    Windows XP setup.bat
    Linux setup.sh

    This script creates the domain folder called BPELDomain in the BEA_HOME\user_projects\domains\ directory, which contains the Admin Server (AdminServer) and Oracle BPEL Server managed server (oracleBPELServer). This configures the required applications, database connections, and adapters.

    Note:

    • While running the setup.bat or setup.sh file, set the evironment variable BEA_HOME to bea folder. For example, C:\bea in Microsoft Windows or \home\userfolder\bea in Linux.

    • Based on the BEA_HOME variable value, the setup script assumes the jdk folder name to bejdk150_06 and appends this value to BEA_HOME, sets it to the JAVA_HOME variable, and checks for the path existence in the file structure. For example, JAVA_HOME=BEA_HOME/jdk150_06.

      If JAVA_HOME path does not exist, then setup file throws a message asking to set the JAVA_HOME before running the setup file.

    • Based on the BEA_HOME variable value, the setup file assumes the WebLogic folder name is weblogic92 and appends this value to BEA_HOME, sets it to the variable WL_HOME, and checks for the path existence in the file structure. For example, WL_HOME=BEA_HOME\weblogic92.

      If WL_HOME path does not exist, then setup file throws a message asking to set the WL_HOME before running the setup file.

    • Setting WL_HOME as environment variable sets the variable WL_JAR_PATH, which contains the following value: WL_HOME\server\lib\weblogic.jar.

      The WL_JAR_PATH is used to load the WebLogic ant task class weblogic.ant.taskdefs.management.WLSTTask.The setup script assumes that weblogic.jar is available at WL_HOME\server\lib folder.

  5. Start NodeManager as follows:

    For... Run...
    Windows XP BEA_HOME\weblogic92\server\bin\startNodeManager.cmd
    Linux BEA_HOME/weblogic92/server/bin/startNodeManager.sh &

    When you start the node manager, it creates a mapping to the BPEL docmain, which enables you to start and stop oracleBPELServer remotely using admin console. You can also start and stop the node manger from the Windows Services by running the installNodeMgrSvc.cmd from the BEA_HOME\weblogic92\server\bin\ directory.

  6. Start BEA WebLogic Server as follows:

    For... Run...
    Windows XP BEA_HOME\user_projects\domains\BPEL_Domain\bin\startWebLogic.cmd
    Linux BEA_HOME/user_projects/domains/BPEL_Domain/bin/startWebLogic.sh &

    This server has to be started before the user can access the BPEL Domain Administrative Console at the following URL:

    http://localhost:8001/console
    

    Installation progress is logged to the WL_Installables\bin\logs\output.log file.

  7. Start the oracleBPELServer managed server by following the startup instructions as follows:

    1. Log in to http://localhost:8001/console, using weblogic as the username and password. The BEA WebLogic Server Administrative Console window is displayed.

    2. Select Environment -> Servers -> oracleBPELServer. The Settings of oracleBPELServer General page is displayed.

      Surrounding text describes orabpelserverpage.gif.
    3. Click the Control tab. The Settings of OracleBPELServer Control page is displayed.

      Surrounding text describes controlpage.gif.
    4. In the Server Status pane, select oracleBPELServer and click Start. The Server Life Cycle Assistant page is displayed.

    5. Click Yes. The oracleBPELServer status shows RUNNING in the Server Status pane.

    Note:

    Do not start Oracle BPEL Server from the Windows Start Menu or by running the BPEL_HOME\bpel\bin\startorabpel script. These actions are not supported.
  8. Log in to the BPEL Console at the following URL, using weblogic as the username and password:

    http://localhost:9700/BPELConsole

2.4 Design-time Deployment Support for BPELPM 10.1.3.3 on WebLogic 9.2

This section describes the various design-time support functions available on BEA WebLogic Server, for the deployment of J2EE applications in JDeveloper. You can deploy BPELPM components on BEA WebLogic Server by using the following two methods:

2.4.1 From the BPELPM Developer Prompt Using Ant

You can use ant in the BPELPM developer prompt to deploy J2EE applications. This section contains the following topics:

2.4.1.1 Prerequisite Checks

  1. Ensure that bpelPlatform is set to weblogic_8 in the BPEL_HOME\bpel\system\config\collaxa-config.xml file.

  2. Ensure that the following properties are set in BPEL_HOME\bpel\utilities\ant-orabpel.properties file:

    • platform to weblogic_8

    • admin.user to valid user in WebLogic realm

    • admin.password to the password of the above user

    • jndi.url to t3://<hostname>:9700

    • jndi.InitialContextFactory to weblogic.jndi.WLInitialContextFactory

    Note:

    If the admin.user property is not set correctly, then the deployment may throw authentication errors.

2.4.1.2 Steps to Deploy Using the BPELPM Prompt

Follow these instructions to deploy BPELPM from the developer prompt using ant:

  1. Open a BPELPM Developer prompt.

  2. Run ant.sh/bat from the BPEL_HOME\bpel\system\appserver\oc4j\ant\bin directory of the BPEL application.

    Note:

    For more information, refer to C:\product\10.1.3.1\OraBPEL_OC4J\bpel\GETTING_STARTED.html.

The only exceptions to be noted are as follows:

  • If the BPEL Process contains any Decision Service applications, UI applications, or Work Flow applications, then these applications will not be automatically deployed in WebLogic Server by the ant script.

  • The corresponding EAR/WAR files is custom built for WebLogic platform but need to be manually deployed on the target server oracleBPELServer.

  • Use Weblogic Admin console (http://<hostname>:8001/console) to deploy the EAR/WAR files to oracleBPELServer.

Note:

Refer to Auto Loan Demo for more details.

2.4.2 From JDeveloper

You can also deploy J2EE applications from JDeveloper. This section contains the following topics:

2.4.2.1 Prerequisite Checks

  1. Download JDeveloper Studio 10.1.3.3 (jdevstudio10133.zip) from

    For Windows - http://www.oracle.com/technology/software/products/jdev/htdocs/soft10133.html.

  2. Copy the bpm-services.jar file from the BPEL_HOME\system\services\lib directory to JDEV_HOME\integration\lib directory.

  3. Copy the orabpel-ant.jar file from the BPEL_HOME\lib directory to the JDEV_HOME\integration\lib directory.

  4. Ensure that the following properties are set in in BPEL_HOME\bpel\utilities\ant-orabpel.properties file: Ensure that bpelPlatform is set to weblogic_8 in the BPEL_HOME\bpel\system\config\collaxa-config.xml file.

    • platform to weblogic_8

    • admin.user to valid user in WebLogic realm

    • admin.password to the password of the above user

    • jndi.url to t3://<hostname>:9700

    • jndi.InitialContextFactory to weblogic.jndi.WLInitialContextFactory

  5. In JDeveloper, create an application server connection of the Standalone OC4J 10.1.3 type.

  6. In JDeveloper, create an Integration Server connection to localhost:9700.

2.4.2.2 Steps to Deploy Using JDeveloper

Follow these instructions to deploy BPELPM from the developer prompt using JDeveloper:

  1. From JDeveloper, right-click and deploy the BPEL application into the required domain.

    Description of deployment.gif follows
    Description of the illustration deployment.gif

The only exceptions to be noted are as follows:

  • If the BPEL Process contains any Decision Service applications, UI applications, or Work Flow applications, then these applications will not be automatically deployed in WebLogic Server by JDeveloper.

  • The corresponding EAR/WAR files is custom built for WebLogic platform but need to be manually deployed on the target server oracleBPELServer in WebLogic.

  • Use Weblogic Admin console (http://<hostname>:8001/console) to deploy the EAR/WAR files to oracleBPELServer.

Note:

Refer to Auto Loan Demo for more details.

2.5 Additional Configuration Steps of the BEA WebLogic Server

The configuration steps mentioned in this section are optional and you can perform these only if there is a need:

2.5.1 Using Application Security

This section describes the following steps to set up application security by using external LDAP store for BEA WebLogic Server 9.2:

Step 1: Create an Authentication Provider

  1. Log in to http://localhost:8001/console, using weblogic as the username and password.

  2. Select Security Realms -> myrealm -> Providers -> Authentication.

  3. Click the Lock & Edit button in the Change Centre pane to activate all the buttons on this page.

  4. Click New to create a new authentication provider, for example, LDAP Authenticator. The Create a New Authentication Provider page is displayed.

  5. Enter a name of the authentication provider in the Name field (for example, LDAP_1)and select LDAPAuthenticator in the Type drop-down.

  6. Click OK. The Authentication Providers table displays the name of the LDAP provider that you created.

Step 2: Confirguring LDAP in BEA WebLogic Server

BEA WebLogic Server does not support or certify any particular LDAP server. Any LDAP v2 or v3 compliant LDAP server should work with BEA WebLogic Server. The LDAP authentication providers, in this release of WebLogic Server (v9.2), are configured to work with the SunONE (iPlanet), Active Directory, Open LDAP, and Novell NDS LDAP servers.

You can use an LDAP authentication provider to access other types of LDAP servers. Choose either the LDAP Authentication provider (LDAPAuthenticator) or the existing LDAP provider that most closely matches the new LDAP server and customize the existing configuration to match the directory schema and other attributes for your LDAP server. The server comes with the following authentication providers, which help to configure different LDAP servers:

  • iPlanet authentication provider

  • Active Directory authentication provider

  • Open LDAP authentication provider

  • Novell authentication provider

  • Generic LDAP authentication provider

If you select the LDAP authentication provider, then every LDAP authentication provider has the following attributes:

  • Enable communication between the LDAP server and the LDAP Authentication provider. For a more secure deployment, BEA recommends using the SSL protocol to protect communications between the LDAP server and WebLogic Server. Enable SSL with the SSLEnabled attribute only if the SSL is enabled for LDAP server. This is referenced by the Hostname and Port (default: 389) attributes.

  • Configure options that control how the LDAP Authentication provider searches the LDAP directory. This is referenced by User name attribute and the Static Group User name attribute.

  • Specify where in the LDAP directory structure users are located. This is referenced by the User Base DN (Distinguished Name) attribute.

  • Specify where in the LDAP directory structure groups are located. This is referenced by the Group Base DN attribute.

  • Define how members of a group are located.

Perform the following steps to configure LDAP in BEA WebLogic Server:

  1. Edit the provider-specific attributes of the LDAP authentication provider through the Administration Console.

    1. Log in to http://localhost:8001/console, using weblogic as the username and password.

    2. Select Security Realms -> myrealm -> Providers -> LDAP_1. The Settings of LDAP_1 page is displayed.

    3. Click Provider Specific.

    4. Click the Lock & Edit button in the Change Centre pane to activate all the buttons on this page.

    5. Edit the required attributes in the Provider Specific page.

    6. Click Save.

  2. Edit performance options that control the cache for the LDAP server.

    1. Click the Performance tab.

    2. Edit Max Group Hierarchies in Cache. The maximum size of the LRU cache for holding group membership hierarchies if caching is enabled. The default is 100.

    3. Edit Group Hierarchy Cache TTL.The maximum number of seconds a group membership hierarchy entry is valid in the LRU cache. The default is 60.

    4. Click Save.

Failover

You can configure an LDAP provider to work with multiple LDAP servers and enable failover, if one LDAP server is not available. To enable failover, change the Host attribute in the security_realm > Providers > provider_specific page, to contain a list of hostnames and ports, for example, hostname1:389, hostname2:389. When using failover, the Parallel Connect Delay and Connect Timeout attributes have to be set for the LDAP authentication provider:

  • Parallel Connect Delay: Specifies the number of seconds to delay when making concurrent attempts to connect to multiple servers. An attempt is made to connect to the first server in the list. The next entry in the list is tried only if the attempt to connect to the current host fails. This setting might cause your application to block for an unacceptably long time, if a host is down. If the value is greater than 0, then another connection setup thread is started after the specified number of delay seconds has passed. If the value is 0, then connection attempts are serialized.

  • Connection Timeout: Specifies the maximum number of seconds to wait for the connection to the LDAP server to be established. If the value is 0, there is no maximum time limit and WebLogic Server waits until the TCP/IP layer times out to return a connection failure. Set to a value over 60 seconds depending upon the configuration of TCP/IP.

Note:

After you create the LDAP authentication provider, perform the following changes and restart the servers that are running under BPELDomain:
  • Select Security Realms > myrealm > Providers > DefaultAuthenticator and change the Control Flag to SUFFICIENT.

  • Select Security Realms > myrealm > Providers > yourLDAPAuthenticator and change the Control Flag to SUFFICIENT.

Users in LDAP server must be inside a BpelGroup group in the LDAP directory. (You should create a BpelGroup group in the LDAP directory and add the desired users to that group, otherwise the LDAP users cannot access applications inside the BPELDomain).

Ensure that admin.user and admin.password in BPEL_HOME\bpel\utilities\ant-orabpel.properties are updated with the credentials of a valid user from the LDAP Authenticator.

For more information, refer to http://e-docs.bea.com/wls/docs92/secmanage/atn.html#wp1198953

2.5.2 Using High Availability Setup

This section describes the High Availability (HA) support available for BPELPM 10.1.3.3 on BEA WebLogic Server 9.2. This section contains the following topics:

2.5.2.1 Prerequisite Checks

Ensure that HA setup of BPELPM is configured on two nodes on two machines. Let's assume the hostnames of the two nodes as hostname01 and hostname02. Also, the load balancing URL as http:\\<loadbalancer>:9800.

2.5.2.2 Steps to Configure HA for BPELPM

Follow these instructions to configure HA for BPELPM on BEA WebLogic Server:

  1. Configure BPELPM on BEA WebLogic Server on hostname01 and hostname02 separately.

    Note:

    • To configure BPELPM on BEA WebLogic Server on a hostname, refer to "Installation and Configuration".

    • While configuring ensure that DB_URL propertypoints to the same database in orabpel_10133_WebLogic\bpelDomain.properties for both the nodes.

  2. Install any load balancing software on one of the hosts (hostname01 or hostname02) or some other host, and point http://hostname01:9700 and http://hostname02:9700 using the common load balancing URL (http://<loadbalancer>:9800).

  3. Modify the BPEL_HOME\bpel\system\config\collaxa-config.xml on both hostname01 and hostname02.

    • Update soapCallbackUrl property in the collaxa-config.xml file to http://<loadbalancer>:9800 so that the soapCallbackUrl property points to the load balancer URL.

  4. Start oracleBPELServer on both the hostname01 and hostname02 hosts.

  5. Log in to the BPEL Process Manager Console at http://<loadbalancer>:9800/BPELConsole.

2.6 Postinstallation Verification Tasks

This section describes the postinstallation verification tasks to be performed, and it contains the following topics:

2.6.1 Verifying Installation from the BEA WebLogic Server Console

Perform the following steps to check if the BEA Admin Console has started:

  1. Navigate to http://localhost:8001/Console. The Oracle BEA WebLogic Server Admin Console window is displayed.

    Description of beaconsole.gif follows
    Description of the illustration beaconsole.gif

    Log in using weblogic as the username and password.

  2. Verify that you can view the oracleBPELServer Home page by selecting Environment -> Servers -> oracleBPELServer -> Configuration -> General.

    Description of beaconsolegn.gif follows
    Description of the illustration beaconsolegn.gif

  3. Verify that you can view the oracleBPELServer startup properties page by selecting Environment -> Servers -> oracleBPELServer -> Configuration -> Server Start. You can also add or modify the server startup properties such as Class Path, Arguments as a BPEL Domain admin.

    Description of beaconserverstart.gif follows
    Description of the illustration beaconserverstart.gif

  4. Verify that the BPELJMSServer is installed under Services -> Messaging -> JMS Servers.

    Description of beajmsservers.gif follows
    Description of the illustration beajmsservers.gif

  5. Verify that the summaries of the JMS resources that have been created for the JMS System module are displayed under Services -> Messaging -> JMS Modules -> bpelJMSModule -> Configuration.

    Description of beaconfig.gif follows
    Description of the illustration beaconfig.gif

  6. Verify that the BPELServerDataSource and BPELServerDataSourceWorkflow are the two JDBC data sources that are created under Services -> JDBC -> Data Sources.

    Description of beadatasources.gif follows
    Description of the illustration beadatasources.gif

2.6.2 Verifying Oracle BPEL Process Manager Console

Perform the following steps to check if the Oracle BPEL Process Manager Console has started:

  1. Navigate to http://localhost:9700/BPELConsole (Or to the location where the software is installed, for example, http://<machine-name>:9700/BPELConsole/. The Oracle BPEL Process Manager Console window is displayed.

    Description of console.gif follows
    Description of the illustration console.gif

  2. Log in using the user-id as configured in the security settings step in "Using Application Security".

    Description of index.gif follows
    Description of the illustration index.gif

2.6.3 Verifying the SelectAllByTitle Sample for the Database Adapter

  1. Log in to the database and start SQL*Plus.

  2. Run the setup.sql script:

    SQL> @Oracle_Home/samples/tutorials/122.DBAdapter/sql/setup.sql;
    

    This script creates and populates the movies table in the database.

  3. Point the database adapter to your database in the BEA WebLogic Server Console under Deployments, DB Adapter, Configuration, Outbound Connection Pools, eis/DB/BPELSamples, Properties.

    Note:

    Refer to Section 2.6.4, "Running Adapter Samples" for more information.
  4. Select Start, All Programs, Oracle - Oracle_Home, Oracle BPEL Process Manager, Developer Prompt.

  5. Change to the following directory:

    tutorials\122.DBAdapter\SelectAllByTitle
    
  6. Run the following command:

    ant
    

    This compiles and deploys all projects dependent on this tutorial. Projects are deployed into BPEL_HOME\bpel\domains\domain_name\deploy.

  7. Select Start, All Programs, Oracle - Oracle_Home, Oracle BPEL Process Manager, BPEL Console.

  8. Click SelectAllByTitle in the Deployed BPEL Processes list.

  9. Enter the movie title on the Initiate page.

  10. Click Post XML Message.

  11. View the results and inspect the instance.

2.6.4 Running Adapter Samples

Ensure that the outbound connection pool properties shown in Table 2-2 are modified.

2.6.4.1 Configuring Outbound Connection Pool for Adapters in Weblogic

You should create the required outbound connection pools that are used by BPEL Process Partnerlinks before deploying BPEL Processes using Adapters. Perform the following steps to create the required outbound connection pools:

  1. Log in to http://localhost:8001/console, using weblogic as the username and password.

  2. Select Deployments, <adapter_name>, Configuration, and Outbound Connection Pools. The Outbound Connection Pool Configuration Table is dispalyed.

  3. Click Lock & Edit.

  4. Click New. The Create a New Outbound Connection page is displayed.

  5. Select the outbound connection displayed in the Outbound Connection Group.

  6. Click Next. The JNDI Name for Outbound Connection Instance page is displayed.

  7. Enter the required JNDI name as referenced by the partnerlink WSDL of the BPEL process under jca:address location.

  8. Click Finish. The Save Deployment Plan Assistant page is displayed.

  9. Select a deployment plan location in the Location field, and click Finish. The Settings for <adapter_name> page is displayed.

  10. Return to the Outbound Connection Pools page and select the outbound connection pool that you created under the Groups and Instances column. The Outbound Connection Properties page is displayed.

  11. Click the respective property value column to update the properties.

  12. Click Save.

  13. Click the Activate Changes button to activate the changes you have made.

Table 2-2 Outbound Connection Pool Properties

Adapter Type Properties

Database

  • driverClassName

  • connectionString

FTP

  • host

  • port

Note: A new authentication alias must be created for connecting to the FTP server.

Applications

  • connectionString

  • userName

  • password

AQ

  • connectionString

  • userName

  • password

JMS

  • connectionFactoryLocation

  • isTopic

  • isTransacted

Note: The istopic property must be set to false for queues. The isTransacted property must be set to false for the JMS samples to run.

MQ

  • channelName

  • portNumber

  • queueManagerName

  • hostName


2.6.5 Deploying Samples Using Ant

Ensure that admin.user and admin.password in BPEL_HOME\bpel\utilities\ant-orabpel.properties are updated with the credentials of a valid user from the authentication store setup for authentication.Samples can be deployed from the developer prompt using the ant script following the above step.The samples containing only BPEL processes can be fully deployed using the ant script.Samples containing additional components such as Decision Service applications, workflow forms, and UI applications need to be deployed in the following manner.

  1. Use the ant script to deploy the BPEL process of the sample.

  2. For each Decision Service application, manually edit the jsps and the decisionservice.xml file to replace the variables for domain, host the port as required. Generate the war or ear file, and deploy into DecisionServer. Start the application.

  3. For each workflow form application, generate the war or ear file, and deploy into oracleBPELServer. Start the Application.

  4. For each UI Application, manually edit the doApply.jsp to replace the variables for domain, host the port as required. Generate the war or ear file, and deploy into oracleBPELServer. Start the application.

2.7 Auto Loan Demo

This appendix describes how to run Auto Loan Demo on BPELPM 10.1.3.3 on WebLogic 9.2 application server. It contains these sections:

2.7.1 Prerequisites on JDeveloper Studio 10.1.3.3

The following one-time changes should be performed on JDeveloper:

  1. Replace the bpm-services.jar within JDeveloper at jdev\integration\lib with the updated jar from BPEL_HOME\system\services\lib

  2. Replace the orabpel-ant.jar within JDeveloper at jdev\integration\lib with the updated jar from BPEL_HOME\lib.

  3. Modify the following properties in jdev\integration\bpel\utilities\ant-orabpel.properties file:

    • Platform to weblogic_8

    • admin.user to a valid user in weblogic realm

    • admin.password to the password of the above user

    • jndi.url to t3://<hostname>:9700

    • jndi.InitialContextFactory to weblogic.jndi.WLInitialContextFactory

  4. On JDeveloper, create an Application Server connection of type "Standalone OC4J 10.1.3".

  5. On JDeveloper, create an Integration Server connection to "<hostname>:9700"

    Note:

    Ignore errors during test connection regarding Mediator at this stage.

2.7.2 Auto Loan Demo Sample

The Auto Loan Flow sample has the following components:

  • BPEL Process: AutoLoanFlow BPEL Process <bpel jar>

  • Decision Service Applications (Business Rules Applications)

    • CreditRatingAgent <ear>

    • LoanAdvisorAgent <ear>

  • UI Application: AutoLoanFlowUI <ear>

  • HWF Tform application: AutoLoanflow LoanApproval <ear>

Since the AutoLoanFlow sample that is bundled with BPELPM standalone is written for OC4J Application Server, it cannot be run as is on WebLogic 9.2 Application Server. Specifically, the Decision Service applications need to be regenerated for WebLogic platform, using JDeveloper. Weblogic requires that the following mandatory deployment descriptor files be present in the application that serves Webservices:

  • weblogic.xml

  • weblogic-webservices.xml

  • weblogic-webservices-policy.xml

Also the java-wsdl-mapping file needs WebLogic specific modifications.

The next section describes the steps to regenerate the Decision Services Applications in Auto Loan Flow for WebLogic.

2.7.3 Modelling Auto Loan Flow Process Using JDeveloper Studio

Perform the following steps to modify the AutoLoanFlow sample for WebLogic:

  1. Delete the following file from the filesystem:

    BPEL_HOME\samples\demos\AutoLoadDemo\AutoLoanFlow\bpel\decisionservices.decs

  2. Open the AutoLoanFlow sample from JDeveloper Studio as a JDeveloper project using the following file:

    BPEL_HOME\samples\demos\AutoLoanDemo\AutoLoanFlow\AutoLoanFlow.jpr

  3. Open the AutoLoanFlow.bpel file from the Applications Navigator (found within the AutoLoanFlow project).

  4. From the Services swim lane of AutoLoanFlow.bpel, delete the following decision service partnerlinks:

    • CreditRatingAgent

    • LoanAdvisorAgent

  5. Follow the steps II, III, IV and V of "Modelling Auto Loan Broker Process" from BPEL_HOME\samples\demos\AutoLoanDemo\AutoLoanBroker.pdf to recreate the two Decision Service applications.

2.7.4 Known Issues on non-Oracle Platforms

The AutoLoanFlow BPEL process has two Decision Service applications as partnerlinks (CreditRatingAgent and LoanAdvisorAgent). By default, the context-root generated for both these J2EE applications are same with the value - /rules/${domain_id}/${process_id}/${process_revision}

The ${} attributes are replaced by actual values during the build and deploy of the Auto Loan Flow. However, as the context-root is not unique for these two applications, these cannot be deployed on WebLogic. When the second application is deployed/started on WebLogic it would complain that the context-root is already in use.This is an issue on non-Oracle application servers when a BPEL pProcess references more than one Decision Service partnerlinks generated from JDeveloper Studio. As a workaround, after generating the Decision Service applications on JDeveloper and before doing a build and deploy, perform the following:

  • Modify the AutoLoanFlow\decisionservices\CreditRatingAgent\ear\META-INF\application.xml file.

    Change <context-root>/rules/${domain_id}/${process_id}/${process_revision}</context-root> to <context-root>/rules/${domain_id}/${process_id}/${process_revision}/CreditRatingAgent</context-root>

  • Modify the AutoLoanFlow\decisionservices\CreditRatingAgent\war\WEB-INF\web.xml file.

    Change <url-pattern>CreditRatingAgent</url-pattern> to <url-pattern>/</url-pattern>

  • Finally, build and deploy the Auto Loan Flow using the Integration Server Connection. In the application navigator, right-click the BPEL project and select Deploy.

    This would automatically deploy the BPEL process into BPEL engine running at the Integration Server connection.

The following J2EE applications should be manually deployed into WebLogic using the WebLogic Admin console:

  • CreditRatingAgent.ear

  • LoanAdvisorAgent.ear

  • AutoLoanFlowUI.ear

  • <domain>_AutoLoanFlow_<version>_LoanApproval.ear

2.7.5 Deploying J2EE Applications on WebLogic

Perform the following steps to deploy the applications to WebLogic:

  1. Start the Weblogic server using the startWeblogic.cmd/sh command.

  2. Log in to WebLogic Admin console using http://<hostname>:8001/console.

  3. Select Deployments.

  4. Click Lock & Edit.

  5. Navigate to the directory where the target ear file is located on the file system.

  6. Select the ear file and choose Deploy.

  7. Choose oracleBPELServer as the target server, and select "I will provide the deployment in this directory" option.

  8. Click Finish Deployment.

  9. Click Activate Changes.

  10. Start the deployed application from list of deployments.

2.7.6 Running the Sample

When the process is deployed, perform the following steps to test the sample:

  1. Open the AutoLoanFlow UI at http://<hostname>:9700/AutoLoanFlowUI.

  2. Click the Initiate New BPEL Loan Flow link.

  3. Accept the default payload and click Submit Loan Application.

  4. Log in to the worklist at http://<hostname>:9700/integration/worklistapp using jstein/welcome1 as the username and password.

  5. Click the Task title (Loan Approval for Irving Stone).

  6. Examine the task payload, the credit rating for that loan should be 500 with "Medium" risk and a Credit Max Amount of 50000.0.

    The provider for the Loan Offer should be "Premium Bank" with an APR of 4.0

  7. Approve the task.

  8. Verify the AutoLoanFlow instance.

2.8 Limitations, Known Issues, Troubleshooting Tips

This section describes the limitations, known issues, and troubleshooting tips for Oracle BPEL Process Manager 10.1.3.3 on BEA WebLogic Server version 9.2.

2.8.1 Limitations

Note the following limitations:

  • BEA WebLogic Server 9.2 and Oracle BPEL Process Manager 10.1.3.1 should be installed as the same user on Linux and the user should not be a root user.

    Note:

    If you install BEA WebLogic Server 9.2 and BPELPM 10.1.3.1 as different users, then the file permissions and ownership for files under the following directories should be verified and changed to BPELPM install user:
    • BPEL_HOME\lib

    • BPEL_HOME\lib\rules

    • BPEL_HOME\system\appserver\oc4j\webservices\lib

    • BPEL_HOME\system\services\lib

    • BPEL_HOME\system\config

    • BPEL_HOME\utilities\

2.8.2 Known Issues

Note the following known issues:

JMS Adapter

  • JMS Adapter throws the following NullPointerException during initialization on non-Oracle platforms:

    JmsConnectionFactory: Unable to set connectionparameters for OracleConnectionManager
    java.lang.NullPointerException
    at
    oracle.tip.adapter.jms.JmsConnectionFactory.<init>(JmsConnectionFactory.java:91)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnectionFactory
    (JmsManagedConnectionFactory.java:80)
    

    This is a benign error and does not stop the JMS connection factory from initializing.

Decision Services

  • The following data type binding warnings and errors are displayed during deployment and start of Decision Service (Business Rules) Applications. These errors and warnings can be ignored.

    <WS data binding error>could not find schema type '{http://www.w3.org/2001/XMLSchema}NCName
    <WS data binding error>could not find schema type
    '{http://websphere.ibm.com/webservices/}SOAPElement
    java.lang.IllegalStateException
    at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalElementNode.
    getSchemaProperty(AnonymousTypeFinder.java:253)
    at
    weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder.getHiddenArrayElement
    ComponentTypeNamed(AnonymousTypeFinder.java:104)
    <WS data binding error>could not find schema type
    '{http://www.w3.org/2001/XMLSchema}long
    <WS data binding error>could not find schema type
    '{http://xml.apache.org/xml-soap}Element
    <WS data binding error>could not find schema type
    '{http://www.w3.org/2001/XMLSchema}anyType
    <WS data binding error>could not find schema type
    '{http://www.w3.org/2001/XMLSchema}string
    could not identify anonymous schema type named 'http://xmlns.oracle.com/AutoLoanFlow/CreditRatingAgent:tProperty[0,unbounded]', ignoring
    <WS data binding error>While processing <exception-mapping> for
    wsdlMessageName='{http://xmlns.oracle.com/AutoLoanFlow/CreditRatingAgent}decis
    ionServiceError',
    wsdlMessagePartElement='{http://xmlns.oracle.com/AutoLoanFlow/CreditRatingAgen
    t}errorInfo'.  Unable to find a BindingType in the binding file  for
    javaTypeName ='oracle.bpel.services.rules.DecisionServiceError',
    xmlTypeName='e=errorInfo@http://xmlns.oracle.com/AutoLoanFlow/CreditRatingAgent'.  The cause of this error is likely because an <exception-mapping> specified
    for {http://xmlns.oracle.com/AutoLoanFlow/CreditRatingAgent}decisionServiceErrorrequires that a <java-xml-type-mapping> exist for java
    type='oracle.bpel.services.rules.DecisionServiceError',
    xmlTypeName='e=errorInfo@http://xmlns.oracle.com/AutoLoanFlow/CreditRatingAgent', with a <root-type-qname> of 
    {http://xmlns.oracle.com/AutoLoanFlow/CreditRatingAgent}errorInfo
    <WS data binding error>oracle.bpel.services.rules.DecisionServiceError is not understood because there is no type mapping for exception class
    

2.8.3 Troubleshooting Tips

The following list explains the troubleshooting tips encountered while installing Oracle BPEL Process Manager with the BEA WebLogic Server, and their resolutions:

2.8.3.1 Using Server Start Up Options

For any class path and security permission errors that you encounter while configuring Oracle BPEL Process Manager on the BEA WebLogic Server, perform the following steps to correct the class path and security policy file options:

  1. Log in to http://localhost:8001/console,using weblogic as the username and password.

  2. Select Environment -> Servers -> oracleBPELServer. The Settings of oracleBPELServer page is displayed.

  3. Click the Server Start tab.

  4. Edit the following properties:

    • Class Path: Contains the path on the machine running Node Manager, which is used to start the oracleBPELServer. You can append a class path value to the class path mentioned in this field.

    • Arguments: Contains the arguments, which is used to start the oracleBPELServer. You can add arguments to the existing argument list that are required to start the server.

    • Security Policy File: Contains the security policy file, which is used to start the oracleBPELServer. You can also add your own policy file in this location. To do, you need to add the following line inside the grant scope of the policy file:

      permission com.collaxa.security.ServerPermission "server", "read";