Using the CLI
To view the status of an application fragment on a Node using ActiveMatrix Administrator CLI, add the
getNodeHealthDetail
target to the
TIBCO_HOME\administrator\<version>\samples\node_build.xml
file. No changes are required in the
TIBCO_HOME\administrator\<version>\samples\node_data.xml
file.
Use the
failOnError
and
verbose
options of the
getNodeHealthDetail
target, as required.
failOnError
:- If the
failOnError
option is set totrue
,failOnError
ensures that agetNodeHealthDetail
target fails if an entity of the requested Node is in a suspicious state. - If the
failOnError
option is set tofalse
, the target does not fail and continues to process further Nodes if they are specified.
- If the
verbose
: gets a status of all the entities for multiple Nodes.- If the
verbose
option is not used or set tofalse
, only failed entities and their status is returned. - If the
verbose
option is set totrue
and there are no failed entities on the Node, a message indicating that none of the application fragments are in a failed state is displayed.
- If the
Target in Node_Build.xml
<target name="getNodeHealthDetail"> <AMXAdminTask action="getNodeHealthDetail" objectSelector="Environment/Node" remote="true" propsFile="${instanceProperties}" dataFile="${dataFile}" failOnError="false"/> <!-- options="verbose" --> </target>
Sample Output
The following shows a sample output where the application fragment status is requested for two Nodes,
DevNode
and
Node2
. None of the entities on
DevNode
are in the failed state. For
Node2
, an Endpoint and Resource Instance have failed.
getNodeHealthDetail: [AMXAdminTask] 31 Jan 2018 17:27:31 INFO - Initializing JSSE's crypto provider class com.sun.net.ssl.internal.ssl.Provider in default mode [AMXAdminTask] 31 Jan 2018 17:27:32 INFO - Connecting to AMX Admin server at 'http://localhost:8120' as user 'root'. [AMXAdminTask] 31 Jan 2018 17:27:32 INFO - Executing action 'nodeHealthDetail' for 2 objects from data file '<TIBCO_HOME>\administrator\<version>\samples\node_data.xml' [AMXAdminTask] 31 Jan 2018 17:27:33 INFO - Application fragments status [AMXAdminTask] 31 Jan 2018 17:27:42 INFO - Node: DevNode [AMXAdminTask] 31 Jan 2018 17:27:50 INFO - None of the application fragments are in failed state for node DevNode [AMXAdminTask] 31 Jan 2018 17:27:50 INFO - Node: Node2 [AMXAdminTask] 31 Jan 2018 17:27:51 INFO - urn:amx:DevEnvironment/test1/Java1_1.0.0.v2018-01-22-1629_inbound_service_NewService/Sample_SOAPService_Binding1 End Point START_FAILED [AMXAdminTask] httpConnector Resource Instance FAILED [AMXAdminTask] [AMXAdminTask] 31 Jan 2018 17:27:51 INFO - Action finished at 31/1/18 5:27 PM in 18.317 seconds BUILD SUCCESSFUL Total time: 21 seconds