WebSpeed
Installation and
Configuration Guide
Migrating Your Existing WebSpeed Version 2 Configuration To WebSpeed Version 3.1
Follow these steps to migrate from WebSpeed Version 2 to WebSpeed Version 3.1:
NOTE: Follow these steps before to installing WebSpeed Version 3.1 on your system. Be sure to stop all WebSpeed applications before you uninstall WebSpeed Version 2.
- Save the current WebSpeed Version 2 configuration. This information is stored within the
webspeed.cnf
file and can be located by looking at the WEBSPEEDCNF environment variable.- You should note the current WebSpeed Version 2 environment variables, specifically PROPATH. If you have customized PROPATH, write the values down and apply them to the WebSpeed Version 3.1 PROPATH. Other WebSpeed Version 2 variables might have been defined within the
wsset.env
file; its WebSpeed Version 3.1 equivalent is theubroker.properties
file.- 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 work directory.- Stop each of the running Transaction Servers with the following command:
- Delete any remaining Transaction Server session and error log files.
- Delete the WebSpeed Version 2 installation directory.
- Install WebSpeed Version 3.1 and modify the
ubroker.properties
file to re-create the Transaction Servers. If you have the Progress Explorer available on a remote machine, you can use it to re-create the WebSpeed Transaction Servers and NameServer. See Table 13–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 UNIX," for instructions.
Keyword Conversion Chart
Table 13–1 contains a list of WebSpeed Version 2 keywords taken from the
webspeed.cnf
file 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 theubroker.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 |