WebSpeed
Installation and
Configuration Guide
Coexistence Of WebSpeed Version 3.0 With WebSpeed Version 3.1
WebSpeed Version 3.0 can coexist with WebSpeed Version 3.1. However, issues will arise if migration is not performed correctly. Therefore, Progress Software recommends that you do not use mixed configurations.
Because of the way they handle memory, some systems might not let you simultaneously load two versions of the same Messenger into memory. If you must support a mixed configuration, the easiest solution is to set up a different Web server and use a different type of Messenger (CGI, ISAPI, or NSAPI) for each version. You would then have to maintain a copy of your application code for each version, changing the URLs to point to the appropriate Web server and WebSpeed Messenger.
Before you decide whether to maintain both versions, consider the following points:
- Registry Keys—WebSpeed Version 3.1 uses a different registry key from the key used by WebSpeed 3.0; therefore, the Version 3.0 registry key will not be overwritten.
- Program Groups—WebSpeed Version 3.1 uses the same default Program Group as WebSpeed 3.0. Remember to use a different Program Group name when you install WebSpeed Version 3.1.
- Progress Explorer—For WebSpeed Version 3.1, the Progress Explorer operates as a plug-in to the MicroSoft Management Console (MMC). The new Progress Explorer cannot connect with the AdminServer of earlier versions of WebSpeed.
- Messengers—The WebSpeed Version 3.1 Messengers are not intended to be backward-compatible with WebSpeed 3.0 Messengers.
WebSpeed Active Server Pages (ASP) Messenger coexistence is not supported.
Configurations using the NSAPI and ISAPI Messenger cannot coexist. Due to the way these Messengers work, an incoming connection cannot be correctly filtered and sent to the appropriate version of the Messenger. Therefore, only one version of these Messengers can exist per Web server. Additionally, it is not possible to configure the Netscape
obj.conf
to support two WebSpeed NSAPI Messengers.Because the ISAPI and CGI Messengers are integrated into the directory structure of the Web server, these two messengers are installed into the Web server
\scripts
directory. Because WebSpeed Version 3.1 Messengers use the same file name as the WebSpeed 3.0 Messengers, an installation of WebSpeed Version 3.1 overwrites the previously installed WebSpeed 3.0 Messengers.You can work around this issue by maintaining both sets of messengers. There are two ways that you can achieve this:
- Re-name the existing WebSpeed
CGIIP.EXE
andWSISA.DLL
messengers to a unique.EXE
and.DLL name
. Then install WebSpeed Version 3.1 on your system. Both sets of messengers will be in the same Scripts directory. You will then have to maintain two sets of application code, modifying the URLs to reference the new messenger name in one and leaving the other to refer to the original messenger names.- Modify the Web server by adding an additional virtual directory to be used as a secondary Scripts directory. You can do this through your Web server administration program prior to installing WebSpeed Version 3.1 on your system. During installation, enter the new Scripts directory name when you are prompted for the Web server Scripts directory. Because the location of the messenger has changed, you need to make a copy of all your existing WebSpeed applications and modify them so that the application URLs refer to the correct Scripts directory. For example:
becomes:
- System Path—The System Path presents a possible conflict. A WebSpeed 3 user might have added to the System Path a reference to the WebSpeed 3
\bin
directory. WebSpeed 3.0 and WebSpeed Version 3.1 use some of the same command-line utilities, such as WTBMAN. The command-line utilities for Version 3.1 are not backward-compatible. If you use the system path to provide access to the WTBMAN utility, only the first WTBMAN found would be executed, and this might be the incorrect version.You can work around this by modifying the path specifically for a command shell. You can configure two command shells, each with a unique path and referencing the correct WebSpeed
\bin
directory. If you added the WebSpeed\bin
directory to the system path, remove it and set it only for the specific command shell.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |