Skip to main content

Support Doc

 Mary Carbonara (MaryCarbonara) Principal Knowledge Management Specialist
Pegasystems Inc.
US
MaryCarbonara Member since 2010 216 posts
Posted: May 17, 2022
Last activity: Nov 27, 2023
Posted: 17 May 2022 10:21 EDT
Last activity: 27 Nov 2023 1:33 EST

Specifying the Hotfix Catalog location for Pega Hotfix Manager

Applies to Pega Platform versions 6 through 8.5

Is your Pega deployment running an older version of Pega Platform?

Best Practice: Keep current with Pega

Update the location of the Hotfix Catalog

Why this change is important

What happens if you do not update the hotfix catalog location

Is your Pega deployment running an older version of Pega Platform?

Older versions of Pega Platform ™ are currently the following releases:

  • Pega Platform versions 6.x
  • Pega Platform versions 7.x
  • Pega Platform versions 8.x, specifically

    • 8.1.0 to 8.1.8

    • 8.2.0 to 8.2.7

    • 8.3.0 to 8.3.4

    • 8.4.0 to 8.4.3

    • 8.5.0

If yes, take one of the following actions:

Best Practice: Keep current with Pega

Avoid the need to apply hotfixes by Keeping current with Pega.

If you cannot apply the latest Pega Platform patch release and need to continue using an older version, then update the link to the location of the Hotfix Catalog in Pega Hotfix Manager.

Update the location of the Hotfix Catalog

If you are using an older version of Pega Platform, update the location of the Hotfix Catalog:

In the ruleset Pega-UpdateManager, edit the Data-Admin-System-Setting to specify pzRefreshCatalogFTPString with the following value:
https://hotfixcatalog.pega.com/CATALOG.ZIP

Note: After you make this change, you do not need to restart the application server.

This change will allow you to obtain the latest Hotfix Catalog, the list of hotfixes used to perform a scan of your system to determine which hotfixes are installed.

Why this change is important

When you use the Hotfix System Scan feature to determine which hotfixes are installed on your Pega system, you can optionally download the latest available catalog, the list of all Pega hotfixes developed and delivered to clients.

If you choose not to download the latest available catalog, then the system scan uses the catalog available on your file system, that is, the catalog inside the hotfix package (the DL file).  If you have never downloaded a hotfix catalog or have never installed a hotfix package (DL file), then the system scan reports that there is no catalog available.

The old Hotfix Catalog location, pegaftp2.pega.com, is decommissioned.

Therefore, you must update the Hotfix Catalog location (the URL) to hotfixcatalog.pega.com by updating the Pega-UpdateManager DASS pzRefreshCatalogFTPString.

What happens if you do not update the hotfix catalog location

If you are using an older version of Pega Platform from the list above, and you have not updated the Hotfix Catalog location, the system throws an exception when checking online for the Hotfix Catalog. If you use the Pega Hotfix Manager landing page to download the latest catalog, you will see the following error screen:

Error for incorrect Hotfix Catalog location
 

In the logs, you see the following ERROR:

ERROR - Unable to read Catalog from filesystem

You also see a stacktrace starting with the following text:

com.pega.pegarules.priv.updatemanager.InstallException: Have exceeded the maximum number of attempts (5) for downloading the catalog.

The stacktrace includes one of the following causes:

Caused by: java.io.FileNotFoundException: hfix/CATALOG/61/CATALOG.ZIP

Caused by: sun.net.ftp.FtpLoginException: Invalid username/password

Caused by: java.net.UnknownHostException: pegaftp2.pega.com

If this happens, you can fix the issue by updating the location of the hotfix catalog as described above.

Related content

Downloading a hotfix catalog

 

This Support Document has been migrated from Pega Documentation:
https://docs.pega.com/pega-services-troubleshooting/specifying-hotfix-catalog-location-pega-hotfix-manager
23Sept2022 Revised to add What Happens If You Do Not Update the Hotfix Catalog Location, tracked by US-498861
28Feb2023 Added Related Content
To see attachments, please log in.
Pega Platform 8.5
Pega Platform
Pega Platform
System Administration
How To

Did you find this content helpful?
Yes
No

  • Reply
  • Pooja Gadige Phil Shannon
Posted: 2 years ago
Posted: 29 Jul 2022 15:42 EDT
Praveen Kumar Bala (Praveen Bala)
Cigna

Cigna
US

@MaryCarbonara Hi, I have updated the DSS, but still i am not able commit the hotfix successfully and not able to do the system scan.

I see below in the logs.

2) Could not run System Scan - there is no Catalog on the system.

1) Successfully acquired database lock for Hotfix Management.

To see attachments, please log in.
Posted: 2 years ago
Updated: 2 years ago
Posted: 1 Aug 2022 15:47 EDT
Updated: 1 Aug 2022 15:48 EDT
Mary Carbonara (MaryCarbonara) Principal Knowledge Management Specialist
Pegasystems Inc.
US

@PraveenB650 

Go to My Support Portal and submit an Incident (INC) to report your problem.

See My Support Portal FAQs, Submitting tickets > What kind of Support tickets can I submit? https://community.pega.com/msp-faqs#p-b615476c-0507-4a64-993a-1a034dede55d       

To see attachments, please log in.
Posted: 1 year ago
Posted: 23 Feb 2023 2:59 EST
Saptarshi Bera (SaptarshiBera)
Zurich Versicherungs-Gesellschaft AG
Pega BPM Engagement Lead
Zurich Versicherungs-Gesellschaft AG
CH

@MaryCarbonara  Affected versions 8.x or only specific versions mentioned : 8.1.9, 8.2.8, 8.3.5, 8.4.4, 8.5.1, and 8.6 ?  We are on 8.5.6. Do we need this DSS change? Please confirm.

To see attachments, please log in.
Posted: 1 year ago
Posted: 23 Feb 2023 11:44 EST
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

@SaptarshiBeraThis only needs to be explicitly updated in specific 8.x versions as the newer ones are already using the correct location.  The list is mentioning that it needs to be fixed in prior versions but probably would be clearer to actually list the versions that need to be updated.

8.1.0 to 8.1.8

8.2.0 to 8.2.7

8.3.0 to 8.3.4

8.5.0

 

To see attachments, please log in.
Posted: 1 year ago
Posted: 23 Feb 2023 11:47 EST
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

@DhanamaliniG

No you do not need to do anything for 8.3.6.  See my comment above about the versions that it is applicable in 8.x.  For 8.3.5 and above you do not need to make the change as the code will handle it.

To see attachments, please log in.
Posted: 1 year ago
Updated: 1 year ago
Posted: 23 Feb 2023 15:09 EST
Updated: 23 Feb 2023 15:14 EST
Mary Carbonara (MaryCarbonara) Principal Knowledge Management Specialist
Pegasystems Inc.
US

@CelesteDufresne_GCS Many thanks for answering the questions posted on this SDoc. I revised the document to precisely identify the Pega Platform versions you named:

8.1.0 to 8.1.8

8.2.0 to 8.2.7

8.3.0 to 8.3.4

8.5.0

To see attachments, please log in.
Posted: 1 year ago
Posted: 2 Mar 2023 13:36 EST
Krishna Chaitanya Peddi (Peddi23)
Centene Corporation
Senior Application Architect
Centene Corporation
US

@MaryCarbonara  - Our application is on 8.6 and I see DSS "pzRefreshCatalogFTPString" as "ftp://catalog:[email protected]/hfix/CATALOG/61/CATALOG.ZIP" . When I scan system in Hotfix Manager it is able to fetch the latest catalog from support and scan is successful. 

Question ->  Should we still update the DSS to "https://hotfixcatalog.pega.com/CATALOG.ZIP"  ? 

 

To see attachments, please log in.
Posted: 1 year ago
Posted: 13 Mar 2023 9:22 EDT
Mary Carbonara (MaryCarbonara) Principal Knowledge Management Specialist
Pegasystems Inc.
US

@Peddi23

I have learned the following from @talba . . . 

"If your application is on 8.6, there is no need to update the pzRefreshCatalogFTPString DSS.

One reason for this discrepancy is that Pega does not modify system settings on update. If this system was previously on an older version of Pega, and has since been updated to 8.6, it will still have this old DSS. However, the Pega engine detects this old setting and uses the new location if necessary. At this point, the catalog hosted on pegaftp2 has been removed, so the fact that you can still download the catalog proves that the system is using the new location.

If you do update the DSS to the new location, that is okay, but it is not necessary to do so - the Pega engine will automatically use the new location if your DSS has never changed."

To see attachments, please log in.
Posted: 1 year ago
Posted: 27 Nov 2023 1:33 EST
Saikishore Sanagapalli (Kishore Sanagapalli)
LTIMindtree
Senior Specialist - Pega Containerization Practitioner
LTIMindtree
SA

@MaryCarbonara

As stated in the document, Updated the latest hotfix catalog in the DSS for Pega Platform 8.8.3. It worked for first couple of times but later onwards, getting the below error. While upload the catalogs, it says unable to read the file system and upload un-successful error.

Error:
  • CatalogLastRefreshDate: Please upload a catalog before proceeding
  

 

Any solution to this issue?

To see attachments, please log in.

Related content:

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

Pega Collaboration Center 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