Kbase P77545: How to set up cgiip messenger to connect to different Webspeed brokers without name server?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/24/2007 |
|
Status: Verified
GOAL:
How to setup the cgiip messenger to connect to different Webspeed brokers without name server?
GOAL:
How to connect the cgiip.wsc messenger script to multiple different Webspeed brokers without NameServer on Windows?
GOAL:
How to connect the cgiip messenger to multiple different Webspeed brokers without using NameServer on Unix?
GOAL:
How can I allow cgiip messenger to connect to multiple different Webspeed brokers without using name server?
GOAL:
How to configure multiple messengers each accessing different Webspeed brokers without using name server?
FACT(s) (Environment):
WebSpeed 3.1x
OpenEdge 10.x
FIX:
The goal can be achieved by creating multiple messenger script files that each references a different Webspeed broker.
The concept is the same on Windows and Unix, however the script file names are different.
On Windows, the messenger script file name is cgiip.wsc.
On Unix, the messenger script file name is wspd_cgi.sh.
On Unix
1. Make multiple copies of the wspd_cgi.sh file to as many different Webspeed brokers you need to support. In following example, there are three different Webspeed brokers all running different webspeed applications. The Webspeed broker names are:
wsmyprod
wmytest
wsmytraining
2. Rename the messenger script files, i.e.
wsmyprod_cgi.sh
wsmytest_cgi.sh
wsmytrain_cgi.sh
3. Make multiple copies of ubroker.properties file and name them differently, ie, ubroker.properties_prod
ubroker.properties_test
ubroker.properties_train
4. Within each messenger script file, use option (4) and point to the corresponding ubroker.properties file,
wsmyprod_cgi.sh --> -f $DLC/properties/ubroker.properties_prod
wsmytest_cgi.sh ---> -f $DLC/properties/ubroker.properties_test
wsmytrain_cgi.sh ----> -f $DLC/properties/ubroker.properties_train
5. Ensure the ubroker.properties file of the messenger, CGIIP, has all correct information defined underneath it.
For example, ubroker.properties_prod has
registerNameServer=0
Host=host1
Port=port1
On Windows
1.Make multiple copies of the cgiip.wsc to as many different Webspeed brokers exist.
2. Rename the messenger script files, i.e.
cgiip1.wsc
cgiip2.wsc
cgiip3.wsc
3. Within each messenger script file, use option (4)
4. Ensure in each of the ubroker.properties file of the messenger, CGIIP, has all correct information defined underneath it.
5. This next step should already be done when using application mapping, however ensure that the .wsc extension is registered within the webserver. Follow solution
16091, "How to set up the .wsc file with CGIIP on IIS?"