Kbase P6632: How to run multiple webspeed versions in one window machine simultaneously
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/04/2008 |
|
Status: Verified
GOAL:
How to run multiple WebSpeed version in one windows machine simultaneously
GOAL:
How to manage use one IIS web server to support multiple versions of webspeed broker?
FACT(s) (Environment):
WebSpeed 3.x
OpenEdge 10.x
Windows
FIX:
Things need to consider in order to run the multiple version of the WebSpeed simultaneously are port number that are being used by AdminServers, NameServers, brokers and the range of TCP ports used by the WebSpeed agents as well as the uniqueness of the NameServer name. Here is how to accomplish this:
1. Modify the registry to specify a different port for each version of the AdminServers. Refer to Progress Solution 18919, "How to Change the Port Number When the 9.x Admin Server is Running On?"
2. Assuming the NameServer NS1 already exists in both version of the WebSpeed, create another NameServer named NS2 with a different port. Usually the NameServer is setup auto start by default. Go to the NameServer properties in the progress Explorer and uncheck auto start for NS1 in the version that has NS2 created. Make the NS2 start automatically instead. Be sure to change the UDP port number for NS2.
3. Go to the broker properties and change the Controlling NameServer to NS2 for the version of the WebSpeed on which the second NameServer is created. The broker is not setup to auto start by default. Depending on the needs, broker can also be setup to start automatically. Again make sure to change the TCP port for the broker. The range of the port also can be changed here. The range of the port is so high that the change may not be necessary but, if the firewall exists, a narrower port range is recommended for each broker in the same or different version in this case.
4. It is very necessary to keep the 2 messengers in different version separate. To do it there are 2 choices:
a) create a separate folder other then scripts and create a virtual directory for it in the IIS. Be sure to allow the execute privilege to that folder. Copy and paste one of those version's messenger to that newly created folder.
or
b) Rename the messenger like cgiip91d.exe or wsisa91d.dll in the scripts directory so both versions of messengers does not over write each other.
5. Go to the messenger properties and change the Controlling NameServer to the version specific NameServer. Again, the messenger listening UDP ports (Max and Min NameServer Client Port range) can also be specified here for each of the version if firewall exists.