Release 10.1A: OpenEdge Application Server:
Administration

> ## Configuring WebSpeed with the Progress Explorer

> To configure WebSpeed in Windows, you can use the Progress Explorer.

> | To define and configure a WebSpeed instance:

> 1. Make sure the AdminServer is running on the host where you want to configure WebSpeed.

> 2. Open the Progress Explorer.

> 3. Connect to the AdminServer on your WebSpeed host (see OpenEdge Getting Started: Installation and Configuration ).

> 4. Do one of the following:

> - To define a new WebSpeed instance, select the WebSpeed folder in the Progress Explorer’s tree view, right-click, and choose New. Enter a unique name for the WebSpeed instance and click OK. Then open the property editor for the new instance by selecting the instance, right-clicking, and choosing Properties.
> - To modify an existing WebSpeed configuration, expand the WebSpeed folder in the tree view, select the WebSpeed instance you want to modify, and open the WebSpeed property editor.

> The WebSpeed instance property editor shows a tree view of property categories on the left and the properties for the selected category on the right.

> 5. Select a property category and set the properties as required. You can accept the default values, if they are appropriate for your application. You probably want to specify the properties under each category. See the Progress Explorer online help for detailed information about each property.

> The Broker category specifies properties of the WebSpeed broker. Expanding this category shows the following property subcategories:

> - General — The Operating mode is fixed stateless, and you probably want to specify a nondefault value for the TCP/IP port number where the WebSpeed broker listens for requests.

> If you want WebSpeed to start whenever you start the AdminServer, select the Auto start check box, and if you want to use a different working directory from the one specified during the WebSpeed product installation, you can also change it here.

> - Owner Information — You can optionally provide Username and Password information for the user who owns the WebSpeed instance.
> - Controlling NameServe r — You must indicate whether you plan to use a NameServer to control WebSpeed access. If so, check the Register With NameServer box and select a controlling NameServer from the list of NameServer instances that you have already configured. Also specify how you want the NameServer to provide the host address of the WebSpeed broker for client connections.
> - AppService Name List — You can either enter any names for the application services supported by WebSpeed or select the Supports default service check box if you want WebSpeed to support the default service for all client connections that do not specify an application service name. If you choose to use application service names, the default application service name is the name of the WebSpeed instance.
> - Logging Setting — You can set the following WebSpeed broker logging options: specify a different pathname from the default for the broker log file; specify the level of logging detail; control whether the logging for a session appends to or overwrites the previous broker log file; specify a comma-separated list of logging entry types to be included in the broker log file, choosing from the valid values listed in the Progress Explorer online help; set a file-size threshold that determines the point at which a new log file is created (0 = unlimited log file size); and specify the maximum number of broker log files to be kept (0 = unlimited number of log files retained). See OpenEdge Development: Debugging and Troubleshooting for detailed information on logging options.
> - Advanced Features — You can specify the maximum number of client connections (Maximum client instances) that the WebSpeed broker can support at one time, the WebSpeed weight factor (Priority weight) for load balancing, the time between retries to register WebSpeed with the controlling NameServer, the time-out period for starting WebSpeed, the time-out period for WebSpeed to accept a client request, and the timeout period for the WebSpeed agent to trim its quota of WebSpeed agents between the maximum and minimum setting (see the Agent category). For more information on these options, see the Progress Explorer online help.

> The Agent category specifies properties of the WebSpeed agents. Expanding this category shows the following property subcategories:

> - General — You can specify a pathname of the WebSpeed agent executable, startup parameters for the WebSpeed agent. For more information, see OpenEdge Deployment: Startup Command and Parameter Reference .

> For `PROPATH`, specify the semicolon-separated list of directories where WebSpeed can locate 4GL procedures to execute. This setting overrides any `PROPATH` environment variable settings on the WebSpeed host when it starts up. Make sure that all of the 4GL procedures (r-code or source) that you want WebSpeed to execute are located in one of these `PROPATH` directories. Otherwise, the procedure must be executed using its fully qualified pathname.

> Specify the minimum and maximum TCP/IP port numbers that the WebSpeed agent can assign to WebSpeed agents that it starts up. (Check with your system administrator for appropriate ranges.)

> Specify the mode for running applications during the current WebSpeed session using the Agent Application Mode. The default mode is Development.

> - Logging Setting — You can set the following WebSpeed agent logging options: specify a different pathname from the default for the server log file; specify the level of logging detail; control whether the logging for a session appends to or overwrites the previous server log file; specify a comma-separated list of logging entry types to be included in the server log file, choosing from the valid values listed in the Progress Explorer online help; set a file-size threshold that determines the point at which a new log file is created (0 = unlimited log file size); and specify the maximum number of server log files to be kept (0 = unlimited number of log files retained). See OpenEdge Development: Debugging and Troubleshooting for detailed information on logging options.
> - Pool Range — These settings determine the number of WebSpeed agents that the WebSpeed agent can start up and maintain for WebSpeed.
> - Advanced Features — Specify the path a WebSpeed application uses relative to your Web server as the Application URL. You can specify settings for Default Cookie Path and Default Cookie Domain.

> To specify the directory that WebSpeed agents use to upload text files, use File Upload Directory.

> To allow the 4GL debugger to run in the WebSpeed session, select the 4GL debugger-enabled check box. Specify the names of any WebSpeed configuration procedures that you want WebSpeed to execute, and any parameters for the Startup procedure. For more information on debugging WebSpeed applications and on AppServer configuration procedures, see OpenEdge Application Server: Developing AppServer Applications .

> The options in the SSL category options define the security settings for an SSL-enabled WebSpeed instance. Note that a WebSpeed-enabled instance for SSL operation does not accept non-SSL client connections. For more information on SSL operations, see OpenEdge Getting Started: Core Business Services . Expanding this category shows the following property subcategories:

> - General — If you check the Enable SSL Client Connections check box, select the alias for the private key/digital certificate entry (in the OpenEdge keystore) that you want to secure connections for this WebSpeed instance. Also enter and confirm the password for this private key and digital certificate. You need not enter a password if you choose to use the default_server certificate and its default password.
> - Advanced Features — By default, caching is enabled for the SSL client session, and you can enter a time-out value that specifies the length of time (in seconds) that a disconnected session is held in the cache. During this specified interval, a connected client can resume its session. To disable session caching, check the box.

> The Messaging category specifies properties for a ServerConnect process started by the application service running on this WebSpeed Transaction Server. It allows you to start a SonicMQ ServerConnect background process at startup. You can also set logging options for the SonicMQ ServerConnect process: specify a different pathname from the default for the broker log file; specify the level of logging detail; control whether the logging for a session appends to or overwrites the previous broker log file; specify a different pathname from the default for the server log file; specify the level of logging detail; control whether the logging for a session appends to or overwrites the previous server log file. See OpenEdge Development: Debugging and Troubleshooting for detailed information on logging options.

> If you want to specify environment variables for WebSpeed execution, select the Environment Variables category. It allows you to enter name-value pairs for environment variable settings. Any values you set here override prior values set for the same environment variables in the operating system.

> Note: Do not set the `PROPATH` variable in this category. Use the Server General category instead.

> 6. Choose the OK button to save the configuration.

> For information about how to use the Progress Explorer to configure WebSpeed, see the Progress Explorer online help.

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