OneCLI global configuration file

The configuration items of OneCLI are listed in the global.config file in INI format. For more information, refer to the global.config file in OneCLI binary.

Note: When using global.config in the executable version of OneCLI, the --config parameter should be used for specifying the absolute path.

The configuration items varied depending on OneCLI versions. Following is the example:

# XClarity Essentials OneCLI consolidates ToolsCenter 1.x tools, i.e. UXSPI for update, DSA for inventory, 
# ASU for configuration
# To point XClarity Essentials OneCLI to old ToolsCenter 1.x version to help manage old MTM using proxy tools
# that come with XClarity Essentials OneCLI
# Users can change the following three config items
# Example for Windows:
# To set UXSPI path, users can change the value of "UXSPI_PATH" from "NONE" to the absolute path to where 
#users put the UXSPI executable file prepared separately
# Do not set the path to the proxy tool "uxspi.exe" inside XClarity Essentials OneCLI
# UXSPI_PATH=C:\lnvgy_utl_uxspi_10.1_winsrvr_32-64.exe
UXSPI_PATH=NONE
# To set DSA path, users can change the value of "DSA_PATH" from "NONE" to the absolute path to where users 
# put the DSA executable file prepared separately
# Do not set the path to the proxy tool "dsa.exe" inside XClarity Essentials OneCLI
# DSA_PATH=C:\lnvgy_utl_dsa_dsala5q-10.1_portable_windows_x86-64.exe
DSA_PATH=NONE
# To set ASU path, users should first extract "asu.exe" out of the official ASU executable wrapper
# (e.g, lnvgy_utl_asu_asut90e-10.1_windows_x86-64.exe), then, change the value of "ASU_PATH" from "NONE" 
# to the absolute path to where users put "asu.exe" extracted above
# Do not set the path to the proxy tool inside XClarity Essentials OneCLI
# default value is "NONE"
# ASU_PATH=C:\asu\asu64.exe
ASU_PATH=NONE
# Set the number of Windows log entries OneCLI inventory collect. It could be an integer, or "All".
ONECLI_EVENTLOG_MAX=4096