Request-Response Implementation

With Request-Response Service, client applications can send SQL statements, stored procedures, functions, or packages on a specified subject to an adapter configuration. The adapter processes the request and returns the results in a response to the client.

Request-Response Service works in the following process:
  1. A client application sends a request on a subject to the adapter. The request might be a query to the database or any DDL or DML command to be performed on the database. Multiple statements, stored procedures, or both can be sent in a single message.
  2. Upon receipt of the message, the adapter executes the statements, stored procedures, or both. Requests within a message are processed as a single transaction.
  3. The adapter sends back a response to the Inbox, subject, or response subject that was set up by the client application. The response consists of a result code or one or more result sets, based on the request. A response can also be an error code or error description, if the request was not successful.

Multiple adapter configurations can be configured so that any one of the adapter configurations receives and processes the request. In case of multiple adapter configurations, you can use TIBCO Rendezvous Distributed Queue or JMS Queue to balance the load across a number of adapter configurations in a queue. The task is assigned to the least loaded member of the queue. For details, see Load Balancing.

For details about requests and responses, see Requests and Responses.

  • Requests
    A request contains one or more SQL statements, stored procedures, functions, or packages to be executed as a transaction.
  • Responses
    A response from the adapter to a client application has a result code and one or more result sets. Each result set contains nested self-describing messages, each of which encodes a result row, such as that returned from a query. A response can also return an error code and error description if the request was not successful.