Before you run the runDeliver script from the cli subdirectory of your BMC Middleware Automation installation, you must perform the following setup tasks:
PROXY_PORTproperties. For more information, see Using a SOCKS proxy with the CLI.
TOKENSproperty. For more information, see Defining tokens for CLI operations.
JVMARGSproperty. For a description of various JVM arguments that you can define, see Defining launcher properties. For each JVM argument, use only the text string used in the Value column on the Launcher Properties page (and not the property name from the Property column). Include spaces between your various JVM arguments, and enclose the full string of the
JVMARGSproperty value in quotation marks (for example:
-licenseoption in every command, set a value for the
LICENSE_FILEproperty. Note that you can alternatively store a copy of the license key file in the cli subdirectory.
INPUT_CONFIG_DIR(for input Configuration files) and
INPUT_PROFILE_DIR(for input Server Profile files).
ANT_LAUNCH_LOG_LEVELproperty. Valid values are
VERBOSE. The default value is
PORT_RULES_FILEproperty and set its value to the full path and name of other properties file that contains your port rule definitions. For more information, see Applying port rules for WebSphere clusters created through the CLI.
ECHO statusCode: %errorlevel%
To verify that your environment is set up properly, you can run the
runDeliver command with the
-h option, as described in Running the CLI.
Ensure that the paths that you set do not contain the following special characters in any directory names:
& (ampersand), ^ (caret), ! (exclamation mark), % (percent sign),; (semicolon), # (pound), . (period), $ (dollar sign), ' (left single quote), ` (grave accent), = (equals sign), ~ (tilde)