1 Installing Oracle SOA Suite with WebLogic Server

1.3.1 Step 1: Configure the Oracle Database

Follow these instructions to install Oracle Database 10g.

1. Install Oracle Database 10g 10.1.0.2. Refer to http://www.oracle.com/pls/db102/homepage for install instructions.

2. Install the Oracle Database 10g 10.1.0.5 patch in the same Oracle home in which you installed Oracle Database 10g. Refer to http://download.oracle.com/docs/cd/B25553_01/install.1012/b25463/infrainexistingdb.htm#sthref415 for installing the patch.

1.3.2 Step 2: Install Oracle SOA Suite Basic 10.1.3.1.0 for OC4J

The install instructions to install basic Oracle SOA Suite 10.1.3.1 for OC4J is available at

http://www.oracle.com/technology/software/tech/soa/index.html

You must install Oracle SOA Suite 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 must 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.

1.3.3 Step 3: Create the Oracle SOA Suite Schemas in the Oracle Database

1. Navigate to the install\soa_schemas\irca folder in the Oracle SOA Suite Installer directory.

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

   set ORACLE_HOME=c:\Oracle10g
   

3. Enter irca.bat on Windows and ./irca.sh in Linux.

   This runs the irca script to create the schemas required for BPEL, ESB, and OWSM.

4. Enter sys password when prompted.

   The orabpel, oraesb, and orawsm schemas are loaded on the Oracle Database.

1.3.4 Step 4: Upgrade SOA Schemas to 10.1.3.4

In this step, you will apply the SOA Suite Patchset 10.1.3.4 and also upgrade ORABPEL and ORAESB schemas to 10.1.3.4.

Step 4-1: Upgrade ORABPEL and ORAESB Schemas to 10.1.3.4

To upgrade ORABPEL and ORAESB schemas to 10.1.3.4, perform the following steps:

1. Run the 10.1.3.4 SOA Schema upgrade scripts for orabpel/oraesb schemas that are available in the SOA Suite 10.1.3.4 Patchset Installation pack.

2. Execute the following script to upgrade the ORABPEL schema:

   install\soa_schema_upgrade\bpel\scripts\upgrade_10133_10134_oracle.sql

3. Execute the following script to upgrade the ORAESB schema:

   install\soa_schema_upgrade\esb\sql\oracle\upgrade_10133_10134_oracle.sql

1.3.5 Step 5: Apply SOA Suite Patchset 10.1.3.4

To apply SOA Suite Patchset 10.1.3.4, perform the following steps:

1. You can download the SOA Suite Patchset 10.1.3.4 from metalink.oracle.com with the following patch number - 7272722 Oracle Fusion Middleware Family: Patchset 10.1.3.4 PATCHSET UPLOAD.

2. Follow the instructions in the patchset to install the patchset on the Oracle SOA Suite 10.1.3.1.

   Caution:

   You should not start/restart the Oracle SOA Suite instance of OC4J server after applying the patch.

3. Shutdown the SOA Suite Post patch upgrade as follows:

   For...	Run...
   Windows XP	SOA_HOME\opmn\bin> opmnctl stopall
   Linux	SOA_HOME\opmn\bin> ./opmnctl stopall

   
   

1.3.6 Step 6: Apply Patch for Oracle SOA Suite 10.1.3.4 on WebLogic 9.2

You must download the Patch for Bug 7337034 (HOTPLUG: SOASUITE 10.1.3.4 ON WEBLOGIC 9.2 - CHANGES FOR HOTPLUGGABILITY) from MetaLink and then apply the patch on Oracle SOA Suite 10.1.3.4.

1. Download the Patch p7337034_101340_GENERIC.zip for Bug 7337034.

2. Follow the instructions given in the Readme.txt file of the patch and apply the patch on Oracle SOA Suite 10.1.3.4.

3. Shutdown the Oracle SOA Suite post patch upgrade as follows:

   For...	Run...
   Windows XP	XP SOA_HOME\opmn\bin> opmnctl stopall
   Linux	SOA_HOME/opmn/bin> ./opmnctl stopall

   
   

1.3.7 Step 7: Install and Configure WebLogic Server Version 9.2

1. Install 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. The contents of this zip file are extracted to Weblogic_SOA10134 folder. This zip file contains both the base (Weblogic_SOA10134_Base) and the HA scripts (WeblogicSOA10134HA). The directory structure when you unzip the Weblogic_SOA10134.zip file is as follows:

   Weblogic_SOA10134 
          Weblogic_SOA10134_Base (Non-HA)
          WeblogicSOA10134HA (HA) 
          Readme.txt
          
   

   Note:

   • The directory to which you download the Oracle SOA Suite should be the same host on which the WebLogic Server is installed.

   • Unzip the Weblogic_SOA10134_Base folder as a non-root user (same user as used to install Oracle SOA Suite 10.1.3.1 for OC4J). For example, Oracle.

   • If installing on Linux, then change the permissions to the Weblogic_SOA10134_Base folder using the chmod -R 755 Weblogic_SOA10134_Base command.

3. Modify the following mandatory installation properties in the Weblogic_SOA10134_Base\SOADomain.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. Ensure that you use forward slash for all the paths in the property files.

   However, the proxy settings properties, such as PROXY_HOST is non-mandatory.

   Property	Description
   BEA_HOME	The directory path in which WebLogic Server is installed. For example, BEA_HOME=C:/bea.
   WL_HOME	The directory path WebLogic Server is installed, which is usually under BEA_HOME. For example, WL_HOME=C:/bea/weblogic92
   JAVA_HOME	JAVA path of WebLogic. For example, JAVA_HOME=C:/bea/jdk150_06
   CREATE_NEW_DOMAIN	Set this property to 'NO' if you wish to create SOA Server as a managed server in any existing domain. Set this property to 'YES' if you wish to create SOA Server in the new domain "SOADomain". For example, CREATE_NEW_DOMAIN=YES (or) CREATE_NEW_DOMAIN=NO
   DOMAIN_HOME	The path for a new WebLogic domain called SOA Domain. For example, DOMAIN_HOME=C:/bea/user_projects/domains
   EXISTING_DOMAIN_NAME	This is the name of the existing domain where you wish to create SOA Server as a managed server. This property value should be set only when you set the CREATE_NEW_DOMAIN as NO. For example, EXISTING_DOMAIN_NAME=MySOADomain
   ADMIN_SERVER_PORT	This is the port where the existing domain's Admin Server is running. This property value should be set only when you set the CREATE_NEW_DOMAIN as NO. For example, ADMIN_SERVER_PORT=7001
   NEW_ADMIN_SERVER_PORT	This is the port where you wish to run the Admin Server. This property value should be set only when you set the CREATE_NEW_DOMAIN as YES. For example, NEW_ADMIN_SERVER_PORT=8001
   SOA_SERVER_NAME	The server, which is created, under SOA Domain. For example, SOA_SERVER_NAME=oracleSOAServer
   SOA_SERVER_PORT	The port where SOA_SERVER_NAME is running. For example, SOA_SERVER_PORT = 9700
   APPS_HOME	The path where applications and adapters will be deployed from. For example, APPS_HOME=C:/bea/user_projects/apps
   SOA_HOME	The directory path in which Oracle SOA Suite is installed. For example, SOA_HOME=C:/product/10.1.3.1/OracleAS_1/
   DB_URL	This is the URL to connect to ORABPEL schema. For example, DB_URL=jdbc:oracle:thin:@stbbn10.us.oracle.com:1521:orcl
   DB_BPEL_PASSWORD	The password for ORABPEL schema in database. For example, DB_BPEL_PASSWORD=ORABPEL
   DB_ESB_PASSWORD	The password for ORAESB schema in database. For example, DB_ESB_PASSWORD=ORAESB
   DB_OWSM_PASSWORD	The password for ORAWSM schema in database. For example, DB_OWSM_PASSWORD=ORAWSM
   PROXY_SET	The valid values are true or false. Indicates whether proxy settings need to be configured for the server.
   PROXY_HOST	The host name of the proxy server. A valid value should be provided, if PROXY_SET is set to true. For example, PROXY_HOST=www-proxy.us.oracle.com
   PROXY_PORT	The port where the proxy server is running. A valid value should be provided, if PROXY_SET is set to true. For example, PROXY_PORT=80
   NON_PROXY_HOST	The list of non-proxy hosts that are divided by a | symbol. A valid value should be provided, if PROXY_SET is set to true. For example, NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|
   SECURITY_MODEL	This is to specify the security model to be used for the SOA Apps deployments. SECURITY_MODEL Possible Values: [ DDOnly | CustomRoles |CustomRolesAndPolicy | Advanced ] For example, SECURITY_MODEL=DDOnly
   SECURITY_GROUP_NAME	This value is to be changed, if you desire to map the role to an existing group in your realm. Otherwise, SECURITY_GROUP_NAME defaults to SoaGroup.

   
   

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

   Note:

   • Before running the setup.bat or setup.sh file, set the environment 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.

   • Some of the above properties may have been set in the SOADomain.properties file, but they should be set again as environment values, since they are needed even before the SOADomain.properties can be read by the script.

   • Refer to Upgrade Path for SOA Suite 10.1.3.3 on WebLogic 9.2 Installation for existing SOA Suite 10.1.3.4 on Weblogic 9.2 customers.

   • This script will prompt to enter a password for the default 'weblogic' user at the command prompt. The password entered would be set as password for the 'weblogic' user. By default, the 'weblogic' user would have access to the Admin console and all the SOA Application pages.

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

   
   

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

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 SOA domain, which enables you to start and stop oracleSOAServer remotely using admin console. You can also start and stop the node manager from the Windows Services by running the installNodeMgrSvc.cmd from the BEA_HOME\weblogic92\server\bin\ directory.

6. Start WebLogic Server as follows:

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

   
   

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

   http://localhost:8001/console
   

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

7. Start the oracleSOAServer 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 WebLogic Server Administrative Console window is displayed.

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

      
      

   3. Click the Control tab. The Settings of OracleSOAServer Control page is displayed.

      
      

   4. In the Server Status pane, select oracleSOAServer and click Start. The Server Life Cycle Assistant page is displayed.

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

   Note:

   Do not start Oracle BPEL Server from the Windows Start Menu or by running the SOA_HOME\bpel\bin\startorabpel script. These actions are not supported.

   The managed server in SOADomain (OracleSOAServer) should not be started using the startManagedWeblogic.cmd/sh commands.

   The managed server for SOA uses custom classpath, security policy, and server properties, which will not be set when the managed server is started using the commands. Instead, always use the Admin Server console to start the managed servers.In order to use the startManagedWeblogic commands, include the values for the following attributes in the setDomainEnv.cmd/sh files from the Server Start page for OracleSOAServer (OracleSOAServer ->Configuration -> Server Start):

   • Classpath

   • Arguments

   • Securuty Policy File

8. Log in to the BPEL console at the following URL, using weblogic as the username and password:

   http://localhost:9700/BPELConsole

1.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:

• Prerequisite Checks

• Steps to Deploy Using the BPELPM Prompt

1.4.2 From JDeveloper

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

• Prerequisite Checks

• Steps to Deploy Using JDeveloper

1.5.1 Deploying Human Task Form EAR

To deploy human task form ear:

1. Change to the …\public_html\…\form in the directory of the sample.

2. Note the ear file created in the directory.

3. Extract the application.xml from the ear into the META-INF folder. Open application.xml and add the following DTD to it.

   <application version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee" (http://java.sun.com/xml/ns/j2ee) 
   
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" (http://www.w3.org/2001/XMLSchema-instance) 
   
   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" (http://java.sun.com/xml/ns/j2eehttp://java.sun.com/xml/ns/j2ee/application_1_4.xsd)>
   

4. Add the modified application.xml back into the ear in the same folder structure in the META-INF folder.

5. Extract the war file from inside the ear file. Extract the web.xml file from the war into the WEB-INF folder. Open web.xml and add the following DTD to it.

   <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
   

6. Put the modified web.xml back into the war in the same folder structure under WEB-INF. Then, add the modified war file back in to the ear.

   See Also:

   For deploying the ear please look up the section under "Deploying J2EE Applications on WebLogic".

1.5.2 Deploying Decision Services EAR

To deploy decision services ear:

1. Change to the ..\decisionservices\.. directory of the sample.

2. Note the ear file created in the directory.

3. Create an exploded directory version of the Decisionservices ear file. For example, if the ear file in your machine is DecisionService.ear, then the steps to create an exploded directory are as follows:

   1. Rename the DecisionService.ear to DecisionService.zip.

   2. Create a new folder with the name of the ear called DecisionService.

   3. Extract the DecisionService.zip to DecisionService folder that you created in Step b. The META-INF folder and DecisionService-web.war file is created in the DecisionService folder.

   4. Navigate to DecisionService folder and rename the DecisionService-web.war to DecisionService-web.zip.

   5. Create a new folder with the name of the war file called DecisionService-web in the DecisionService folder.

   6. Extract the DecisionService-web.zip to DecisionService-web folder that you created in Step e.

   7. Delete the DecisionService-web.zip from the DecisionService folder.

   8. Navigate to DecisionService-web folder, and you will notice the following three folders: META-INF, public_html, and WEB-INF.

   Note:

   Here, WebLogic needs the decision services ear to be deployed as an exploded directory version and not as an .ear file.

   Repeat steps a to h to create an exploded directory version of the ear file that you would want to deploy.

   See Also:

   For deploying the ear please look up the section under "Deploying J2EE Applications on WebLogic".

1.6.1 Verifying Installation from the WebLogic Server Console

Perform the following steps to check if the Admin console has started:

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

   
   Description of the illustration beaconsole.gif
   
   

   Log in using weblogic as the username and password.

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

   
   Description of the illustration beaconsolegn.gif
   
   

3. Verify that you can view the oracleSOAServer startup properties page by selecting Environment -> Servers -> oracleSOAServer -> 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 the illustration beaconserverstart.gif
   
   

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

   
   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 -> SOAJMSModule -> Configuration.

   
   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 the illustration beadatasources.gif
   
   

1.6.2 Verifying BPEL, ESB, OWSM Consoles

Perform the following steps to check if the BPEL, ESB, OWSM consoles have started:

1. Navigate to http://localhost:<default_port>/BPELConsole/ (Or to the location where the software is installed, for example, http://<machine-name>:<default_port>/BPELConsole/. The BPEL Console window is displayed as shown in Figure 1-1.

   Navigate to the http://localhost:<default_port>/esb/. The ESB Console window is displayed, as shown in Figure 1-2.

   Navigate to the http://localhost:<default_port>/ccore/Login.jsp. The OWSM Console window is displayed, as shown in Figure 1-3.

   Figure 1-1 BPEL Console Window

   
   Description of "Figure 1-1 BPEL Console Window"
   
   

   Figure 1-2 ESB Console Window

   
   Description of "Figure 1-2 ESB Console Window"
   
   

   Figure 1-3 OWSM Console Window

   
   Description of "Figure 1-3 OWSM Console Window"
   
   

2. Log in to the BPEL Console using the username and password, the Oracle Enterprise Manager BPEL Control page is displayed, as shown in Figure 1-4.

   Figure 1-4 Oracle Enterprise Manager BPEL Control

   
   Description of "Figure 1-4 Oracle Enterprise Manager BPEL Control"
   
   

   Log in to the ESB Console using the username and password, the Oracle Enterprise Manager ESB Control page is displayed, as shown in Figure 1-5.

   Figure 1-5 Oracle Enterprise Manager ESB Control

   
   Description of "Figure 1-5 Oracle Enterprise Manager ESB Control"
   
   

   Log in to the OWSM Console using the username and password, the Oracle Enterprise Manager Web Services Manager Control page is displayed, as shown in Figure 1-6.

   Figure 1-6 Oracle Enterprise Manager OWSM Control

   
   Description of "Figure 1-6 Oracle Enterprise Manager OWSM Control"
   
   

3. Verify that the esbprotocol.jar file is copied to <BEA_HOME>\jrockitXX\jre\lib\ext directory.

   If not this may be due to a different JAVA_HOME specified in the SOADomain.properties file. The WebLogic managed servers uses jrockit JRE, by default, to start the servers (on Windows and Linux) and ESB expects the esbprotocol.jar file to be present in the jre/lib/ext directory of the JRE. Copy the esbprotocol.jar file found in SOA_HOME/integration/esb/lib before starting the managed server on WebLogic. If esbprotocol.jar is not found in the server's jre/lib/ext, ESB console will throw the following error post server start:

   "Designtime cache has not been initialized".

1.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 WebLogic Console under Resources, Resource Adapters, DB Adapter, J2C Connection Factories, BPEL Samples, Custom Properties, Connection String. Also, set the username and password.

4. Restart oracleSOAServer.

5. Select Start, All Programs, Oracle - Oracle_Home, Oracle SOA Suite, Developer Prompt.

6. Change to the following directory:

   tutorials\122.DBAdapter\SelectAllByTitle
   

7. Run the following command:

   ant
   

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

8. Select Start, All Programs, Oracle - Oracle_Home, Oracle SOA Suite, BPEL Console.

9. Click SelectAllByTitle in the Deployed BPEL Processes list.

10. Refer to the MOVIES table, and enter the movie title on the Initiate page. For example, 'The Aviator'.

11. Click Post XML Message.

12. View the results and inspect the instance.

1.6.4 Verifying the OrderBooking Tutorial Sample

The web application DTD link in the web.xml files included with Oracle SOA Suite must be modified before deployment to the WebLogic Server.

1. Search for the web.xml file in the Oracle_Home\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI\WEB-INF directory.

2. Make the following change in the above mentioned web.xml file:

   Change:

   <ejb-local-ref id="EjbRef_TaskServiceBean_Message"> <ejb-ref-name>ejb/local/TaskServiceBean</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <local-home>oracle.bpel.services.workflow.task.ejb.TaskServiceLocalHome</local-home>
   <local>oracle.bpel.services.workflow.task.ejb.TaskServiceLocal</local> <ejb-link>TaskServiceBean</ejb-link>
   </ejb-local-ref>
   <ejb-local-ref id="EjbRef_TaskMetadataServiceBean_Message"> <ejb-ref-name>ejb/local/TaskMetadataServiceBean</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <local-home>oracle.bpel.services.workflow.metadata.ejb.TaskMetadataServiceLocalHome</local-home> <local>oracle.bpel.services.workflow.metadata.ejb.TaskMetadataServiceLocal</local>
   <ejb-link>TaskMetadataServiceBean</ejb-link>
   </ejb-local-ref>
   

   To:

   <ejb-local-ref id="EjbRef_TaskServiceBean_Message">
   <ejb-ref-name>ejb/remote/TaskServiceBean</ejb-ref-name>
   <ejb-ref-type>Session</ejb-ref-type>
   <local-home>oracle.bpel.services.workflow.task.ejb.TaskServiceRemoteHome</local-home>
   <local>oracle.bpel.services.workflow.task.ejb.TaskServiceRemote</local>
   <!--ejb-link>TaskServiceBean</ejb-link-->
   </ejb-local-ref>
   <!--   <ejb-local-ref id="EjbRef_TaskMetadataServiceBean_Message">
   <ejb-ref-name>ejb/local/TaskMetadataServiceBean</ejb-ref-name>
   <ejb-ref-type>Session</ejb-ref-type>
   <local-home>oracle.bpel.services.workflow.metadata.ejb.TaskMetadataServiceLocalHome</local-home>
   <local>oracle.bpel.services.workflow.metadata.ejb.TaskMetadataServiceLocal</local>
   <ejb-link>TaskMetadataServiceBean</ejb-link>
   </ejb-local-ref>
   -->
   

3. Create an xml file by the name weblogic.xml in the Oracle_Home\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI\WEB-INF directory.

   Add the following to the weblogic.xml file:

   <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 6.1//EN" "http://www.bea.com/servers/wls610/dtd/weblogic-web-jar.dtd">
   <weblogic-web-app>
      <reference-descriptor>
          <ejb-reference-description>
            <ejb-ref-name>ejb/remote/TaskServiceBean</ejb-ref-name>
            <jndi-name>ejb/bpel/services/workflow/TaskServiceBean</jndi-name>
          </ejb-reference-description>
      </reference-descriptor>
   </weblogic-web-app>
   

   Save the weblogic.xml file.

4. Rename CompleteTask.jsp to CompleteTask_oc4j.jsp in SOA_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI\ directory.

5. Copy CompleteTask.jsp from SOA_HOME\bpel\samples\tutorials\127.OrderBookingTutorial directory to SOA_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI\ directory.

6. Select Start, All Programs, Oracle - Oracle_Home, Oracle SOA Suite, DeveloperPrompt.

7. Change directories to the following:

   tutorials\127.OrderBookingTutorial
   

8. Start SQL*Plus and run the following script:

   SQL> @PracticeFiles\insertTable.sql;
   

   This creates the required sample tables in the database.

9. Change all the BPEL partner links in the bpel.xml files to update to the default port, as defined in the SOADomain.properties file.

10. Run the following command:

    ant
    

    This compiles and deploys all projects dependent upon this tutorial. However, WAR files for CreateOrderBookingUI and SelectManufacturingUI must be manually deployed into the WebLogic Server.

11. Change to the <ORACLE_HOME>\j2ee\home\applications directory.

12. Note the CreateOrderBookingUI.war file that was created when you ran ant in Step 10.

13. Change to the OrderApproval\public_html\OrderApproval\form directory.

14. Note the default_OrderApproval_1_0_OrderApproval.ear file that was created when you ran ant in Step 10.

15. Select Install Application in the Administrative Console to deploy the war files to the WebLogic Server.

    Access the Administrative Console at the following URL:

    http://hostname:8001/console
    

16. Select oracleSOAServer as the deployment target.

17. Repeat Steps 12 through 16 for the war or ear file.

18. Restart oracleSOAServer from the console.

19. Run the following OrderBooking Tutorial steps:

    1. Initiate the process using http://localhost:<default_port>/CreateOrderBookingUI where default_port is as defined in the SOADomain.properties file.

    2. Open the console in audit or flow mode. Follow the steps that appear on the console and click task links to complete the task.

    3. After the process moves beyond supplier selection, the human workflow is added, for manual user approval (or rejection). This process has a timeout of 5 minutes and defaults to order status is rejected. Follow this step by opening the worklist URL at

       http://localhost:default_port/integration/worklistapp/Login

       where default_port is as defined in the SOADomain.properties file.

1.6.5 Running Adapter Samples

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

1.6.6 Deploying Samples Using Ant

Ensure that admin.user and admin.password in SOA_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 must 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, refer to Deploying Decision Services EAR under Deploying Human Task and Decision Services EAR Files. Start the application.

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

   Note:

   When deploying BPEL processes into oracleSOAServer on WebLogic 9.2, you only must specify the following two properties in build property files:

   • http.hostname = <SOA_hostname>

   • http.port = 9700

   These properties can be either defined in the build.properties file in your project or in the ant-orabpel.properties file. You can also create a customized build property file, which will overwrite the other two build propery files when properties get loaded by ant.

   Once properties are loaded by ant, the order in which the properties are loaded are as follows:

   1. Customized build property file

      To use this file when deploying a BPEL project, use the following command:

      ant -propertyfile <name>, where <name> is the build property filename created by users.
      

   2. build.properties file in your BPEL project

   3. If BPEL_HOME environment variable is specified, then BPEL_HOME/utilities/ant-orabpel.properties will be used, otherwise, JDEV_HOME/integration/bpel/utilities/ant-orabpel.properties is loaded by ant, where JDEV_HOME is the JDeveloper installation directory.

   It is recommended using build.properties file or customized build property files when deploying BPEL processes using ant.

1.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 SOA_HOME\bpel\system\services\lib

2. Replace the orabpel-ant.jar and orabpel.jar files within JDeveloper at jdev\integration\lib with the updated jar from SOA_HOME\bpel\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.

1.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 Oracle SOA Suite standalone is written for OC4J Application Server, it cannot be run as is on WebLogic 9.2 Application Server. Specifically, the Decision Service applications must 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.

1.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:

   SOA_HOME\bpel\samples\demos\AutoLoanDemo\AutoLoanFlow\bpel\decisionservices.decs

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

   SOA_HOME\bpel\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 SOA_HOME\bpel\samples\demos\AutoLoanDemo\AutoLoanBroker.pdf to re-create the two Decision Service applications.

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

Also, the following deployment descriptor changes are needed to successfully deploy the J2EE applications on Weblogic

• Modify the AutoLoanFlow\public_html\LoanApproval\form\ear\META-INF\application.xml file.

  Change <?xml version="1.0" encoding="UTF-8"?> to <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">

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

  Change <application version="1.4" xmlns="http://java.sun.com/xmlns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"> to <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/j2ee/dtds/application_1_3.dtd">

• 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. Perform the following steps:

1. Navigate to Oracle_HOME\bpel\samples\demos\AutoLoanDemo.

2. Execute Oracle_HOME\bpel\bin\devprompt.sh and then run ant from Oracle_HOME\bpel\samples\demos\AutoLoanDemo. This will generate the directory structure and ear files.

3. Deploy from WebLogic Admin console pointing to Oracle_HOME\bpel\samples\demos\AutoLoanDemo\AutoLoanFlow\decisionservices\CreditRatingAgent\ear as an exploded directory.

4. Deploy from WebLogic Admin console pointing to Oracle_HOME\bpel\samples\demos\AutoLoanDemo\AutoLoanFlow\decisionservices\LoanAdvisorAgent\ear as an exploded directory.

5. Deploy from WebLogic Admin console pointing to Oracle_HOME\bpel\samples\demos\AutoLoanDemo\AutoLoanFlowUI\ear as an exploded directory.

6. Deploy from WebLogic Admin console pointing to Oracle_HOME\bpel\samples\demos\AutoLoanDemo\AutoLoanFlow\public_html\LoanApproval\form\<domain>_AutoLoanFlow_<version>_LoanApproval.ear.

1.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 oracleSOAServer 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.

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

1.8.1 Limitations

Note the following limitations:

• WebLogic Server 9.2 and Oracle SOA Suite 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 WebLogic Server 9.2 and Oracle SOA Suite 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 Oracle SOA Suite install user:

  • SOA_HOME\bpel\lib

  • SOA_HOME\bpel\lib\rules

  • SOA_HOME\bpel\system\appserver\oc4j\webservices\lib

  • SOA_HOME\bpel\system\services\lib

  • SOA_HOME\bpel\system\config

  • SOA_HOME\bpel\utilities\

1.8.2 Known Issues

Note the following known issues:

• JMS Adapter

• Decision Services

• JDK Version Mismatch Causes Admin and Managed Servers Not to Start

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
  

JDK Version Mismatch Causes Admin and Managed Servers Not to Start

The Admin Server and Managed Server fail to startup with the following exception due to the JDK version mismatch:

weblogic.management.ManagementException: [Management:141266]Parsing Failure in config.xml:
javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = -9120448754896609940
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:122)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:38)at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:374)at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)

If the above error is seen during server startup, then refer to the following links:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6267224

http://forums.bea.com/thread.jspa?threadID=400001009

Workaround

Set the system property -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 for both the Admin Server and the Managed Servers. This issue is fixed in WebLogic 9.2 MP1.

1.8.3 Troubleshooting Tips

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