Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 TIBCO ActiveMatrix Adapter for Tuxedo : Adapter Services

Adapter Services
The adapter acts as an agent to export and import data into the Tuxedo system in an event-driven fashion. The adapter offers publication, subscription, request-response, and request-response invocation services.
This section describes how the adapter services interact with the Tuxedo environment to provide message connectivity. Figure 2 shows the adapter services in relation to other components in a Tuxedo system.
Figure 2 TIBCO ActiveMatrix Adapter for Tuxedo Services
Publication Service
A publication service is used to publish data from Tuxedo to the TIBCO environment. The adapter receives a message from a Tuxedo integrated application and the publication service converts the retrieved data into the TIBCO ActiveEnterprise wire format and publishes the data to the TIBCO environment.
Figure 3 illustrates a publication service work flow.
Figure 3 Typical Publication Service Flow
Publication Service Features
Example Scenarios
Here are the example scenarios for using a publication service:
A Publication service can publish event data received from the Tuxedo system. For example, a user may put in a request on the Tuxedo client for an operation such as save or delete. The Tuxedo system processes the event and posts it on the Tuxedo EventBroker engine. The adapter’s Publication service, which is registered to the Tuxedo EventBroker to listen for events, picks up the message and publishes it.
The Publication service can publish data received from the Tuxedo system. For example, a user may put in a request on the Tuxedo client for an operation like save or delete. The Tuxedo system puts the data into the queue of Tuxedo, in which the adapter checks the message. After receiving the message, the adapter publishes the message onto the TIBCO environment.
The Publication service can publish data received from the Tuxedo system. For example, a user may put in a request on the Tuxedo client for an operation like save or delete. The Tuxedo server program invokes callPub/callCArrayPub or callSyncPub/callSyncCArrayPub methods of the Adapter Agent with the required arguments. The Rendezvous Adapter Agent passes the data to the adapter, which publishes the message.
The Publication service can publish data received from the Tuxedo system. For example, a user may put in a request on the Tuxedo client for an operation like save or delete. The Tuxedo system invokes the agent, which invokes the callPubJMS method or the callCArrayPubJMS method and posts the data into JMS server, from which the adapter receives the message. After receiving the message, the adapter publishes the message onto the TIBCO environment.
Subscription Service
A subscription service is used to subscribe to messages from the TIBCO environment and post them into the Tuxedo application. A subscription service invokes Tuxedo services using the Tuxedo service name and communication paradigm specified in the incoming message.
Figure 4 illustrates a subscription service work flow.
Figure 4 Typical Subscription Service Flow
Subscription Service Features
When the Queue-based or Conversational communication paradigm is used, a reply is published using the available reply subject.
In the case of Queue-based communication, even if a reply is not required, a reply subject should be specified while configuring the Subscription service. You also need to set the ReplyQueue parameter in the ubbconfig file. See TIBCO ActiveMatrix Adapter for Tuxedo Configuration and Deployment Appendix D Message Formats for details.
When the Conversational communication paradigm is used, the adapter retrieves the specified number of rows as configured in a single conversation, but publishes each row as a separate TIBCO ActiveEnterprise message.
For the sending application ( TIBCO ActiveMatrix BusinessWorks) to recognize the last batch of messages from the adapter (so that it can stop waiting and proceed further), the IsEnd boolean field is set by the adapter. This happens only if at least 1 row has been retrieved.
Sequences are not to be used with the Conversational communication paradigm. For the Conversational communication paradigm, only FML32 buffer type is supported.
If certified messaging is used, delayed acknowledgement is available. After a message is received, the adapter sends an acknowledgement to the publication service only after the message has been processed successfully by the Tuxedo system.
The FML32, STRING and CArray buffer types are supported.
Example Scenario
An external system publishes a message in the TIBCO environment, which is mapped to the adapter schema. The adapter configuration subscribes to this message and invokes the specified Tuxedo service using the specified communication paradigm.
Request-Response Service
A request-response service is used to serve the requests coming from external applications through the TIBCO environment. The adapter supports request-response scenarios by acting as an RPC server. When the adapter receives a request, it takes the raw requested data, converts it into formatted Tuxedo schema, and sends it to Tuxedo using a designated Tuxedo interface.
Figure 5 illustrates a request-response service work flow.
Figure 5 Typical Request-Response Service Flow
Request-Response Service Features
The FML32, String and CArray buffer types are supported.
Multithreading is available for synchronous communication. Multithreading allows the adapter to process multiple messages concurrently ensuring better performance.
Example Scenario
An external system publishes a message in the TIBCO environment, which is mapped to the adapter’s request schema. The adapter configuration receives this message and invokes the specified Tuxedo service using the synchronous communication paradigm. The data returned by the service is mapped to the adapter’s reply schema and returned to the requesting external system via the TIBCO environment.
Request-Response Invocation Service
A Request-Response Invocation Service is used to request data from external applications through the TIBCO environment. The adapter receives a request from the Tuxedo application and sends the request through the TIBCO environment. When a response is returned from the TIBCO environment, the adapter sends the response back to the application.
Figure 6 illustrates a request-response service work flow.
Figure 6 Typical Request-Response Invocation Service Flow
Request-Response Invocation Service Features
The FML32, String and CArray buffer types are supported.
Example Scenario
The Tuxedo system may be configured to query for customer information from an external system. The Tuxedo system invokes the adapter configuration, which sends out a request and receives a reply from the external system. The adapter then sends the reply to the Tuxedo system.

Copyright © TIBCO Software Inc. All Rights Reserved