Kbase P68605: How to setup the WebSpeed CGIIP Messenger to use two different NameServers?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/05/2009 |
|
Status: Unverified
GOAL:
How to setup the WebSpeed CGIIP Messenger to use two different NameServers?
GOAL:
How to setup the WebSpeed CGIIP Messenger to use NameServers on two or more different machines?
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
CGIIP Messenger installed on machine 'A' is required to pass the requests to the WebSpeed Transaction Server using the NameServer installed on the same machine 'A' and in addition to that to another one which resides on machine 'B' also hosting the WTS.
Configuration layout:
+------------+ +--------------+
| machine A | | machine B |
| | | |
| cgiip | | |
| NS1 | | NS2 |
| WS broker | | WS broker |
+------------+ +--------------+
*** Option 1 (no additional licenses)
a). Create two messenger scripts by copying the cgiip.wsc (Windows), or wspd_cgi.sh (Unix). We will call them 'cgiip1.wsc' and 'cgiip2.wsc'.
b). In 'cgiip1.wsc' you can configure just option (2) '-i wsbroker1' and that one will use the default controlling NameServer which is already installed on machine A.
c). The second script (cgiip2.wsc) would have option (4) where you would add: '-i wsbroker1 -f <PATH>\myprop.properties' .
d). In the file 'myprop.properties' you can define controlling NameServer for the CGIIP messenger that resides on the remote machine B.
To utilize the WTS on machine A one would use: http://machineA/scripts/cgiip1.wsc/program.w
and for the WTS on machine B it would be: http://machineA/scripts/cgiip2.wsc/program.w
*** Option 2 (no additional licenses)
If the two WebSpeed Transaction Servers have different names for the WebSpeed broker's service that registers with the NameServer, so for example on machine A you have service 'wsbroker1' and on machine B you have service 'wsbroker2', then you can use neighboring NameServers.
a). Using Progress Explorer (or manually modifying the ubroker.properties) on the machine A create a remote NameServer (let's call it NS2) which has the host name of machine B and its appropriate port.
b). Assign this remote NameServer NS2 to the already existing local NameServer on machine A (probably NS1) as the neighboring NameServer.
In this case, if you specify in the URL the service name which is not registered with the NameServer on machine A, then the request will be forwarded to the remote NameServer on machine B.
For example, this would run on machine A: http://machineA/scripts/cgiip.exe/WService=wsbroker1/program.w
and this would run on WTS on machine B: http://machineA/scripts/cgiip.exe/WService=wsbroker2/program.w
*** Option 3 (with NameServer Load Balancing license)
If you have NameServer Load Balancing license, then you can utilize messenger UDP broadcast that queries all NameServers listening on the same port in the specified network segment specified by the IP subnet mask in the messenger properties. This is covered in details in the Progress documentation "Progress Installation and configuration Guide for Windows",. chapter "7.5 Understanding Load Balancing"..