WebSpeed
Installation and
Configuration Guide
Coexistence Of WebSpeed Version 2 With WebSpeed Version 3.1
WebSpeed Version 2 can coexist with WebSpeed Version 3.1. However, issues will arise if you do not perform the installation correctly. Although there are fewer conflicts than in WebSpeed NT configurations, the primary problem, which is maintaining duplicate application code in order to accommodate changes to the application URL, still exists.
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 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:
- Messengers—WebSpeed Version 3.1 Messengers are not intended to be backward-compatible with WebSpeed Version 2 Messengers. The WebSpeed CGIIP Messenger is not copied into the Web server’s Scripts directory by the install program. Instead, this messenger is executed through a shell script that is located within the Web server Scripts directory.
Configurations using the NSAPI Messenger cannot coexist. Due to the way this Messenger works, an incoming connection cannot be correctly filtered and sent to the appropriate version of the Messenger. Therefore, only one version of this Messenger can exist per Web server. Additionally, it is not possible to configure the Netscape
obj.conf
file to support two WebSpeed NSAPI messengers.Both WebSpeed Version 2 and WebSpeed Version 3.1 provide a sample script called
wspd_cgi.sh
that is copied into the Scripts directory during the installation. To avoid overwriting this file, rename the original script prior to installing WebSpeed Version 3.1 on your system.In order to support both versions of the WebSpeed CGI Messenger, you must create an additional copy of the existing scripts, making the necessary modifications so that the environment settings are correct and the correct Messenger is executed. You must copy your application and modify the application URLs to point to the new script.
For example:
becomes:
- Path—The path presents a possible conflict. You might have added to the path a reference to the WebSpeed Version 2
/bin
directory. WebSpeed Version 2 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 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. Remember, if the WebSpeed/bin
directory was added to the system environment path, it should be removed and set only for the specific command shell.- Command-line Utilities—Both WebSpeed Version 2 and WebSpeed Version 3.1 support two command-line utility programs, WTBMAN and WSCONFIG. These utilities are not backward-compatible. WebSpeed Version 3.1 also includes additional command utilities:
- Static HTML files—Static HTML files are an issue, especially in development configurations, because both versions of the WebSpeed Workshop use static HTML files and look for them in one specific directory. Because these files have the same names, they cannot reside in the Web server’s document root directory. This creates problems for coexistence.
As a workaround, creating a second Web server on the system, with its own document root directory and running at a different port number, would solve the problem; but, again, it requires changes to the WebSpeed application URLs to incorporate the new port number.
- Environment Variables—When you start a Netscape Web Server, your startup script sets environment variables that are specific to each version of WebSpeed. This prevents you from simultaneously running two versions of WebSpeed on the same Netscape Web server.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |