This documentation supports the 18.08 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Configuring the Assignment Engine server settings

You can use the AR System Assignment Engine: Server Settings form to enable the Assignment Engine logs and configure the logging settings.

Best Practice

BMC recommends using the Remedy Management Console to manage the Assignment Engine server settings. For more information, see Managing AR Server Group components by using global and local level configurations.

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.


AR System Assignment Engine: Server Settings form 

To configure the AR System Assignment Engine: Server Settings form, navigate to BMC Remedy AR System Administration Console > Quick Links > Assignment Engine Administration > Sever Settings

Important

Note the following points when modifying the form:

  • The Max Back-up Index value defines the maximum number of backup (.bak) log files that can be created when the log file reaches the Max Log File Size value and a new log file is created.
  • If you modify the Number of Threads value, you must restart the server to apply changes.
  • AE-RPC-Socket setting is now obsolete and cannot be modified using the ar.cfg file or AR System Configuration Generic UI form.
  • You cannot modify the Assignment Engine logging settings using the ar.cfg file. 

 The following Assignment Engine settings are modified by using the AR System Configuration Generic UI form. Do not use the ar.cfg file to modify the following configuration settings:

  • AE-Trace
  • AE-Trace-File
  • AE-Log
  • AE-Log-File
  • AE-Worker-Thread

Assignment Engine log file format

The format of the Assignment Engine log files is consistent with the AR System server log files. The actual content may vary according to Assignment Engine logging needs. The following sample shows an Assignment Engine log file entry:

<ASSN> <TID:0000000314> <USER: Remedy Application Service> 
<Overlay-Group: 0> /* Mon Aug 25 2014 14:59:13.2000 */
INFO Main Thread is waiting for Cache to be built for the first time.

For more information, see Assignment Engine logs.

To check whether the Assignment Engine logging is enabled, verify the value of the com.bmc.arsys.assignment setting. For more information, see Configuration settings A-B

Was this page helpful? Yes No Submitting... Thank you

Comments