Try OpenEdge Now
skip to main content
Administration
AppServer and Internet Adapter Administration : Configuring and Managing the AppServer : Configuring AppServer components : Configuring an AppServer with OpenEdge Management or OpenEdge Explorer
 
Configuring an AppServer with OpenEdge Management or OpenEdge Explorer
You can use OpenEdge Management or OpenEdge Explorer to configure the AppServer on Windows or UNIX.
To configure an AppServer instance:
1. Make sure the AdminServer is running on the host where you want to configure the AppServer (see General steps for using OpenEdge Management or OpenEdge Explorer to configure an AppServer instance).
2. Start OpenEdge Management or OpenEdge Explorer using the appropriate startup procedure, access the AppServer installation you want to configure, then define a new AppServer instance or select an existing instance (see OpenEdge Management and OpenEdge Explorer: Getting Started, OpenEdge Management and OpenEdge Explorer: Configuration, or the online help).
3. Open the configuration pages for the AppServer instance, if they are not already open, and edit them. This displays the current instance settings for properties specified in the ubroker.properties file. These properties are displayed in separate groups, each of which is named for a particular property category. In OpenEdge Management or OpenEdge Explorer, these properties are listed with longer, more readable names that correspond to the actual names of properties in the properties file.
4. 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 set at least some properties under each category. See the online help for detailed information about each property.
The Broker category specifies properties of the AppServer broker. Selecting 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. You can also specify the name of the group (UNIX only).
*Controlling NameServer — You must indicate whether you plan to use a NameServer to control AppServer access. If so, check the Register With NameServer checkbox 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 OpenEdge Management or OpenEdge 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).
In addition, you can choose to allow the dynamic updating of properties and determine how the AppServer behaves when a client connection terminates. You can also set properties related to debugging and identify where you want code published from Progress Developer Studio for OpenEdge to be placed.
For more information on these options, see the OpenEdge Management or OpenEdge Explorer online help.
The Agent category specifies properties of the AppServer agents. Selecting 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 Customizing the AppServer agent executable.
*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 Managing code pages.
*For PROPATH, specify the semicolon-separated list of directories where the AppServer can locate ABL 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 ABL 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.)
*Specify how often data is flushed by the agent to the broker.
*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 online help; set a file-size threshold that determines the point at which a new log file is created (0 = unlimited log file size); specify the maximum number of server log files to be kept (0 = unlimited number of log files retained); and specify the interval (in seconds) for the server log file watchdog thread. 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 Specifying the server pool parameters.
*Advanced Features — To allow the ABL 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 - Security and Auditing. Selecting 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 Environment variable settings.
Note: Do not set the PROPATH variable in the Environment Variables category. Use the Server General category instead.
5. Save the configuration.