CLI scripts used to update the messaging configuration fail for some of environments after upgrading to AMX 3.2.0 with the error message, "Parent Component does not exist, cannot perform action on child Component".
book
Article ID: KB0092934
calendar_today
Updated On:
Products
Versions
TIBCO ActiveMatrix Service Grid
-
TIBCO ActiveMatrix BusinessWorks Service Engine
-
Not Applicable
-
Description
Description: The ANT scripts used to update the messaging configuration
(as described in the AMX 3.2.0 > Governance > Monitoring >
Update messaging configuration) failed for some environments. Symptoms: ERROR - Parent Component does not exist, cannot perform action on child Component.
Cause: The platform application name provided in the build data file "mcrconfig_data.xml" under folder "<tibco_home>\administrator\3.2\scripts\governance\" is different from the name of the actual platform application deployed.
Environment
Product: TIBCO ActiveMatrix Service Bus
Version:3.2.0
OS: All Supported Operating Systems
--------------------
Product: TIBCO ActiveMatrix BusinessWorks Service Engine
Version:5.10.0
OS: All Supported Operating Systems
--------------------
Product: TIBCO ActiveMatrix Service Grid
Version:3.2.0
OS: All Supported Operating Systems
--------------------
Resolution
Check the platform application name provided in the "mcrconfig_data.xml" file and the name of the actual platform application deployed in the environment. For example, the application name deployed in Admin is "amx.platform-app", whereas in the "mcrconfig_data.xml" file it might be "com.tibco.amx.platform". This usually
happens after upgrading to version 3.2.0. You can fix this by updating the "mcrconfig_data.xml" file with the same platform application name as shown in AMX Administrator.
Issue/Introduction
CLI scripts used to update the messaging configuration fail for some of environments after upgrading to AMX 3.2.0 with the error message, "Parent Component does not exist, cannot perform action on child Component".