It's all about the answers!

Ask a question

Setup stuck at "Loading configuration settings..."


James Labrie (18123818) | asked Jan 18 '11, 4:40 a.m.
Hi,

I'm now setting following environment.

WebSphere Application Server 7.0.0.13
RTC 3.0

I installed JTS and am doing setup, but at step2, which is "Configure Public URI", it does not proceed with the message "Loading configuration settings...".

What is considered the cause of this?
And could anyone let me know how to solve this problem?


Regards
James

12 answers



permanent link
Daniel Chirillo (1801723) | answered Aug 25 '12, 5:00 p.m.
For me, the culprit was not configuring WAS to Use available authentication data when an unprotected URI is accessed.    Step 3 at the top of:  http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_s_server_installation_setup_WAS.html

permanent link
Nicolas Constans (22723) | answered Jan 18 '11, 6:32 a.m.
JAZZ DEVELOPER
Hello, I am facing the exact same problem.
Any help on this topic would be greatly appreciated :)

-Nicolas

permanent link
Pierre Pellet (11) | answered Jan 19 '11, 7:53 a.m.
Hi
Same symptom running RTCz (on z/OS) with Tomcat (no WAS) and Derby (no DB2) & JAVA 6.0
Any hint on this issue ? Many thanks in advance
Pierre

permanent link
Nicolas Constans (22723) | answered Jan 19 '11, 8:09 a.m.
JAZZ DEVELOPER
OK, we managed to solve the issue by:

- stopping everything and clearing the WAS temp directory
- adding this entry to every teamserver.property file:"com.ibm.team.repository.server.jts.url=https\://<SERVER_NAME>\:9443/jts"
- running again jts/setup

-Nicolas

permanent link
K p (611216) | answered Jan 19 '11, 10:12 a.m.
OK, we managed to solve the issue by:

- stopping everything and clearing the WAS temp directory
- adding this entry to every teamserver.property file:"com.ibm.team.repository.server.jts.url=https\://<SERVER_NAME>\:9443/jts"
- running again jts/setup

-Nicolas


Im having same problem. I did tried adding above property, But no luck.

Any suggestions on this to solve this issue?

Thanks,
Kiran

permanent link
Pierre Pellet (11) | answered Jan 20 '11, 9:03 a.m.
Hi buddies,
Found a typo in the JTS batch JCL script, where I had typed "export JAZZ_HOME=:etc/jazz" rather than "export JAZZ_HOME=/etc/jazz/"

Strange enough, the server did not complain about that mistake.

Fixing the typo, then restarting the server allowed to resume setup OK.

Bye

permanent link
Maksim Marholin (313) | answered Feb 02 '11, 7:49 a.m.
Hi.
I had the same problem. I've update WAS to 7.0.0.13 and installed the latest Java fix pack. Also, I use Nicolas instruction and restarted all servers. The problem was solved.

permanent link
John Vasta (2.6k15) | answered Feb 02 '11, 8:58 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
I just want to note, for the benefit of those who may find this topic when searching for similar problems, that it appears fairly common that when upgrading applications deployed in WAS, the undeploy process does not clean up all the old bits of the application. Then when the new applications are deployed, you end up with a mix of old and new bits, and that causes problems.

We have a tech note on this issue at

http://www-01.ibm.com/support/docview.wss?uid=swg21455119

The manual cleanup recommendation is also mentioned in the "upgrading" section of the documentation at

http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/topic/com.ibm.jazz.install.doc/topics/t_update_post-mig_setup.html

permanent link
Robert Elliott (101116) | answered Feb 14 '11, 2:13 p.m.
I am installing a new instance of RTC 3.0 on WebSphere 7 and db2 on RH Linux 5 and have run into this same problem. I have tried installing it according to a variety of instructions and attempted the workarounds mentioned above. I am still stuck. Any other ideas?

permanent link
Michael Toole (31168) | answered Aug 10 '11, 9:43 a.m.
i was having the same problem on windows server 2008 r2. Once i disabled the firewall it started working.

Hope this helps someone...

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.