How to use CLI scripts to enable/disable Java and/or Platform debuggersin TIBCO ActiveMatrix Service Grid (AMSG).
Article ID: KB0086929
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Service Grid | - |
| Not Applicable | - |
Description
Description:
Enabling Java and Platform debuggers using CLI scripts in TIBCO ActiveMatrix Service Grid (AMSG).
Resolution
In the CLI build script (build.xml) add the following ant tasks to "enable" or "set" the Java and/or TIBCO ActiveMatrix(R) Platform Debuggers:
Note that:
- Action "disable" is used to disable Java and/or platform debuggers.
<AMXAdminTask remote="true" propsFile="${remote-properties.file}"
action="set" dataFile="${basedir}/jv.helloworld1.soa.deployment-config.xml"
objectSelector="Environment//Node//Debugger[@name='Java Debugger']"
overwrite="false" merge="true"
createIfNotExists="true" force="false" failOnError="true"
/>
/>
<AMXAdminTask remote="true" propsFile="${remote-properties.file}"
action="enable" dataFile="${basedir}/jv.helloworld1.soa.deployment-config.xml"
objectSelector="Environment//Node//Debugger[@name='Platform Debugger']"
overwrite="false" merge="true"
createIfNotExists="true" force="false" failOnError="true"
/>
/>
Note that:
- Action "disable" is used to disable Java and/or platform debuggers.
- Action "set" is used to set (i.e., enable or disable) Java debuggers.
- Action "enable" is used to enable Java debuggers only.
Attached are the sample CLI scripts for your reference (Filename: node_debugger_build.xml, node_debugger_data.xml).
Attached are the sample CLI scripts for your reference (Filename: node_debugger_build.xml, node_debugger_data.xml).
Issue/Introduction
How to use CLI scripts to enable/disable Java and/or Platform debuggersin TIBCO ActiveMatrix Service Grid (AMSG).
Feedback
Yes
No
Powered by
