One or more instances of the BeanConnect resource adapter and one or more BeanConnect proxy instances may run in a BeanConnect cluster configuration. All the instances in the cluster are configured identically. Three different scenarios result from this:
n:1 relation: Several resource adapter instances in the application server and one proxy instance.
An n:1 relationship is useful in cases where the applications in an application server cluster conducts only a low level of communication with EIS partners.
Even in the event of an n:1 relation, you must configure a proxy cluster as otherwise the system is operating in multi-resource adapter mode which behaves completely differently, see Multiple resource adapter mode . The proxy cluster ensures, for example, that any change is performed in all the instances of the resource adapter.
1:m relation: One resource adapter instance and several proxy instances
This option makes sense if communication is almost exclusively inbound.n:m relation: Several resource adapter instances and several proxy instances
You always configure all the resource adapter instances in the Management Console if multiple resource adapter instances are running in a cluster in the application server. This is where you configure the cluster for the application server.
If there is more than one proxy in the proxy cluster then there is one special proxy known as the master proxy. This proxy is the (first) point of contact for the Management Console when fetching the configuration data for the cluster. If the currently defined master proxy cannot be administered then the Management Console demands that another proxy, for which administration is possible, is defined as the master proxy. The configuration data is then fetched from this proxy. If any changes are made to the configuration, the Management Console ensures that the administration data of all the proxies in the proxy cluster is modified consistently.