Changing CLM application names when using WAS
Hi all
When installing CLM 4.x into WAS, the applications by default are named jts_war ccm_war clmhelp_war admin_war qm_war rm_war Can the name of the application be changed to any other during the installation without affecting CLM? Are there any references inside Jazz that refer to the name of the application as installed in WAS? For instance, say you want to rename the applications like this: jts_war_406 ccm_war_406 clmhelp_war_406 etc Note: This is not talking about changing the context root or the web module - simply the display name inside WAS. many thanks anthony |
2 answers
Hi Anthony,
I believe it's pretty safe to change the display name of the .war deployment, since it's just a default name assigned by WAS (if you change the .war file name, the display name will change accordingly during deployment). Actually, I rarely use "jts_war", "ccm_war" and etc as the display names in my WAS deployment, since I prefer just "jts" and "ccm". No ill effect that I can see in all the WAS deployments that I have so far. Another thing to note is that "jts_war" is not written in any of the configuration files. The display name of a .war file normally appears in the configuration file of an .ear (Enterprise ARchive) file, and we don't use EAR files in Jazz products. |
Ralph Schoon (63.4k●3●36●46)
| answered Aug 05 '14, 2:09 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Anthony,
as far as I know you can use the IM silent install scripts to do that. There is also a manual way, which is described in https://jazz.net/library/article/1093 which is basically renaming the WAR file as well as the conf folder. Comments
Ralph Schoon
commented Aug 05 '14, 2:10 a.m.
| edited Aug 05 '14, 2:10 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
PS: You have to do that BEFORE you run the setup for that application and register it to a JTS, otherwise you are effectively trying to change the context root.. Because the name of the application reflects into its URI.
Anthony, I can see the reason why you would want to install with a different context root. I can't imagine why you would want to do what you describe above. What is the use case?
Thanks Ralph.
1
Christian Glockner
commented Aug 05 '14, 6:34 a.m.
Just to elaborate on the use-case: This is using WAS ND with approximately 10 nodes. Those 10 nodes are not all going to be running the same version of CLM. So in order to be able to maintain different versions of the CLM applications in a WAS ND cell, one app is installed for each node, i.e. jts_war_node1, jts_war_node2, ccm_war_node1, ccm_war_node2 etc. That way each node has its own application and the applications can be upgraded individually for each node without affecting the others.
Ralph Schoon
commented Aug 05 '14, 7:21 a.m.
| edited Aug 05 '14, 7:24 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
This is a question for a WAS expert, really. Which I am not.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.