Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

WSDL generation error prevents invocation of SOAP services

Valid from Pega Version 8.4.2

Status

A Known Issue was introduced in the 8.4.2 Pega Platform patch release, which impacts both upgrades and new installations of that version.

Description

Due to changes introduced in the SOAP functionality for the case-mismatch error in SR-D98509/INC-119725, the WSDL is being generated for SOAP services with an incorrectly-capitalized element, which prevents the service from being invoked.  The element should be “name” instead of “Name”.

Workaround

Clients must perform the following workaround after they define a new SOAP connector in Pega Platform:

  1. To download the WSDL from Pega Platform:
    1. After using the SOAP Wizard (Dev Studio > Configure > Integration > Services > Service Wizard) the WSDL URL is shown at the bottom right of the Dev Studio screen.
    2. Click the URL to display the XML.
    3. Save the WSDL file to your local system.
  2. In the text editor of your choice, modify "Name" to "name" in every <element “name” = … > tag in the WDSL.
  3. Save your changes to the local file.
  4. To reload the WSDL into Pega Platform:
    1. In Dev Studio, open the Configure menu.
    2. Select Integration > Connectors > Create SOAP Integration.
    3. In the New SOAP integration wizard, select Upload WSDL from File.
    4. Complete the upload using the wizard prompts.

This is a design-time issue, not a run-time issue; therefore, clients only have to perform this workaround process once. Existing SOAP services should not be impacted; however, if clients modify an existing SOAP service definition by re-running the wizard, clients must reapply the workaround for Pega Platform to recognize the SOAP definition changes.  

Resolution

This issue will be addressed in the Pega Platform Patch Release 8.4.3.  Clients who upgrade to that version or later should not see this issue.

Use JDBC 4 compliant drivers for better performance

Valid from Pega Version 7.1.7

For better performance, ensure that you are using JDBC 4-compliant drivers.  For more information on supported and non-supported JDBC drivers, please reference the Platform Support Guide.

Use Tomcat 7 for better performance

Valid from Pega Version 7.1.7

For better performance with a Tomcat web server, use Tomcat 7.

Tomcat 6 has a limitation that causes the server to treat the JDBC driver as if it were a JDBC 3-compliant driver, even if the system is using a JDBC 4-compliant driver. Customers using Tomcat will see better performance if they upgrade to Tomcat 7 and use a JDBC 4-compliant driver.

Engine will not start if the incorrect JDBC driver is used

Valid from Pega Version 7.1.7

The engine will not start up if the incorrect JDBC driver is used. The following configurations are unsupported:

  • Using a Multi-tenant Oracle system with one of the Oracle JDBC drivers with issues (see the chart in the Platform Support Guide)
  • Using a Multi-tenant system with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
  • Using Microsoft SQL Server with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)

When any of these unsupported configurations are encountered, Pega 7 will not start. Before this change, the engine would appear to start up properly, but would encounter issues during other parts of the engine startup or during actual use of the system.

IBM WebSphere Application Server V8: Edit the URL for Enabling System Management Application

Valid from Pega Version 7.1.7

WebSphere 8 does not correctly resolve the URL to enable System Management Application. As a workaround, when you configure the application server, you can do either of these actions:

  • Enter the full URL in the format:
    ​http://hostname:port/prsysmgmt/getnodes.action

  • Set the com.ibm.ws.webcontainer.redirectcontextroot property to true.

Open ports required for cluster communication

Valid from Pega Version 7.1.7

In a Pega 7 system, there can be multiple servers, or nodes, and each node can contain multiple JVMs.  In Pega 7.1.7, the port range 5701-5800 needs to be left open for cluster communication.   The number of available ports in this range needs to be greater than or equal to the greatest number of JVMs on any one node in the cluster.  So for example, if there are 3 JVMs on one node, and 7 JVMs on another node, there need to be at least 7 ports available.  By default, the system will begin with port 5701, and then look for the next port in the sequence (5702, followed by 5703).

 

If these ports are not available, you will see the following error:

 

ERROR   - PegaRULES initialization failed. Server: ABCDEF123

com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed

< . . . Java dump here . . . >

Caused by: com.hazelcast.core.HazelcastException: ServerSocket bind has failed. Hazelcast cannot start! config-port: <port>, latest-port: <port>

 

Recommended heap sizes

Valid from Pega Version 7.1.7

The heap is a storage area in the Java virtual machine (JVM) allocated for both short-term and long-term (shared) object storage. If the server does not have enough memory allocated to run Pega 7, the system can hang without an error message. If this occurs, your values need to be higher than the recommendations based on your server hardware and the number of other applications on the server.

Pegasystems recommends using these settings:

  • Initial Heap Size (Xms): 1 GB
  • Maximum Heap Size (Xmx): 12 GB (8 GB minimum)

If your application server is using the Oracle JVM, also add the PermSize and MaxPermSize settings:

  • PermSize (-XX:PermSize): at least 256MB
  • MaxPermSize (-XX:MaxPermSize): at least 512MB

Set the JVM memory options to increase the amount of system memory allocated to the application server running Pega 7 by selecting Designer Studio > System > Operations > System Management Application and then selecting a listed node.

See the Pega 7.1.7 Installation Guides for more information about how to make these setting changes.

The System Management Application is supported only on Microsoft Internet Explorer

Valid from Pega Version 7.1.7

Microsoft Internet Explorer (IE) is required for the System Management Application (SMA). No other browser is supported.

Create and modify tenants only from the Tenant Management landing pages or SOAP operations

Valid from Pega Version 7.1.7

When creating or modifying tenants, do not use any of the following methods:

  • Creating a new tenant definition from the Data-Admin-Tenant list
  • Using the Save As feature to create a tenant from an existing tenant
  • Creating a tenant from the rule form from the Action > Create menu

Although these methods might appear to work, the resulting tenants have no associated metadata and are not valid. Always use landing pages or SOAP operations to create or modify tenants.

Schema not found error when importing a Rule-Admin-Product file

Valid from Pega Version 7.1.8

If you import a Rule-Admin-Product file (RAP) file that includes a schema that has a view, grammar parsing changes can mean that the Pega 7 Platform is unable to find the schema.

To enable the Pega 7 Platform to find the schema:

  1. Review the error message that indicates that the schema was not found and identify the following items:
    • The name of the schema that is causing the error
    • The table name in the format: wrong_schema_name.table_name...
    • The DDL that the Pega 7 Platform is trying to apply
  2. Use the table name to identify the correct schema name in your system. This schema is usually your data schema, but might also be an external database.
  3. Download the DDL.
  4. Correct the schema name and save the DDL.
  5. Manually apply the DDL.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us