![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This section explains the synchronous and asynchronous ActiveEnterprise operations, as well as how to implement them.
The terms synchronous and asynchronous have special meaning in this context, as defined in this section.
• A synchronous client invokes an operation and then waits for the specified time for the reply to arrive.
• An asynchronous client invokes an operation and specifies a reply listener class, which will be used to process the reply. Using asynchronous invocation, an adapter can invoke multiple remote operations without having to wait for the reply.
• A synchronous server provides an implementation where the reply can immediately be built and sent back.
• An asynchronous server provides an implementation where the reply is built asynchronously. When the reply is ready, it is sent back to the client.The synchronous or asynchronous characteristics are inherently private to the client or server implementation. Synchronous or asynchronous clients are fully inter-operable with either asynchronous or synchronous servers.
• In-Process Invocation—Whenever the server and the client reside in the same MApp, the invocation is optimized to prevent unnecessary communication overhead. In that case, the SDK does not broadcast requests to anyone outside that process and does not send out messages.Most ActiveEnterprise operations, regardless of whether they use remote or in-process invocations, expect a reply. The reply can be expected synchronously or asynchronously (see Synchronous and Asynchronous).The SDK also supports one-way invocation. When an operation is declared as one-way, no reply is expected by the client.
− Configure the operations to be performed using TIBCO Designer Schema resources. See TIBCO Designer Palette Reference.
− Specify the services using the TIBCO Designer Generic Adapter Configuration. If necessary, customize the endpoints and sessions that are automatically created. See TIBCO Designer Palette Reference.
− The client builds a request instance based on the operation schema information and invokes the corresponding operation. The client receives a reply in the form of a reply instance.
− The server registers an implementation for each operation based on the schema information. The server implementation receives a request instance object and builds a reply instance object.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |