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.

  1. Record the current WebSpeed Version 2 configuration with the following command:
  2. wsconfig -e filename 
    

    This command starts the WebSpeed Configuration utility that documents your current WebSpeed settings, except the PROPATH.

  3. 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.
  4. Save any custom changes made to the Version 2 web-disp.p file and re-apply them to the Version 3.1 web-disp.p file.
  5. Note any internationalization or code-page issues.
  6. If you have customized your WebSpeed Messenger error messages, save the wsCusErr.txt file located in the WebSpeed working directory.
  7. Use the WebSpeed Configuration utility to stop the running Transaction Servers with the following command:
  8. wtbman -stop ts-name 
    

  9. Reboot the system to make sure that the ISAPI/NSAPI messengers are released from memory.
  10. Uninstall WebSpeed Version 2. Afterwards, delete any remaining Transaction Server session and error log files.
  11. 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.
  12. 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.

  13. 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.

Table 12–1: WebSpeed Version 2 To Version 3.1 Conversion Chart For Windows NT
WebSpeed Version 2 Keywords (NT Registry)
WebSpeed Version 3.1 Keywords (ubroker.properties)
InstallPath—Installation directory; set by the install
Also stored in the registry; set by the install
RootPath—Web server document root directory
RootPath—Web server document root directory
ScriptPath—Web server Messenger directory
ScriptPath—Web server Messenger directory
DefaultService—Transaction Server supports the default application service
defaultService—Transaction Server supports the default application service
AllowMsngrCmds—Allow internal admin commands
AllowMsngrCmds—Allow internal admin commands
Components—Leave at default
components—Leave at default
InfoVersion—Leave at default
infoVersion—Leave at default
WsType—Values 1 for broker, 2 for dispatcher
N/A
PortNum—Transaction Server port number
portNumber—Transaction Server port number
Location—Values 200 for local, 100 for remote
location—local or remote (NameServer only)
StartUp—auto-start value
AutoStart—Yes/No
StartInstances—Initial agents to start
initialSrvrInstance—Initial Agents to start
MaxInstances—Maximum number of agents
maxSrvInstance—Maximum number of Agents
BeginNewInstances—Minimum number of free agents
minSrvrInstance—Minimum number of Agents that will be maintained
AgentMinPort—Minimum port number for an agent process
srvrMinPort—Minimum port number for an Agent
AgentMaxPort—Maximum port number for agent process
srvrMaxPort—Maximum port number for a server process
NumBrokers—Number of brokers controlled by the dispatcher
N/A
IdleTimeout—Wait period to shut down idle agents
IdleTimeout—Time Agent can be idle before Broker flags it to be trimmed if more Agents than minSvrInstance active
PriorityWeight—Transaction Server load balancing weight factor
priorityWeight—Transaction Server load balancing weight factor
HostName—System machine name
hostName—System machine name
DefaultDirectory—Application directory
workDir—Transaction Servers’ working directory
ServiceExeFile—Broker executable name
ClassMain—Broker startup executable
WSISADLLFile—ISAPI messenger name
[WebSpeed.Messengers.WSISA] section; set value to msngrExecFile—to the path + executable name
WSNSADLLFile—NSAPI messenger name
[WebSpeed.Messengers.WSNSA] section; set value to msngrExecFile—to the path + executable name
CGIIPExeFile—CGI Messenger name
[WebSpeed.Messengers.CGIIP] section; set value to msngrExecFile—to the path + executable name
IISDllFIle—Renamed broker executable
N/A
AgentExeFile—Agent executable name
srvrExecFile—The agent executable name
AgentParams—Agent startup parameters
srvrStartupParam—Agent startup parameters
ErrorLogFile—Broker error log name
brokerLogFile—Broker error log name
SessionLogFile—Broker session log name
srvrLogFile—Broker session log name
User—The user ID
userName—User ID to start Transaction Server
Group—The group ID for broker process
groupName—Password to start Transaction Server
ServiceNameList—Lists brokers for dispatchers
ServiceNameList—Lists application services for the Transaction Server
Language—Not used
N/A
Environment—Production or development mode
srvrAppMode—Production or development mode
Debugging—Enabled to allow debugging
srvrDebug—Enabled to allow debugging
ApplicationURL—Default is blank
applicationURL—Default is blank
DefaultCookiePath—Default is blank
DefaultCookieDomain—Default is blank
StateTransport—Leave at default
State Transport—Leave at default
StateSavingMethod—Leave at default
StateSavingMethod—Leave at default
StateSavingDirectory—Leave at default
StateSavingDirectory—Leave at default


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095