It's all about the answers!

Ask a question

Cannot proceed with Express Setup


Tiffany Pei (139623) | asked Jul 02 '15, 7:33 a.m.
After I installed CLM 5.0, I ran https://clm:9443/jts/setup, and then clicked on Express Setup.
At Configure Public URI page, there was no public URL showing in Step 1: Configure Public URI box.
The Next Button is grey out. What's wrong?

Comments
Howard Hsiao commented Jul 02 '15, 7:37 a.m.
JAZZ DEVELOPER

Just to confirm, did you click on the check box that says
"I understand that once the Public URI is set, it cannot be modified except with additional administrative commands and in a limited set of scenarios, which can result in broken links from other applications that do not support changing URLs."?


Howard Hsiao commented Jul 02 '15, 7:39 a.m.
JAZZ DEVELOPER

What was the result of clicking on "Test Connection"?


Tiffany Pei commented Jul 02 '15, 8:45 a.m.

I checked the box saying that "I understand that ....".
After I clicked on "Test Connection", it stuck at "Testing Connection..."


Howard Hsiao commented Jul 02 '15, 12:08 p.m.
JAZZ DEVELOPER

Just for a test, if you use https://127.0.0.1:9443/jts/setup to do the express setup, are you able to see the public URI in Step 1: Configure Public URI box?


Tiffany Pei commented Jul 03 '15, 1:47 a.m. | edited Jul 03 '15, 1:47 a.m.

Yes, I could see the public URI when https://127.0.0.1:9443/jts/setup was used.


Howard Hsiao commented Jul 03 '15, 1:53 a.m.
JAZZ DEVELOPER

Ok, there seems to be something wrong with the hostname "clm".

Is it the hostname of your machine?
Or is it just an entry in the hosts file that points to 127.0.0.1?
If "clm" is not the true hostname of your machine, please see if https://<true-hostname>:9443/jts/setup can show the correct URI in JTS setup?


Tiffany Pei commented Jul 03 '15, 1:56 a.m.

"clm" is just an entry in the hosts file. I am able to see the public URI in JTS setup when I use "https://<true-hostname>:9443/jts/setup.


1
Howard Hsiao commented Jul 03 '15, 2:28 a.m.
JAZZ DEVELOPER

If you want to setup a proper CLM server, the hostname used in public URI should be globally accessible and the hostname "clm" should be resolved at DNS level, not local hosts file.
It is ok to define an alias hostname in hosts file for a "standalone" CLM server for testing purpose.
May I know what other entries in hosts file also reference to 127.0.0.1?


Tiffany Pei commented Jul 03 '15, 2:44 a.m.

The entries in my hosts file that references to 127.0.0.1
127.0.0.1 doors_svr
127.0.0.1 clm


Howard Hsiao commented Jul 03 '15, 2:48 a.m.
JAZZ DEVELOPER

Now I can see the problem.
If you have multiple entries for 127.0.0.1 and the hostname of public URI is not the first entry of 127.0.0.1 then you will get empty entry in the Step 1: Configure Public URI box.
Please put 127.0.0.1 clm in front of 127.0.0.1 doors_svr.


Tiffany Pei commented Jul 03 '15, 2:54 a.m.

It worked, thanks!!

showing 5 of 11 show 6 more comments

Accepted answer


permanent link
Howard Hsiao (5.5k17) | answered Jul 03 '15, 2:54 a.m.
JAZZ DEVELOPER
Most probable cause:
The hostname in public URI is not the true hostname and is only defined in the hosts file.
When JTS setup tries to search for that hostname alias, it only searches the first entry of 127.0.0.1 and cannot find that hostname, hence it does not show anything in "Step 1: Configure Public URI" box.

Test the probable cause:
Put "127.0.0.1 <the-hostname-in-public-URI>" in front of any other entries referencing 127.0.0.1 in the hosts file

Think beyond the fix:
If you want to setup a proper CLM server, the hostname used in public URI should be globally accessible and the hostname "clm" should be resolved at DNS level, not local hosts file.
Tiffany Pei selected this answer as the correct answer

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.