This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Starting and stopping the Approval Server

The Approval Server is an ARDBC plug-in that runs in the plug-in server. By default, armonitor starts the plug-in server along with the BMC Remedy AR System server. Therefore, the Approval Server is also loaded automatically when you start the BMC Remedy AR System server.

The armonitor executable uses the armonitor.cfg (Windows) or armonitor.conf (UNIX) file to determine which services to start. Starting the plug-in server is controlled by the following line:

Windows

"$BMC_AR_SERVER_HOME$$\$arplugin.exe" $BMC_UNICODE_OPTION$ -i "$BMC_AR_SERVER_HOME$" -m

UNIX

$BMC_AR_SERVER_HOME$$/$bin$/$arplugin -s $BMC_AR_SERVER_NAME$ -i $BMC_AR_SERVER_HOME$

When the plug-in server starts, it checks the BMC Remedy AR System configuration file (ar.cfg or ar.conf ) for a list of plug-ins to load. The installation script adds one of the following entries for the Approval Server plug-in to the BMC Remedy AR System configuration file:

  • Plugin: arasj$VERSION$.jar (Windows)
  • Plugin: arapprove (UNIX)

To stop and start the Approval inside the default Java plug-in server

  1. To stop the Approval Server:
    1. Comment the Preview plugin entry in the ar.cfg file. For example:

      #Server-Plugin-Alias: ARSYS.ARDBC.PREVIEW ARSYS.ARDBC.PREVIEW vw-pun-rem-qa63.pune-labs.bmc.com:9999
    2. Comment the Preview plugin entry in the <installationFolder>\ pluginsvr \pluginsvr_config.xml file. For example:

      <!--<plugin>z
               <name>ARSYS.ARDBC.PREVIEW</name>
               <pathelement type="location">C:/Program Files/BMC Software/ARSystem/approval/bin/arasj80_build002.jar</pathelement>
               <classname>com.bmc.arsys.approval.main.ApprovalPlugin</classname>
               <pathelement type="location">C:/Program Files/BMC Software/ARSystem/arserver/api/lib/arcmnapp80_build002.jar</pathelement>
               <pathelement type="location">C:/Program Files/BMC Software/ARSystem/arserver/api/lib/arutil80_build002.jar</pathelement>
            </plugin>-->
         </plugins>
         <!--<maskingImplementation>com.bmc.arsys.approval.signal.SignalMaskForASJ</masking
      Implementation>-->
      </pluginsvr_config>
  2. To start the Approval Server, remove the comment markers from the files discussed in steps 1a and 1b.

To stop and start the Approval Server if it is running a separate plug-in

  1. To stop the Approval Server:
    1. Comment the Preview plugin entry in the ar.cfg file. For example:

      #Server-Plugin-Alias: ARSYS.ARDBC.PREVIEW ARSYS.ARDBC.PREVIEW vw-pun-rem-qa63.pune-labs.bmc.com:9999
    2. Comment the Approval Server Entry in the armonitor.cfg file. For example:

      #"C:\Program Files\Java\jre6\bin\java" -Xmx256m   -classpath "D:\Program Files\BMC Software\ARSystem\approval\bin;D:\Program Files\BMC Software\ARSystem\pluginsvr\arpluginsvr80_build002.jar;D:\Program Files\BMC Software\ARSystem\approval\bin\arasj80_build002.jar;D:\Program Files\BMC Software\ARSystem\arserver\api\lib\arcmnapp80_build002.jar;D:\Program Files\BMC Software\ARSystem\approval\bin\armaskingImpl80_build002.jar;D:\Program Files\BMC Software\ARSystem\arserver\api\lib\log4j-1.2.14.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x "IBMC-8PQF8BS" -i "D:\Program Files\BMC Software\ARSystem" -m
  2. To start the Approval Server, remove the comment markers from the files discussed in steps 1a and 1b.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Piotr Sadowski

    Hi,

    I think there are couple of mistakes. Please take a look.

    1.In example given in "Starting the plug-in server is controlled by the following line:" there are wrong environments:

    (For Microsoft Windows)

    "$BMC_AR_SERVER_HOME$/arplugin.exe" $BMC_UNICODE_OPTION$ -i "$BMC_AR_SERVER_HOME$" -m

     

    (For UNIX)

    $BMC_AR_SERVER_HOME$/bin/arplugin -s $BMC_AR_SERVER_NAME$ -i $BMC_AR_SERVER_HOME$

     

    2.In section 1a) of "To stop and start the Approval Server if it is running a separate plug-in" there should be changed port number (like  ARSystemInstallDir/Approval/bin/pluginsvr_config.xml file in section:

    <pluginsvr_config>

            <port>9800</port>)

    #Server-Plugin-Alias: ARSYS.ARDBC.PREVIEW ARSYS.ARDBC.PREVIEW serverName:9800

    3.In section 1b) of "To stop and start the Approval Server if it is running a separate plug-in" there should be correct entry in armonitor.conf - as described in Configuring BMC Remedy Approval Server with a separate plug-in server instance:

    (For Microsoft Windows)

    "C:\Program Files\Java\jre7\bin\java" -Xmx256m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -classpath "C:\Program Files\BMC Software\ARSystem\approval\bin;C:\Program Files\BMC Software\ARSystem\pluginsvr\arpluginsvr80_build001.jar;C:\Program Files\BMC Software\ARSystem\approval\bin\arasj80_build001.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arcmnapp80_build001.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\log4j-1.2.14.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x "vw-pun-rem-qa63" -i "C:\Program Files\BMC Software\ARSystem" -m

     

    (For UNIX)

    /opt/jdk6_64/jre/bin/java -Xmx256m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -classpath /data1/ar/IA/approval/bin:/data1/ar/IA/pluginsvr/arpluginsvr80_build001.jar:/data1/ar/IA/approval/bin/arasj80_build001.jar:/data1
    /ar/IA/api/lib/arcmnapp80_build001.jar:/data1/ar/IA/api/lib/log4j-1.2.14.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x premlnx02 -i /data1/ar/IA -m

    4.There should be additional point 1c) about killing the arplugin process. When armonitor find out that this process doesn't work it will restart it and reload new configuration from ar.conf and armonitor.conf

    Regards,

    Piotr

    Jan 09, 2015 08:59
  2. Kamalakannan Srinivasan

    Hello,

    Thank you for your comment. I will verify this with the concerned SME and get back to you.

    Thanks,

    Kamal

     

    Jan 12, 2015 03:48
  3. Kamalakannan Srinivasan

    Hi Piotr,

    Please note the following as per my discussion with the SME:

    First comment -  I have made the required changes.

    Second comment - The port number change is required only in case of configuring for a different plug-in server and this topic does not involve such configuration.

    Third comment - The entries are needed only while configuring ARMonitor. This topic is related to stopping and starting while running a separate plug-in.

    Fourth comment - We are dealing only with a plug-in server and ARPlugin/ARMonitor is not involved. Hence the question of killing such a process does not arise.

    Regards,

    Kamal

     

    Feb 05, 2015 12:59