Hi,
We are trying to deploy a sonic connect service for a webservice hosted on a sonic ESB on two different machines but we're kind of stuck on the best way to set the endpoint of the service.
what we would like:
http://server1:8080/wsservice
and
http://server2:8080/wsservice
But it seems you can only specify one adres in the connect properties file (to the best of our knowledge).
The current setup: if you configure the service with the adress of server one, the ESB container on server2 complains and vice versa.
Our current way of thinking is to define an extra connectservice for server2 and deploy the first connectservice only on server1 and the second only on server2, but I don't like it very much because you have some duplication and the deployment setup gets a bit complexer.
Does anybody has a recommandation for this type of setup? I doubt we're the first ones to deploy such a thing :-).
One more thing: before the two servers there is a loadbalancer which distributes the load between these two servers.
T.i.a,
Koen
Hello,
You can use expresions to define the hostname (search Sonic workbench help for Expression.
There is a Progress Solution that explains the details:
http://progress.atgnow.com/esprogress/openSolution.do?tabs=true
solution ID: P178021
hth
Stefan
Thanks Stefan,
This is just what we needed.
Cannot answer your private message. It seems you have not activated that.
Please mail me at sfritz at progress.com
Another alternative is to set the URL to:
This will cause the SC service to listen on all network interfaces on any server.
Thomas
In the solution P178021, it says this:
The above example uses a ESB container deployment parameter (${container['MyHostName']}) to define the hostname/IP-address of the web service port.
Where do I set this MyHostName parameter?
Thank you
SMC --> configure tab --> select MF container where the ESB container is deployed to
Select the ESB container --> right mouse click --> properties --> deployment parameters
Regards
Stefan
Found it! Thank you!