This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

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

Assignment Engine logs

If you are running BMC Remedy AR System applications (such as ITSM or CSS or any application that uses the Assignment Engine component), when the BMC Remedy AR System server is restarted, the server searches for specific tags in the Application Configuration forms. Consequently, you might see warnings in the ARerror.log file. For example:


Sun Mar 12 13:03:45 2006  AssignEng : No schema was found for tag (ARAPPWARN 4831)
Sun Mar 12 13:03:45 2006     SHR Tag: ApplicationProperties;



These warnings are normal and always occur when you restart the server. You can ignore them.

Assignment log files can help you identify functionality issues that might be encountered because the rules are not set up correctly or the processes are not configured correctly. The logs track how the Assignment Engine handled an application command.

To set Assignment Engine trace logs (aetrace.log and ae.log), set the following parameters in the ar.cfg (ar.conf) file:

  • AE-LOG:ON
  • AE-TRACE:ON
  • AE-TRACE-FILE:<log file path>/aetrace.log
  • AE-LOG-FILE:<log file path>/ae.log

For information about enabling assignment engine logging, see Configuring the Assignment Engine.

If you call BMC Support, have a copy of this log available for faster resolution. (Logging is set to ON by default.)

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments