Run the sample

Client application

To run this sample, use the Business Process Choreographer Explorer.

Business Process Choreographer Explorer (BPC Explorer)

To start the BPC Explorer in the integrated test environment of your WebSphere® Integration Developer, perform the following steps:

  1. In WebSphere Integration Developer, switch to the Servers view.
  2. In the table, right-click WebSphere Process Server v7.0.
  3. From the pop-up menu, select Launch > Business Process Choreographer Explorer.

To start the BPC Explorer on WebSphere Process Server, perform the following steps:

  1. In a web browser, open URL http://yourhost:yourport/bpc.

    2. Note: Replace yourhost with your server's internet address and replace yourport with the port of your server's HTTP transport, for example

If security is enabled, the BPC Explorer opens with a login screen:

  1. Enter a valid User ID and Password. The default User ID is admin.
  2. Click Login.

The BPC Explorer opens:

Starting the sample business process

To start the update customer process, perform the following steps:

  1. Switch to the BPC Explorer.
  2. In the Process Templates section, click Currently Valid.

    3. The Currently Valid Process Templates view is displayed:

  3. Select UpdateCustomerProcess, then click Start Instance.

    4. The Process Input Message view opens:

  4. In the customerNo field, enter a numeric value.
  5. In the firstName field, enter a string.
  6. In the familyName field, enter a string.
  7. In the creditCardNumber field, enter a string.
  8. In the creditCardCompany field, enter a string.
  9. Click Submit.

If you enter the values that are listed in the following table, the process generates the described results:

No Field Value Output / Error message Remarks
1 firstName EMPTY STRING Error: data incomplete. A custom exception is thrown: DataIncomplete
2 familyName EMPTY STRING Error: data incomplete. A custom exception is thrown: DataIncomplete
3 customerNo > 99 Customer data created. A custom exception is thrown: RecordDoesNotExist and handled by the process
4 familyName "xcpt" Unknown error. A runtime exception is thrown: IllegalStateException

Process output

Output message

Since the update customer process is a microflow, the process output message is displayed immediately after the process input message has been submitted:

In the error cases an error message is displayed:

SystemOut.log file

Inspect the SystemOut.log of your WebSphere Process Server. The update customer process writes statements similar to the following ones to the SystemOut.log:

[1/15/09 11:25:15:828 CET] 00000946 SystemOut O OpenDatabaseConnection
[1/15/09 11:25:15:828 CET] 00000946 SystemOut O UpdateCustomerRecord
[1/15/09 11:25:15:843 CET] 00000946 SystemOut O CloseDatabaseConnection

[1/15/09 11:26:16:812 CET] 00000946 SystemOut O OpenDatabaseConnection
[1/15/09 11:26:16:812 CET] 00000946 SystemOut O UpdateCustomerRecord
[1/15/09 11:26:16:859 CET] 00000946 SystemOut O CreateCustomerRecord
[1/15/09 11:26:16:875 CET] 00000946 SystemOut O CloseDatabaseConnection

In error cases, the update customer process writes statements similar to the following ones to the SystemOut.log:

[1/15/09 11:31:11:468 CET] 0000005b BpelEngine I
CWWBE0061E: A fault 'DataIncomplete' was raised by activity 'ThrowDataIncompleteFault'.

[1/15/09 11:26:33:562 CET] 00000946 SystemOut O OpenDatabaseConnection
[1/15/09 11:26:33:562 CET] 00000946 SystemOut O UpdateCustomerRecord
[1/15/09 11:26:34:078 CET] 00000946 SystemOut O CloseDatabaseConnection due to error
[1/15/09 11:26:34:109 CET] 00000946 BpelEngine I
CWWBE0003E: An error occurred during the invocation of the activity implementation 'UpdateCustomerRecord'. java.lang.IllegalStateException: Name must not be xcpt!