Setting security options using Server information form settings
Every BMC Remedy AR System server has a variety of configuration settings that control how the server works and how it interacts with users. Configuration settings are specific for each server.
Use the Advanced tab in the AR System Administration: Server Information form from the BMC Remedy AR System Administration Console to create settings for security. This tab also contains performance-related settings. You must be an administrator to make changes.
For more information about the BMC Remedy AR System Administration Console, see Navigating the BMC Remedy AR System Administration Console.
This form shows the local level value of the configuration. If a local value does not exist, the form displays the global level configuration. If you modify the value on this form, the local level configuration value is modified.
For example, if a configuration shows global level value and you modify the value by using this form, the local level value gets created for the configuration.
To set advanced options
- In a browser, open the AR System Administration Console, and click System > General > Server Information. The AR System Administration: Server Information form appears.
- Click the Advanced tab.
AR System Administration: Server Information form — Advanced tab
(Click to expand the image.)
Edit the options listed in the following table as needed, and click Apply.
Default Web Path
Specifies the base URL for the mid tier and is used by clients such as Flashboards. The URL appears as:
hostName is the name of the server (for example, eng.remedy.com).
contextPath is the URL context path of the AR System application registered with the servlet engine. This is set up during installation. The default value is arsys. If your company has multiple domains, use a fully qualified path name.
Maximum Depth for Hierarchical Query
For forms that contain hierarchical data, such as manager and employee relationships, specifies the maximum number of levels in the hierarchy that a recursive query retrieves. By default, the maximum is 25. Enter any integer greater than 0. See ARGetListEntryWithMultiSchemaFields.
Maximum Vendor Temp Tables
Specifies the maximum number of temporary tables that can exist on an AR System server for a single vendor form. The ARGetListEntryWithMultiSchemaFields function stores data from vendor data sources in these tables. By default, only one temporary table can exist for each vendor form. This setting applies to all vendor forms on the server. It is overridden by the value of an individual vendor form's Maximum Vendor Temp Tables property
Suppress Server Domain in URL
Suppresses the server domain in the URL. The option is clear by default.
Maximum Line Length in Email
Specifies the maximum line length that can be in an email. The default is 1024. If a single line of the message is over this length, a return is automatically inserted. Limits the line length of email messages passed through the mail server to protect users from excessively long lines.
Email Notification Web Path
Specifies the base URL that appears in email notifications. If this field is left blank, the Default Web Path is used. (The Email Notifications Web Path field is available because the Default Web Path is specified for other applications like Flashboards, and it might be different from the mid tier web path for opening requests in a notification.) If your company has multiple domains, use a fully qualified path name.
Active Link Run Process Directory
Specifies the only directory that the Run Process active link action can run from, for example, C:\arsys. If no directory is specified, active link processes can run from any directory.
Active Link Run Process Shell(UNIX servers only)
Specifies the type of shell the Run Process action can use, for example, /bin/csh. If no path is specified, administrators can specify any shell.
Enables the administrator to use the arcache utility. See arcache.exe or arcache. The option is selected by default.
Client Managed Transaction (CMT) Configuration
Maximum Concurrent Transactions
Specifies the maximum number of concurrent client-managed transactions. The default is 10, and the maximum value you can enter is 100.
Specifies the maximum time (in seconds) allowed to hold a transaction before a timeout occurs. The default is 60 seconds, and there is no maximum. If a timeout occurs, the server automatically rolls the transaction back, and the client receives an error on the next operation that uses the transaction handle.
Localized Error Messages
Enables the administrator to enable or disable localization of the server. Selected indicates that the server is localized and enabled for such tasks as searching entries in localized forms, or using AR System Message Catalog to load the message. Clients are enabled to display localized messages, but clients still have local catalogs, such as the user.dll. You must select the Localize Server check box to see localized error messages. Cleared and indicates that the server is not localized. Such tasks as searching localized forms and the localization of messages are disabled. The server does not use the AR System Message Catalog form, and messages are shown from the error catalog. The default message is displayed.
Note: If users in a different locale open a form with localized views before you select this option, you must flush the mid tier cache after setting this option to make the localized view available on the web. See Configuring the Cache Settings page.
By default, when the BMC Remedy AR System server reads a system message (type 0) from the AR System Message Catalog form, it caches the message text in memory to avoid reading the message from the database each time the message is needed. To modify this default behavior, see the "Localized-Messages-To-Cache" in Configuration settings E-M.
Catalog Form Name
Displays the name of the form the server uses to resolve error messages when "Localize Server" is selected. For more information about the AR System Message Catalog form, see Localizing messages manually.
Maximum Filters for an Operation
Specifies the number of filters that can be performed in an operation. The default and recommended number is 10000. Increase this number at your own risk only if you reach a limit in your system and you have verified that your workflow is valid.
Maximum Stack of Filters
Specifies the maximum number of nested filters and filter guides that execute to prevent recursive actions on the server. The default and recommended number is 25. Increase this number at your own risk only if you reach a limit in your system and you have verified that your workflow is valid.
Server Recording Mode
Specifies how the server records server statistics. Select one of the following options: Off, the default, do not record server statistics; Cumulative Queue, record a cumulative statistic that is a combination of all the queue statistics; and Cumulative and Individual Queue, record a cumulative statistic that is a combination of all the queue statistics as well as statistics of each queue individually. Information is recorded in the Server Statistics form, which is installed when you install AR System.
Recording Interval (seconds)
Specifies how often the server records server statistics. The default is 60 seconds. Remember that one (Cumulative Queue) or more (Cumulative and Individual Queue) entries are recorded in the Server Statistics form during each interval. If you have a short interval, many records are created. This can affect the performance of the system and the size of the database if you configure with too short an interval.
Server Group Names
If the server belongs to a server group, specifies the name of the group. All servers in the server group share this setting.
Specifies how often the server communicates with other servers in the group. Each server can register its own status, determine whether any server is delinquent, establish the parameters needed for sending signals, and determine operational responsibilities. The default value is 60 seconds, the minimum is 30 seconds, and there is no maximum. All servers in the server group share this setting, and when it is changed, all the AR System servers in the group must be restarted.
Preference Server Option
Specifies where user preferences are read from. The options are User Defined, where users can choose whether to use a preference server, and this server might or might not be used depending on whether the Centralized Preference forms are defined; Use This Server, where users must use a preference server, and this server is an available preference server; Use Other Server, where users must use a preference server, and this server is not available as a preference server. See Establishing a mandatory preference server.
Preload Tables Configuration
Preload Tables At Init Only
If the number of preload threads is not zero, specifies whether the threads are used only at server startup or for all cache reloads from the database. See Setting the Preload Tables Configuration option. The values are Yes, if preload threads are configured (use them only at server startup) and No. If preload threads are configured, always use them when loading the cache from the database.
Number of Preload Threads
Specifies the number of preload threads used when information is loaded from the database into the server cache. The maximum value is 30 or twice the number of preload segments, whichever is lower. The server might reduce the number of threads at runtime if it determines that threads would be started with no work to do. If this field is set to 0, the Preload Tables Configuration option is off.
Number of Preload Segments
Specifies the total number of preload segments handled by the preload threads. Vary this setting to balance the load between preload threads and to optimize cache load time. A good initial setting for this option is 1/3 the number of schemas (forms) in the AR System server. See Setting the Preload Tables Configuration option.