Remedy - Server - How to restart the Java Plugin Server (Unix/Linux/Windows)

Version 10
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    Remedy AR System Server


    APPLIES TO:

    BMC Remedy AR System Server v8.x, v9.x



    QUESTION:

    The main Java Plugin server command process is located in either:   
        
    • C:\Program Files\BMC Software\ARSystem\Conf\armonitor.cfg (for Windows)
    •  
       
        
    • /etc/arsystem/[serverName]/armonitor.conf (for Linux)
    •  

    When AR System starts it will start all the processes listed in the armonitor.cfg/armonitor.conf.

    In certain scenarios, like after having set the Remedy Java Plugin Server in Debug mode (8.x only), we will need to stop and restart the Java process running the main Remedy Java Plugin server.
    Note: In 9.x, changing the Plugin Server Log Level no longer requires a Java Plugin Server restart


    ANSWER:

     

    Legacy ID:KA312905

      
      The below steps will show how to restart the Java Plugin server for:
    1- Unix/Linux.
    2- Windows.

    1- Unix/Linux
    1- Locate the armonitor.conf file (usually at
      /etc/arsystem/[serverName]/armonitor.conf)  
     
      2- Check the entry for the main Java Plugin server. This will be the java command line which is for the ARPluginServerMain
    Example:
    ......
    /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/bin/java -Xmx512m -classpath /opt/bmc/ARSystem/pluginsvr:/opt/bmc/ARSystem/pluginsvr/arpluginsvr90_build001.jar:/opt/bmc/ARSystem/approval/bin/armaskingImpl90_build001.jar:/opt/bmc/ARSystem/api/lib/arcmnapp90_build001.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR Server Name} -i /opt/bmc/ARSystem
    ......

    3- Locate the same java process running in the Unix/Linux box. This can be done doing the following:
        a) Type in the Shell:
              ps -ef|grep java|grep ServerMain
        b) The result will be the running java process belonging to the main Remedy Java Plugin server.
              Example:
                 # ps -ef|grep java|grep ServerMain
                 root     28497 27322  0 Jun15 ?        02:52:19 ./java -Xmx512m -classpath          
                 /opt/bmc/ARSystem/pluginsvr:/opt/bmc/ARSystem/pluginsvr/arpluginsvr90_build001.jar:/opt/bmc/ARSystem/approval/bin/armaskingImpl90_build001.jar:/opt/bmc/ARSystem/api/lib/arcmnapp90_build001.jar
                 com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR Server Name} -i /opt/bmc/ARSystem
                 #


    4- To kill the process use the KILL command against the Java Plugin Server PID:
              Example (following the above):
              kill -9 28497

    5- The Java process will be restarted right away by AR Armonitor. We can check if the related Java process is running by typing again:
              ps -ef|grep java|grep ServerMain

    6- The running Remedy Java Plugin server process will be displayed this time having a different PID which is as expected.
              Example:
                 # ps -ef|grep java|grep ServerMain
                 root     12528 11317  0 Jun15 ?        02:52:19 ./java -Xmx512m -classpath          
                 /opt/bmc/ARSystem/pluginsvr:/opt/bmc/ARSystem/pluginsvr/arpluginsvr90_build001.jar:/opt/bmc/ARSystem/approval/bin/armaskingImpl90_build001.jar:/opt/bmc/ARSystem/api/lib/arcmnapp90_build001.jar
                 com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR Server Name} -i /opt/bmc/ARSystem
                 #

    7- The Remedy Java Plugin server has now been restarted.


    2- Windows
    1- Locate the armonitor.cfg file (usually at
      C:\Program Files\BMC Software\ARSystem\Conf)  
     
      2- Check the entry for the main Java Plugin server. This will be the java command line which is for the ARPluginServerMain
              Example:
                  "....\Java\jre7\bin\java" -Xmx512m -classpath "....\BMC Software\ARSystem\pluginsvr;....\BMC Software\ARSystem\pluginsvr\arpluginsvr91_build001.jar;.....\BMC
                 Software\ARSystem\approval\bin\armaskingImpl91_build001.jar;.....\BMC Software\ARSystem\arserver\api\lib\arcmnapp91_build001.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR Server Name} -i
                  ".....\BMC Software\ARSystem" –m


    3- To identify which java process in the Windows Task Manager belongs to this process mentioned above, the best way is to set the Task Manager Console this way:
              In the Task Manager > View > Select Columns…

              User-added image

    4- Select the columns PID and Command Line

              User-added image

              User-added image
    And press OK

    5- Now we check and look the armonitor.cfg line for the main Java Plugin server and in the Task Manager’s Command Line column to identify it.

              User-added image

    6- Once identified, note down the PID, for this example is 2432.

    7- Right click on it and terminate the process.

    8- The armonittor.exe will start the java process again under a different PID  as per the below scr.


              User-added image
    The arjavaplugin.log file will also be updated. This is located at:
      
       
    • C:\Program Files\BMC Software\ARSystem\Arserver\Db\arjavaplugin.log for Windows, or
    •  
    • /opt/bmc/ARSystem/db/arjavaplugin.log for Linux
      
     
     
     
     
     
     
     
     
     
     
     
      

     


    Article Number:

    000014935


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles