Each interface is defined terms of the services one application provides to others, and the underlying technical details of how an application provides these services is deliberately hidden. One application needs not know anything about the other application's underlying data and functionality.
If the Publication Service sends a message in response to a target application event, the event is communicated to the publisher through notification mechanism of the target application. If there is no notification mechanism in the target application, the Publication Service must be configured to be polled using a timer.
A Subscription Service converts the data it receives into an MInstance of the appropriate class that should match the subscriber service definition. The subscriber must then perform whatever target application task appropriate for the service, such as inserting the data into target application.
For compatibility with TIBCO ActiveMatrix BusinessWorks, the adapter needs to provide at least the reliable message quality of service. The adapter should clearly define the available service and support a quality of service for each service.
Using the Request-Response Service, an adapter acts as a Request-Response server for ActiveEnterprise operations. Operations are defined in a schema in the repository. Input and output parameters and exceptions must be defined for each operation.
Using the Request-Response Invocation Service, the adapter acts as a request-response client for ActiveEnterprise operations. A client is defined in the configuration and invokes an AE operation in a synchronous or asynchronous manner. A client invokes an operation by constructing an
MClientRequest object and then calling
synchInvoke(),
asynchInvoke() or
onewayInvoke().
For compatibility with TIBCO ActiveMatrix BusinessWorkss, the adapter needs to provide at least the Operation Server Service if client/server operations are applicable and defined.