It's all about the answers!

Ask a question

Unable to register RM with JTS, installed in a distributed topology

Raghu NS (112) | asked Oct 18 '22, 2:35 p.m.

I am trying to setup RM and JTS in a distributed topology. Below are the configuration details

JTS-CCM-GC installed on Windows VM1
RM installed on Windows VM2
Using basic user registry and both servers are having same basicUserRegistry file
SSO is enabled on both by adding below lines in server.xml
        <webAppSecurity singleSignonEnabled="true"/>
       <webAppSecurity ssoDomainNames="windows-vm1-jts-server" />
       <ltpa keysFileName="resources/security/ltpa.keys" keysPassword="WebAS" expiration="120" />
"ltpa.keys" files are same on both the VMs


During RM application registration step of JTS setup below error is seen:
The webpage at https://windows-vm2-rm:9443/rm/customSetup?embed=true#/steps/1&parent=https%3A%2F%2Fwindows-vm1-jts%3A9443%2Fjts%2FcustomSetup%23%2Fsteps%2F18 might be temporarily down or it may have moved permanently to a new web address.
When I login to RM/admin URI and Advanced Properties, "Pending oAuth Consumer Registration Info" has a value as below:
<rdf:RDF    xmlns:rdf=""    xmlns:j.0="" >   <rdf:Description rdf:nodeID="A0">    <j.0:oauthConsumerPreAuthId>jts_user</j.0:oauthConsumerPreAuthId>    <j.0:oauthConsumerName>Jazz Team Server</j.0:oauthConsumerName>    <j.0:oauthConsumerTrusted>true</j.0:oauthConsumerTrusted>    <j.0:oauthConsumerSecret>secret</j.0:oauthConsumerSecret>    <j.0:oauthConsumerKey>key</j.0:oauthConsumerKey>    <rdf:type rdf:resource=""/>  </rdf:Description></rdf:RDF>

How to resolve this issue and successfully register RM on JTS in distributed topology.

Ian Barnard commented Oct 19 '22, 3:47 a.m. | edited Oct 19 '22, 3:48 a.m.

Bare hostnames like https://windows-vm2-rm:9443 aren't recommended, this might be the problem?

The only obvious thing that's different from once I setup dual liberty is that your ssoDomainNames looks like it's one of the hostnames - make it the same for both, e.g. myelm, delete ltpa.keys, start your jts and then copy the new ltpa.keys to the other server.

BTW is going out of support on October 31 - you won't be able to get support or fixes after that. You would be better off installing 7.0.2.

One answer

permanent link
David Honey (1.8k17) | answered Oct 19 '22, 4:52 a.m.

I recommend that you submit a ticket with IBM technical support. This forum is not a replacement for normal support channels.

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.