Configuring Request-Response Service
Request-Response Service often acts as a Request Reply server or Remote Procedural Call (RPC) server. When running as Request-Response Service, the adapter receives requests from other applications, parses them, and translates them into queries to the database to retrieve data. The output data is wrapped in an MInstance and sent back to the caller.
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.
A request might be a query to the database or any DDL or DML command to be performed on the database. The adapter processes the statement, procedure, or both. Requests within a message are processed as a single transaction. 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 configurations receives and processes the request. For multiple configurations, you can use TIBCO Rendezvous Distributed Queue or JMS Queue to balance the load across a number of configurations in a queue. The task is assigned to the least loaded member of the queue. For details, see Load Balancing.