Step commands

The step's command element specifies the scripting tool that runs the step and identifies the file that contains the actual script.

Any arguments that are required by the script or tool can also be specified with the arg file attribute. The arg file attributes should be defined in the order compatible with the scripting tool.

The Ping Server Button command script is written in Groovy. Groovy is scripting language similar to Java™. The following code is the command element for the Ping Server Button step:

    <command program="${GROOVY_HOME}/bin/groovy">
      <arg value="-cp"/>
      <arg path="classes:lib/commons-codec.jar:lib/CommonsUtil.jar:lib/ucr-plugin-util.jar:lib/rtc-plugin-helper.jar:lib/commons-lang3.jar"/>
      <arg file="PingServerButton.groovy"/>
      <arg file="${PLUGIN_INPUT_PROPS}"/>
      <arg file="${PLUGIN_OUTPUT_PROPS}"/>
    </command>

The command instructs the Groovy interpreter to run the PingServerButton.groovy script.

This line is part of every command:

<arg file="${PLUGIN_INPUT_PROPS}"/>

This line creates a file that contains the properties. The properties in the file are those properties that are furnished at run time and others that are defined earlier that are required by the step. See Example plug-in. The ${PLUGIN_INPUT_PROPS} variable resolves to the location of this properties file.

This line is also part of every command:

<arg file="${PLUGIN_OUTPUT_PROPS}"/>

This line refers to the file returned after finishing the step. The properties in this file are available to later steps in the process. The ${PLUGIN_OUTPUT_PROPS} variable resolves to the location of this properties file.