Synchronous Non-Blocking WebLogic Integration-to-Tuxedo Connectivity Asynchronous WebLogic Integration-to-Tuxedo Connectivity Asynchronous Tuxedo Q-to-WebLogic Integration Connectivity

8-2 WebLogic Tuxedo Connector Administration Guide for Oracle WebLogic Server ■ Using the defined Business Operation invoke the JATMI tpcall method specifying the service name. ■ Process TypedFML32 response buffers using defined Business Operations.

8.1.3 Define Exception handlers

Define WebLogic Integration Exception handlers to process exceptions.

8.2 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 fromto XMLFML32. ■ The response is written to the specified JMS reply queue. ■ The WebLogic Integration event node waits on the response queue for a response message.

8.3 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. – XMLFML32 translation errors.

8.4 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: Connecting WebLogic Integration and Tuxedo Applications 8-3 – Infrastructure errors. – FML32XML 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.

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