--- title: Connection pooling configuration description: Certain connectors can be pooled, while other connectors are non-poolable. Learn more about the five Pooling mechanisms used in OpenICF and understand Connectors by pooling mechanism. component: openicf page_id: openicf:connector-reference:pooling canonical_url: https://docs.pingidentity.com/openicf/connector-reference/pooling.html section_ids: pooling-mechanisms: Pooling mechanisms icf-pooling: ICF pooling http-pooling: HTTP pooling jdbc-connectors: JDBC connectors connector-specific-pooling: Connector-specific pooling non-poolable-connectors: Non-poolable connectors pooling-table: Connectors by pooling mechanism --- # Connection pooling configuration Certain connectors can be pooled, while other connectors are non-poolable. Learn more about the five [Pooling mechanisms](#pooling-mechanisms) used in OpenICF and understand [Connectors by pooling mechanism](#pooling-table). ## Pooling mechanisms If a connector depends on a third-party library that has its own pooling mechanism, then ICF leverages that pooling mechanism. For example, an HTTP connector uses an Apache HTTP client and a DB connector uses a Tomcat JDBC. OpenICF uses an ICF pooling mechanism only if: * A connector has no third-party library pooling mechanism, or * If OpenICF can't control the amount of connections the third-party library uses. For example, the [Microsoft Graph API connector](ms-graph-api.html). OpenICF uses the following pooling mechanisms to manage connections. ### ICF pooling ICF pooling maintains connector objects and is managed by the framework. This pooling mechanism improves throughput and is used by, and is only relevant to, the connectors that implement the `PoolableConnector` interface. For an ICF-pooled connector, ICF maintains a pool of connector instances and reuses these instances for connector operations. When an operation must be run, an existing connector instance is taken from the connector pool. If no connector instance exists, a new instance is initialized. When the operation has been run, the connector instance is released back into the connector pool, ready to be used for a subsequent operation. The following example shows a pool configuration option object for an ICF poolable connector: ```json { "maxObjects" : 10, "maxIdle" : 10, "maxWait" : 150000, "minEvictableIdleTimeMillis" : 120000, "minIdle" : 1 } ``` To configure ICF connection pooling, set the following values in the connector configuration file `poolConfigOptions` property: * `maxObjects` The maximum number of connector instances in the pool, both idle and active. The default value is `10` instances. * `maxIdle` The maximum number of idle connector instances in the pool. The default value is `10` idle instances. * `maxWait` The maximum period to wait for a free connector instance to become available before failing. The default period is `150000` milliseconds, or 150 seconds. * `minEvictableIdleTimeMillis` The minimum period to wait before evicting an idle connector instance from the pool. The default period is `120000` milliseconds, or 120 seconds. * `minIdle` The minimum number of idle connector instances in the pool. If `minIdle=0`, then a connector pool cleaner thread will run and close expired connections. ### HTTP pooling Connectors that use HTTP pooling require an HTTP client and leverage `PoolingHttpClientConnectionManager` to manage a pool of HTTP connections. Each connector defines and supports different properties that configure the pooling connection manager. ### JDBC connectors This pooling mechanism applies to connectors interacting with a database. A Tomcat JDBC driver handles the pooling. ### Connector-specific pooling For connector-specific pooling, the connector implements the pooling and can include properties to configure the pool. ### Non-poolable connectors For non-poolable connectors, ICF creates a new instance of the connector class and uses a new or existing instance of the connector configuration to initialize the instance before the operation runs. After the operation is run, OpenICF disposes of the connector instance. ## Connectors by pooling mechanism To ensure you configure the correct pooling option for a connector, consult the following table for a list of connectors by pooling type. **Connectors by pooling mechanism** | ICF | HTTP | JDBC connectors | Connector-specific | Non-poolable | | ----------------------------------------------- | ----------------------------------------------- | ----------------------------------- | ----------------------------------------- | ------------------------------------------------------- | | [Adobe Marketing Cloud](adobe.html) | [Adobe Admin Console](adobe-admin-console.html) | [Database table](dbtable.html) | [Amazon Web Services (AWS)](aws-iam.html) | [AS400](as400.html) | | [Groovy connector toolkit](groovy.html) | [Box](box.html) | [Oracle EBS](ebs.html) | | [AWS IAM Identity Center](aws-iam-identity-center.html) | | [Kerberos](kerberos.html) | [Cerner](cerner.html) | [SAP HANA Database](saphanadb.html) | | [CSV file](csv.html) | | [LDAP](ldap.html) | [DocuSign](docusign.html) | [Scripted SQL](scripted-sql.html) | | [Duo](duo.html) | | [Microsoft Graph API](ms-graph-api.html) | [Dropbox](dropbox.html) | | | [Google Apps](google.html) | | [PeopleSoft](peoplesoft.html) | [Epic](epic.html) | | | [Groovy connector toolkit](groovy.html) | | [PowerShell connector toolkit](powershell.html) | [Google Cloud Platform (GCP)](gcp.html) | | | [Multiple CSV](multicsv.html) | | [ServiceNow](servicenow.html) | [HubSpot](hubspot.html) | | | [Multiple CSV Cloud](multicsvcloud.html) | | [SSH](ssh.html) | [IBM RACF](racf.html) | | | [SAP S/4HANA](sap-hana.html) | | [Workday](workday.html) | [Marketo](marketo.html) | | | | | | [MongoDB](mongodb.html) | | | | | | [PingOne](pingone.html) | | | | | | [SaaS REST](rest.html) | | | | | | [Salesforce](salesforce.html) | | | | | | [SAP](sap.html) | | | | | | [SAP SuccessFactors](successfactors.html) | | | | | | [SCIM](scim.html) | | | | | | [Scripted REST](scripted-rest.html) | | | | | | [Snowflake](snowflake.html) | | | | | | [Webex](webex.html) | | | |