Using the ANT property for "componentID" in the CLI (Command Line Interface) does not work as expected.

Using the ANT property for "componentID" in the CLI (Command Line Interface) does not work as expected.

book

Article ID: KB0088053

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix Service Grid -
TIBCO ActiveMatrix BusinessWorks Service Engine -
Not Applicable -

Description

Description:
CLI script not able to detect the feature even though a matching feature exists.

Symptoms:
CLI scripts to delete the feature not able to identify the feature and the build completed successfully without processing any objects.


Cause:
Check how the "objectSelector" attribute is given for the AMXAdminTask (in build file) used to delete the feature. Check if the ANT property is used in order to match the exact feature.

Example. Given the objectSelector in CLI build file as follows:


<AMXAdminTask
            remote="true"
            action="delete"
            objectSelector="Environment/Node/Feature[@componentID='$compID']"  
            propsFile="${remote-properties.file}"
            dataFile="${deploy-config.file}"
            overwrite="true"
            merge="true"
            createIfNotExists="true"
            force="false"
            failOnError="true" />


From the Data File:
 
        <Environment xsi:type="amxdata:Environment" name="${target.env}">
                <Node xsi:type="amxdata:Node" name="${target.node}">
                        <Feature xsi:type="amxdata_base:FeatureID" componentID="$compID" version="${version}" />
                </Node>
        </Environment>

For the above mentioned build file, the usage of @componentID='${compID}' for "objectSelector" would only work if you specify the hard coded feature name (for componentID ) in for the data file. Check if the data file also uses the ANT property for componentID.

Resolution

Changing the objectSelector attribute from [@componentID='${compID}'] to ['${compID}'] as shown below. And this usage would work in both scenarios where the data file is using hard coded value or using ant property.

Before change:
objectSelector="Environment/Node/Feature[@componentID='${compID}']"

After change:
objectSelector="Environment/Node/Feature['${compID}']"

Issue/Introduction

Using the ANT property for "componentID" in the CLI (Command Line Interface) does not work as expected.
Powered by Wolken Software