...

To uncompress and extract the installation files from the product distribution file, issue the following command:

Panel

Html bobswift
<pre> zcat sb-7.2.x.x-linux-3.10-x86_64.tar.Z \| tar xvf - </pre>

This command assumes that the name of the distribution file is sb-7.2.x.x-linux-3.10-x86_64.tar.Z.

...

To uncompress and extract the installation files from the product distribution file, issue the following command:

Panel

...

Html bobswift
<pre> zcat sb-7.2.x.x-linux-3.10-s390x.tar.Z

...

Distribution File

 | tar xvf -
</pre>

This command assumes that the name of the distribution file is sb-7.2.x.x-linux-3.10-s390x.tar.Z.

Distribution File

The following table identifies the files contained in the distribution file.

...

To uncompress and extract the installation files from the product distribution file, issue the following command:

Panel

Html bobswift
<pre> zcat sb-7.2.x.x-linux-3-x86_64-deb.tar.Z \| tar xvf - </pre>

This command assumes that the name of the distribution file is sb-7.2.x.x-linux-3-x86_64-deb.tar.Z.

...

To uncompress and extract the installation files from the product distribution file, issue the following command:

Panel

...

Html bobswift
<pre> zcat sb-7.2.x.x-linux-3.10-ppc64le.tar.Z \| tar xvf - </pre>

This command assumes that the name of the distribution file is sb-7.2.x.x-linux-3.10-ppc64le.tar.Z.

...

To start the installation script, unvinst, issue the following command:

Panel

See Linux Installation Script Parameters and 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

title	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 Installing Multiple Agents on a Single Machine).

...

The Universal Broker daemon will be installed and run as the username and groupname specified with the installation script parameters, below.

Note

title	Note

For this release of Linux RPM, the previous non-RPM version will not be uninstalled. The Administrator can remove the remaining files/directories as needed.

...

The following table describes the optional parameters that are available in the UNIX install script (unvinst) when installing Universal Agent.

The parameters are grouped into the following categories:

...

Anchor
Linux Installation Script Parameters
Linux Installation Script Parameters
Linux Installation Script Parameters

The following table describes the optional parameters that are available in the UNIX install script (unvinst) when installing Universal Agent.

The parameters are grouped into the following categories:

Category	Description
Base	Used for base install.
OMS	Used for an active OMS configuration.
UAG	Used for an active UAG configuration.
CLI	Used for Universal Controller CLI programs install.
User Mode	Used for user mode installation.
Third-party	Used to manage third-party components.

The following example illustrates Universal Agent for Linux installed with the installation script, unvinst, and optional parameters.

...

‑create_group
‑‑create_group‑keystore
‑‑keystoreUAG Parameters-c
‑convert
‑‑convert_opsagent‑oms_servers
‑‑oms_servers‑uag_autostart
‑‑uag_autostartOMS Parameters‑oms_autostart
‑‑oms_autostartCLI Parameters‑opscli
‑‑opscliUser Mode Parameters-U
-usermode_install
--usermode_install-unvdir
--unvdir‑unvcfgdir
‑‑unvcfgdir‑unvdatadir
‑‑unvdatadir‑unvport
‑‑unvportThird-Party Parameters‑python
‑‑python

Parameter

Description

Default

Anchor

	Base
	Base

Base Parameters

-u
‑user

Anchor

	--user
	--user

--user

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.

If the user account that you want to use already exists, specify that user account.
If the user account does not exist, the install creates it.
If you want to change the user account for an installed Universal Agent for Linux system, you must perform a re-installation and use this parameter to change the user account.
If --user is omitted from unvinst, the default is used.
If --usermode_install is yes, there is no default.

ubroker

‑create_user

Anchor

	--create_user
	--create_user

‑‑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
‑‑userdir

Home directory for the created user account specified by --user.

If this directory does not exist, it is created when the specified user is created.
If the user specified by --user already exists, but the home directory of that user is not the default directory (/home/<username>), --userdir must specify the path to that home directory.
If --userdir is omitted from unvinst, the default is used.

/home/<username>

-g
‑group
‑‑group

Normal UNIX groupname; the Universal Broker daemon will run as this specified group. All installed files will be assigned to this group.

If the group that you want to use already exists, specify that user account.
If the user account does not exist, the install creates it.
If you want to change the user account for an installed Universal Agent for Linux system, you must perform a re-installation and use this parameter to change the user accountgroup.
If this group does not exist, the install creates it.
If --usergroup is omitted from unvinst, the default is used.
If --usermode_install is yes, there is no default.

ubroker

‑create_usergroup

Anchor

	--create_usergroup
	--create_usergroup

‑‑create_usergroup

Specification (yes or no) for whether or not to create the user name group that will own the installed files as a local usergroup.

yes

‑userdir
‑‑userdir

Home directory for the created user account specified by --user.

If this directory does not exist, it is created when the specified user is created.
If the user specified by --user already exists, but the home directory of that user is not the default directory (/home/<username>), --userdir must specify the path to that home directory.
If --userdir is omitted from unvinst, the default is used.

/home/<username>

-g
‑group
‑‑group

Normal UNIX groupname; the Universal Broker daemon will run as this specified group. All installed files will be assigned to this group.

If the group that you want to use already exists, specify that group.
If this group does not exist, the install creates it.
If --group is omitted from unvinst, the default is used.

ubroker

Anchor

--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

Anchor

-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
--security

Sets the value (default, inherit, pam, pam_sessions, or trusted) of the following configuration options for Universal Agent server components:

SECURITY: UAG Server
USER_SECURITY: UCMD Server
USER_SECURITY: UCTL Server
USER_SECURITY: UDM Server
USER_SECURITY: UEM Server

The appdef value for -security controls how product configuration options are set; it does not map to a product configuration option.

Note

title	Note

pam_sessions is a valid value only for the UCMD Server and UDM Server.

(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.

Note

title	Note

--ubroker_start is ignored for user mode installs.

yes

Anchor

UAG UAG

Anchor

--convert_opsagent

Causes unvinst to execute opsmerge.sh (residing in /opt/universal/uagsrv/bin), which performs the following tasks:

Searches for an existing Opswise Automation Center Agent 1.6 or 1.7 install and converts properties stored in the agent.props file to corresponding configuration options in the Universal Automation Center Agent (UAG) configuration file, uags.conf.
Searches for an active Opswise Automation Center Agent 1.6 or 1.7 daemon process and attempts to stop it.
Assigns the ID used by the Opswise Automation Center Agent 1.6 or 1.7 to UAG by moving the qname file from the Opswise Automaton Center install directory to the /var/opt/universal/uag/var directory.

-d
‑opsdir
‑‑opsdir

If --convert_opsagent is specified: Identifies the primary install directory for Universal Agent.

If --opsdir is omitted from unvinst, the default is used.

/home/opswise

Anchor

--oms_servers

Specifies a value, in the format port@host[,port2@host,...,portn@hostn], for the port and network address of the OMS server(s) to be used as network communications providers.

Note

title	Note

You should always include --oms_servers in unvinst; OMS is the network communications provider between a Controller 7.2.x.x and Agent 7.2.x.x.

UAG configuration: The value specified for --oms_servers is set automatically for the UAG OMS_SERVERS configuration option.

(none)

‑ac_agent_clusters
‑‑ac_agent_clusters

Specifies the Universal Controller-defined clusters to which this agent will belong.

UAG configuration: The value specified by --ac_agent_clusters is set automatically for the UAG AGENT_CLUSTERS configuration option.

(none)

‑ac_agent_ip
‑‑ac_agent_ip

Specifies the IP address or host name (which resolves to an IP address) that the Agent reports to the Controller.

UAG configuration: The value specified by --ac_agent_ip is set automatically for the UAG AGENT_IP configuration option.

(none)

‑ac_netname
‑‑ac_netname

Specifies the network ID that Universal Agent will use.

UAG configuration: The value specified by --ac_netname is set automatically for the UAG NETNAME configuration option.

(none)

-ac_extension_accept_list
--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.

A single value of * indicates that all extensions are accepted.
A single value of none indicates that no extensions are accepted.

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.

If the value is yes, the Controller will preemptively deploy all extensions acceptable by UAG.
If the value is no, the Controller will only send Extension modules as needed (on demand).

The value specified for this parameter sets the EXTENSION_DEPLOY_ON_REGISTRATION configuration option value.

no

-ac_extension_cancel_timeout
--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:

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_process_cancel_timeout
--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:

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_enable_ssl
‑‑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

Anchor

--uag_autostart

Specifies (yes or no) whether or not the Universal Automation Center Agent (UAG) Server starts automatically when the Universal Broker is started.

UAG component definition: The value specified by --uag_autostart is set automatically for the UAG AUTOMATICALLY_START component definition option.

yes

Anchor

OMS OMS

‑oms_port
‑‑oms_port

Specifies the port to use to listen for OMS connection requests.

OMS configuration: The value specified by --oms_port is set automatically for the OMS SERVICE_PORT configuration option.

(none)

Anchor

--oms_autostart

Specifies (yes or no) whether or not OMS is started automatically by Universal Broker when Universal Broker starts.

OMS component definition: The value specified by --oms_autostart is set automatically for the OMS AUTOMATICALLY_START and RESTART component definition options.

no

Anchor

CLI CLI

Anchor

--opscli

Specifies (yes or no) whether or not the Universal Controller Command Line Interface (CLI) tools will be installed.

no

Anchor

User Mode User Mode

Anchor

--usermode_install

Specifies (yes or no) for a user mode installation, which defines both of the following:

Whether or not this Agent can be installed on a machine where an Agent already is installed (see Installing Multiple Agents on a Single Machine).
Whether or not the user can specify installation parameters (--unvdir, --unvcfgdir, --unvdatadir, and --unvport) that control where the Agent will be installed and configured (see Changing the Default Installation Directories).

no

Anchor

--unvdir --unvdir

Anchor

unvdir

If --usermode_install is set to yes: Specifies the Agent binaries (installation) directory.

(none)

Anchor

unvcfgdir

If --usermode_install is set to yes: Specifies the Agent configuration files directory.

<--unvdir>/etc

Anchor

unvdatadir

If --usermode_install is set to yes: Specifies the Agent data files directory.

<--unvdir>/var

Anchor

unvport

If --usermode_install is set to yes: Specifies the Universal Broker port.

(none)

Anchor

Third-party Third-party

Anchor

python

Specifies (yes or no) whether the Python 3.7 Distribution for Universal Agent is installed.

no

Additional Parameter

-?
-h
‑help
‑‑info

Displays command line help.

n/a

...

Anchor

	-keystore
	-keystore

‑keystore
‑‑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
--security

Sets the value (default, inherit, pam, pam_sessions, or trusted) of the following configuration options for Universal Agent server components:

SECURITY: UAG Server
USER_SECURITY: UCMD Server
USER_SECURITY: UCTL Server
USER_SECURITY: UDM Server
USER_SECURITY: UEM Server

The appdef value for -security controls how product configuration options are set; it does not map to a product configuration option.

Note

title	Note

pam_sessions is a valid value only for the UCMD Server and UDM Server.

(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.

Note

title	Note

--ubroker_start is ignored for user mode installs.

yes

Anchor

	UAG
	UAG

UAG Parameters

-c
‑convert

Anchor

	--convert_opsagent
	--convert_opsagent

‑‑convert_opsagent

Causes unvinst to execute opsmerge.sh (residing in /opt/universal/uagsrv/bin), which performs the following tasks:

Searches for an existing Opswise Automation Center Agent 1.6 or 1.7 install and converts properties stored in the agent.props file to corresponding configuration options in the Universal Automation Center Agent (UAG) configuration file, uags.conf.
Searches for an active Opswise Automation Center Agent 1.6 or 1.7 daemon process and attempts to stop it.
Assigns the ID used by the Opswise Automation Center Agent 1.6 or 1.7 to UAG by moving the qname file from the Opswise Automaton Center install directory to the /var/opt/universal/uag/var directory.

-d
‑opsdir
‑‑opsdir

If --convert_opsagent is specified: Identifies the primary install directory for Universal Agent.

If --opsdir is omitted from unvinst, the default is used.

/home/opswise

‑oms_servers

Anchor

	--oms_servers
	--oms_servers

‑‑oms_servers

Specifies a value, in the format port@host[,port2@host,...,portn@hostn], for the port and network address of the OMS server(s) to be used as network communications providers.

Note

title	Note

You should always include --oms_servers in unvinst; OMS is the network communications provider between a Controller 7.2.x.x and Agent 7.2.x.x.

UAG configuration: The value specified for --oms_servers is set automatically for the UAG OMS_SERVERS configuration option.

(none)

‑ac_agent_clusters
‑‑ac_agent_clusters

Specifies the Universal Controller-defined clusters to which this agent will belong.

UAG configuration: The value specified by --ac_agent_clusters is set automatically for the UAG AGENT_CLUSTERS configuration option.

(none)

‑ac_agent_ip
‑‑ac_agent_ip

Specifies the IP address or host name (which resolves to an IP address) that the Agent reports to the Controller.

UAG configuration: The value specified by --ac_agent_ip is set automatically for the UAG AGENT_IP configuration option.

(none)

‑ac_netname
‑‑ac_netname

Specifies the network ID that Universal Agent will use.

UAG configuration: The value specified by --ac_netname is set automatically for the UAG NETNAME configuration option.

(none)

-ac_extension_accept_list
--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.

A single value of * indicates that all extensions are accepted.
A single value of none indicates that no extensions are accepted.

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.

If the value is yes, the Controller will preemptively deploy all extensions acceptable by UAG.
If the value is no, the Controller will only send Extension modules as needed (on demand).

The value specified for this parameter sets the EXTENSION_DEPLOY_ON_REGISTRATION configuration option value.

no

-ac_extension_cancel_timeout
--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:

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_process_cancel_timeout
--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:

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_enable_ssl
‑‑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

Anchor

	--uag_autostart
	--uag_autostart

‑‑uag_autostart

Specifies (yes or no) whether or not the Universal Automation Center Agent (UAG) Server starts automatically when the Universal Broker is started.

UAG component definition: The value specified by --uag_autostart is set automatically for the UAG AUTOMATICALLY_START component definition option.

yes

Anchor

	OMS
	OMS

OMS Parameters

‑oms_port
‑‑oms_port

Specifies the port to use to listen for OMS connection requests.

OMS configuration: The value specified by --oms_port is set automatically for the OMS SERVICE_PORT configuration option.

(none)

‑oms_autostart

Anchor

	--oms_autostart
	--oms_autostart

‑‑oms_autostart

Specifies (yes or no) whether or not OMS is started automatically by Universal Broker when Universal Broker starts.

OMS component definition: The value specified by --oms_autostart is set automatically for the OMS AUTOMATICALLY_START and RESTART component definition options.

no

Anchor

	CLI
	CLI

CLI Parameters

‑opscli

Anchor

	--opscli
	--opscli

‑‑opscli

Specifies (yes or no) whether or not the Universal Controller Command Line Interface (CLI) tools will be installed.

no

Anchor

	User Mode
	User Mode

User Mode Parameters

Anchor

	--usermode_install
	--usermode_install

-U
-usermode_install
--usermode_install

Specifies (yes or no) for a user mode installation, which defines both of the following:

Whether or not this Agent can be installed on a machine where an Agent already is installed (see Installing Multiple Agents on a Single Machine).
Whether or not the user can specify installation parameters (--unvdir, --unvcfgdir, --unvdatadir, and --unvport) that control where the Agent will be installed and configured (see Changing the Default Installation Directories).

no

Anchor

	--unvdir
	--unvdir

-unvdir

Anchor

	unvdir
	unvdir

--unvdir

If --usermode_install is set to yes: Specifies the Agent binaries (installation) directory.

(none)

‑unvcfgdir

Anchor

	unvcfgdir
	unvcfgdir

‑‑unvcfgdir

If --usermode_install is set to yes: Specifies the Agent configuration files directory.

<--unvdir>/etc

‑unvdatadir

Anchor

	unvdatadir
	unvdatadir

‑‑unvdatadir

If --usermode_install is set to yes: Specifies the Agent data files directory.

<--unvdir>/var

‑unvport

Anchor

	unvport
	unvport

‑‑unvport

If --usermode_install is set to yes: Specifies the Universal Broker port.

(none)

Anchor

	Third-party
	Third-party

Third-Party Parameters

‑python

Anchor

	python
	python

‑‑python

Specifies (yes or no) whether the Python 3.7 Distribution for Universal Agent is installed.

no

Additional Parameter

-?
-h
‑help
‑‑info

Displays command line help.

n/a

Anchor
Installation Script Example
Installation Script Example
Installation Script Example

The following example illustrates Universal Agent for Linux installed with the installation script, unvinst, and optional parameters.

Panel

Html bobswift

<pre>
sh ./unvinst --user user1 --userdir /homedir/user --group usergroup 
             --keystore no --convert_opsagent --opsdir /homedir/ops 
             --oms_servers 7878@oms2 --oms_port 7878 --oms_autostart yes 
             --ac_agent_clusters GA Cluster,CA Cluster --ac_agent_ip 127.0.0.1
             --ac_netname OPSAUTOCONF --opscli yes --uag_autostart yes
             --usermode_install yes --unvdir /opt/universal 
             --unvcfgdir /etc/universal --unvdatadir /var/opt/universal --unvport 7887
</pre>

Anchor
User Mode Installation
User Mode Installation
User Mode Installation

...

Listing Universal Agent for Linux Information

RPM Commands

Information

...

on installed packages is listed with the rpm command. The command must be executed with the superuser ID.

To list information for the Universal Agent for Linux, issue the following command:

Panel

Html bobswift
<pre> rpm -qi unv rpm -qi unv-opscli </pre>

Debian Commands

Information on installed packages is listed with the rpm dpkg command. The command must be executed with the superuser IDauthority.

To list information for the Universal Agent for Linux, issue the following commandcommands:

Panel

Debian Commands

Information on installed packages is listed with the dpkg command. The command must be executed with superuser authority.

To list information for the Universal Agent for Linux, issue the following commands:

...

Removing Universal Agent for Linux

System Install Removal

...

Step 1

...

Stop the ubrokerd daemon.

...

Step 2

...

Html bobswift
<pre> sudo dpkg -l unv sudo dpkg -l unv-opscli </pre>

Removing Universal Agent for Linux

System Install Removal

Step 1

Stop the ubrokerd daemon.

Step 2

Make a backup copy of the /var/opt/universal and /etc/universal directories.

Step 3

RPM Commands

Using the superuser ID, remove all Universal Agent for Linux packages by issuing the following commands:

Panel

Html bobswift
<pre> rpm -e unv-opscli rpm -e unv </pre>

Panel

Html bobswift
<pre> rm -rf /etc/universal </pre>

Panel

Html bobswift
<pre> rm -rf /var/opt/universal

and /etc/universal directories.

Step 3

RPM Commands


</pre>

Debian commands

Using the superuser IDauthority, remove all Universal Agent for Linux packages by issuing the following commands:

Panel
Panel
Panel

Debian commands

Using the superuser authority, remove all Universal Agent for Linux packages by issuing the following commands:

panel

Panel

Html bobswift
<pre> sudo dpkg -r unv-opscli sudo dpkg -r unv </pre>

Panel

Html bobswift
<pre> rm -rf /etc/universal </pre>

Panel

Html bobswift
<pre> rm -rf /var/opt/universal </pre>

Step 4

Delete the Agent user account (ubroker) and its home directory:

panel

Panel

Html bobswift
<pre> userdel -r ubroker </pre>

Step 5

Delete the Agent group (ubroker):

Panel

Html bobswift
<pre> groupdel ubroker </pre>

User Mode Install Removal

Step 1

Stop the Usermode Broker.

Step 2

Make a backup copy of the <--unvcfgdir> and <--unvdatadir> directories.

Step 3

Using the superuser ID, remove all Universal Agent for Linux packages by issuing the following commands:

Panel

Html bobswift
<pre> rm -rf <---unvdir> </pre>

Panel

Html bobswift
<pre> rm -rf <--unvcfgdir> </pre>

Panel

Html bobswift
<pre> rm -rf <--unvdatadir> </pre>

Step 4

Delete the Agent user account (ubroker) and its home directory:

Panel

Html bobswift
<pre> userdel -r [Usermode Broker user] </pre>

Step 5

Delete the Agent group (ubroker):

Panel

Html bobswift
<pre> groupdel [Usermode Broker group] </pre>

Note

title	Agent

To remove an Agent executing in an unprivileged user mode environment (see User Mode Installation), simply stop the ubrokerd daemon and remove the ./universal installation directory. To make sure that you do not mistakenly remove a system install directory, attempt the removal with a non-privileged user account or the Broker account.

...

All supported Linux installations - except for SUSE 9 and below - require the sample PAM configuration file delivered with Universal Agent to be copied to directory /etc/pam.d:

Panelpanel

Html bobswift
<pre> cp /opt/universal/ucmdsrv/samp/ucmd.pam /etc/pam.d/ucmd </pre>

PAM Configuration File

All Universal Agent components utilize the same PAM configuration file.

...

Universal Agent for Redhat systems 5.0 and greater

auth	include	system-auth-auth
auth	required	pam_nologin.so
account	include	system-auth

Universal Agent for SUSE-based systems 10.0 and greater

auth	required	pam_unix2.so nullok
auth	required	pam_nologin.so
account	include	common-account

Alternative Universal Agent for SUSE 10.1

auth	required	pam_unix2.so nullok
auth	required	pam_nologin.so
account	include	systemcommon-authaccount

...

auth	required	pam_unix2.so nullok
auth	required	pam_nologin.so
account	include	common-account

...

auth	required	pam_unix2.so nullok
auth	required	pam_nologin.so
account	include	common-account

Configuring the Agent to Run a Task without a Password

Prior to release 5.1, Universal Automation Center used the ops_suexec.nopass file, which listed all trusted users.

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:

...

Configuring the Agent to Run a Task without a Password

Prior to release 5.1, Universal Automation Center used the ops_suexec.nopass file, which listed all trusted users.

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:

Html bobswift

<ul>
<li> If you do not want security, set the value to <b>none</b>.
<li> If you want security, set the value to <b>pam</b> and update the following files: 
<ul>
<li> Check the <b>/etc/pam.d/ucmd</b> configuration file to ensure that it contains the minimum PAM security settings (see

Examples of Customized PAM Configuration Files,

Html bobswift

 above).
<li> Add the following to <b>/etc/universal/uacl.conf</b> for each user: <b>uag_work_request [username],allow,noauth</b>
<br>
Also, verify that the user has a <b>/home</b> directory defined.
</ul>
</ul>

Versions Compared

Old Version 4

New Version 5

Key

Distribution File

Distribution File

Anchor
Linux Installation Script Parameters
Linux Installation Script Parameters
Linux Installation Script Parameters

Anchor
Installation Script Example
Installation Script Example
Installation Script Example

Anchor
User Mode Installation
User Mode Installation
User Mode Installation

Listing Universal Agent for Linux Information

RPM Commands

Debian Commands

Debian Commands

Removing Universal Agent for Linux

System Install Removal

Removing Universal Agent for Linux

System Install Removal

User Mode Install Removal

PAM Configuration File

Configuring the Agent to Run a Task without a Password

Configuring the Agent to Run a Task without a Password

Page Comparison

Versions Compared

Old Version 4

New Version 5

Key

Distribution File

Distribution File

AnchorLinux Installation Script ParametersLinux Installation Script Parameters Linux Installation Script Parameters

AnchorInstallation Script ExampleInstallation Script ExampleInstallation Script Example

AnchorUser Mode InstallationUser Mode InstallationUser Mode Installation

Listing Universal Agent for Linux Information

RPM Commands

Debian Commands

Debian Commands

Removing Universal Agent for Linux

System Install Removal

Removing Universal Agent for Linux

System Install Removal

User Mode Install Removal

PAM Configuration File

Configuring the Agent to Run a Task without a Password

Configuring the Agent to Run a Task without a Password

Anchor
Linux Installation Script Parameters
Linux Installation Script Parameters
Linux Installation Script Parameters

Anchor
Installation Script Example
Installation Script Example
Installation Script Example

Anchor
User Mode Installation
User Mode Installation
User Mode Installation