- Overview
- The ForgeRock Identity Connector Framework (ICF)
- Supported Connectors
- Adobe Marketing Cloud Connector
- AS400 connector
- AWS Connector
- Cerner Connector
- CSV File Connector
- Database Table Connector
- DocuSign Connector
- Epic Connector
- Google Cloud Platform Connector
- Google Apps Connector
- Groovy Connector Toolkit
- HubSpot Connector
- Kerberos Connector
- LDAP Connector
- Marketo Connector
- MongoDB Connector
- MS Graph API Java Connector
- PeopleSoft Connector
- PowerShell Connector Toolkit
- IBM RACF Connector
- Salesforce Connector
- SAP Connector
- Before You Start
- Using the SAP Connector With an SAP HR System
- Using the SAP Connector to Manage SAP Basis System (R/3) Users
- Configuring the SAP Connector For SNC
- Implementation Specifics
- OpenICF Interfaces Implemented by the SAP Connector
- SAP Connector Configuration
- SAP S/4HANA Connector
- SCIM Connector
- Scripted REST Connector
- Scripted SQL Connector
- ServiceNow Connector
- SSH Connector
- SAP SuccessFactors Connector
- Workday Connector
- Configure Connectors
- Sample Provisioner Files
- Configure Connectors With the Admin UI
- Configure Connectors Over REST
- Connector Reference Properties
- Pool Configuration
- Operation Timeouts
- Connection Configuration
- Synchronization Failure Configuration
- Configure How Results Are Handled
- Specify Which Attributes Are Updated
- Set the Supported Object Types
- Configure Operation Options
- Remote Connectors
- Check External System Status Over REST
- Remove a Connector
- ICF Interfaces
- ICF Operation Options
- Connection Pooling Configuration
- IDM Glossary
Connection Pooling Configuration
Certain connectors support the ability to be pooled. For a pooled connector, ICF maintains a pool of connector instances and reuses these instances for multiple provisioning and reconciliation operations. When an operation must be executed, 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 executed, the connector instance is released back into the connector pool, ready to be used for a subsequent operation.
For an unpooled connector, a new connector instance is initialized for every operation. When the operation has been executed, ICF disposes of the connector instance.
Because the initialization of a connector is an expensive operation, reducing the number of connector initializations can substantially improve performance.
To configure 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. The default value is
1
instance.