Connecting WebLogic Process Integrator and Tuxedo Applications

 

Note: For more information on how to integrate applications, see BEA WebLogic Integration.

The WebLogic Tuxedo Connector tBridge provides the necessary infrastructure for WebLogic Process Integrator users to integrate Tuxedo applications into their business workflows. The following sections discuss WebLogic Process Integrator - Tuxedo integration using the WebLogic Tuxedo Connector.

• Synchronous WebLogic Process Integrator-to-Tuxedo Connectivity

• Synchronous Non-Blocking WebLogic Process Integrator-to-Tuxedo Connectivity

• Asynchronous WebLogic Process Integrator-to-Tuxedo Connectivity

• Asynchronous Tuxedo /Q-to-WebLogic Process Integrator Connectivity

• Bi-directional Asynchronous Tuxedo-to-WebLogic Process Integrator Connectivity

 

---

Synchronous WebLogic Process Integrator-to-Tuxedo Connectivity

WebLogic Process Integrator executes a blocking invocation against a Tuxedo service using a JATMI EJB. This process consists of three parts:

• Defining WebLogic Process Integrator Business Operations.

• Invoking an eLink Adapter.

• Defining WebLogic Process Integrator Exception Handlers.

Defining Business Operations

Define WebLogic Process Integrator Business Operations for the JATMI methods to be used:

• TypedFML32 buffer manipulation methods.

• Use the JATMI tpcall() method.

  Example: out_buffer = tpcall (service_name, in_buffer, flags)

Invoking an eLink Adapter

Invoke an eLink adapter from a WebLogic Process Integrator process flow:

• Build TypedFML32 request buffers using defined Business Operations.

• Using the defined Business Operation invoke the JATMI tpcall() method specifying the service name.

• Process TypedFML32 response buffers using defined Business Operations.

Define Exception handlers

Define WebLogic Process Integrator Exception handlers to process exceptions.

 

---

Synchronous Non-Blocking WebLogic Process Integrator-to-Tuxedo Connectivity

WebLogic Process Integrator sends a message to synchronously invoke a Tuxedo service:

• 1:1 relationship between JMS queue and the call to a Tuxedo service.

• 1:1 relationship between the response from the Tuxedo service and a JMS queue.

• WebLogic Process Integrator writes a message to JMS queue.

• Once the message is on the JMS queue then tBridge moves the message to the target Tuxedo service.

• The message is translated from/to XML/FML32.

• The response is written to the specified JMS reply queue.

• The WebLogic Process Integrator event node waits on the response queue for a response message.

 

---

Asynchronous WebLogic Process Integrator-to-Tuxedo Connectivity

WebLogic Process Integrator sends a guaranteed asynchronous message to a Tuxedo /Q:

• 1:1 relationship between JMS queue and Tuxedo /Q.

• WebLogic Process Integrator writes a message to JMS queue.

• Once the message is on the JMS queue then tBridge moves the message to the target Tuxedo /Q on a per message basis.

• Messages in error are forwarded to a specified JMS error queue:

  • Infrastructure errors.

  • XML/FML32 translation errors.

 

---

Asynchronous Tuxedo /Q-to-WebLogic Process Integrator Connectivity

Tuxedo /Q sends a guaranteed asynchronous message to WebLogic Process Integrator:

• 1:1 relationship between JMS queue and Tuxedo /Q.

• Tuxedo writes a message to Tuxedo /Q.

• Once the message is committed on Tuxedo /Q, the message is forwarded via the Tuxedo /T Domain Gateway to the WebLogic Tuxedo Connector tBridge and target JMS queue.

• Messages which cannot be forwarded from Tuxedo are enqueued on a Tuxedo /Q error queue.

• Messages in error are forwarded to a specified Tuxedo /Q error queue, including:

  • Infrastructure errors.

  • FML32/XML translation errors.

• A workflow is created that waits for the message on the JMS queue. It is defined in the Start workflow node or in the Event node of an existing workflow instance.

 

---

Bi-directional Asynchronous Tuxedo-to-WebLogic Process Integrator Connectivity

Tuxedo executes a blocking invocation of a WebLogic Process Integrator process flow. Use two asynchronous instances to connect from JMS to Tuxedo /Q and from Tuxedo /Q back to JMS.