4 Post Installation

4.1 Configuring BPEL Samples

Complete the following steps to configure BPEL Samples and seed default JAZN Users for HWF and Worklist Application:

1. Update the SOA_ORACLE_HOME/bpel/utilities/ant-orabpel.properties file by setting the following properties values:

   • set the admin.user to soaadmin

   • set the admin.password to the cleartext password of soaadmin

2. Open a BPEL Dev prompt and navigate to the SOA_ORACLE_HOME/bpel/samples directory.

3. Execute the obant.sh/bat install script.

   The obant script will backup existing and unzip the latest samples.

   • Set the tokenized parameters in the samples to values from the ant-orabpel.properties file.

     The steps seed the default jazn user community for identity service/Workflow samples/worklistApp.

   • Change the admin.password to admin.encrypted.password based on the provided cleartext value.

   • The steps seed the default jazn user community for identity service/Workflow samples/worklistApp.

4.2 Configure ESB Systems using ESB Console

Complete the following steps to configure ESB systems using ESB Console:

1. Change the ESB System configuration from the esb console

2. Ensure that the system information for the ESB services have the following values:

   • Virtual Host: The hostname of ESB design-time instance

   • Port: The port number of ESB design-time instance

   • Topic Location: ESB_JAVA_DEFERRED

The value of the Connection Factory Location parameter does not matter for ESB on Oracle WebLogic Server; this is because ESB, by default, uses AQ messaging. ESB also uses the AQ JMS API to connect to the AQ Messaging topics.

4.3 Configuring ESB Design time Parameters

Update the ORAESB.ESB_PARAMETER table to ensure that the values for DT_OC4J_HOST and DT_OC4J_HTTP_PORT are the same as the host name and port number of the managed server running ESB Services application.

The default values from the installation are:

• DT_OC4J_HOST = localhost

• DT_OC4J_HTTP_PORT = 9700

4.4 Starting soa10g_server Using Node Manager Instead of the startManagedWeblogic script

To start the managed server from the AdminConsole instead of from startManagedWeblogic.sh/.bat command, set the StartScriptEnabled=true parameter in the nodemanager.properties file.

Note that the nodemanager.properties file is only generated when you start NodeManager for the first time.

In order to generate the nodemanager.properties file:

1. Start NodeManager using in the MW_HOME/wlserver_10.3/server/bin directory using either the startNodeManager.cmd (Microsoft Windows) or startNodeManager.sh (Linux).

2. Edit the MW_HOME/wlserver_10.3/common/nodemanager/nodemanger.properties file, set the parameter StartScriptEnabled=true.

3. Terminate the node manager process.

4. Re-start the node manager again.

After completing these steps, you should be able to start and stop the managed server from the WebLogic Admin Console.

4.5 OWSM ServerAgent to secure BPEL Processes

The section describes how to enable the OWSM ServerAgent to secure BPEL processes. Complete the following steps:

1. Create the Server Agent from the OWSM user interface with Container Type = OTHER.

   Verify that you have created a new component. For example, C0003003 service_agent Server Agent.

   Be sure to add the Required Policies to the ServerAgent.

   Refer to step 6 for BPEL Process specific policies

2. Inject the soabpel.ear file with the ServerAgent using the wsmadmin installAgent with the following updates to SOA_ORACLE_HOME/owsm/bin/agent.properties:

   • agent.componentType=serveragent

   • agent.containerType=WEBLOGIC

   • agent.containerVersion=10.3.1

   • webservice.application.input=SOA_ORACLE_HOME/soa/applications/soabpel-ServerAgent/soabpel.ear

   • webservice.application.webapp.name=startup.war

   • agent.component.id=C0003003

   Verify that - CoreSvFilter - ServletFilterHook is added in the soabpel./startup.war.xml file.

3. Restart Oracle SOA Suite with Oracle WebLogic Server with the re-generated soabpel.ear file.

4. Initiate async and sync bpel from the Initiate page and SoapUI HelloWorld CreditRatingService.

5. Check the OWSM console for service_agent calls.

   Go to Operation Management > Overall Statistics > Message Logs > service_agent.

6. Verify that the ServerAgent processed calls from the message logs.

   For example:

   1 /orabpel/default/HelloWorld/1.0  Tuesday, August 18, 2009 01:00:18 PM Request
   2 /orabpel/default/HelloWorld/1.0 Tuesday, August 18, 2009 01:00:22 PM Response
   3 /orabpel/default/CreditRatingService/1.0 Tuesday, August 18, 2009 01:04:14 PM Request
   4 orabpel/default/CreditRatingService/1.0 Tuesday, August 18, 2009 01:04:17 PM Response
   

4.6 Changing dehydration store for BPEL, ESB and OWSM

For BPEL and ESB, the following steps describe how the dehydration store details can be changed from the WLS Admin console:

1. Login to WLS Admin console.

2. Goto SOADomain -> Services -> JDBC -> Datasources.

3. There are 5 datasources which are created for BPEL and ESB:

   • BPELServerDataSource

   • BPELServerDataSource

   • Workflow

   • esbaqdatasource

   • esbds

4. To change the dehydration store details click on each datasource link, go to Connection Pool and provide the appropriate information in the required fields.

For OWSM:

1. Change the database information in the install.properties file found in the SOA_ORACLE_HOME/owsm/bin directory.

2. Stop the managed server (soa10g_server).

3. From the command prompt, goto the SOA_ORACLE_HOME/owsm/bin directory.

4. Run wsmadmin.bat(sh) install.

5. This will update the OWSM configuration properties and regenerate the OWSM applications.

6. Start the managed server (soa10g _server).

4.7 Client side Configurations for HWF API Clients

To enable client side configuration for HWF API Clients:

1. Update the SOA_ORACLE_HOME/bpel/system/services/config/wf_client_config.xml file with a valid WLS user for SOADomain.

   For example:

   <user>soaadmin</user>
   <password>welcome1</password>
   

2. HWF clients should refer to the following in the classpath for HWF API over Remote/SOAP binding

   WLS_HOME/server/lib/weblogic.jar
   SOA_ORACLE_HOME/bpel/system/classes
   SOA_ORACLE_HOME/bpel/lib/orabpel.jar
   SOA_ORACLE_HOME/bpel/lib/orabpel-boot.jar
   SOA_ORACLE_HOME/bpel/lib/orabpel-exts.jar
   SOA_ORACLE_HOME/bpel/lib/orabpel-common.jar
   SOA_ORACLE_HOME/webservices/lib/saaj-api.jar
   SOA_ORACLE_HOME/webservices/lib/orasaaj.jar
   SOA_ORACLE_HOME/lib/xmlparserv2.jar
   SOA_ORACLE_HOME/lib/xml.jar
   SOA_ORACLE_HOME/bpel/lib/oracle_http_client.jar
   

3. HWF clients should define the following system properties for HWF API over Remote/SOAP binding:

   -Djavax.xml.parsers.DocumentBuilderFactory=oracle.xml.jaxp.JXDocumentBuilderFactory
   -Djavax.xml.parsers.SAXParserFactory=oracle.xml.jaxp.JXSAXParserFactory
   -Djavax.xml.transform.TransformerFactory=oracle.xml.jaxp.JXSAXTransformerFactor
   -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl
   -Djavax.xml.soap.SOAPFactory=oracle.j2ee.ws.saaj.soap.SOAPFactoryImpl
   -Djavax.xml.soap.SOAPConnectionFactory=oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnectionFactory
   -Djavax.xml.soap.SOAPElementFactory=oracle.j2ee.ws.saaj.soap.SOAPFactoryImpl
   

4.8 Steps to Enable Notification

To enable Notification on your Oracle SOA Suite with Oracle WebLogic Server installation you need to obtain the velocity-dep-1.5.jar file. This file is required for the notification feature to work.

The BPEL notification feature is disabled by default. To enable the BPEL notification feature, you must download the velocity-dep-1.5.jar file.

To enable notification:

1. Download the velocity-dep-1.5.jar file from http://archive.apache.org/dist/velocity/engine/1.5.

2. Place the JAR file in the $Oracle_Home/bpel/lib directory (UNIX) or the Oracle_Home\bpel\lib directory (Microsoft Windows).

3. Restart the managed server for SOADomain.

This enables the BPEL notification feature to display in Oracle BPEL Control.

4.9 Configuring Identity Service with LDAP repository

Complete the following steps to use the Oracle Internet Directory LDAP provider:

1. Stop the managed server.

2. Backup the existing SOA_ORACLE_HOME/bpel/system/services/config/is_config.xml file.

3. Make a copy of SOA_ORACLE_HOME/bpel/system/services/config/ldap/is_config_for_OID.xml and rename it as SOA_ORACLE_HOME/bpel/system/services/config/is_config.xml.

4. Point is_config.xml to a valid Oracle Internet Directory repository.

5. Backup the existing SOA_ORACLE_HOME/j2ee/home/config/jazn.xml file as .orig in the same location.

6. In the SOA_ORACLE_HOME/j2ee/home/config/jazn.xml file, comment out the section using the XML provider and uncomment out the section using LDAP.

7. Provide the Oracle Internet Directory details as shown below.

   For example:

   <jazn provider="LDAP" location="ldap://pdrab02-4.us.oracle.com:40864"
   default-realm="us">
      <property name="ldap.user" value="cn=orcladmin"/>
      <property name="ldap.password" value="!welcome1"/>
      <property name="ldap.protocol" value="no-ssl"/>
   </jazn>
   

8. Restart managed server

4.10 Deploying Human Task and Decision Services .ear Files

• Deploying Human Task Form EAR

• Deploying Decision Services .ear

4.11 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 SOA_ORACLE_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI\WEB-INF directory.

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

   • Move:

     SOA_ORACLE_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI\WEB-INF\web.xml
     

     To:

     SOA_ORACLE_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\
     PriceQuote\SelectManufacturingUI\web.xml_oc4j
     

   • Move:

     SOA_ORACLE_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI\web.xml_weblogic
     

     To:

     SOA_ORACLE_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI\WEB-INF\web.xml
     

3. Create an .xml file named weblogic.xml in the SOA_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_ORACLE_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI\ directory.

5. Copy completeTask.jsp_weblogic to completeTask.jsp in SOA_ORACLE_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturingUI directory

6. Open Bpel Dev prompt

7. Change directories to the following:

   SOA_ORACLE_HOME\bpel\samples\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, SelectManufacturingUI, default_SelectManufacturing_1_0_Approval., and default_OrderApproval_1_0_OrderApproval.ear for Human Workflow must be manually deployed into the Oracle WebLogic Server..

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

12. Note the CreateOrderBookingUI and SelectManufacturingUI were created when you ran ant in Step 10.

13. Change to the SOA_ORACLE_HOME\bpel\samples\tutorials\127.OrderBookingTutorial\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. Change to Oracle_Home\bpel\samples\tutorials\127.OrderBookingTutorial\PriceQuote\SelectManufacturing\public_html\Approval\form directory.

16. Note the default_SelectManufacturing_1_0_Approval.ear file that was created when you ran ant in Step 10.

17. 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>:<adminport>/console
    

18. Select soa10g_server1 as the deployment target.

19. Restart soa10g_server1 from the console.

20. Run the following OrderBooking Tutorial steps:

    1. Initiate the process using http://<hostname>:<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://<hostname>:default_port/integration/worklistapp/Login where default_port is as defined in the SOADomain.properties file.

4.12 Running Adapter Samples

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

4.13 Design-time Deployment Support Oracle SOA Suite 10.1.3.5.1 on Oracle WebLogic Server 10.3.1

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

• From the BPELPM Developer Prompt Using Ant

• From JDeveloper

4.14 Exception During Managed Server Shutdown

When you shut down the ESB Managed server you will may receive the following exception message:

SEVERE: ESB server shutdown: Failed to stop one or more System 
java.lang.NullPointerException 

This ESB server shutdown exception occurs when you have wrong data. For example, TOPIC_NAME, HOSTNAME, and PORT to any one or more ESB Systems in the ESB console.

When you correct the data values to ESB Systems the change will not take effect until you restart the server.

Set following values in ESN console for everty ESB Service:

• Virtual Host: The hostname of ESB design-time instance

• Port: The port number of ESB design-time instance

• Topic Location: ESB_JAVA_DEFERRED