How to perform a Checklist for Approval Server configuration

Version 5
    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:

    8.x, 9.x, 18.x, 19.x



    QUESTION:

    How to perform a Checklist for Approval Server configuration?
     


    ANSWER:

    1.-Validate if your approval server is configure to run on the plugin server or on a separate plugin
     
    Steps to validate if Approval Server runs on plugin server port 9999:

    ar.conf
    Server-Plugin-Alias: ARSYS.ARDBC.PREVIEW ARSYS.ARDBC.PREVIEW {servername/FQDN}:9999
    Approval-Server-Suspended: F (On to rank 1 approval server)
    Approval-Server-Suspended: T (On to all other servers)
    Approval-RPC-Socket: 390680

    ARSystemInstallDir/pluginsvr/pluginsvr_config.xml
    <plugin>
    <name>ARSYS.ARDBC.PREVIEW</name>
    <classname>com.bmc.arsys.approval.main.ApprovalPlugin</classname>
    <filename>/opt/bmc/ARSystem/approval/bin/arasj91_build002.jar</filename>
    <pathelement type="path">UPGRADE</pathelement>
    <pathelement type="location">/opt/bmc/ARSystem/approval/bin/arasj91_build002.jar</pathelement>
    <pathelement type="location">/opt/bmc/ARSystem/arserver/api/lib/arcmnapp91_build002.jar</pathelement>
    <pathelement type="location">/opt/bmc/ARSystem/arserver/api/lib/arutil91_build002.jar</pathelement>
    </plugin>

    Note: The configuration of the plugin ARSYS.ARDBC.PREVIEW from the ARSystemInstallDir/approval/bin/pluginsvr_config.xml should be commented or removed if you are using the configuration from ARSystemInstallDir/pluginsvr/pluginsvr_config.xml

    Armonitor.conf
    Plugin-server-line:
    ${BMC_JAVA_HOME}/java -Xmx1024m -classpath /opt/bmc/ARSystem/pluginsvr:/opt/bmc/ARSystem/pluginsvr/arpluginsvr91_build003.jar:/opt/bmc/ARSystem/api/lib/arcmnapp91_build003.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x server-name -i /opt/bmc/ARSystem
    Separate-Approval-server-line
    #/usr/java/jre1.8.0_73/bin/java -Xmx256m -classpath /opt/bmc/ARSystem/approval/bin:/opt/bmc/ARSystem/pluginsvr/arpluginsvr91_build003.jar:/opt/bmc/ARSystem/approval/bin/arasj91_build003.jar:/opt/bmc/ARSystem/api/lib/arcmnapp91_build003.jar:/opt/bmc/ARSystem/api/lib/log4j-1.2.14.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x server-name -i /opt/bmc/ARSystem -m
     
    Steps to validate if Approval Server runs on a separate plugin port 9800:

    ar.conf
    Server-Plugin-Alias: ARSYS.ARDBC.PREVIEW ARSYS.ARDBC.PREVIEW {servername/FQDN}:9800
    Approval-Server-Suspended: F (On to rank 1 approval server)
    Approval-Server-Suspended: T (On to all other servers)
    Approval-RPC-Socket: 390680

    ARSystemInstallDir/approval/bin/pluginsvr_config.xml
    <plugin>
    <name>ARSYS.ARDBC.PREVIEW</name>
    <classname>com.bmc.arsys.approval.main.ApprovalPlugin</classname>
    <filename>/opt/bmc/ARSystem/approval/bin/arasj91_build002.jar</filename>
    <pathelement type="path">UPGRADE</pathelement>
    <pathelement type="location">/opt/bmc/ARSystem/approval/bin/arasj91_build002.jar</pathelement>
    <pathelement type="location">/opt/bmc/ARSystem/arserver/api/lib/arcmnapp91_build002.jar</pathelement>
    <pathelement type="location">/opt/bmc/ARSystem/arserver/api/lib/arutil91_build002.jar</pathelement>
    </plugin>

    Note: The configuration of the plugin ARSYS.ARDBC.PREVIEW from the ARSystemInstallDir/pluginsvr/pluginsvr_config.xml  should be commented or removed if you are using the configuration from ARSystemInstallDir/approval/bin/pluginsvr_config.xml

    Armonitor.conf
    Plugin-server-line:
    ${BMC_JAVA_HOME}/java -Xmx1024m -classpath /opt/bmc/ARSystem/pluginsvr:/opt/bmc/ARSystem/pluginsvr/arpluginsvr91_build003.jar:/opt/bmc/ARSystem/api/lib/arcmnapp91_build003.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x server-name -i /opt/bmc/ARSystem
    Separate-Approval-server-line
    /usr/java/jre1.8.0_73/bin/java -Xmx256m -classpath /opt/bmc/ARSystem/approval/bin:/opt/bmc/ARSystem/pluginsvr/arpluginsvr91_build003.jar:/opt/bmc/ARSystem/approval/bin/arasj91_build003.jar:/opt/bmc/ARSystem/api/lib/arcmnapp91_build003.jar:/opt/bmc/ARSystem/api/lib/log4j-1.2.14.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x server-name -i /opt/bmc/ARSystem -m

    Note: The Approval server is configured to run on the plugin server OOTB
    Note II: Avoid to have approval server running on plugin server and on a separate plugin at the same time this is going to create a conflict and approval server could not work or could process approvals twice.


    2.-Check Approval server configuration on Remedy Console Plugin server configuration
    Administration console > System > General > Plugin server configuration > Plugin Server Instance could be server-name + 9999 or server-name + 9800 it depends of the configuration that you are using

    Approval Server Preview Plugin

    Note: The configuration of the plugin from the picture of the step 2 should match with the configuration of the pluginsvr_config.xml

    3.-Check Approval Server Configuration on Remedy Console Centralized Configuration
    Administration console > System > General > Centralized Configuration > com.bmc.arsys.approval

    Central Config

    3.1.-All the following options should be in your centralized configuration under com.bmc.arsys.approval if you have a missing setting you can add it manually

    Central Config 2

     4.-Validate if the approval server runs with the plugin logs in debug mode, the below document shows how to enable plugin server on port 9999 in debug mode if you want to enable the logs for the separate plugin you only need to select the port 9800 instead. 
    Remedy - Server - v.9.x How to enable DEBUG Java Plugin Server Logging in AR System in the arjavaplugin.log file

    4.1.-The Approval Server on plugin server port 9999 should generate a file called arjavaplugin.log
    4.2.-The Approval Server on a separate plugin port 9800 should generate a file called approvalplugin.log
    4.3.-To validate if the approval plugin is working you should be the next line on the arjavaplugin.log or approvalplugin.log: <ARSYS.ARDBC.PREVIEW>Approval Plugin is already loaded

    5.-Test Approval Server, you can follow the next article to make a basic test and validate if the approval server is working
    Remedy - Approval - How to test Approval Server is working fine or not.

    For more details how to configure 'Approval Server' works the online documentation can be referenced with the following link:
    Approval Server concepts
    Configuring BMC Remedy Approval Server with a separate plug-in server instance
    Remedy - Approval - How to enable the Approval log and set the logging in DEBUG mode
     

    NOTE: This article is also available in Spanish, use the link below or search by Article Number 000166045. / NOTA: Este artículo también est disponible en Español, usar el siguiente enlace o buscar por el Número de Artículo 000166045.

      

    Cómo realizar un checklist de la configuración del servidor de aprobaciones

     


    Article Number:

    000165982


    Article Type:

    FAQ/Procedural



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