Article

How to set up cgiip messenger to connect to different Webspeed brokers without name server?

Information

 
Article Number000093491
EnvironmentProduct: OpenEdge
Version: 10.X,11.X
OS: Windows
Question/Problem Description
How to set up cgiip messenger to connect to different Webspeed brokers without NameServer?
Is it possible to configure cgiip messenger to connect to different Webspeed brokers without NameServer?
Unable to use '-f' option with cgiip to connect to Webspeed brokers without NameServer
How to use '-f' switch without '-i'  with cgiip?
How to connect the cgiip messenger to multiple different Webspeed brokers without using NameServer on Unix?
Steps to Reproduce
Clarifying Information

 
Error Message
Defect/Enhancement Number
Cause
Resolution
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) or option(3) to use '-f' option

4. Ensure in each of the ubroker.properties file of the messenger, CGIIP, has all correct information defined underneath it. 

cgiip -f <properties file> # Started with a specific property file, this overrides the default property file ($DLC/ubroker.properties). 
If -i <WS_service> is specified that service name in the <properties file> will be used. If -i <WS_service> is not specified then the default service must be set in <properties files>. 
Workaround
Notes
Attachment 
Last Modified Date12/21/2018 12:21 PM


Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025