Deploy clm on two different servers without IHS
I have current setup of CLM with CCM and JTS on server 1(SUSE, WAS,DB2) without IHS.
Now I have to configure DM & RM on Server 2 . While regestering the application while running jts setup I am getting the following error : The server could not access the discovery URL for the application. If you have configured a virtual host for an application, the virtual hostname must be used in the URL for the application.ID CRJAZ2081E hide details Unable to load /jts/proxy?uri=https%3A%2F%2Frmdm.site%3A9443%2Fdm%2Fscr status: 404 Let me know How do I resolve the same. I am also able see the xml content from server1 by provinding url : https://server2:9443/dm/scr |
One answer
Ralph Schoon (62.0k●3●36●43)
| answered Dec 16 '14, 11:35 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
IHS would not be required to set this up. You might have to log into both applications.
404 means that the URL can not be found. It might be worthwhile if you explain more what steps you did on both servers already. In addition there are log files for the applications and you might want to look at those too. Comments and check the firewalls between the two servers.. iptables is pretty restrictive generally by default.
SERVER 1 :
Ralph Schoon
commented Dec 17 '14, 3:02 a.m.
| edited Dec 17 '14, 3:03 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
There is a detailed description on how to deploy on WAS in the online documentation.
The article or workshop contains IHS or reverse proxy . Here I am doing without IHS.
Ralph Schoon
commented Dec 17 '14, 6:46 a.m.
| edited Dec 17 '14, 6:47 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
IHS does NOT matter except that it guarantees the public URI has the same prefix - which is by the way the strongly suggested practice, because you don't want the server name in the public URI, you want a pubic URI that is machine independent, so that if you change to another hardware you don't have to do a UIR change (server rename). Server rename is tolerable for some use cases (e.g. in sourcing) but has performance impacts if done too often.
|
