Since “globally-scoped” JDBC connection pools are accessible to any J2EE application deployed on the target servers, LiveCycle Configuration Manager (LCM) gives you the option of not using that option and instead keeping the JDBC data source definition within the LiveCycle EAR file (“secure datasources”).
The default value for the maximum connection pool size is 30. This is too low if Content Services ES2 is also deployed. For Content Services ES2, this needs to be increased to 60 or 80. To do this after the fact, a re-build and re-deployment of the EAR will be necessary. To avoid this hassle, it is recommended that you do this before you run LCM as part of your intial install. The steps are:
1) Navigate to $LIVECYCLE_INSTALL_ROOT/configurationManager/config/wl/datasources/your_db/
2) Edit IDP_DS-jdbc.xml with a good XML editor that won’t mangle the XML file
3) Change “initial-capacity” from 1 to 5 and “max-capacity” from 30 to 80
5) Run LCM and re-build the EAR files
6) Un-deploy the existing EAR files
7) Deploy the newly-built EARs
Please note that for form fragments in the LiveCycle repository to be accessible, you need to use “globally-scoped” JDBC connection pools.