Configuring Distributed Server Option logging

You can configure logging for  that have a license for .

To configure  logging

1. Open the AR System Administration: Server Information form for the local , and click the Log Files tab.
   (Click on the image to expand it.)
   
2. Select DSO Log.

3. In the Log Level list, select one of these options:
4. (Optional) In the Name field, enter a path and file name for the  log files.
    If you leave this field empty,  uses the default file names (see Distributed-Server-Option-logging) 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  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 .
    For information about the other options on the Log Files tab, see Setting-log-files-options.
7. (Optional) Add the following entries to the  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  log files.
   • DSO-Log-Max-Backup-Index: maxIndexNum
      This entry specifies the maximum number of  log backup files to save on your system. If you do not set it, the default is 5.
      See Backing-up-Distributed-Server-Option-log-files.
8. (Optional) To prevent ARERR 302 from being logged during distributed deletes:
   (Click on the image to expand it.)
   
   
   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 .
       See Logging-the-ARERR-302-error-during-distributed-deletes.

9. If you added or changed the value of either configuration file entry in step 7, restart the .

   Note

   For information about logging failed pending distributed operations, see Monitoring-and-managing-pending-distributed-operations.