This documentation supports the 9.1 version of Remedy Action Request System.

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

Using the C plug-in server for dynamic plug-in loading

Plug-ins are configured in the ar.cfg file. A new plug-in is added to the plug-in server through the AR System server. Previously, adding a new plug-in definition required that you stop and restart the AR System server. An API interface in the plug-in server can add the new plug-in definitions dynamically, without stopping and restarting the AR System server.

See the plug-in server configuration file (ar.cfg or ar.conf).

To add the plug-in information to the C plug-in server configuration file

  1. Double-click the driver.exe file.
    The default location of this file is C:\Program Files\BMC Software\ARSystem\Arserver\api\driver.
  2. Enter the required login and server information.
  3. Enter the gsi (Get Server Info) command to get the current plug-in information.
  4. Enter the following details:
    • Number of server info operations--The number of servers for which you want the current plug-in information.
    • Operation--The operation number for getting the current plug-in information that is present in the ar.cfg file.
      A list of current plug-ins is displayed.
  5. Enter the ssi(Set Server Info) command to add the new plug-ins.


    If you enter the ssi command without entering the gsi command first, the old plug-in entries are overwritten and only the new entries are recorded.

  6. Enter the following details:
    • Number of server info operations--The number of servers for which the new plug-ins are to be added.
    • Operation--The operation number for adding the new plug-ins.
    • Datatype--The number for the type of data.
      A list of new plug-ins that are added is displayed. The value for the ReturnCode must be OK.

      The plug-in information is now updated in the ar.cfg file.
Was this page helpful? Yes No Submitting... Thank you