Adapter Client Configuration

This page describes the Adapter Client Configuration settings. The following properties can be set:

Iterator Size

The number of elements that are received in one fetch. This number can be compared to the cursor size in a database, which enables you to limit the amount of data that is retrieved. The amount of data also depends on the number of fields and the associated tables of one record.

Timeout

The time in milliseconds to wait for an answer before the Adapter times out when performing a request to another Adapter. Setting this timeout to 0 indicates no timeout. Be aware that setting the value to 0 can lead to hanging clients in case of problems during the transport or in the server. There is also a method to overwrite this timeout in an application.

Client BusComponent

All Adapters and Connectors are identified by a BusComponent. The Client BusComponent field is used to identify local clients.
A client adapter can be identified by an anonymous or named BusComponent.
An adapter is named when it is linked to an existing BusComponent in the directory. You do that by specifying the linked BusComponent in the Client BusComponent field. Click the drop-down button to choose a BusComponent from the list.
An Adapter is anonymous when the Client BusComponent field is left empty. In that case, the Adapter composes a name at runtime (computer name + root + user name).
When using one of the socket transport, it is preferred to use an anonymous Adapter; in other words, leave the field empty.
When using MQ Series or MSMQ, you can enter the name of BusComponent that describes the queue.

Default Backend

The default backend is the backend that a manager will connect to when you make a call with this manager. You can overrule this in your code when you initialize the manager for a specific backend. To select a default backend, click the drop-down button and select one of the server BusComponents.