Siebel System Administration Guide > Structure of the eapps.cfg File > Parameter Descriptions of the eapps.cfg File >

[swe] Section


The parameters that follow can be found in this section of the eapps.cfg file. These parameters apply to all of the Siebel Business Applications that you configured.

DisableNagle

This parameter, when set to True, disables the Nagling algorithm feature of Microsoft IIS Web server. The default value is False. This parameter is optional and, if required, must be manually input into the [swe] section of the file.

Language

This parameter defines the language version of Siebel Business Applications. For example, enu stands for U.S. English.

LogDirectory

This parameter defines the location of the log directory, whose default location is

SWSE_ROOT\LOG (Windows)

SWSE_ROOT/log (UNIX)

NOTE:  To configure SWSE logging, set the appropriate environment variables. For more information, see Siebel System Monitoring and Diagnostics Guide.

MaxQueryStringLength

This parameter controls the size of HTTP POST requests from the SWSE. The default value is 500000 bytes (approximately 500 KB). Values for this parameter include:

  • -1 to use the default value.
  • Any value greater than 0 to set the limit of this parameter, in bytes, to the indicated value, for example, 250000.

NOTE:  The HTTP GET method has a 2 MB request limit, which is defined by the HTTP protocol.

ClientRootDirectory

This parameter defines the location of the SWSE installation, whose default location is referred to as SWSE_ROOT. For more information about the SWSE installation, see the Siebel Installation Guide for the operating system you are using.

SessionMonitor

Use this parameter to determine whether to gather statistics on all of the current sessions and report them in the SWSE stats page. To enable session monitoring, set SessionMonitor to True. When this parameter is set to True, the SWSE stats page contains information about sessions of users who have logged in to the system. If a user exits properly, using the Logout command, then this information is removed from the stats page. If a user exits out of the application by closing the application or if the session times out, then the session information remains on the stats page until the Web server is restarted.

Session data includes each user's user name and unencrypted session ID, so it is important to restrict visibility to the SWSE stats page when SessionMonitor is enabled. To prevent non-administrators from viewing the SWSE stats page, you can change the StatsPage parameter to a value known only to administrators.

If SessionMonitor is disabled (set to False), then sessions remain unmonitored and do not appear on the application SWSE stats page.

NOTE:  The collection of session information results in a slight degradation in performance.

For more information about configuring and viewing the SWSE stats page, see Siebel System Monitoring and Diagnostics Guide.

AllowStats

This parameter enables or disables application-specific statistics reporting in the SWSE stats page. To enable the collection of application-specific statistics, set AllowStats to True. AllowStats set to False disables statistics gathering. The default is True (enable statistics collection).

NOTE:  If it is set to False, then only system-level statistics are displayed on the SWSE stats page.

LogSegmentSize

This parameter determines how large a segment of the log file is, in 512 byte blocks. For example, if you set this parameter to 5, then the log segment will be 2.5 KB in size. A value of 0 turns off segmentation.

LogMaxSegments

This parameter determines the number of log segments that will be kept. If you set this parameter to 1, then only one segment is kept. When this segment reaches the size specified by the LogSegmentSize parameter, the segment is overwritten. In general, set this parameter to a high value, such as 20. In this case, the twenty-first segment overwrites the first segment, and so forth. A value of 0 turns segmentation off.

Siebel System Administration Guide Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.