You can't change the Pega-RULES cookie name. We always add the context root to the cookie path so this separates the values so they wont cause issues. You can change the context root of /prweb, like in your example URLS, at deployment time.
We do get support requests for applications sharing the same domain with different context roots with regards to load balancing, PRPC and other applications hosted in same domain. This ends up being an issue with the JSESSIONID that is typically used for session affinity. By default in some application servers they do not append the path to the cookie. Modification to include path or rename JSESSIONID cookie are done at application server level and this always resolves these types of issues.
Hope this helps.
Posted: 3 years ago
Updated: 3 years ago
Posted: 25 May 2018 15:02 EDT Updated: 25 May 2018 15:33 EDT
Paul Gentile (PaulGentile_GCS)
Sr. Software Solutions Engineer
What you're looking to do is to change the JSESSIONID cookies to JSESSIONID_App1 and JSESSIONID_App2. Also, set the path on each to the context root (E.g. "/prweb"). This is the best practice approach to having multiple applications running through a single server and keeping their sessions from colliding...