WebSpeed
Installation and
Configuration Guide
Migrating Your Existing WebSpeed Version 2 Configuration To WebSpeed Version 3.1
Follow these steps to migrate between WebSpeed Version 2 and WebSpeed Version 3.1:
NOTE: Follow these steps before installing WebSpeed Version 3.1 on your system. Be sure to stop all WebSpeed applications before you uninstall WebSpeed Version 2.
- Record the current WebSpeed Version 2 configuration with the following command:
This command starts the WebSpeed Configuration utility that documents your current WebSpeed settings, except the PROPATH.
- The WebSpeed Configuration utility contains an Agent Options tab. The PROPATH settings on this tab are not recorded when you export by WSCONFIG. If you have added values to the PROPATH, write them down. One difference between WebSpeed Version 2 and WebSpeed Version 3.1 is that the PROPATH definition displayed on the Agent Options tab is shared by all Transaction Servers; changing PROPATH in WebSpeed Version 2 affects all Transaction Servers. In WebSpeed Version 3.1, each Transaction Server must be uniquely configured with its own PROPATH.
- Save any custom changes made to the Version 2
web-disp.p
file and re-apply them to the Version 3.1web-disp.p
file.- Note any internationalization or code-page issues.
- If you have customized your WebSpeed Messenger error messages, save the
wsCusErr.txt
file located in the WebSpeed working directory.- Use the WebSpeed Configuration utility to stop the running Transaction Servers with the following command:
- Reboot the system to make sure that the ISAPI/NSAPI messengers are released from memory.
- Uninstall WebSpeed Version 2. Afterwards, delete any remaining Transaction Server session and error log files.
- Install WebSpeed Version 3.1 and re-create the Transaction Servers using the Progress Explorer. See Table 12–1 for a list of keywords that have changed from WebSpeed Version 2 to Version 3.1.
As of WebSpeed Version 3.0, the NameServer is a mandatory component. You should review the documentation describing the NameServer. In WebSpeed Version 2, the NameServer is not required and is included only in the Enterprise version. In WebSpeed Version 2, you create the brokers. Then you have the option to create a Dispatcher, and assign brokers to the Dispatcher during configuration. In WebSpeed Version 3.1, you define the NameServer; then, as you create each Transaction Server, you assign the Transaction Server to a NameServer. Remember that you must recompile all 4GL files in your applications.
- Start the new WebSpeed Version 3.1 Transaction Servers. See "Configuring WebSpeed On Windows," for instructions.
Keyword Conversion Chart
Table 12–1 contains a list of WebSpeed Version 2 keywords taken from the Windows NT Registry and associates them with their WebSpeed Version 3.1 equivalents. You can use this chart as a guide during the process of re-creating the WebSpeed Version 2 Transaction Servers and Dispatchers as WebSpeed Version 3.1 Transaction Servers and NameServers. Progress Software recommends that you use the Progress Explorer to re-create the NameServer and WebSpeed Transaction Servers. However, you can manually edit the values used by WebSpeed Version 3.1, which are defined in the
ubroker.properties
file. It is important to note that the location of the keywords within this file is positional; moving keywords between groups could cause errors. If you choose to edit this file manually, see the "Overview Of the ubroker.properties File" section in "Configuring WebSpeed On UNIX," for more information.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |