Page 1 of 2   next page »

In the first article I gave an overview of BPM and covered the specifications in this area. I described the order change example and the steps needed to create the business process in WLI. In the second article we saw how to create a process application, specifically how to create the application orderChange. In this application I created a new process called orderChange.jpd. To start the process I added a ClientRequest received. Next we added the Web service validate config.

In the third article I added a decision point to handle the result from validate config Web service. The decision point helps in handling both the positive and negative outcome of the result from the process. Then I added to the process a database control to check the order status of the order to be changed, and last I added another decision node to handle the result from the database Control. In the last article we saw how the change order is written out to a file, and we also saw how this change order was added to an ERP-based system specifically for SAP. We also examined the code for the process.

In this article we will see how the JPD file created can be exported to a BPEL file. We will also see how the process is executed and you can see the end result on WebLogic's Test Browser. We will also see how the process in monitored in WLI and also how HP's OpenView can be used to monitor the process.

Exporting to BPEL
In the earlier article we saw how to create a business process in WLI. It creates a JPD file based on PD4J specification. WLI gives you the facility to export this file to a WS-BPEL file through the BPEL exporter.

Below is the aforementioned JPD file now exported to BPEL:

<process name="orderchange"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:jpd="http://www.bea.com/wli/jpd"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:wli="http://www.bea.com/workshop/bpel/wli"
xmlns:ctrl="http://www.bea.com/workshop/bpel/ctrl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.openuri.org/"
expressionLanguage="http://www.w3.org/TR/2003/WD-xquery-20031112/" >

This shows the partner information:

<partnerLinks>
<partnerLink name="client" partnerLinkType="generated" myRole="provider"
partnerRole="client" />
<partnerLink name="validateConfignew" partnerLinkType="unresolved-type" />
<partnerLink name="orderstatus1" partnerLinkType="unresolved-type" />
<partnerLink name="ChangeorderFile" partnerLinkType="unresolved-type" />
</partnerLinks>

This is the start of the process:

<variables>
<variable name="orderChangexsd" type="unresolved-type" />
<variable name="fileproperties"
type="com.bea.wli.control.dynamicProperties.FileControlPropertiesDocument" />
</variables>

OrderChangeRequest as ClientRequest:

<sequence>
<receive jpd:name="orderChangeRequest" partnerLink="client" portType="clientPT"
operation="orderChangeRequest" variable="orderChangexsd" createInstance="yes" >
</receive>

JPD code is included as comments:

<jpd:javacode code="{
//#START: CODE GENERATED - PROTECTED SECTION - you can safely add code above this
comment in this method. #//
// input transform
// parameter assignment
this.orderChangexsd = orderChangexsd;
//#END : CODE GENERATED - PROTECTED SECTION - you can safely add code below this
comment in this method. #//
}
">
</jpd:javacode>

The process calling the validateConfig Web service:

<invoke jpd:name="validateConfig" partnerLink="validateConfignew"
portType="unresolved-type" operation="validateConfig" >
</invoke>

The first decision point to see if the configuration is valid:

<switch jpd:name="Is configuration Valid?">
<case jpd:name="Yes" condition="data($outValidateConfig/ns:Status) =
"true"">

Page 1 of 2   next page »