Skip to main content

Table of Contents

Deleting connection parameters in the prconfig file

For Pega Platform versions that are earlier than 8.6, if you modified the connection parameters in your prconfig file, delete the parameters from the file to avoid parameter overrides.

  1. Extract the prconfig file.

    1. Stop Pega Platform.

    2. Undeploy Pega Platform.

    3. Extract the current prconfig.xml file from the WAR file or EAR file.

  2. Open the prconfig file in an XML or text editor.

  3. Find and delete the following parameters:

    1. For the DSS that specifies each database user connection pool size, find and delete prconfig/database/databases/<database name>/connectionPoolSize.

    2. For the DSS that specifies the connection timeout in seconds, find and delete prconfig/database/databases/<database name>/MaxConnectionTime.

    3. For the DSS that specifies the leak detection threshold in miliseconds, find and delete prconfig/database/databases/<database name>/leakDetectionThreshold/default.

    4. For the DSS that specifies the default schema of the external database, find and delete prconfig/database/databases/<database name>/defaultSchema/default.

  4. Repackage the WAR file or EAR file.

  5. Redeploy Pega Platform with the application server facilities.

  6. Implement the changes to the prconfig file by restarting the application server.

You can now specify connection pool parameters directly from the DB-Admin-DB-Name rule. For more information, see Creating and updating external database instance with JDBC URLs.
Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us