Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

What custom properties are required for the DB2 UDB Connection Pool in the z/OS mainframe environment?

Updated on November 15, 2015


An administrator asks: The guide for installing Process Commander Version 5.5 SP1 on WebSphere Application Server indicates that the following custom properties must be added for the DB2 Connection Pool if DB2 Universal Database is being used:

Name: currentSchema Value: <user schema name>

Name: currentFunctionPath Value:SYSIBM, SYSFUN, <user schema name>

Name: webSphereDefaultIsolationLevel Value:2

Do these properties also apply to DB2 in the z/OS mainframe environment?



Yes. If you are using WebSphere Application Server Version 6.0, 6.1, or 7.0, you must add the custom properties for the DB2 UDB Connection Pool listed above when you create data sources during installation.

In addition to the properties listed above, you must also add the following custom properties for the DB2 UDB Connection Pool:





Add these properties to the custom properties page of the data source you specified for the jdbc/PegaRULES JNDI location. 

For example, in the WebSphere Administration console, go to JDBC Providers > Pega - UDB JDBC Driver > Data sources > PegaRULES > Custom properties > New.

Best Practice

In addition to specifying the properties listed above, consider making the following changes for all WebSphere environments regardless of the host operating system:

  1. Add the following custom property:

    Note:  The “I” in interval is upper case.

  2. Increase the minimum number of connections from 1 to 20 and the maximum number of connections to 100.  These two new values should be considered a minimum.
  3. If the application server is connecting to the database using an alternate userid, that is, the JAAS setting is not the same as the database owner used at database creation time, it may be necessary to use the alternate userid  instead of the database owner for the user schema name parameters listed above.


Related Topic

pdfPegaRULES Process Commander Release V5.5 SP1, Installing on WebSphere 6.1 Application Servers


Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us