Question
How to change the prpc application context (prweb) on Weblogic Application Server
How to change the application context named prweb by another (for example pegasystem) in Weblogic Application Server?
We use the EAR deployment and PRPC 7.3.1 version
We have investigated in the Product Suport Community in the following URLs but these recomeations aren't function in weblogic
https://pdn.pega.com/community/product-support/question/change-prweb-co…
https://pdn.pega.com/community/product-support/question/how-change-prwe…
***Edited by Moderator Marissa to add SR Details***
Hi Mahesh,
Thanks for interesting
We want access two different pega prpc environments from the same web server (same domain) configured as reverse proxy.
For example, www.mydomain.com/prwebdev and www.mydomain.com/prwebtest
Regards
Thanks for letting us know the reason behind this change, after discussion with our product specialists regarding this change in Weblogic its a lengthy process which involves so many changes it seems. So their suggestion is to raise an SR if it is your mandatory requirement, so that they can work on it.
Thanks for your reply, before we raised the question in this forum, we have created a SR and we're waiting a answer
You can link the SR and update the solution in the post as some other users also looking for similar implementation.
Hello!
Please let us know the SR# here and we can link them for you!
Regards,
Hi GustavoV0328!
I was able to locate your SR and link this post to it as well as update this post with that information.
Thanks!
Hi Marissa,
Thank you for your interesting and update this post with the SR number
Regards
You're welcome! :)
Thank you for your interest, the issue has been resolved. The detail steps are in the SR, but include modifiy the plan.xml file, update to the tag <context-root> in weblogic.xml file into prweb.war. Additionally update to the tag <context-root> in application.xml file in ear file.
This issue has been resolved and SA-54609 Application context name change in Weblogic Application Server has been generated as a resolution.
If you have the same/similar issue, please reference this SA.
Hello All,
We're looking at the same thing for WebSphere and Tomcat. Does this solution just work for Weblogic or would updating the .ear file as per SA-54609 work for us too? (I would need to get resources to test this out - hence asking before I get in a long process of finding it out myself!)
Many thanks,
Angelo
Hi Gustavo,
May i know the reason behind changing this application context from the default one?
Regards
Mahesh