Release 10.1A: OpenEdge Application Server:
Administration

> ## Configuring an AppServer with the Progress Explorer

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

> | To define and configure an AppServer instance:

> 1. Make sure the AdminServer is running on the host where you want to configure the AppServer (see the "General steps for using the Progress Explorer to configure an AppServer instance" section).

> 2. Open the Progress Explorer.

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

> 4. Do one of the following:

> - To define a new AppServer, select the AppServer folder in the Progress Explorer’s tree view, right-click, and choose New. Enter a unique name for the AppServer 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 AppServer configuration, expand the AppServer folder in the tree view, select the AppServer instance you want to modify, and open the AppServer property editor.

> The AppServer 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 AppServer broker. Expanding this category shows the following property subcategories:

> - General — You must specify an Operating mode, and you probably want to specify a non default value for the TCP/IP port number where the AppServer agent listens for requests.

> If you want the AppServer 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 AppServer product installation, you can also change it here.

> - Owner Information — You can optionally provide Username and Password information for the user who owns the AppServer instance.
> - Controlling NameServe r — You must indicate whether you plan to use a NameServer to control AppServer access. If so, check the Register With NameServer check 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 AppServer broker for client connections.
> - AppService Name List — You can either enter any names for the application services supported by this AppServer or select the Supports default service check box if you want this AppServer 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 AppServer instance.
> - Logging Setting — You can set the following 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 AppServer can support at one time, the AppServer weight factor (Priority weight) for load balancing, the time between retries to register the AppServer with the controlling NameServer, the timeout period for starting the AppServer, the timeout period for an AppServer to accept a client request, and the timeout period for the AppServer agent to trim its quota of AppServer 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 AppServer agents. Expanding this category shows the following property subcategories:

> - General — You can specify a pathname of the AppServer agent executable (Server executable file). You generally only need to specify a different value than the default if you build a new AppServer agent executable using the OEBuild utility. For more information, see the "Customizing the AppServer agent executable" section.

> Specify the OpenEdge startup parameters for the AppServer agent (Server startup parameters). These are the standard OpenEdge client startup parameters, and can include any parameters that you require for each AppServer session, including (but not limited to) all of the standard database, code-page, and process management parameters. For more information, see OpenEdge Deployment: Startup Command and Parameter Reference .

> The AppServer can run with a different code page than the client application. For more information, see the "Managing code pages" section.

> For `PROPATH`, specify the semicolon-separated list of directories where the AppServer can locate 4GL procedures to execute. This setting overrides any `PROPATH` environment variable settings on the AppServer host when it starts up. Make sure that all of the 4GL procedures (r-code or source) that you want the AppServer 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 AppServer agent can assign to AppServer agents that it starts up. (Check with your system administrator for appropriate ranges.)

> - Logging Setting — You can set the following 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 AppServer agents that the AppServer agent can start up and maintain for the AppServer. For more information on setting these values, see the "Specifying the server pool parameters" section.
> - Advanced Features — To allow the 4GL debugger to run in the AppServer session, select the 4GL debugger enabled check box. Specify the names of any AppServer configuration procedures that you want the AppServer to execute, and any parameters for the Startup procedure. For more information on debugging AppServer 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 AppServer instance. Note that an AppServer enabled 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 box, select the alias for the private key/digital certificate entry (in the OpenEdge keystore) that you want to secure connections for this AppServer 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 an OpenEdge Adapter for SonicMQ ServerConnect (ServerConnect) process started by the application service running on this AppServer. It allows you to start a ServerConnect process at startup. You can also set logging options for the ServerConnect: 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 AppServer 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. For more information, see the "Environment variable settings" section.

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

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

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