Previous Topic: SelListCacheExclude

Next Topic: Configuring Auto Assignment

SelListCacheMax

SelListCacheMax

Defines the maximum number of records in a table that can be cached in the web engine. The web engine keeps the entire contents of tables at or below its cache size in its own memory, improving its performance in building <PDM_SELECT> lists using these tables. Specifying a higher value for this property improves performance at the expense of memory usage.

Default: 10

SelListCacheMax is ignored for tables used in hierarchical search lists, such as category on requests, issues, and change orders. The web engine always stores the entire contents of tables used in hierarchical search lists in its own memory. If you have a large number of values in any of these tables, you may want to specify the SelListCachePreload property.

SelListCachePreload

Specifies one or more tables to be loaded into the web engine’s select cache at startup time. Tables not specified in this property are loaded the first time they are used. If SelListCacheMax is large, or if you have a large number of records in a hierarchical search list (such as category), you may want to specify the table in SelListCachePreload. This avoids a response time delay the first time a user accesses a form using the table.

The specification for the SelListCachePreload property is a blank-separated list of object names. Each object name can be followed by an optional list of attribute names in parentheses. The attributes specified in the list are loaded into the web engine. If no attributes are specified, only the common name and rel attr value of the object are loaded. This is sufficient for drop-down selects, but may not be sufficient for hierarchical searches. If you modify the hierarchical search forms (hiersel_xx.htmpl, where xx is an object name), be sure that the SelListCachePreload property specifies every attribute used in the form. If you omit an attribute, the cache is reloaded when the form is used.

The SelListCachePreload property is optional. If it is omitted, nothing is loaded into the select cache until a user requests a form using a drop-down select or a hierarchical search.

chgcat(description owning_contract) chgstat crs isscat(description owning_contract) issstat pcat(description cr_flag in_flag pr_flag owning_contract) pri tskstat urg pcat_cr(description cr_flag in_flag pr_flag owning_contract) pcat_pr(description cr_flag in_flag pr_flag owning_contract) pcat_in(description cr_flag in_flag pr_flag owning_contract)
StayCacheList

Specifies the names of forms that are never removed from the forms cache, regardless of the length of time they have been displayed. This property ensures that the fixed frames on a frame display remain for the lifetime of a session. It can be used with caution to cause other forms to be permanently cached. The default is as follows:

scoreboard.htmpl top_splash.htmpl buttons.htmp hiersel_admin_tree.htmpl
SuppressHtmplCache

Specifies that the web engine should reread all files defining the contents of a page each time the page is requested. Parsing an HTMPL file takes a significant amount of web engine processing time, and usually involves reading several physical files (because most pages use PDM_INCLUDE tags). The web engine normally saves parsed files in its own memory so that future requests for the same page can be satisfied immediately. This markedly improves performance, but can be inconvenient for users in the process of developing new or updated pages, as the web engine must be recycled for changes to take effect.

This property is optional and requires no value. If it is specified, the web engine does not cache parsed files, and changes to HTMPL files take effect immediately. Because of its impact on performance, this property should not be specified in a production environment.

SuppressLoginAndLogoutMsg

Specifies that the web engine should not log a message to the CA SDM log file each time a user logs in or logs out of the web interface.

This property is optional. If it is not specified, the web engine logs a message each time a user logs in or logs out.

SuppressMacroCache

Specifies that the web engine should discard all saved macros each time a new page is requested. The web engine normally saves parsed macros in its own memory so that future requests for the macro can be satisfied immediately. This improves performance, but can be inconvenient for users in the process of developing new or updated macros, as the web engine must be recycled for changes to take effect.

This property is optional. If it is specified, the web engine does not cache parsed macros, and changes to macros take effect immediately. Because of its impact on performance, this property should not be specified in a production environment.

Timeout

Specifies the number of minutes that a user’s session can be idle before it is automatically terminated, freeing up all server resources.

Note: The Timeout setting must be longer than the ExclLockSeconds setting. ExclLockSeconds is specified in seconds and Timeout is specified in minutes.

TooManyMatches

Specifies the text of the message to display under a field when a user’s key for a lookup field is ambiguous and the number of matches for the key exceeds the value of MaxSelectList. This property is optional; if omitted, it defaults to Too Many Matches.

UpdatedAnnouncementsPopup

The interval that browser checks for a new announcement. When a new announcement is found, it automatically shows the announcement in a popup window. The interval value is in minutes. To reduce the impact to the browser performance, it’s recommended to set this variable to the value greater than 5 (minutes).

UseDirector

Specifies when the WebDirector is controlling this web engine. The following table defines possible values:

Value

Description

No

The web engine is independent of the WebDirector. This is the default value.

Yes

The WebDirector must initiate all sessions, including the login form. If a user attempts to make a direct connection to the web engine, the web engine asks the WebDirector for a referral.

AfterLogin

The web engine refers a session to the WebDirector after authenticating a user. A web engine configured with UseDirector AfterLogin is responsible solely for authentication, and is thereby a candidate for the use of secure sockets (SSL) for maximum security.

BeforeLogin

The web engine refers a session to the WebDirector before authenticating a user. A web engine configured with UseDirectory BeforeLogin never displays a login page, and never accepts a login password.

This property is optional. If omitted, the web engine does not use the WebDirector.