WSDL generation error prevents invocation of SOAP services
Valid from Pega Version 8.4.2
A Known Issue was introduced in the 8.4.2 Pega Platform patch release, which impacts both upgrades and new installations of that version.
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”.
Clients must perform the following workaround after they define a new SOAP connector in Pega Platform:
- To download the WSDL from Pega Platform:
- 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.
- Click the URL to display the XML.
- Save the WSDL file to your local system.
- In the text editor of your choice, modify "Name" to "name" in every <element “name” = … > tag in the WDSL.
- Save your changes to the local file.
- To reload the WSDL into Pega Platform:
- In Dev Studio, open the Configure menu.
- Select Integration > Connectors > Create SOAP Integration.
- In the New SOAP integration wizard, select Upload WSDL from File.
- 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.
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.
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:
- 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
- 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.
- Download the DDL.
- Correct the schema name and save the DDL.
- Manually apply the DDL.
WebSphere log error with Java 8 for Enterprise JavaBeans
Valid from Pega Version 7.1.8
For environments that are deployed by using Java 8 on IBM WebSphere Application Server version 126.96.36.199 through the last 8.5.5.x fix pack, the log might report that a class was not found when the application server attempts to start Enterprise JavaBeans. If Java EE functionality is not needed, no further action is required. However, to use Enterprise JavaBeans, see WebSphere log error with Java 8 for Enterprise JavaBeans.