Adapters are responsible for making information from different applications available to other applications across an enterprise. To do so, an adapter is configured to provide one or more of the FOLLOWING services: 

• Publication Service 
• Subscription Service 
• Request-Response Service 
• Request-Response Invocation Service

1) Publication Service : 

An adapter publication service recognizes when business events happen in a vendor application, and asynchronously sends out the event DATA in realtime to interested systems in the TIBCO environment. For example, an adapter can publish an event each time a new customer ACCOUNT is added to an application. Other applications that receive the event can then update their records just as the original application did. When an application receives a request to create a customer record, the application notifies the adapter about the request and the adapter publishes the event. 

User Interface-----------------Application X--------------Adapter -------------- TIBCO Messaging 

Create record Send to adapter Publishing 

Polls on the source data table (base table). 

Reads data from the source table. Sends the data to the message bus.

2 ) Subscription Service: 

An adapter subscription service asynchronously performs an action such as updating business objects or invoking native APIs on a vendor application. The adapter service listens to external business events, which trigger the appropriate action. Referring to the previous example, an adapter subscription service can listen for customer record creation events (happening in an application and published to the TIBCO infrastructure) and update another application. 

TIBCO Messaging------------Adapter-----------Application Y Subscribing Update record 

Reads data from the message bus. 

Gives the data to the destination table.

3) Request-Response Service: 

In addition to asynchronously publishing and subscribing to events, an adapter can be used for synchronously retrieving data from or executing transactions within a vendor application. After the action is performed in the vendor application, the adapter service sends a response back to the requester with either the results of the action or a confirmation that the action occurred. This entire process is called request-response, and it is useful for actions such as adding or deleting business objects. 

Receives requests from other applications. 

Parses the requests. Returns response (Sends only the requested data to the message bus).

4 Request-Response Invocation Service:

An adapter request-response invocation service is similar to the request-response service, except that the roles are reversed. The vendor application is now the requester or initiator of the service, instead of the provider of the service. The adapter service acts as a proxy, giving the vendor application the ability to invoke synchronously functionality on an external system.

Adapters are responsible for making information from different applications available to other applications across an enterprise. To do so, an adapter is configured to provide one or more of the following services: 

1) Publication Service : 

An adapter publication service recognizes when business events happen in a vendor application, and asynchronously sends out the event data in realtime to interested systems in the TIBCO environment. For example, an adapter can publish an event each time a new customer account is added to an application. Other applications that receive the event can then update their records just as the original application did. When an application receives a request to create a customer record, the application notifies the adapter about the request and the adapter publishes the event. 

User Interface-----------------Application X--------------Adapter -------------- TIBCO Messaging 

Create record Send to adapter Publishing 

Polls on the source data table (base table). 

Reads data from the source table. Sends the data to the message bus.

2 ) Subscription Service: 

An adapter subscription service asynchronously performs an action such as updating business objects or invoking native APIs on a vendor application. The adapter service listens to external business events, which trigger the appropriate action. Referring to the previous example, an adapter subscription service can listen for customer record creation events (happening in an application and published to the TIBCO infrastructure) and update another application. 

TIBCO Messaging------------Adapter-----------Application Y Subscribing Update record 

Reads data from the message bus. 

Gives the data to the destination table.

3) Request-Response Service: 

In addition to asynchronously publishing and subscribing to events, an adapter can be used for synchronously retrieving data from or executing transactions within a vendor application. After the action is performed in the vendor application, the adapter service sends a response back to the requester with either the results of the action or a confirmation that the action occurred. This entire process is called request-response, and it is useful for actions such as adding or deleting business objects. 

Receives requests from other applications. 

Parses the requests. Returns response (Sends only the requested data to the message bus).

4 Request-Response Invocation Service:

An adapter request-response invocation service is similar to the request-response service, except that the roles are reversed. The vendor application is now the requester or initiator of the service, instead of the provider of the service. The adapter service acts as a proxy, giving the vendor application the ability to invoke synchronously functionality on an external system.