Discussion
Pegasystems Inc.
AU
Last activity: 6 Apr 2018 19:26 EDT
Update 7.1.8 to 7.2 questions
My customer is planning an update from 7.1.8 to 7.2. The following questions have come up from a review of the Pega 7.2 Update Guide (as at May 10, 2016), in conjunction with the Pega 7.2 Installation Guide (Tomcat / Oracle):
- Update Guide pg 27 - "Redeploying applications" - this section mentions not redeploying the *.war files from 7.2 if we are updating from 7.1.7 or later. The customer has verified that the binaries between 7.1.8 and 7.2 are different, so it seems risky to not deploy the 7.2 war binaries when using the 7.2 distribution. What is the rationale behind this? Are there risks in deploying the 7.2 war's anyway?
- Install Guide pg 35 - "Configuring web SSO" - adding the xerces, xaml and xml-apis JAR files to the endorsed directory. Should these be the ones provided in the distribution (if any - I don't have the distribution handy) or should these be sourced separately? If separately, are there particular versions that should be used for Pega 7.2 ?
- Update Guide pg 32 - Step 5 - updating the Dynamic System Setting for CaptureScreenshotsResourcePath - what is the recommendation for the host portion of this value in a clustered environment? Should it be set to 'localhost' (so that each node makes 'local' REST calls for screenshot capture), would this need to point to the load balancer (resulting in remote REST calls), or are distinct prconfig entries required per node to ensure each node's URL resolves to itself - but not as localhost?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
AU
Further to the question re the JARs required in the 'endorsed' folder for Web SSO, my customer has reported the following:
- The install guide references xerces.jar ... the Update distribution contains only xercesImpl.jar. Is this the JAR that is intended to be promoted to the endorsed folder for an Update?
- The install guide references xaml.jar ... neither the Install nor Update distributions contained such a library. From where should it be sourced, and should it be included in the distributions?
- The install guide references xml-apis.jar ... the Update distribution contains one. Is this the JAR that is intended to be promoted to the endorsed folder for an Update?
Updated: 27 May 2016 13:46 EDT
Pegasystems Inc.
IN
Update Guide pg 27 - "Redeploying applications" - this section mentions not redeploying the *.war files from 7.2 if we are updating from 7.1.7 or later. The customer has verified that the binaries between 7.1.8 and 7.2 are different, so it seems risky to not deploy the 7.2 war binaries when using the 7.2 distribution. What is the rationale behind this? Are there risks in deploying the 7.2 war's anyway?
[Answer] “Post Pega 7.2 update, we can deploy 7.2 wars (Don't have any impacts). This is suggested to avoid deployment of new wars, where customer have to retrofit the customizations present in the older war (they might have had changes in the files like, prconfig.xml etc). There is possible risk of missing any configuration upon deploying new wars”.
Update Guide pg 27 - "Redeploying applications" - this section mentions not redeploying the *.war files from 7.2 if we are updating from 7.1.7 or later. The customer has verified that the binaries between 7.1.8 and 7.2 are different, so it seems risky to not deploy the 7.2 war binaries when using the 7.2 distribution. What is the rationale behind this? Are there risks in deploying the 7.2 war's anyway?
[Answer] “Post Pega 7.2 update, we can deploy 7.2 wars (Don't have any impacts). This is suggested to avoid deployment of new wars, where customer have to retrofit the customizations present in the older war (they might have had changes in the files like, prconfig.xml etc). There is possible risk of missing any configuration upon deploying new wars”.
Update Guide pg 32 - Step 5 - updating the Dynamic System Setting for CaptureScreenshotsResourcePath - what is the recommendation for the host portion of this value in a clustered environment? Should it be set to 'localhost' (so that each node makes 'local' REST calls for screenshot capture), would this need to point to the load balancer (resulting in remote REST calls), or are distinct prconfig entries required per node to ensure each node's URL resolves to itself - but not as localhost?
[Answer]
Case 1: prScreenShot war is deployed on each node of clustered environment. In this case we specify ‘localhost’ in URL. For example, node 1 hosts both prpc and prScreenShot application. Similarly node 2 hosts prpc and prScreenShot applications. Then, DSS we can specified with ‘localhost’ in URL.
Case 2: Deploying prScreenShot war on different node altogether, where all the clustered nodes can commonly access prScreenShot. In this case, we need to specify the host name/ip in the URL, where we have deployed prScreenShot. For example, node 1, node 2, node 3 are prpc nodes and node x is prScreenShot hosted node. Then we need to specify node x in the URL and the same should be used in DSS.
Install Guide pg 35 - "Configuring web SSO" - adding the xerces, xaml and xml-apis JAR files to the endorsed directory. Should these be the ones provided in the distribution (if any - I don't have the distribution handy) or should these be sourced separately? If separately, are there particular versions that should be used for Pega 7.2 ?
[Answer]
1. These jars are required only for Pega instances deployed on Weblogic.
2. There is a typo in the name of the 2nd jar. It should be xalan instead of xaml.
With regards to the specific versions of these three jars:
xalan-2.7.1.jar (not included in the distribution, this has to be sourced separately)
xercesImpl-2.10.0.jar (included in the distribution, we have a newer 2.11.0 version now – Path: 115041_Pega72.zip\scripts\lib)
xml-apis-1.4.01.jar (included in the distribution – Path: 115041_Pega72.zip\scripts\lib)
This is a requirement only for SAML Web SSO feature and when Pega is deployed on Weblogic.