The following options are displayed in the Server Properties panel:
Max Concurrent Sessions
Host Session Threads
Event Handler Options
Create Pooled Sessions Concurrently
Rogue Session Management
Model Debug Message Management
Version and License Information
Select an option to view or configure it. In view mode, you can view configuration information, you cannot modify it. To modify configuration information, use the Administrator profile to log on and switch the Administrative WebStation to configure mode.
Max Concurrent Sessions is the maximum number of concurrent sessions allowed
to run on this Server. The range of values is 1 - 5000, and the default is 10.
Max Concurrent Sessions must match the number of licenses purchased by your organization. If you are running multiple Servers, the combined total of Max Concurrent Sessions on all Servers must match the number of licenses purchased. For example, if you have three Servers and you purchased 75 licenses, you can set Max Concurrent Sessions on your Servers to 20, 25, and 30 respectively. You can divide the numbers any way you want, as long as the total on all Servers does not exceed your number of licenses.
Note: On the Server included with the Development Kit , the range of values is 1 - 5, and the default is 5.
The Inactivity Timeout is the number of minutes a data object-to-host session connection can be idle before the host session disconnects from the data object and either terminates or returns to its session pool. The range of values is 0 - 2147483647 and the default value is 30 minutes. Setting the Inactivity Timeout to 0 means the session will never time out.
Note: The inactivity timeout used for a session is the timeout that is in effect when the session connects. If you change the timeout, the new value will be used for sessions that connect after the change is saved to the Server; it will not affect sessions that were connected when the change was made.
Specifies the number of processes, or instances of the Host Integrator Server, that can run on the machine where the Server is installed.
Each session between a data object and the host requires a minimum of two file handles. If your system allows a maximum of 1024 file handles per process, setting Server processes to 1 allows approximately 500 sessions to run at the same time. If your system allows more file handles per process, for example 2048, then setting Server processes to 1 allows approximately 1000 sessions to run.
The range is 1 - 8, and the default is 1.
Specifies the number of threads the Windows platform Server dedicates to processing host session activity. The range of values is 1 - 32, and the default is 2. For best performance, set the Windows thread count equal to the platform's CPU count, but never less than 2.
Disable event handler timeouts controls the use of event handler timeouts on the Server. If event timeout is enabled, the event timeout specified in the model is used. If event timeout is disabled, no timeouts are enforced when an event handler is processing an event.
Enable script manager debug port allows you to enable or disable the debug port on the Server. This port is used by the script manager for communicating with a Java debugger.
Requested event handler debug port is the port number from which the Host Integrator Server will start searching for an available remote debugging port. The default value is 5005.
Assigned event handler debug port is the JVM remote debug port that is currently in use. If the requested debug port is unavailable, then a higher number will be requested until an available port is found.
The Session Server initializes and connects the minimum number of sessions (Count) specified for each session pool, making them available for use by client applications when the server is started. This setting determines whether the Host Integrator Session Server creates new pooled host connections concurrently or serially. The default is to create them concurrently (enabled). Disable this setting for slower or older hosts if concurrent creation could cause errors when multiple session pools are initialized.
Note: The Session Server does not accept connection requests from clients or from the Administrative WebStation while it is in the process of preconnecting pooled sessions. The pooled session connection process is completed after the login script terminates. If you disable this setting, the process of serially creating pooled sessions at startup may take a significant amount of time on a slower host with a high pooled sessions count. Also, misconfigured session settings can produce multiple delays as each session in the pool attempts to connect.
Rogue sessions within a session pool exhibit a circular behavior when attempting to log in and reconnect under conditions such as the following:
You can configure the server to handle these rogue sessions so that they are "quarantined" until you have addressed the underlying problem. Select this option to enable rogue session management. When enabled, any session that has been suspended for any of the conditions described above has the Rogue session setting enabled in the Active Sessions list.
Use Host Integrator troubleshooting tools, such as the Session Manager, the View Session option within the Administrative WebStation, the Server Management Errors list in the Administrative WebStation to diagnose the problem. After the necessary modification has been made (for example, the expired password in the model variable list has been updated), go to the Active Sessions list, enter configuration mode and remove the sessions that have a Rogue Session setting checked. The session is then available again for use within the session pool.
When developing models in the Design Tool, model debug message recording is always on. When deploying models to the server, you can specify the model debug messages recording level as a deployment descriptor, or you can change Model Debug Message Recording in the Administrative WebStation's model configuration or session pool configuration. By default, the model debug messages recording level for a deployed model is to record nothing. When debugging, the recommended setting is to record errors only.
The settings below handle the size and location of the runtime model debug message recording files.
By default, this is in the \etc\reports directory for the Host Integrator installation. You can change the directory location on the local machine.
Model debug message files (with a .vmr extension) are saved in a structure based on the time a server started. The time-stamped directory contains model debug message files named by model name and session ID, for example, CICSAccts.8.vmr. Since older .vmr files are automatically removed from the server (by default, after 7 days), you should copy the files (or increase or disable the cleanup thresholds) if ongoing analysis is necessary.
Note: Changing the setting for the directory will not take effect until the server is restarted.
The size of the in-memory buffer for model debug messages. The cache size is the amount of memory per session on the server. (For example, 500 concurrent sessions x 2 MB cache size = 1000 MB of system memory required.) When this limit is reached, the model debug message contents are written to the model debug messages file. The model debug message recording process continues, and additional messages are added to the file when appropriate.
If you find that model debug message recording is slowing down the server, you may want to increase this value.
The amount of time that a model debug message file remains on the server. If Model Debug Message
Space Threshold is set to 0, then daily maintenance is performed and any model debug message files
older than the setting specified will be removed. The default is 7 days.
If Model Debug Message Space Threshold is set to a number greater than 0, then hourly maintenance
of model debug messages is performed and any model debug message older than the setting specified
will be removed, regardless of disk space availability.
The amount of disk space, in MB, that is maintained for the most recent model debug message files.
The model debug message directory is reduced to this size on an hourly basis, keeping the newest
files that fit within this threshold. The reduction process removes oldest files when necessary. A
good value for this setting is half of the maximum space for model that you want to allocate for
model debug message files.
If you want to enforce a maximum for model debug message space, it is recommended that you specify
a dedicated virtual drive on the local machine.
The remaining items in the Server Configuration panel provide non-configurable information about your Host Integrator product license. In addition to the Host Integrator Server version number, the product ID and licensed session limit are listed. If you are using a time-limited evaluation version of Host Integrator Server, the grace period and expiration date are also listed.