Question about Public URI
![]()
Hi,
We have now following environment. JTS3.0 WAS7.0 + fix13 DB2 9.7 We are now planning to create high availability environments by installing HTTP server. I'm referring to following link. http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/index.jsp?topic=/com.ibm.jazz.install.doc/topics/c_ha.html And, in the following link about "Planning your URIs" http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/index.jsp?topic=/com.ibm.jazz.install.doc/topics/c_planning_URLs.html following thing is mentioned. ------------------------------------------------------------------ After the resources have been stored in the repository, the public URI cannot be changed. ------------------------------------------------------------------ We are already using RTC, which means we have already completed the setup, and the Public URIs are now https://servername:9443/jts and https://servername:9443/ccm. According to the article, the Public URI cannot be changed, so, do we have to reinstall JTS in order to create high availability environment? We want to use the Public URI like https://servername/jts and https://servername/ccm. |
4 answers
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Mar 23 '11, 10:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The warning about not changing the server URI is not a constraint on the
server (there are ways to change the URI of a server), but rather a constraint resulting from the way data is currently stored in RTC. In particular, some of the inter-object relationships are stored as URI's that contain the Public URI segment, so changing the server URI will cause those relationships to dangle. This issue is being tracked in work item 127009. Cheers, Geoff On 3/23/2011 2:23 AM, jamesla wrote: Hi, |
![]()
Hi Geoff,
Thank you for your answer. I have some additional questions. >there are ways to change the URI of a server In "Advanced Properties", there is a property "Public URI Root". So I think one of the ways to change the URI of a server is to change the property "Public URI Root" in "Advanced Properties". Is my understanding correct? >but rather a constraint resulting from the way data is currently stored in RTC. So, because of this problem, Public URI should not be changed. Also, in case there is a possibility that a high availability environment will be created in the future, HTTP server has to be installed initially to use the Public URI like https://servername/jts and https://servername/ccm even though the initial environment is not a high availability environment. Is this understanding correct? |
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Mar 24 '11, 6:12 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'm not an expert on configuring RTC for high availability, so I'll have
to defer that part of the question to others. WRT Public Root URI, yes, you set the Public URI Root in the Advanced Properties page of your server. That tells RTC to use that as the prefix for URL references to data in that server. But note that if you already were running that server at a different URL, then there may be other changes you will need to make to start-up scripts and property-files, and to any other repositories that have a reference to your server under its old name. That's another area I'm not expert at (:-). One thing I do is shutdown the server after changing the root URI, restart it, and then grep through any text files (such as the .properties files) to see if there are any remaining references to the old URL. If I find none, then I'm happier. If I find there still are some, that means I have to get some help (:-). Cheers, Geoff On 3/24/2011 9:23 AM, jamesla wrote: Hi Geoff, |
![]()
Hi Geoff,
Thank you very much for your answer again :) >I'm not an expert on configuring RTC for high availability, so I'll have to defer that part of the question to others. Ok, I'm waiting for someone to answer the question below. ---------------------------------------------------------------------------------------------------------------------------------------------- In order to avoid changing the Public URI, if there is a possibility that a high availability environment will be created in the future, HTTP server has to be installed initially to use the Public URI like https://servername/jts and https://servername/ccm so that we don't need the change the Public URI later. Is this understanding correct? ---------------------------------------------------------------------------------------------------------------------------------------------- |