Async Binary Update Sample

This sample provides a design pattern that is appropriate when the application architecture requires a binary message to be processed from a JMS provider. For testing purposes a reply queue is used although that is not mandated by the pattern.

Note: This sample is available on dev2dev and is not supported by BEA.

About the Sample

The sample consists of single WebLogic Integration application sample with an asynchronous business process (a JPD), a standalone Java client, and associated artifacts including WSDL, Process Control, and Schema.

1. The client invokes the JPD by sending non-XML data through a JMS queue.
2. A user-provided message driven bean (MDB) consumes the JMS message and calls a JPD using a JPD proxy.
3. The non-XML data is converted to XML, the XML is persisted for future reference, and then forwarded for further processing.
4. XML data with a validation code is returned, persisted, converted to non-XML format, and then received by the client through a JMS reply queue.

Workflow of the Sample

As the architecture diagram below illustrates, an MDB listens for the incoming message, converts it to XML on arrival, and calls the JPD for further processing. Upon completion of the process, an outbound XML message is created and sent to an outbound message handler that converts it to non-XML format before sending it to the client.

Required Software

This sample requires the following software:

• WebLogic Integration 9.2, MP2 or later (includes Jython 2.1). Download WebLogic Integration 9.2 from the download page on dev2dev.
• WLI Common Utilities, version 2.5. Download WLI Common Utilities from the download page.
• WebLogic Server Scripting Tool (WLST) (included with WLI Common Utilities). WLST can also be downloaded from the download page.
• Note: WLST Offline and WLST Online are available for download and evaluation from BEA's dev2dev site, but have not been formally included in the WebLogic Platform 9.2 product. WLST is supported through BEA newsgroups only, and the utility and APIs are subject to change. BEA intends to formally support this capability in a future release of WebLogic Platform.

Notes

Variants in this pattern may include:

• Using a foreign JMS Provider such as IBM MQ Series. For more information, see Using Foreign JMS Providers with WebLogic Server
• Using the WLI JMS event generator rather than a user-provided MDB.

Supporting Materials

In addition to providing application code, the sample includes the following items:

• Instructions and scripts for creating a Java client using ant are provided to act as a WebSphere MQ
• Instructions and scripts for configuring a BEA WebLogic Integration cluster to support the application
• Instructions and scripts for deploying the application to an appropriately configured cluster
• Instructions, guidelines, and caveats for designing asynchronous processes for client interactions

Download

You can download the The Async Binary Update sample and WLI Common Utilities from the sample download page on dev2dev.