Where to download prweb.war for Pega 24.2 docker image
Hi,
I need to upgrade Pega 8.8 to Pega 24.2.
I am using Pega 8.8 container Image. After switch to use Pega 24.2 container image, I'm able to open the Pega Studio. However, the Pega studio is version 8.8. I guess I need to update the prweb.war.
Where can I get the prweb.war ?
-When you say that you switch to 24.2 Image, Have you used that in specific yaml?
-Are you using the latest version of Pega Helm-chart for the Upgrade?
-During the Upgrade, Think Pega needs a new Empty Rules schema. Also please check that out.
Thanks @AkshithReddyT for the reply and questions.
I didn't use Pega Helm-chart, not yaml.
I update with the Podman by tagging to latest version.
Is the new Empty Rules schema will update the Pega Studio to 24.2 ?
@MingEeL4 Ok, so the Podman nothing but, its kinda your own Container I think.
Exactly not sure on that, Please refer
https://support.pega.com/support-doc/pega-infinity-deployment-changes-faqs
There's no prweb.war file concepts when it comes to Docker images. I assume you're in the process for Pega upgrade from On-Prem to containers. You will have Pega Provided Docker images for Installation of Pega with help of Helm charts.
prweb.war and ear deployments were part of traditional VM deployment structure. Pega 24.2 means, Only Container based architecture and you will not have any scope to work with war / ear files.
Please elaborate more on your query to help me understand better.
I'm currently using container image of Pega 8.8. I pulled container image of Pega 24.2 and able to use it, service started good.
However, the Pega Studio still showing Pega Platform version 8.8. I'm trying to find out how to have the Pega Studio also upgrade to version 24.2.
After using Pega image 24.2, Pega studio show "Pega Platform 8.8.0".
After i click "System Information", show following.
It is PRPC-8.8.0-44. Is there any caching that I need to clear ? FYI, I have another host that is still using Pega image 8.8, that connected to and using the same database. Not sure if this is the reason ?
Java version showing 17, which is correct, as this is used in Pega 24.2 image.
PegaRULES Build Information
| BuildName | PRPC-8.8.0-44 |
| BuildDate | 2022-09-28 10.05 EDT |
| BuildMajorVersion | 08 |
| BuildMinorVersion | 08 |
System Properties
| java.version | 17.0.13 |
| java.runtime.version | 17.0.13+11 |
The moment you use the Pega:24.2 docker image, it should automatically appear.
You Will need to shutdown all the connections and perform cleanup of Pega System DB Cache Tables and start connection of one instance to see which one is causing the issue.
Could you please advice how do I cleanup the Pega System DB Cache Tables? is there a guide that I could refer ?
give the below queries to DBA to run. it will cleanup. This is has to be done while the system is down. Although it has nothing to do with Pega versioning descrepency you reported, it's the start point to find out what's causing the issue.
TRUNCATE table pegadata.pr_sys_delayed_queue; TRUNCATE table pegadata.pr_data_stream_nodes; TRUNCATE table pegadata.pr_data_stream_sessions; TRUNCATE table pegadata.pr_sys_statusnodes; TRUNCATE table pegadata.pr_sys_statusdetails; TRUNCATE table pegadata.pr_data_stream_node_updates; TRUNCATE TABLE pegadata.pr_perf_stats;
I tried this by stopping the pega service, then run the queries, and start the pega service. Pega studio still showing 8.8.
While starting up Pega, I can see some lines in logs still printing about 8.8.
05-Mar-2025 05:12:58.305 INFO [main] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:08-08-01
2025-03-05 05:13:18,303 [ main] (ervlet.WebAppLifeCycleListener) INFO - System Start Date: Wed Mar 05 05:13:18 GMT 2025 2025-03-05 05:13:18,338 [ main] (ervlet.WebAppLifeCycleListener) INFO - PegaRULES Web Tier 8.8.0 2025-03-05 05:13:18,338 [ main] (ervlet.WebAppLifeCycleListener) INFO - PRPC-8.8.0-44: 2022-09-28 10.05 EDT 2025-03-05 05:13:18,338 [ main] (ervlet.WebAppLifeCycleListener) INFO - prpc-platform.git (14c6b9492f002b53e70a8f241533d4d3bafab790) 2025-03-05 05:13:18,338 [ main] (ervlet.WebAppLifeCycleListener) INFO - Now starting the PegaRULES Web Tier...
I tried this by stopping the pega service, then run the queries, and start the pega service. Pega studio still showing 8.8.
While starting up Pega, I can see some lines in logs still printing about 8.8.
05-Mar-2025 05:12:58.305 INFO [main] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:08-08-01
2025-03-05 05:13:18,303 [ main] (ervlet.WebAppLifeCycleListener) INFO - System Start Date: Wed Mar 05 05:13:18 GMT 2025 2025-03-05 05:13:18,338 [ main] (ervlet.WebAppLifeCycleListener) INFO - PegaRULES Web Tier 8.8.0 2025-03-05 05:13:18,338 [ main] (ervlet.WebAppLifeCycleListener) INFO - PRPC-8.8.0-44: 2022-09-28 10.05 EDT 2025-03-05 05:13:18,338 [ main] (ervlet.WebAppLifeCycleListener) INFO - prpc-platform.git (14c6b9492f002b53e70a8f241533d4d3bafab790) 2025-03-05 05:13:18,338 [ main] (ervlet.WebAppLifeCycleListener) INFO - Now starting the PegaRULES Web Tier...
2025-03-05 05:13:35,027 [ main] (pboard.StorageStreamCommonImpl) INFO - engineCodeVersion: 08-08-01
2025-03-05 05:13:35,962 [ main] ( etier.impl.EngineStartup) INFO - PegaRULES Enterprise Tier 8.8.0 2025-03-05 05:13:35,962 [ main] ( etier.impl.EngineStartup) INFO - PRPC-8.8.0-44: 2022-09-28 10.05 EDT
My team member found it in the Pega Platform 24.2 zip file downloaded from https://my.pega.com/ -> "Software" -> "My Software" page.
For now, we are not using deployment yaml file along with helm charts.
So you're trying to upgrade Pega in standard VM deployment structure. From 24.2, VM Deployments is de-supported by Pegasystems. May Be that could be the reason.
You can do one more thing.... Run some DB quries to fetch PRPC / PegaRules Engine table data and see
It is not completely VM deployments, because we are using the Pega 24.2 image.
I guess then I will need to do this update: docs.pega.com/bundle/platform/page/platform/deployment/patch-update-84-later-intro.html
Do you have the queries which table or fields to fetch the PRPC / PegaRules Engine table data ?
I Don't understand.
1. If you're on VM Deployments / ON-Prem, You would be using the Pega Platform zip package for upgrade.
2. If you're on On-prem cloud / Client Cloud, You would be using the Pega Docker images and PostgreSQL.
How come you're using Docker Images in Half VM Deployment Structure you mentioned me. In such cases,
Using the Docker images alone will not help you to upgrade. (The below options are Half VM Deployments Structure - Not sure if the below steps will work)
1. You will need to update your ear file and war files of Pega Platform Jar file (App Server Side)
2. You will need to run upgrade script over the db.
Note: Please help me to understand your architecture better so that i can fix your concern.