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.
LinkedIn
Copied!

Table of Contents

Obtaining connection pool diagnostic data by using REST services

Beginning with Pega® Platform 7.4, HikariCP is used for connection pooling for databases that configured by using a URL. As a result, you cannot use the System Management Application (SMA) to view diagnostic data from your application to troubleshoot connection pooling issues. Instead, you can use the dataconfigs and datasources REST services to get diagnostic data. Use the dataconfigs service to get information about how the databases are configured in Pega Platform. Use the datasources service to get information about the current state of the databases. You can access these services either from Designer Studio or from a browser.

The services return a JSON object that you can copy into a JSON editor, such as JSON Editor Online, for easier viewing.

Accessing the REST services from Designer Studio

The recommended method of accessing the REST services is from Designer Studio.

  1. From the Records Explorer, click Integration-Resources > Service Package.
  2. In the Service Package Name column, locate and click the api service package.
  3. In the URI Template field, locate the following REST services:
    • nodes/{nodeID}/dataconfigs
    • nodes/{nodeID}/datasources
  4. In the Test Endpoint column, click Test.
  5. In the Value field, enter either the node ID of the node from which you want diagnostic data or all to get data for all nodes.
  6. Click Test.

Accessing the REST services from a browser

If you do not have access to Designer Studio, you can access the REST services from a browser by using the following URLs:

  • http://localhost:8080/prweb/api/v1/nodes/<all or the node ID>/dataconfigs
  • http://localhost:8080/prweb/api/vi/nodes/<all or the node ID>/datasources

If your application URL uses HTTP instead of HTTPS, an error message indicating that you must use TLS/SSL is displayed. To fix this error:

  1. From the Records Explorer, click Integration-Resources > Service Package.
  2. In the Service Package Name column, locate and click the api service package.
  3. Click the Context tab.
  4. Clear the Require TLS/SSL for REST services in this package check box.
  5. Click Save.

Have a question? Get answers now.

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