Customizing an SAP daemon error log on AIX or Linux

By default, the SAP daemon error logs (SAP Callback) start when you create them. When you create an SAP Callback daemon, InfoPrint Manager creates an SAP directory (sapcbd.sysname, where sysname is the SAP application server) under /var/pd for each daemon. Use this procedure to customize the SAP error log:

Note: Any SAP daemons running on this AIX or Linux server are changed by this customization.

  1. Find the sap_error.cfg file from the /usr/lpp/pd/bin directory where the file is installed and copy it into the /var/pd directory:
    cp /usr/lpp/pd/bin/sap_error.cfg /var/pd/sap_error.cfg
    Note: If you already customize your SAP daemon error logs, remember to change the name or move the current sap_error.cfg file in /var/pd so that your customization values can be copied over into the newer version of the file.
  2. Open the copy of the sap_error.cfg file that you created and specify the settings for the log attributes that you want (as shown in Figure Sample sap_error.cfg file provided by InfoPrint Manager). For example, you can modify the log-backup-number attribute, which allows you to specify the number of backup logs that InfoPrint saves, including the initial error.log.BAK file.

    Sample sap_error.cfg file provided by InfoPrint Manager

    #
# ErrorLog Configuration File
#
# Log size (units = KBytes)
log-size = 1024
# Wrap On?
log-wrap = true
# Severity?
log-severity = debug
# Number of backup log files
log-backup-number = 10

    When you start an SAP Callback daemon after a shutdown, it backs up the first error log by creating an error.log.BAK file. With each successive restart, it creates an additional .BAK file, adding a timestamp as a fourth qualifier. By default, the log-backup-number attribute specifies a value of 10, meaning that you can have nine back up files with timestamps and the initial .BAK file. You can reduce this number as low as 1 or increase it as high as 999.

    For a complete list of the error log attributes that you can customize, see the RICOH InfoPrint Manager: Reference publication.

  3. Once you have finished defining your options, save and close the /var/pd/sap_error.cfg file.
    Note: If you do not need the customization change to take effect immediately, you can skip the final two steps and just wait until the next time the SAP daemon is restarted.
  4. From an AIX or Linux command line, you must do one of these tasks for the SAP Callback daemon to shut down so that these customization changes can take effect.
    • For the SAP Callback daemon, type stopcbd sysname (where sysname is the three-character SAP R/3 system name).
  5. To restart the SAP Callback daemons:
    From an AIX command line: 
    /etc/rc.iprsap
    All SAP daemons restart automatically if you have followed the configuration directions in Configuring to start callback daemons at system reboot on AIX.
    From Linux command line: 
    /etc/rc.iprsap
    From the InfoPrint Management Interface:
    1. Select the SAP Callback daemons you want to restart.
    2. Right-click on it and select Start.
Parent topic: Optional OMS configuration tasks