Question


SWIFT
MY
Last activity: 4 Mar 2025 4:47 EST
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 ?
-
Reply
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!


Evoke Technologies
US
-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.


SWIFT
MY
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 ?
Updated: 24 Feb 2025 6:31 EST


Evoke Technologies
US
@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


LTIMindtree
SA
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.


SWIFT
MY
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.


LTIMindtree
SA
No Way, It will not reflect like that. Are you talking about Pega Admin Studio Settings Option, you see difference from the 24.2 image version?


SWIFT
MY
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 |


LTIMindtree
SA
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.


SWIFT
MY
Could you please advice how do I cleanup the Pega System DB Cache Tables? is there a guide that I could refer ?


LTIMindtree
SA
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;
Updated: 4 Mar 2025 4:10 EST


SWIFT
MY
My team member found it in the Pega Platform 24.2 zip file downloaded from https://my.pega.com/ -> "Software" -> "My Software" page.


LTIMindtree
SA
You said you're on containers. What's the need of using the Pega Platform 24.2.zip file package?
If you're in containers, you will need to use a deployment yaml file along with helm charts.