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.

Restarting the plug-in server using the Set Server Info command

When any changes such as C plug-in or Java plug-in-related changes, binary updates that take place during installation, plug-in related updates to the ar.conf file, or changes to the AR System Administration:Plugin Server Configuration form are done to the C plug-in file or Java plug-in form, you are able to restart only the plug-in server instead of restarting the AR System server.

To restart the plug-in server using the Set Server Info command

  1. Double-click the driver.exe file. The file is located in the following path:
    • (Windows) <ARInstallationFolder>\Arserver\api\driver
    • (UNIX) <ARInstallationFolder>/bin


      On UNIX, set the LD_LIBRARY_PATH environment variable to the directory where the arserver.exe is located. For example, export LD_LIBRARY_PATH= opt/bmc/ARSystem/bin

  2. To initialize, enter the init command.
  3. To log on, enter the log command and provide details such as user name, password, and server name. For more information about the driver.exe commands, see Using the driver program from the command line.
  4. If you are not using the port mapper, enter the ssp (Set Server Port) command and then enter the server port number.
  5. Enter 0 or a blank for Using private socket
  6. Enter the ver command to verify the login information.
  7. Enter the ssi(Set Server Info) command and perform the following: 
    1. Enter 1 for the Number of server info operations that you want to perform.
    2. Enter 348 as the Operation number to forcefully shut down the plug-in server.
    3. Enter 2 for integer as the Datatype
    4. Enter 0 or 1 as the Integer Value.

When the AR monitor detects that the plug-in server is down, it checks if any changes are made to the ar.cfg file. If the changes are detected, the recent ar.cfg is loaded before the stopped plug-in server is automatically restarted.

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