Weired errors while configuring JTS
Hi All,
We got some weired errors while configuring JTS.
Currently, the live project is running on tomcat in its default port 443
Exisiting public URI is similar to this "https://HelloWorld/jts"
Now we are in the process to migrate the live project to a new environment.
Proposed new environment:
AIX6.1/IBM HTTP Server/WAS 7.1/oracle/openLDAP
IHS(server1 - runs on port 443) -> WAS (server2 - runs on port 10000) -> OpenLDAP (server3- runs on its default port 389 -> Oracle 11.2 (server4))and the firewall is opened in both ways between WAS and IHS ports.
All end users request hits the IHS server which inturn points to WAS server where CLM applications resides.
New environment Public URI - "https://HelloWorld/jts" - HelloWorld points to IHS on port 443. We changed the etc/hosts file on the WAS server to point HelloWorld to IHS server IP address.
After this setup, we started the WAS and able to run JTS with the user account in LDAP, but we got weired error in synchronize the user records stored in the Jazz Team Server (during finalize ccm). I guess the communication between ccm to jts is not happening properly.Manually we tried to invoke ccm/jts and qm link and it works fine.
To my understanding, ccm should invoke jts through IHS while running finalizing task.
Error in ccm.log:
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
Have you guys find any problem in our new environment design?
Please update your valuable comments on this.
Cheers.
Jose
We got some weired errors while configuring JTS.
Currently, the live project is running on tomcat in its default port 443
Exisiting public URI is similar to this "https://HelloWorld/jts"
Now we are in the process to migrate the live project to a new environment.
Proposed new environment:
AIX6.1/IBM HTTP Server/WAS 7.1/oracle/openLDAP
IHS(server1 - runs on port 443) -> WAS (server2 - runs on port 10000) -> OpenLDAP (server3- runs on its default port 389 -> Oracle 11.2 (server4))and the firewall is opened in both ways between WAS and IHS ports.
All end users request hits the IHS server which inturn points to WAS server where CLM applications resides.
New environment Public URI - "https://HelloWorld/jts" - HelloWorld points to IHS on port 443. We changed the etc/hosts file on the WAS server to point HelloWorld to IHS server IP address.
After this setup, we started the WAS and able to run JTS with the user account in LDAP, but we got weired error in synchronize the user records stored in the Jazz Team Server (during finalize ccm). I guess the communication between ccm to jts is not happening properly.Manually we tried to invoke ccm/jts and qm link and it works fine.
To my understanding, ccm should invoke jts through IHS while running finalizing task.
Error in ccm.log:
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
Have you guys find any problem in our new environment design?
Please update your valuable comments on this.
Cheers.
Jose