Using RPC Mode

You can configure an adapter configuration to act as a remote procedure call (RPC) server on behalf of a client. TIBCO ActiveMatrix Adapter for Database uses the TIBCO Adapter SDK Operations API for an RPC server. Selecting RPC mode creates an object in the repository to describe the RPC server that the adapter configuration starts.

The structure of the TIBCO Repository class objects that provide MOperation support is presented. Based on these class descriptions, you can create an RPC client to send requests to the adapter in the expected structure. For convenience, class structure is shown in XML format.

One-Way and Two-Way Invocation

You can use one-way or two-way messaging in an RPC operation:

One-way Messaging
The BusinessWorks client sends a request containing a message to the adapter server, and no reply is expected from the adapter server. The client does not have to wait for the reply and is free to continue processing the request. The request is not always sent immediately to the server but waits in a queue until the server processes it.
Two-way messaging
In an RPC operation, two-way messaging is used by default. The BusinessWorks client waits until it receives an answer from the adapter server before continuing processing. If the BusinessWorks client does not receive a reply from the adapter server within a certain period of time, a timeout occurs. The client cannot send a second request until the first request is processed or until a timeout occurs.

Schema Types

Two schema types can be used for a server object created in the repository. They are standard RPC operation and custom RPC operation.

For details, see Standard RPC Operation and Custom RPC Operation.