It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,875

question asked: Nov 29 '11, 3:05 p.m.
question was seen: 6,587 times
last updated: Nov 29 '11, 3:05 p.m.

Related questions

CRJAZ2118E only one path segment allowed! Why??

0
Daniel Stefan Haischt (214●1●23●22) | asked Nov 29 '11, 3:05 p.m.
Hi,

I am trying to setup CLM 3.0.1.1 on a WAS ND 7.0.0.19 app server where the JTS app will be served at the following context root:

/clm3/jts

On step 2 "Configure Public URI" I am running into the following error:

CRJAZ2118E The URI property specified as "https://rtc.polly.boeblingen.de.ibm.com/clm3/jts" must contain exactly one non-empty path segment.

Why isn't it possible to use a context root that uses several, virtual sub-directories? I think using such context roots is quiet common if you want to introduce a certain naming scheme that guarantees unique path values.


I am now using hyphens instead of slashes in support of hosting multiple JTS server instances on the same WAS ND infrastructure. So I would say the extra check for nested context root path values doesn't prevent somebody to have a setup that doesn't adhere to the default, intended setup strategy (here: don't use nested context root path values). AFAIK the GUI check for multiple/nested context root path values has been introduced with 3.0.1.1 were it wasn't present in 3.0.1.

This is my topology:

WAS ND 7.0.0.19 plus fronting IHS

CLM V3, CLM V4 and DM V3.5 installed on the same WAS ND infrastructure using the following WAS nodes:

CLM3_CCM
CLM3_RM
CLM3_QM
CLM3_DM

CLM4_CCM
CLM4_RM
CLM4_QM

So if I get it correct it is not possible to have something like...

https://fobar.com/jts

... cause that would clash with the JTS of either CLM4, CLM3 or DM35


Regards,
Daniel S. Haischt

Accepted answer

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Nov 30 '11, 11:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You'll probably want to take a look at Work item 167593 "Allow
multi-segment context names, which share a common initial segment.".

Cheers,
Geoff

On 11/29/2011 3:08 PM, danielshaischt wrote:
Hi,

I am trying to setup CLM 3.0.1.1 on a WAS ND 7.0.0.19 app server where
the JTS app will be served at the following context root:

/clm3/jts

On step 2 "Configure Public URI" I am running into the
following error:

CRJAZ2118E The URI property specified as
"https://rtc.polly.boeblingen.de.ibm.com/clm3/jts" must
contain exactly one non-empty path segment.

Why isn't it possible to use a context root that uses several, virtual
sub-directories? I think using such context roots is quiet common if
you want to introduce a certain naming scheme that guarantees unique
path values.

Regards,
Daniel S. Haischt
Daniel Stefan Haischt selected this answer as the correct answer

5 other answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Nov 30 '11, 7:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Daniel,

are you trying to install several instances of the CLM solution on the same application server and try to avoid conflicting context roots?

I am pretty sure I have read a tech note once. What i know is working is rename the .WAR file e.g. ccm.war to ccm2.war. You also need a corresponding server/conf/ccm2 folder.

I think it is possible to use the installation manager silent install to do the install. Seel https://jazz.net/library/article/524/ section "Understanding and preparing for the upgrade process" it indicates what to do to change the context root there. Please keep in mind you can't change the context root later.
0
permanent link
Daniel Stefan Haischt (214●1●23●22) | answered Nov 30 '11, 7:46 a.m.
Hi Ralph,

Daniel,

are you trying to install several instances of the CLM solution on the same application server and try to avoid conflicting context roots?

I am pretty sure I have read a tech note once. What i know is working is rename the .WAR file e.g. ccm.war to ccm2.war. You also need a corresponding server/conf/ccm2 folder.

I think it is possible to use the installation manager silent install to do the install. Seel https://jazz.net/library/article/524/ section "Understanding and preparing for the upgrade process" it indicates what to do to change the context root there. Please keep in mind you can't change the context root later.


Yes, renaming the WAR files would be another solution. Right now I am working with dashes in my context root values (e.g. clm3-ccm) and yes I am trying to install both CLM V3 and CLM V4 on the same WAS ND app server instance.

Concerning the conf directory I came up with the following structure which required tweaking the provisioning profile files accordingly: 

+---clm3-admin

+---clm3-ccm

+---clm3-jts

+---clm3-qm

\---clm3-rm


Cheers
Daniel
0
permanent link
Daniel Stefan Haischt (214●1●23●22) | answered Nov 30 '11, 12:24 p.m.
Hi Ralph,

Daniel,

are you trying to install several instances of the CLM solution on the same application server and try to avoid conflicting context roots?

I am pretty sure I have read a tech note once. What i know is working is rename the .WAR file e.g. ccm.war to ccm2.war. You also need a corresponding server/conf/ccm2 folder.

I think it is possible to use the installation manager silent install to do the install. Seel https://jazz.net/library/article/524/ section "Understanding and preparing for the upgrade process" it indicates what to do to change the context root there. Please keep in mind you can't change the context root later.


Yes, renaming the WAR files would be another solution. Right now I am working with dashes in my context root values (e.g. clm3-ccm) and yes I am trying to install both CLM V3 and CLM V4 on the same WAS ND app server instance.

Concerning the conf directory I came up with the following structure which required tweaking the provisioning profile files accordingly: 

+---clm3-admin

+---clm3-ccm

+---clm3-jts

+---clm3-qm

\---clm3-rm


Cheers
Daniel

I guess I got it sorted out. If you'll want to go with the above dash-based naming convention, you really have to name the WAR files, the directories under ../cont/* and the context root values accordingly to match with each other.

Cheers
Daniel
0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Nov 30 '11, 12:37 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, consistent naming seemed to be the trick here. Good that it starts working for you.
0
permanent link
Daniel Stefan Haischt (214●1●23●22) | answered Dec 02 '11, 4:58 a.m.
You'll probably want to take a look at Work item 167593 "Allow
multi-segment context names, which share a common initial segment.".

Cheers,
Geoff

On 11/29/2011 3:08 PM, danielshaischt wrote:
Hi,

I am trying to setup CLM 3.0.1.1 on a WAS ND 7.0.0.19 app server where
the JTS app will be served at the following context root:

/clm3/jts

On step 2 "Configure Public URI" I am running into the
following error:

CRJAZ2118E The URI property specified as
"https://rtc.polly.boeblingen.de.ibm.com/clm3/jts" must
contain exactly one non-empty path segment.

Why isn't it possible to use a context root that uses several, virtual
sub-directories? I think using such context roots is quiet common if
you want to introduce a certain naming scheme that guarantees unique
path values.

Regards,
Daniel S. Haischt


Thanks Geoffrey!

I was able to circumvent the issues by using a dash notation for context root values (e.g. clm3-jts vs /clm3/jts). This worked fine for CLM3 and CLM4 where it didn't for DM3. In the latter case the dm.properties file was expected under ../conf/dm/dm.properties and it looked like, according the the WAS SystemOut.log, that dm/dm.properties was hard coded in the application so there was no way to circumvent this issue in this particular case.

Cheers
Daniel

Your answer

Register or to post 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.