Using context root /jazz while deploying on WAS
Can we use a context root other than /jazz when deploying jazz.war on WAS?
The issue is with RRC that customer is trying to use a context root /jazzRRC, she can access the following URLs just fine
https://hostname:port/jazzRRC/setup
& https://hostname:port/jazzRRC
But she is having issues accessing this URL
https://hostname:port/rdm/setup
Please help?
The issue is with RRC that customer is trying to use a context root /jazzRRC, she can access the following URLs just fine
https://hostname:port/jazzRRC/setup
& https://hostname:port/jazzRRC
But she is having issues accessing this URL
https://hostname:port/rdm/setup
Please help?
One answer
Can we use a context root other than /jazz when deploying jazz.war on WAS?
The issue is with RRC that customer is trying to use a context root /jazzRRC, she can access the following URLs just fine
https://hostname:port/jazzRRC/setup
& https://hostname:port/jazzRRC
But she is having issues accessing this URL
https://hostname:port/rdm/setup
Please help?
Hi there - you might find it helpful to check out this guide which details setting up RRC with another context root (in the context of installing RRC alongside RTC):
https://jazz.net/wiki/bin/view/Main/DeployingRationalRequirementComposerServerandRationalTeamConcertServerintothesameWebSphereApplicationServerorApacheTomcatServer
Essentially you want to ensure that the RRC config files are pointing to the correct updated context root. From the linked document:
1) fronting.properties displays:com.ibm.rdm.fronting.server.serverBaseUrl=https://www.example.com:9443/rrcjazz
2. RTC\jazz\server\conf\rdm\friendsconfig.rdf displays: https://serverhostname_orIPaddress:9443/rrcjazz ;