Example for Configuring Load Balancing in Custom RPC Service

To configure load balancing in custom RPC Service, you can add just one service to an adapter configuration and then start the adapter service twice. If you create two adapter configurations and add a custom RPC Service service to each adapter configuration, only one adapter configuration handles messages successfully.

This is because the adapter configuration names contained in the operation aeschema class paths are different. When you develop a business process, you can only relate one adapter configuration to the business process. When you use the business process to send requests, only the related adapter configuration handles messages. The other adapter configuration fails to handle messages.

To resolve this issue, perform the following steps to configure load balancing in custom RPC Service.

Prerequisites

An adapter configuration named custom_RPC is created.

Procedure

In the Project Explorer view, double-click custom_RPC.adadbmodel.
Click the Adapter Services tab in the adapter configuration editor.
Click Add in the All Adapter Services panel.
In the Adapter Service General Configuration window, select Request-Response from the Service Type list and click Next.
In the Schema Type window, select a stored procedure, function, or package for the service.
By default, the SQL_REQUEST class is displayed in the Schema field.
In the Transport Session window, select the TIBCO Rendezvous Distributed Queue or JMS Queue transport session.
In this example, the JMS Queue transport session is used.
Click Finish.
Start the custom_RPC adapter configuration twice.

What to do next

After you complete the load balancing configuration, you can develop a business process to verify your configuration. In the business process, create two requests and send data to the adapter configuration custom_RPC. If the adapter configuration can handle the requests respectively, the load balancing configuration takes effect.