There are currently two ways to set up a content server to enable integration with Oracle SOA Suite:

• Scenario One involves installing WebCenter Content in a domain that has been extended by Oracle SOA Suite. This involves installing all parts into one domain in a particular order. The Oracle SOA Suite libraries are available to all and the class path is augmented to contain the Oracle SOA Suite libraries.

• Scenario Two involves manually copying the required libraries used by Oracle SOA Suite and augmenting the class path used to launch WebCenter Content inside of Oracle WebLogic Server.

The difference between the two scenarios is that the installation of Oracle SOA Suite augments the class path for you, while in Scenario Two this is a manual step. In the future, WebCenter Content will ship with the appropriate Oracle SOA Suite libraries.

1. Log in to the Content Server instance as a system administrator.
2. Choose Administration, then Admin Server, then Component Manager.
3. In the paragraph at the top of the page, click the Advanced Component Manager link.
4. Notice that there are two lists of Enabled and Disabled Components. Select BpelIntegration in the lower Disabled Components list.
5. Click Enable to move the item from the lower list to the upper.
6. At the bottom of the page, click Update.
7. Log in to the Oracle WebLogic Server Administration Console.
8. On the left-hand side of the console, click Domain Structure, then Environment, then Servers. The Summary of Servers page is displayed.
9. From the Control tab, select your server, then click Restart SSL.

The integration uses BPEL client libraries to communicate with Oracle BPEL Process Manager. A process configuration is required to identify connection parameters, a BPEL process, and a BPEL operation. Additionally, a process configuration identifies document metadata fields and literal values assigned to the parameters passed to the BPEL operation.

After the connections have been configured, processes can be defined and configured on the Process Configurations page. Use the Actions menu to change a process configuration.

Figure A-2 Process Configurations Page

Description of "Figure A-2 Process Configurations Page"

Access the Process Configurations page from Administration > Oracle BPEL Administration > Process Configurations.

After you create a process configuration, you must define process properties and payload mappings. For information on how to edit process properties, see Process Properties. For information on how to edit fields mappings, see Payload Mappings.

After you have defined and configured the processes, view and verify the failed processes on the Process Faults page. Use the Actions menu to view the failed processes.

Figure A-5 Process Faults Page

Description of "Figure A-5 Process Faults Page"

Access the Process Faults page from Administration > Oracle BPEL Administration > Process Faults.

The Process Faults page displays a form with five columns. Each of the columns is defined in the following table.

Use the Actions menu to clear or repair the faults.

1. Start the Workflow Administration applet.
2. Add a new Criteria Workflow. For this example, the workflow name is orabpeltest.
3. Add a step to the workflow. For this example, use initiateprocess as the step name.
4. Add step users.

   Figure A-6 Add New Step Dialog

   
5. Select the Exit Conditions tab and select at least one reviewer. (This is an arbitrary setting, but in this instance, it leaves the content item in this workflow step after a BPEL process is initiated.)

   Figure A-7 Add New Step Dialog, Exit Conditions Tab

   
6. Add an exit condition by selecting the Use Additional Exit Condition check box and then clicking Edit…
7. In the Edit Additional Exit Condition dialog, check Custom Condition Expression and add the following script:

   wfGet("conversationId") and 
   obIsInstanceClosed("process_3", wfGet("conversationId"))

   Figure A-8 Additional Exit Condition Dialog

   

   Note:

   Note that the Idoc Script function obIsInstanceClosed tests if the BPEL instance with the specified conversation ID is still open. The conversation ID is stored in the workflow companion data when the process is invoked.

8. On the Events tab, click Edit… for the Entry event.

   Figure A-9 Add New Step Dialog, Events Tab

   
9. In the Edit Script dialog, click the Custom tab.
10. Click the Custom Script Expression check box to enable the script window.
11. Type the following lines into the script window:

    <$if not conversationId$>
    <$obConfigID="process_3"$>
    <$obInvokeProcess(obConfigID)$>
    <$endif$>

    Figure A-10 Edit Script Dialog

    

    Note:

    The component defines Idoc Script functions that can be used to start and determine the state of an invoked process. The obInvokeProcess Idoc Script function takes the name of the process configuration ID as its one argument. Alternatively, you can use the ORABPEL_INVOKE_BPEL service. This service requires the obConfigID variable to be set to the name of a process configuration. The service reads the process configuration and uses it to determine how to connect to BPEL process manager.

12. Click OK to finish editing the script.
13. Click OK to finish editing the workflow step.
14. Enable the workflow.

When a content item enters the workflow and initiates a BPEL process, an identifier is created and stored in the companion data file to identify the related BPEL process. This identifier is stored with the key "conversationId" and can be obtained from the companion data with custom Idoc Script in a workflow step event.

1. From the Administration menu in WebCenter Content, choose System Audit Information.
2. Enable the requestaudit, idocscript, and bpelintegration trace sections.
3. Select the Verbose and Save check boxes.
4. Click Update.