changeMonitoringConfig

The changeMonitoringConfig method provides an option to change monitoring configuration.

You can change rolling window length, statistics gathering interval (bucket size), notification interval, and isPartialWindow. This modification overrides configuration details provided by monitoring application and reset after monitoring application restart.

Type

Synchronous, IMPACT_ACTION.

Arguments

Name Type Description
Rolling Window Length (in seconds) Long Select the rolling window length in seconds.

Possible values are: 60, 120, 180, 240, 300.

Statistics Gathering Interval (in seconds) Long Selects statistics gathering interval time in seconds.

The contents of the list box are: 5, 10, 15, 20, 30, 40, 50, 60.

Notification Interval (in seconds) Long Selects the notification interval in seconds.

The contents of the list box are: 10, 15, 20, 30, 40, 50, 60.

Is Partial Window Boolean Select true or false for the sliding window statistics include the current working bucket?

Possible values are: true, false.

Returns

None.

Troubleshooting following issue:

Issue HKAM-441:
After the successful upgrade from AMX330 HF27 to AMX342, on Hawk Console, invoking method changeMonitoringConfig() for microagents fails with the following error.

"class java.lang.Integer cannot be cast to class java.lang.Long (java.lang.Integer and java.lang.Long are in module java.base of loader 'bootstrap')"

Workaround:

We have seen this issue (Method invocation failed for changeMonitoringConfig() method) in our upgraded setup and to solve this we need to follow below steps in our upgraded Config home.

Note: If you upgraded from any of the HF of 330 to AMX 342 Setup, then you have to follow some additional steps from Step A to Step G before Step 1 if not then you can skip Step A to G and directly follow from

Step 1.

  1. Go to below location: <TIBCO_HOME>\amx\3.4\hkam\scripts

  2. Under this folder copy below files:
    1. configure-hkam

    2. configure-hkam.bat

    3. configure-hkam-3.4.2.xml

  3. Go to below location and paste the copied file.

    <TIBCO_HOME><TIBCO_CONFIG>\hkam\Admin-amxadmin-instanceOne\script

    Note: You will see this 3 file already exist in this folder , so you have to simply replace this 3 file with existing one.
  4. Open configure-hkam file in notepadd++ and change the configure-hkam-<OLD_SETUP_VERSION>.xml to configure-hkam-3.4.2.xml

    Example:

    $JAVA_HOME/bin/java -cp $ANT_JAR org.apache.tools.ant.launch.Launcher -f ${SETUP_HOME}/configure-hkam-3.4.2.xml

  5. Open configure-hkam.bat file in notepadd++ and update below 3 line.

    Note: For JAVA_HOME , Provide back slash as shown below and for ANT_JAR, give forward slash

    Example:
    set JAVA_HOME=<TIBCO_HOME>\tibcojre64\11

    set ANT_JAR=<TIBCO_HOME>/tools/lib/antpackage.jar

    "%JAVA_HOME%\bin\java" -cp "%ANT_JAR%" org.apache.tools.ant.launch.Launcher -f "%SETUP_HOME%configure-hkam-3.4.2.xml"

  6. Go to the below location and open this file hawkamxhpa-Admin-amxadmin-instanceOne.hma and uncomment the classpasth code block which is commented before.

    <TIBCO_HOME>\<TIBCO_CONFIG>\hkam\Admin-amxadmin-instanceOne\plugin

  7. Open CMD and go to below location and run this command called, configure-hkam.bat , After successful run, you will get Build successful message.

    <TIBCO_HOME>\<TIBCO_CONFIG>\hkam\Admin-amxadmin-instanceOne\scripts

Additional Steps END for 330HF

  1. After successful upgrade to AMX 342 on top of your existing setup, go to below Location and open below File for all Host Instance.
    <TIBCO_HOME>/<CONFIG_HOME>/hkam/<All_Instance_Name>/plugin/hawkamxhpa-<All_Instance_Name>.hma file

  2. Replace the existing classpath code block with below code block of your hawkamxhpa-<All_Instance_Name>.hma file.

    Note: If you see the <classpath> code block of your file and below <classpath> code block, You will see the difference in AMX plugin version (here highlighted version in bold), the below version are AMX 342 version. which we have to give to fix this issue as shown below.
    <classpath>
    <path><TIBCO_HOME>/components/shared/1.0.0/plugins/com.tibco.hawk.microagent.amx.common_1.4.200.002.jar</path>
    <path><TIBCO_HOME>/components/shared/1.0.0/plugins/com.tibco.hawk.microagent.amx.hpa_1.4.200.002.jar</path>
    <path><TIBCO_HOME>/components/shared/1.0.0/plugins/com.tibco.hawk.microagent.amx.service_1.4.200.003.jar</path>
    <path><TIBCO_HOME>/components/shared/1.0.0/plugins/com.tibco.tpcl.javax.system.exports_5.0.500.002/xml-apis.jar</path>
    <path><TIBCO_HOME>/components/shared/1.0.0/plugins/com.tibco.tpcl.org.apache.harmony.asn1_5.0.200.002-M15/harmony-asn1.jar</path>
    </classpath>
  3. After successfully replacing the classpath block.

  4. Restart the TibcoHost.

  5. Start Hawk Console, Hawk Agent and HawkHma.

  6. Go to Hawk Console and select Node microagent and invoke changeMonitoringConfig() method.

  7. Successfull message popup window will be displayed.