Configuration using PCM rules pconfig

BMC PATROL for JBoss Application Server supports configuration of the KM without the usage of PATROL Console. This can be performed using PCM. 

The KM installation contains a rule set file for PCM. The rule set file path file is:$PATROL_HOME/rulesets/Shipped/pjb/3_2_00/pjb_ruleSet.cfg 

This file is installed either during custom install of the KM or when it is installed on a host where PCM already exists. The rule set file contains configuration rules required to configure a JBoss environment and to enable options for debug reporting.

Note

Some of the values used within PCM are encrypted values and not plain text. For more information on Agent configuration, please refer to the PCM user guide. PATROL Agent can be configured using PATROL tools or BPPM CMA but not both in parallel.

 You can add environments using PCM pconfig, using the following template: 

Code Bolck
PATROL_CONFIG
"/PJB/Default/logLevel" = {
REPLACE = "<<INFO|DEBUG>>"
},
"/PJB/Default/JBossEnvList" = {
REPLACE = "<<each jboss environment name you add should be on this list, \n is the seperator>>"
},
"/PJB/JBoss/<<environment name>>/hostName" = {
REPLACE = "<<hostname or IP of the system on which JBoss server is running>>"
},
"/PJB/JBoss/<<environment name>>/localUser" = {
REPLACE = "<<Local OS account with read and execute permissions on the directory of $WL_HOME>>"
},
"/PJB/JBoss/<<environment name>>/runtimeList" = {
REPLACE = "11,12,13,14,15,16,17,18,19,20,22,23,24,25,26,27,28,29,30,31,32,33,34,35,35.1,35.2,50"
},
"/PJB/JBoss/<<environment name>>/port" = {
REPLACE = "<<Monitored jboss port to connect with>>"
},
"/PJB/JBoss/<<environment name>>/jbossHome" = {
REPLACE = "<<jboss local home location>>"
},
"/PJB/JBoss/<<environment name>>/javaHome" = {
REPLACE = "<<java home location - by default this set to the java coming with the PAtrol Agent>>"
},
"/PJB/JBoss/<<environment name>>/userName" = {
REPLACE = "<<JBoss Global Security account>>"
},
"/PJB/JBoss/<<environment name>>/trustStoreFile" = {
REPLACE = "<<This is for secure ssl connection, the trust file should be supply>>"
},
"/SecureStore/PJB_MAIN/<<environment name>>_trustStoreFile_Pass" = {
REPLACE = "PJB_MAIN;PJB_ENVIRONMENT/<<Password of the trust file>>"
},
"/PJB/JBoss/<<environment name>>/isTrustStorePassChange" = {
REPLACE = "<<when using secure SSL connection, if the trust file password change set this value to 1>>"
},
"/PJB/JBoss/<<environment name>>/keystoreFileName" = {
REPLACE = "<<This is for secure 2 way ssl ,the key store file should be supply>>"
},
"/SecureStore/PJB_MAIN/<<environment name>>_keystoreFileName_Pass" = {
REPLACE = "PJB_MAIN;PJB_ENVIRONMENT/<<Password of the keystore file>>"
},
"/PJB/JBoss/<<environment name>>/isKeystorePasswordChange" = {
REPLACE = "<<This is for secure 2 way ssl, if the key store file password change set this value to 1>>"
},
"/PJB/JBoss/<<environment name>>/jvmArgs" = {
REPLACE = "<<optinal- JVM args for the java collector>>"
},
"/PJB/JBoss/<<environment name>>/javaDebugLevel" = {
REPLACE = "<<3 = Info (default), 4 = Fine , 5 = Finest>>"
},
"/PJB/JBoss/<<environment name>>/disableInstance" = {
REPLACE = "<<optinal -  this will disable the creation of the instance on the patrol tree view>>"
},
"/PJB/JBoss/<<environment name>>/BPPMI2D" = {
REPLACE = "<<optinal -  when set to false this will disable the creation of the instance on the patrol tree view>>"
},
"/PJB/JBoss/<<environment name>>/diagReport" = {
REPLACE = "<<optinal -  this will generate diagnostic report for support>>"
},
"/SecureStore/PJB_MAIN/<<environment name>>_Pass" = {
REPLACE = "PJB_MAIN;PJB_ENVIRONMENT/<<JBoss Global Security password>>"
},
"/PJB/JBoss/<<environment name>>/isPasswordChange" = {
REPLACE = "1"
},
"/SecureStore/PJB_MAIN/<<environment name>>_localPassword_Pass" = {
REPLACE = "PJB_MAIN;PJB_ENVIRONMENT/<<Password of local OS account>>"
},
"/PJB/JBoss/<<environment name>>/isLocalPasswordChange" = {
REPLACE = "1"
}

Note

When PATROL Agent is reporting data in BPPM, the JBoss Application Server nodes are shown as devices on the BPPM UI. This is called "instance to device mapping". In some cases, you might want to disable this feature to display all instances and parameters of the KM under the device in the Configured Patrol Agent. To disable "instance to device mapping" for a given installation of Patrol Agent and KM, you must apply the following PCM rule: /PJB/Default/BPPMI2D " = { REPLACE = "false" },

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*