How to migrate TIBCO Hawk ActiveMatrix Plug-in ("HKAM") after upgrading TIBCO ActiveMatrix ("AMX") enterprise to version 3.3.0 .

How to migrate TIBCO Hawk ActiveMatrix Plug-in ("HKAM") after upgrading TIBCO ActiveMatrix ("AMX") enterprise to version 3.3.0 .

book

Article ID: KB0093187

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix Service Grid -
TIBCO ActiveMatrix Service Bus -
TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) -

Description

Description:
After upgrading TIBCO ActiveMatrix ("AMX") enterprise to 3.3.0 version, the AMX microagent may have a problem being loaded in the Hawkagent because the old version hkam 1.1.0 or 1.2.0 is not compatible with AMX 3.3.0.

Issue/Introduction

How to migrate TIBCO Hawk ActiveMatrix Plug-in ("HKAM") after upgrading TIBCO ActiveMatrix ("AMX") enterprise to version 3.3.0 .

Resolution

The compatible version of HKAM is bundled with AMX 3.3.0. Follow the instructions to re-configure HKAM in the AMX HTTP document->Hawk Configuration->Chapter 2 Configurations->Configuration Instructions
https://docs.tibco.com/pub/activematrix_service_grid/3.3.0_september_2013/doc/html/wwhelp/wwhimpl/js/html/wwhelp.htm

For customized variables in hawkagent, the old variable file can be merged with CONFIG_HOME/hkam/<host_instance_name>/data/Hawk-amx_variables.properties .

For customized plugins in hawkagent, the old hma files and jar files can be copied into CONFIG_HOME/hkam/<host_instance_name>/plugin. Please make sure the URLs in hma files have been corrected.

FOr customized rulebases in hawkagent, the old rulebase files can be copied into CONFIG_HOME/hkam/<host_instance_name>/rulebases.