Running the Server on another machine...
I configured my server (IP: 192.168.0.2) as I did wen I setup the Jazz
server on my local machine:
- defining a couple of jazzusers in users.xml
- a keystore using the keytool
- adding in teamserver.properties
com.ibm.team.repository.server.repourl.port.http = 8080
com.ibm.team.repository.server.repourl.port.https = 9443
- adding a new <connector> in server.xml
- replacing <realm> with a new one pointing to my users.xml file.
Fyi, the same configuration works great on my local machine...
When I launch the web UI against:
http://192.168.0.2:8080/jazz/web,
the Web UI shows up but when I try to login, nothing happens and after
the timeout, the web browser says that the server is not reachable...
On the other hand when I give him directly the following URL:
https://192.168.0.2:9443/jazz/web
Then it asks me to accept the certificate, ... and I'm connected to the
server...
I must certainly do something wrong or I have to do something else that
I don't know to setup correctly tomcat in such situation...
Any suggestion?
server on my local machine:
- defining a couple of jazzusers in users.xml
- a keystore using the keytool
- adding in teamserver.properties
com.ibm.team.repository.server.repourl.port.http = 8080
com.ibm.team.repository.server.repourl.port.https = 9443
- adding a new <connector> in server.xml
- replacing <realm> with a new one pointing to my users.xml file.
Fyi, the same configuration works great on my local machine...
When I launch the web UI against:
http://192.168.0.2:8080/jazz/web,
the Web UI shows up but when I try to login, nothing happens and after
the timeout, the web browser says that the server is not reachable...
On the other hand when I give him directly the following URL:
https://192.168.0.2:9443/jazz/web
Then it asks me to accept the certificate, ... and I'm connected to the
server...
I must certainly do something wrong or I have to do something else that
I don't know to setup correctly tomcat in such situation...
Any suggestion?
2 answers
When you click the login link, what URL does it attempt to go to?
Compare this vs. the https URL you've successfully visited. Are they the
same?
If not, how are they different?
PS: If you want to examine the web UI properties, you can do the
following:
- Go to the web UI
- In your browser's location bar (the control that displays the current
URL),
type (for example):
javascript:alert(com.ibm.team.repository.server.repourl.port.https)
If nothing happens or you get an error, it means the variable's not set
(or you
mistyped the variable). If the var's set, it will pop up a dialog with
the
value of the var.
Compare this vs. the https URL you've successfully visited. Are they the
same?
If not, how are they different?
PS: If you want to examine the web UI properties, you can do the
following:
- Go to the web UI
- In your browser's location bar (the control that displays the current
URL),
type (for example):
javascript:alert(com.ibm.team.repository.server.repourl.port.https)
If nothing happens or you get an error, it means the variable's not set
(or you
mistyped the variable). If the var's set, it will pop up a dialog with
the
value of the var.
You were right, Bill. thanks
Actually, a wrong (invisible) character was inserted between the 2 lines:
com.ibm.team.repository.server.repourl.port.http = 8080
com.ibm.team.repository.server.repourl.port.https = 9443
So, when I tested
javascript:alert(com.ibm.team.repository.server.repourl.port.https)
I got 'null' instead of 9443.
To fix the problem, I re-inserted a CR/LF and restarted the Server...
Now it works great!
Thanks again...
Actually, a wrong (invisible) character was inserted between the 2 lines:
com.ibm.team.repository.server.repourl.port.http = 8080
com.ibm.team.repository.server.repourl.port.https = 9443
So, when I tested
javascript:alert(com.ibm.team.repository.server.repourl.port.https)
I got 'null' instead of 9443.
To fix the problem, I re-inserted a CR/LF and restarted the Server...
Now it works great!
Thanks again...