SOPERA Adapter 8.0 | webMethods SOPERA Adapter Documentation | webMethods SOPERA Adapter Installation and User’s Documentation | Overview of webMethods SOPERA Adapter | Communication Styles Support
 
Communication Styles Support
 
Creating Service Consumers
Creating Service Providers
SOPERA Adapter enables the communication between the SOPERA infrastructure and the webMethods product suite by processing requests from SOPERA participants and sending requests to those participants. SOPERA participants are business applications that consume services (service consumers) or provide services (service providers). You can use one of the following communication styles of SOPERA services as part of calling the SOPERA services from your adapter services:
*Request-response. The service consumer sends a request message to the service provider. The provider processes the request and returns a response message to the consumer. The request-response operation can be:
*Blocking. The service blocks the service invocation until a response message is sent to the consumer.
*Non-blocking. The service invocation returns before the response has been received.
*One-way. The service consumer sends a request message to the service provider, but does not expect any response.
*Notification. The service provider sends a message to multiple service consumers transparently. In effect this communication style implements a publish-subscribe communication. The service provider “publishes” a message that is received by any consumer that has subscribed to it.
Note:SOPERA notification should not be confused with an adapter notification. An adapter notification is an element on Integration Server that receives data from the backend system. SOPERA notification is a communication style for a publish-subscribe type of message exchange.
*Request-callback. The request-callback communication style is similar to the request-response style in that the service consumer sends a message to the provider and then the provider sends back a message. The difference is that the sending of the request and callback messages is implemented as independent one-way operations that are correlated by the SOPERA library. With this style, the callback can be received at any future point of time after the request has been sent and might actually go to a different physical system than that from which the request originated. In a similar way, the provider does not have to send the callback immediately and might delegate the sending of the callback to a different component.