...
Category | Default Configuration | Description |
---|---|---|
Base components | Always installed. | Base components are always installed and activated. They include the Universal Broker, Universal Command (UCM), Universal Data Mover (UDM), and others. Base components provide the core agent infrastructure and workload services. |
Universal Automation Center Agent (UAG) | Always installed, but inactive. | Universal Controller utilizes UAG agents to provided distributed, workload automation services. |
Universal Message Service (OMS) | Always installed, but inactive. | OMS is message-oriented middleware that should be deployed on a small set of centrally located servers. It should not be activated on every Agent install. OMS is the network provider for UAG and the Universal Controller. |
Universal Controller command line programs | Not installed. | Universal Controller command line programs provide a command line interface to the Universal Controller. The installation of Universal Controller command line programs is optional. The command line programs are only required on Agents that need to interface with the Universal Controller via the command line. |
Third-party components | Not installed. | This category includes components not developed or maintained by Stonebranch, Inc. |
...
To start the installation script, unvinst, issue the following command:
Panel |
---|
See Universal Agent for Linux Installation#Linux Installation Script Parameters and Universal Agent for Linux Installation#Installation Installation Script Example, below, for a description of the optional parameters that you can issue with unvinst and an example of unvinst with these parameters.
Note | ||
---|---|---|
| ||
If you want to install multiple Agents on the same machine, or add one or more additional Agents to a machine with a previously installed Agent, some of these installation parameters are required (see Universal Agent for Linux Installation#Installing Installing Multiple Agents on a Single Machine). |
This is a silent install. The output from unvinst is written to file install.log in the current directory. The Agent is installed into directory /opt.
...
The parameters are grouped into the following categories:
Category | Description |
---|---|
Used for base install.Universal Agent for Linux Installation#OMS | |
Used for an active OMS configuration. | |
Used for an active UAG configuration. | |
Used for Universal Controller CLI programs install. | |
Universal Agent for Linux Installation#User User Mode | Used for user mode installation. |
Universal Agent for Linux Installation#ThirdThird-party | Used to manage third-party components. |
Parameter | Description | Default | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
-u
| Normal UNIX username that is used to execute the Universal Broker daemon. The install grants this user account ownership of all installed files, with the exception of the Universal Agent server components (for example: ucmsrv, udmsrv, and uemsrv) which, due to security requirements, are owned by root and will have their "set user ID on execution" bit set.
| ubroker | ||||||||||||
‑create_user
| Specification (yes or no) for whether or not to create the user name that will own the installed files as a local user. | yes | ||||||||||||
‑userdir | Home directory for the created user account specified by Universal Agent for Linux Installation# --user.
|
| ||||||||||||
-g | Normal UNIX groupname; the Universal Broker daemon will run as this specified group. All installed files will be assigned to this group.
| ubroker | ||||||||||||
‑create_group
| Specification (yes or no) for whether or not to create the group that will own the installed files as a local group. | yes | ||||||||||||
‑‑keystore | Specification (yes or no) for whether or not to create encryption keys during installation and set up the local Universal Broker as a keystore owner. | no | ||||||||||||
-security | Sets the value (default, inherit, pam, pam_sessions, or trusted) of the following configuration options for Universal Agent server components:
The appdef value for -security controls how product configuration options are set; it does not map to a product configuration option.
| (none) | ||||||||||||
-ubroker_start --ubroker_start | Specifies (yes or no) whether or not Universal Broker is started by the Installer when installation is completed. If --ubroker_start is not included in the script, Universal Broker will be started when installation is complete.
| yes | ||||||||||||
| ||||||||||||||
-c
| Causes
| |||||||||||||
-d | If Universal Agent for Linux Installation# --convert_opsagent is specified: Identifies the primary install directory for Universal Agent.
|
| ||||||||||||
‑oms_servers
| Specifies a value, in the format
| (none) | ||||||||||||
‑ac_agent_clusters | Specifies the Universal Controller-defined clusters to which this agent will belong. | (none) | ||||||||||||
‑ac_agent_ip | Specifies the IP address or host name (which resolves to an IP address) that the Agent reports to the Controller. | (none) | ||||||||||||
‑ac_netname | Specifies the network ID that Universal Agent will use. | (none) | ||||||||||||
-ac_extension_accept_list | Specifies a comma-separated list of one or more Universal Extensions that the agent will accept via auto-deployment from the Controller.
The value specified for this parameter sets the EXTENSION_ACCEPT_LIST configuration option value. | * | ||||||||||||
-ac_extension_python_list --ac_extension_python_list | Specifies a comma-separated list of zero or more Python locations. Each item in the list is expected to contain a complete path to a Python executable. The value specified for this parameter sets the EXTENSION_PYTHON_LIST configuration option value. | /usr/bin/python3,/usr/bin/python,/usr/libexec/platform-python | ||||||||||||
-ac_extension_deploy_on_registration --ac_extension_deploy_on_registration | Controls Extension deployment behavior from the Universal Controller.
The value specified for this parameter sets the EXTENSION_DEPLOY_ON_REGISTRATION configuration option value. | no | ||||||||||||
-ac_extension_cancel_timeout | Set the EXTENSION_CANCEL_TIMEOUT UAG configuration option, which specifies the length of time 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:
Minute, hour, and day maximums are set to ensure that their value represented as a number of seconds does not exceed 2147483647. | 10 | ||||||||||||
‑ac_enable_ssl | This option is deprecated starting with Universal Agent 7.1.0.0. UAG Server will always attempt to -ac_process_cancel_timeout | Set the PROCESS_CANCEL_TIMEOUT UAG configuration option, which specifies the length of time an OS 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:
Minute, hour, and day maximums are set to ensure that their value represented as a number of seconds does not exceed 2147483647. | 10 | |||||||||||
‑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 | ||||||||||||
‑uag_autostart
| Specifies (yes or no) whether or not the Universal Automation Center Agent (UAG) Server starts automatically when the Universal Broker is started. | yes | ||||||||||||
| ||||||||||||||
‑oms_port | Specifies the port to use to listen for OMS connection requests. | (none) | ||||||||||||
‑oms_autostart
| Specifies (yes or no) whether or not OMS is started automatically by Universal Broker when Universal Broker starts. | no | ||||||||||||
| ||||||||||||||
‑opscli
| Specifies (yes or no) whether or not the Universal Controller Command Line Interface (CLI) tools will be installed. | no | ||||||||||||
| ||||||||||||||
-usermode_install --usermode_install | Specifies (yes or no) for a user mode installation, which defines both of the following:
| no | ||||||||||||
| If Universal Agent for Linux Installation# --usermode_install is set to yes: Specifies the Agent binaries (installation) directory. | (none) | ||||||||||||
‑unvcfgdir
| If Universal Agent for Linux Installation# --usermode_install is set to yes: Specifies the Agent configuration files directory. |
| ||||||||||||
‑unvdatadir
| If Universal Agent for Linux Installation# --usermode_install is set to yes: Specifies the Agent data files directory. |
| ||||||||||||
‑unvport
| If Universal Agent for Linux Installation# --usermode_install is set to yes: Specifies the Universal Broker port. | (none) | ||||||||||||
| ||||||||||||||
‑python
| Specifies (yes or no) whether the Python 3.7 Distribution for Universal Agent is installed. | no | ||||||||||||
Additional Parameter | ||||||||||||||
-? | Displays command line help. | n/a |
...
A user mode installation, implemented through use of the Universal Agent for Linux Installation#usermode usermode_install installation parameter, lets you install multiple Agents on a single machine and change the default installation directories for any Agent being installed.
...
Installation Parameter | Value |
---|---|
Universal Agent for Linux Installation#--usermode_install | yes |
Universal Agent for Linux Installation#--user | A username that is different than the username specified for any other Agent installation on this machine. |
Universal Agent for Linux Installation#--unvdir | An Agent binaries (installation) directory that is different than the installation directory specified for any other Agent installation on this machine. |
Universal Agent for Linux Installation#--unvport | A Universal Broker port that is different than the port specified for any other Agent installation on this machine. |
...
If you want to change these default directories, or if you want to install multiple Agents on the same machine, you must set the Universal Agent for Linux Installation# --usermode_install parameter to yes and specify new values in the following parameters. These directories must be different for each Agent on the same machine.
...
Installation Parameter | Default Directory | Files Installed |
---|---|---|
Universal Agent for Linux Installation#--unvdir | /opt/universal | Agent binaries |
Universal Agent for Linux Installation#--unvcfgdir | /etc/universal | Agent configuration files |
Universal Agent for Linux Installation#--unvdatadir | /var/opt/universal | Agent data files |
...
As of release 5.1, this file no longer is used. To apply your desired security configuration, access the UAG SECURITY configuration option in the uags.conf
configuration file:
Universal Agent for Linux Installation#Examples Examples of Customized PAM Configuration Files,