8 Connecting WebLogic Integration and Tuxedo Applications

The Oracle WebLogic Tuxedo Connector Tuxedo Queuing Bridge provides the necessary infrastructure for WebLogic Integration users to integrate Tuxedo applications into their business workflows. The following sections discuss WebLogic Integration - Tuxedo interoperability using the Oracle WebLogic Tuxedo Connector.

• Synchronous WebLogic Integration-to-Tuxedo Connectivity

• Synchronous Non-Blocking WebLogic Integration-to-Tuxedo Connectivity

• Asynchronous WebLogic Integration-to-Tuxedo Connectivity

• Asynchronous Tuxedo /Q-to-WebLogic Integration Connectivity

• Bi-directional Asynchronous Tuxedo-to-WebLogic Integration Connectivity

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

Synchronous WebLogic Integration-to-Tuxedo Connectivity

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

• Defining WebLogic Integration Business Operations.

• Invoking an eLink Adapter.

• Defining WebLogic Integration Exception Handlers.

Defining Business Operations

Define WebLogic Integration 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 Integration 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 Integration Exception handlers to process exceptions.

Synchronous Non-Blocking WebLogic Integration-to-Tuxedo Connectivity

WebLogic Integration 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 Integration writes a message to JMS queue.

• Once the message is on the JMS queue then Tuxedo Queuing Bridge 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 Integration event node waits on the response queue for a response message.

Asynchronous WebLogic Integration-to-Tuxedo Connectivity

WebLogic Integration sends a guaranteed asynchronous message to a Tuxedo /Q:

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

• WebLogic Integration writes a message to JMS queue.

• Once the message is on the JMS queue then Tuxedo Queuing Bridge 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 Integration Connectivity

Tuxedo /Q sends a guaranteed asynchronous message to WebLogic Integration:

• 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 Tuxedo Queuing Bridge 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 Integration Connectivity

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