Versions Compared

Old Version 5

changes.mady.by.user IT Stonebranch

Saved on

compared with

New Version Current

changes.mady.by.user Stonebranch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following illustrates the command line syntax used to install the Agent:

<pre> 
sb-7.2.0.
&lt;level&gt;
<level>-windows-
&lt;platform&gt;
<platform>.exe [/v"
command line parameters
"]  [/s] [/w] [/x]
</pre>
 Panel
 Html bobswift
 Html bobswift
In this syntax:
  • <level> is the numeric package level.
  • <platform> is x64 for the 64-bit Universal Agent distribution file.
...
 OMS component definition options are set to <b>no</b>. Universal Broker will not start the OMS Server automatically when it is started. This allows the OMS Server to be started manually any time after the Broker is started.
</ul>
  •  OMS component definition option is set to yes, which instructs Universal Broker to start the OMS Server automatically when it is started.
  • If no (the default) is specified, or if this option is not included on the command line, the AUTOMATICALLY_START and RESTART OMS component definition options are set to no. Universal Broker will not start the OMS Server automatically when it is started. This allows the OMS Server to be started manually any time after the Broker is started.
This OMS_AUTOSTART value is used to initialize the state of a check box on the OMS Server Start-up Option dialog, which displays for new installs and upgrades from Universal Agent releases earlier than 5.2.0. Changing the state of this check box will override the value specified from the command line.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  CLI 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  CLI 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  CLI 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, OPSCLI is not required unless you want to change the current install state. OPSCLI is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Controller Command Line Interface on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  UCMD 
 
  •  Manager 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  UCMD 
 
  •  Manager 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  UCMD 
 
  •  Manager 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UCMDMGR is not required unless you want to change the current install state. UCMDMGR is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Command Manager on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  UCMD 
 
  •  Server 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  UCMD 
 
  •  Server 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  UCMD 
 
  •  Server 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UCMDRSV is not required unless you want to change the current install state. UCMDSRV is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Command Server on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  UCTL 
 
  •  Server 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  UCTL 
 
  •  Server 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  UCTL 
 
  •  Server 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed
.
</ul>
  • .
Since, by default, each component's install state is preserved during an upgrade or maintenance, UCTLRSV is not required unless you want to change the current install state. UCTLSRV is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Control Server on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  UDM 
 
  •  Server 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  UDM 
 
  •  Server 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  UDM 
 
  •  Server 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UDMRSV is not required unless you want to change the current install state. UDMSRV is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Data Mover Server on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  UELD 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  UELD 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  UELD 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UELD is not required unless you want to change the current install state. UELD is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Event Log Dump on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  UEM 
 
  •  Server 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  UEM 
 
  •  Server 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  UEM 
 
  •  Server 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UEMRSV is not required unless you want to change the current install state. UEMSRV is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Event Monitor Server on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  UQUERY 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  UQUERY 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  UQUERY 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UQUERY is not required unless you want to change the current install state. UQUERY is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Query on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  USAP 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  USAP 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  USAP 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, USAP is not required unless you want to change the current install state. USAP is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Connector on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  Universal 
 
  •  Spool 
 
  •  Utilities 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  Universal 
 
  •  Spool 
 
  •  Utilities 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  Universal 
 
  •  Spool 
 
  •  Utilities 
 
  •  already 
 
  •  are 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  they 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, USPOOL is not required unless you want to change the current install state. USPOOL is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Spool Utilities on the Custom Setup dialog when installing Universal Agent via the graphical interface.
<ul>
<li> <b>n</b> - Creates no user interface.
<li> <b>b</b> - Creates a basic user interface, which displays a simple dialog box to report progress and any errors.
<li> <b>r</b> - Creates a reduced user interface, which displays progress and errors in customized windows.
</ul>

  • n - Creates no user interface.
  • b - Creates a basic user interface, which displays a simple dialog box to report progress and any errors.
  • r - Creates a reduced user interface, which displays progress and errors in customized windows.
See Command Line Switches, Command Line Installation Examples, and Detecting the Completion of a Silent Install for additional information regarding silent installs.
Parameter
Description
Default
 Anchor
AC_AGENT_CLUSTERS
AC_AGENT_CLUSTERS
AC_AGENT_CLUSTERS=clusters
Sets the AGENT_CLUSTERS UAG configuration option to specify the Universal Controller-defined agent clusters to which this agent will belong.
(none)
 Anchor
AC_AGENT_IP
AC_AGENT_IP
AC_AGENT_IP=IP address
Sets the AGENT_IP UAG configuration option to have UAG Server register with Universal Controller using a specific IP address.
(none)
AC_ENABLE_SSL
This option is deprecated starting with Universal Agent 7.1.0.0. UAG Server will always attempt to use SSL/TLS for OMS connections.
n/a
AC_EXTENSION_ACCEPT_LISTSets the EXTENSION_ACCEPT_LIST UAG configuration option, which is a comma-separated list of Universal Extensions the Agent will accept. The default value for this option is "*", which will cause the Agent to accept all extensions. Specify a value of "none" to cause the Agent to disallow execution of all Extensions.*
AC_EXTENSION_CANCEL_TIMEOUT=value[s|m|h|d]
Sets the EXTENSION_CANCEL_TIMEOUT UAG configuration option, which specifies the length of time that a Universal Extension task is given to complete its response to a CANCEL request.
If the task fails to finish its own termination processing within the specified timeout period, UAG Server will forcefully terminate the task.
The specified timeout must be numeric, but a one-letter suffix is accepted to specify (s)econds, (m)inutes, (h)ours, or (d)ays. If no time unit is specified, the default is seconds.
The following maximums are enforced:
  • 2147483647 or 2147483647s
  • 35791394m
  • 596523h
  • 24855d
Minute, hour, and day maximums are set to ensure that their value represented as a number of seconds does not exceed 2147483647.
10
AC_EXTENSION_DEPLOY_ON_REGISTRATIONSets the EXTENSION_DEPLOY_ON_REGISTRATION UAG configuration option that controls whether UAG Server will automatically receive Universal Extensions from Universal Controller at Agent startup.NO
AC_EXTENSION_PYTHON_LISTSets the EXTENSION_PYTHON_LIST UAG configuration option, which is a comma-separated list of all Python interpreters that should be considered for Universal Extension execution. There are some default locations the Agent will check even if this option is not specified. See the EXTENSION_PYTHON_LIST option's description for more information.(none)
AC_NETNAME=value
Specifies a value for a network ID that uniquely identifies the Agent on this system to the Universal Controller. The install uses this value to set the UAG NETNAME configuration option. The value specified in AC_NETNAME will override any currently configured options, including those imported from agent.props, if CONVERT_OPSAGENT is set to yes.
 
If AC_NETNAME is omitted from the command line, and no other value specifies the Agent's network ID, the default is used.
OPSAUTOCONF
 Anchor
BROKERPWD
BROKERPWD
BROKERPWD=BrokerAccountPassword
Used by the install when RUNBROKERASUSER=1 to specify the password for the account used to execute the Universal Broker service. The install also uses BROKERPWD to initialize the Password shown in the Universal Broker Service Account dialog.
 
Valid values are any 256 characters or less.
 
BROKERPWD is ignored if RUNBROKERASUSER=0.
 
 Note
titleNote
If the BROKERPWD option is set from the command line, and an installation log is generated (using the /l option to msiexec), the password value may be displayed in the log file, depending on the logging options used. Specifically, the c, p, and v flags will show the value of the BROKERPWD command line option. We recommend using /liarewum to set installation log file options to collect as much information as possible without exposing any sensitive information.
 
If the BROKERPWD option is not used from the command line, all logging options may be turned on (using /l*v) without exposing any sensitive information.

(none)
BROKERUID=BrokerAccountId
Used by the install when RUNBROKERASUSER=1 to override the default or currently configured user ID associated with the account used to execute the Universal Broker service. The install also uses BROKERUID to initialize the User ID shown in the Universal Broker Service Account dialog.
 
Valid values are any 20 characters or less. For domain accounts, a domain name of up to 256 characters is accepted, but the user ID is still limited to 20 characters.
 
BROKERUID is ignored if RUNBROKERASUSER=0.
(none)
 Anchor
CONVERT_OPSAGENT
CONVERT_OPSAGENT
CONVERT_OPSAGENT={yes|no}
Specification for whether or not to convert an existing Opswise Automation Center Agent (1.5, 1.6, or 1.7) to Agent 7.2.x.
 
The installation process will invoke a script, opsmerge.vbs, which stops the Agent and converts the configuration options stored in its agent.props file to corresponding configuration options in the Universal Automation Center Agent (UAG) uags.conf file. The script also performs several other tasks needed for the conversion.
 
 Note
titleNote
You must include this parameter when upgrading an Opswise Automation Center Agent (1.5, 1.6, or 1.7) to Agent 7.2.x.

no
INSTALLDIR=installdir
Sets the root installation directory to installdir. Each component will be installed under this directory. 
 
INSTALLDIR is required only if you want to install Universal Agent for Windows under a directory different from the one specified by the PROGRAMFILES environment variable (typically C:\Program Files\Universal). If the directory contains spaces, you must use double ( " ) quotation marks around the path name.
(none)
 Anchor
KEYSTORE
KEYSTORE
KEYSTORE={yes|no}
Specification for whether or not to create encryption keys during installation and set up the local Universal Broker as a keystore owner.
OMS={yes|no}
Specification for whether or not to install the Universal Message Service (OMS) during new installs, upgrades, or maintenance.
html-bobswift
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  OMS 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  OMS 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  OMS 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, OMS is not required unless you want to change the current install state. OMS is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Message Service on the Custom Setup dialog when installing Universal Agent via the graphical interface.
yes
OMS_AUTOSTART={yes|no}
Specification for setting the start-up behavior of the Universal Message Service (OMS) Server component.
html-bobswift
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
 Html bobswift
 OMS component definition option is set to <b>yes</b>, which instructs Universal Broker to start the OMS Server automatically when it is started.
<li> If <b>no</b> (the default) is specified, or if this option is not included on the command line, the 
AUTOMATICALLY_START
 Html bobswift
 and 
RESTART
 Html bobswift
no
 Anchor
OMS_SERVERS
OMS_SERVERS
OMS_SERVERS=port@ipaddr[,_port
 Html bobswift
<b>n</b>
@ipaddr
 Html bobswift
<b>n</b>
n@ipaddrn_,...]
A list of one or more locations where an OMS Server resides.
(none)
OPSCLI={yes|no}
Specification (yes or no) for whether or not to install the Universal Controller Command Line Interface (CLI) during new installs, upgrades, or maintenance.
 Html bobswift
no
PYTHON={yes|no}
Specification for whether or not the Python 3.7 Distribution for Universal Agent is installed.
no
 Anchor
RUNBROKERASUSER
RUNBROKERASUSER
RUNBROKERASUSER={0|1}
Controls whether the Universal Broker service executes as an Administrative user account or as Local System.
  • If RUNBROKERASUSER=1, the install will perform the following steps:
    1. If the Universal Broker service is not installed or currently is configured to run as Local System, the install will set the service's start-up account to UBrokerService or the user ID specified by the BROKERUID command line option.
    2. If the Universal Broker service is installed and already is configured to run as a user account, the Broker's start-up account will not be changed (allows customized user accounts to be preserved during upgrades).
       
  • If RUNBROKERASUSER=0, the install will perform the following steps:
    1. If the Universal Broker service is not installed or is currently configured to run as an account other than Local System, the install will set the service's start-up account to Local System.
       
       Note
      titleNote
      The Universal Broker service's properties will be set to allow Universal Broker to interact with the desktop. This is supported only when Universal Broker runs as Local System.

    2. If the Universal Broker service is installed and is currently configured to run as Local System, the Universal Broker service's properties will not be changed.
1: new installs 
0: upgrades earlier than 4.3.0
UAG_AUTOSTART={yes|no}
Sets the AUTOMATICALLY_START UAG server component definition option to control whether Universal Broker automatically starts the UAG Server.
yes
UAGSRV={yes|no}
Specification for whether or not to install Universal Automation Center Agent (UAG) during new installs, upgrades, or maintenance.
html-bobswift
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  UAG 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  UAG 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  UAG 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UAGSRV is not required unless you want to change the current install state. UAGSRV is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Automation Center Agent on the Custom Setup dialog when installing Universal Agent via the graphical interface.
yes
UCMDMGR={yes|no}
Specification for whether or not to install the Universal Command (UCMD) Manager during new installs, upgrades, or maintenance.
 Html bobswift
yes
UCMDSRV={yes|no}
Specification for whether or not to install the Universal Command (UCMD) Server during new installs, upgrades, or maintenance.
 Html bobswift
yes
UCMDSRVWORKFOLDER=WorkFolderPath
Sets the Universal Command Server working folder. This value is used only if the Universal Command Server is being installed.
 
If the folder contains spaces, you must use double ( " ) quotation marks around the path name.
INSTALLDIR\UcmdHome
UCTLMGR={yes|no}
Specification (yes or no) for whether or not to install the Universal Control (UCTL) Manager during new installs, upgrades, or maintenance.
html-bobswift
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  UCTL 
 
  •  Manager 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  UCTL 
 
  •  Manager 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  UCTL 
 
  •  Manager 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UCTLMGR is not required unless you want to change the current install state. UCTLMGR is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Control Manager on the Custom Setup dialog when installing Universal Agent via the graphical interface.
yes
UCTLSRV={yes|no}
Specification for whether or not to install the Universal Control (UCTL) Server during new installs, upgrades, or maintenance.
 Html bobswift
yes
UCTLSRVWORKFOLDER=WorkFolderPath
Sets the Universal Control Server working folder. This value is used only if the Universal Control Server is being installed.
 
If the folder contains spaces, you must use double ( " ) quotation marks around the path name.
INSTALLDIR\UcmdHome
UDMMGR={yes|no}
Specification for whether or not to install the Universal Data Mover (UDM) Manager during new installs, upgrades, or maintenance.
html-bobswift
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  UDM 
 
  •  Manager 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  UDM 
 
  •  Manager 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  UDM 
 
  •  Manager 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UDMMGR is not required unless you want to change the current install state. UDMMGR is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Data Mover Manager on the Custom Setup dialog when installing Universal Agent via the graphical interface.
yes
UDMSRV={yes|no}
Specification (yes or no) for whether or not to install the Universal Data Mover (UDM) Server during new installs, upgrades, or maintenance.
 Html bobswift
yes
UDMSRVWORKFOLDER=WorkFolderPath
Sets the Universal Data Mover Server working folder. This value is used only if the Universal Data Mover Server is being installed.
 
If the folder contains spaces, you must use double ( " ) quotation marks around the path name.
INSTALLDIR\UdmHome
UELD={yes|no}
Specification for whether or not to install Universal Event Log Dump (UELD) during new installs, upgrades, or maintenance.
 Html bobswift
yes
UEMMGR={yes|no}
Specification for whether or not to install the Universal Event Monitor (UEM) Manager during new installs, upgrades, or maintenance.
html-bobswift
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  the 
 
  •  UEM 
 
  •  Manager 
 
  •  will 
 
  •  be 
 
  •  installed.

<li> If <b>no</b> is 
  • If no is specified, 
 
  •  the 
 
  •  UEM 
 
  •  Manager 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  the 
 
  •  UEM 
 
  •  Manager 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.

</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UEMMGR is not required unless you want to change the current install state. UEMMGR is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Event Monitor Manager on the Custom Setup dialog when installing Universal Agent via the graphical interface.
yes
UEMSRV={yes|no}
Specification for whether or not to install the Universal Event Monitor (UEM) Server during new installs, upgrades, or maintenance.
 Html bobswift
yes
UEMSRVWORKFOLDER=WorkFolderPath
Sets the Universal Event Monitor Server working folder. This value is used only if the Universal Event Monitor Server is being installed.
 
If the folder contains spaces, you must use double ( " ) quotation marks around the path name.
INSTALLDIR\UemHome
UPPS={yes|no}
Specification for whether or not to install the Universal Connector for PeopleSoft (UPPS) during new installs, upgrades, or maintenance.
html-bobswift
<ul>
<li> If <b>yes</b> is 
  • If yes is specified, 
 
  •  UPPS 
 
  •  will 
 
  •  be 
 
  •  installed.
 
<li> If <b>no</b> is 
  • If no is specified, 
 
  •  UPPS 
 
  •  will 
 
  •  not 
 
  •  be 
 
  •  installed. 
 
  •  If 
 
  •  UPPS 
 
  •  already 
 
  •  is 
 
  •  present 
 
  •  on 
 
  •  the 
 
  •  system 
 
  •  (via 
 
  •  a 
 
  •  previous 
 
  •  installation), 
 
  •  it 
 
  •  will 
 
  •  be 
 
  •  removed.
 
</ul>
Since, by default, each component's install state is preserved during an upgrade or maintenance, UPPS is not required unless you want to change the current install state. UPPS is ignored during an uninstall.
 
Setting this parameter has the same effect as selecting whether or not to install Universal Connector for PeopleSoft on the Custom Setup dialog when installing Universal Agent via the graphical interface.
yes
UQUERY={yes|no}
Specification for whether or not to install the Universal Query (UQUERY) during new installs, upgrades, or maintenance.
 Html bobswift
yes
USAP={yes|no}
Specification for whether or not to install the Universal Connector (USAP) during new installs, upgrades, or maintenance.
 Html bobswift
yes
USPOOL={yes|no}
Specification (yes or no) for whether or not to install the Universal Spool Utilities, Universal Spool List (USLIST) and Universal Spool Remove (USLRM), during new installs, upgrades, or maintenance.
 Html bobswift
yes
 Anchor
/q
/q
/q{n|b|r}
Suppresses the product installation dialogs.
 
Use this parameter in addition to the #/s command line switch for a completely silent install. 
 
The following flags are available for /q:
 Html bobswift
n/a
 Anchor
/L
/L
/L[*v]
Instructs the installation process to create an installation log file named <logfilepath> (full path name). If <logfilepath> contains spaces, you must enclose it with double ( " ) quotation marks.
 
*v are flags used to specify the level of detail (verbose) contained in the log file. To reduce the amount of output generated, *v can be omitted. However, using these options is good practice; they can assist Stonebranch Customer Support with problem determination should any errors occur during installation.
n/a
...