Since the iWay Service Manager (iSM) infrastructure allows input message processing in parallel threads, single connections for multiple adapter instances can slow traffic which impacts performance dramatically. To increase performance, iWay Application Adapter for Microsoft Dynamics CRM 2011 On-Premises supports a pool of HTTP connections which can be used in parallel. Every time when an adapter instance needs to send a request and get a response from MS CRM, it takes a connection from that pool and returns it back when the request is processed. You can edit or modify the connection pool. You can also use a special parameter which specifies how many connections can be pooled.

A connection can remain idle for 100 seconds before being reused. This value is defined internally and cannot be set from any configuration.

To process messages, the adapter uses the following two connections:

• An administrative account to retrieve information about field type.
• A regular user account.

Since the connections use different accounts, they cannot be mixed and therefore they are stored in different pools. The connection pool size determines the maximum number of connections in each pool. That means that the adapter can have double the number of connections. But due to metadata being cached, administrative connections are used much less.

The pool can have as many connections as you want, but many connections can consume system resources. The number of connections should be reasonable.

Note: When using a connection pool and configuring the iWay Adapter Service (com.ibi.agents.XDAdapterAgent) in the iSM Administration Console or as a Service object in a process flow, ensure that the Persist Connection parameter is set to persist (agent). If this parameter is set to none, then the adapter connection and the connection pool is destroyed after every call is made to MS CRM.