How to restart Cloud Plug-in server without restarting Enterprise AR system?

Version 2
    Share This:

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


    PRODUCT:

    Cloud Lifecycle Management


    APPLIES TO:

    BMC Cloud Lifecycle Management



    QUESTION:

    Environment: CLM 2.1

    A few troubleshooting techniques require the Cloud Plug-in server restart (Example, Changing Super user password). As the Cloud Plug-in server is hosted on Enterprise AR system, it is not always possible to restart the Enterprise AR system. Is there a way to restart Cloud Plug-in server alone without impacting other AR applications running on Enterprise AR system?


    ANSWER:

     

    Legacy ID:KA362624

      

    Several components of Enterprise AR system are started along with the AR server startup using the armonitor file located in the AR System Install directory. Cloud Plug-in server is one of those entries in armonitor file which typically looks like the below. Killing the specific process will restart the Cloud Plug-in server. Ensure that there are no CLM specific activities on the system before executing this procedure and none of the users are accessing the Cloud Admin, end user Portals.

      

    On Windows (Default location: C:\Program Files\BMC Software\ARSystem\Conf\armonitor.cfg) and the entry for Cloud Plug-in will looks like below:

      

    "C:\Program Files\Java\jre6\bin\java" -Xmx512m  -classpath "C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Cloud_Portal\javapluginsvr;C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Cloud_Portal\plugin;C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Cloud_Portal\javapluginsvr\arpluginsvr7604_build002.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x vw-pun-cus-sp36 -i "C:\Program Files\BMC Software\ARSystem"

      

    On Linux: (Default location: /opt/bmc/ARSystem/conf/armonitor.conf or /etc/arsystem/<host name>/armonitor.conf) and the entry for Cloud Plug-in will looks like below:

      

    /opt/bmc/BMCCloudLifeCycleManagement/Cloud_Portal/javapluginsvr/loadpluginsvr.sh

      

    Use the armonitor.log to find the process ID of the above process. On Windows, there might be multiple java processes running several Plug-ins and other Applications. Please make sure to kill the java process corresponding to the Cloud Plug-in. Follow the below steps to kill the specific Java process ID which is corresponding to the Cloud Plug-In:

      

    1: Connect to the Enterprise AR machine and start the "Task Manager"
    2: Open the "View" from toolbar, click on "Column" and mark the "Command Line" check
    3: Sort the processes by "Image Name" and select the "Java" processes.
    4: Switch to the "Command Line" column and find the "C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Cloud_Portal\javapluginsvr". This will give you the exact Java process ID for Cloud Plug-In
    5: Highlight the exact Java process and click the "End Process". This will restart the Cloud Plug-In java process.
    On Linux, find the process ID of the loadpluginsvr.sh (ps -ef | grep 'loadpluginsvr') and kill it (kill -9 <PID>)
     

      
    Related Products:  
       
    1. BMC Cloud Lifecycle Management

     


    Article Number:

    000030068


    Article Type:

    FAQ/Procedural



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