This documentation supports the 20.08 version of Remedy Action Request System, which is available only to BMC Helix subscribers (SaaS).
To view an earlier version, select the version from the Product version menu.


Configuring server settings for BMC Remedy Approval Server logging and loopback calls

The AP:Admin-ServerSettings form contains settings for generating the BMC Remedy Approval Server log file, setting the definition check interval, and configuring RPC and Loopback sockets.

To configure the server settings

(Click on the image to expand it)

  1. In a browser, open the AP:Administration form, and click the Server Settings link in the navigation pane.
  2. On the AP:Admin-ServerSettings form, open the Basic tab.
  3. To generate a log of the approval server activity, check Approval Debug Mode.
  4. In the Log File Name field, type the full path to the debug log file.
    See Approval Server debug log.
  5. Specify the Approval Debug Type for the type of logging level for the approval logs. See BMC Remedy Approval Server logging.

    Note

    The approval logs are not generated by default, you should select the Approval Debug Mode checkbox to turn on the logging. 

  6. In the Definition Check Interval field, accept the default (300), or enter a new value.
    The Definition Check Interval is the number of seconds after which the approval server checks for changes to process definitions.
    • A larger number can improve BMC Remedy AR System performance.
    • A smaller number is useful while creating and testing a process.
    • A zero (0) in this field causes immediate implementation of a definition.
  7. To cause the approval server to use a dedicated private queue when it makes calls to the BMC Remedy AR System server, enter an RPC port number in the Private AR Server RPC Socket field.
    Select an available RPC port number from the valid ranges. See Private queues for loopback calls.
    Leave this field empty if your BMC Remedy Approval Server implementation does not use a dedicated queue for loopback calls to the BMC Remedy AR System server.
  8. To cause the approval server to use the plug-in loopback RPC socket for loopback calls (as required for the preview feature), enter the loopback queue RPC port number in the Plugin Loopback RPC Socket field. Use an RPC port number from the ranges given in Private queues for loopback calls..
    Leave this field empty if your plug-in server does not use a dedicated loopback RPC port. See Plugin Loopback RPC Socket.
  9. Specify the Due-Soon Interval in Hours or Days for approval requests to be highlighted when an approver logs in to Approval Central.
  10. Specify the Recent History Interval in Hours or Days for approval requests to be displayed in the My Approval History section of Approval Central for an approver.
  11. Specify the Thread Count for the number of threads that will process various approval requests.
  12. Specify the Rejected By Others Interval for duration within which a user can see all the his/her requests which were rejected by others. Select the unit of measurement (Days or Months) using the adjacent drop-down list.
  13. Click Save to save your changes.
  14. If you set a value for the Private AR Server RPC Socket or Plugin Loopback RPC Socket field, restart the BMC Remedy AR System server.
Was this page helpful? Yes No Submitting... Thank you

Comments