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.

Configuring BMC Remedy Distributed Server Option logging

You can configure logging for BMC Remedy AR System servers that have a license for BMC Remedy Distributed Server Option.

To configure DSO logging

  1. Open the AR System Administration: Server Information form for the local BMC Remedy AR System server, and click the Log Files tab.
  2. Select DSO Log.
  3. In the Log Level list, select one of these options:

    Option

    Description

    Error

    Logs only errors. Depending on the processing stage, this option includes information about the pending distributed operation, mapping, mapping qualifier (if any), and target server RPC or TCP/IP setting to put the errors in context.

    Warning

    Logs errors and warnings. Depending on the processing stage, this option includes information about the pending distributed operation, mapping, mapping qualifier (if any), and target server RPC or TCP/IP setting to put the errors and warnings in context.

    Info

    Logs errors, warnings, and other information to provide a step-by-step record of BMC Remedy Distributed Server Option activities.

  4. (Optional) In the Name field, enter a path and file name for the BMC Remedy Distributed Server Option log files.
    If you leave this field empty, BMC Remedy AR System uses the default file names (see BMC Remedy Distributed Server Option log files) and adds the log files to the following directories:
    • (UNIX) ARSystemServerInstallDir/db/
    • (Windows) ARSystemServerInstallDir\Arserver\Db

      Important

      When naming log files, do not use special characters, such as a colon ( : ) , forward slash ( / ) , or question mark ( ? ) . Use only alphanumeric characters.

  5. (Optional) In the Maximum Log-File Size field, specify a maximum log size. By default, the maximum size of BMC Remedy Distributed Server Option logs is 10 MB. See Backing up BMC Remedy Distributed Server Option log files.
  6. Click OK or Apply.
    Your changes take effect immediately. You do not have to restart the BMC Remedy AR System server.
    For information about the other options on the Log Files tab, see Setting log files options .
  7. (Optional) Add the following entries to the BMC Remedy AR System server configuration file (ar.cfg on Windows or ar.conf on UNIX):
    • Log-DSO-Field-Values: T
      If you set the log level to Error or Warning, add this entry to include a list of source entry field/value pairs for errors and warnings in the BMC Remedy Distributed Server Option log files.
    • DSO-Log-Max-Backup-Index: maxIndexNum
      This entry specifies the maximum number of BMC Remedy Distributed Server Option log backup files to save on your system. If you do not set it, the default is 5.
      See Backing up BMC Remedy Distributed Server Option log files.
  8. (Optional) To prevent ARERR 302 from being logged during distributed deletes:
    1. Click the DSO tab.
    2. Select Suppress No Such Entry Error for Distributed Delete.
    3. Click Apply.
      Your change takes effect immediately. You do not have to restart the BMC Remedy AR System server.
      See Logging the ARERR 302 error during distributed deletes.
  9. If you added or changed the value of either configuration file entry in step 8, restart the BMC Remedy AR System server.

    Note

    For information about logging failed pending distributed operations, see Logging failed pending items.

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

Comments