Versions Compared

Old Version 1

changes.mady.by.user Former user

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.

...

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

Panel


Html bobswift
<pre>
zcat sb-7.2.x.x-aix-7.1-ppc64.tar.Z | tar xvf -
</pre>


This command assumes the following:

  • Name of the distribution file is sb-7.12.x.x-aix-7.1-ppc64.tar.Z.
  • File is located in the current working directory.

...

File

Description

Readme.unv

Summary of the installation procedure.

unv-7.12.x.x-aix-7.1-ppc64.rpm

AIX RPM file format package.

unv-opscli-7.12.x.x-aix-7.1-ppc64.rpm

Universal Controller Command Line Interface (CLI) RPM file format package.

unvinst

Installation script.

upimerge.sh

Script that uses the Universal Installation Merge (UIM) module.

usrmode.inc

User-mode installer main script.

unvfiles.tar

User-mode installer modules archive; a set of scripts loaded and executed by usrmode.inc.

unv-python3.7.tar

Python 3.7 Distribution for Universal Agent.

...

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.

UAG is activated using the Universal Agent for AIX Installation# --oms_servers parameter.

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.

OMS is activated using the Universal Agent for AIX Installation# --oms_autostart parameter.

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.

Universal Controller command line programs are installed using the Universal Agent for AIX Installation# --opscli parameter.

Third-party components

Not installed.

This category includes components not developed or maintained by Stonebranch, Inc.
 
For example, Universal Agent 7.12.0.0 provides a Python 3.7 distribution that can be installed under the Universal Agent install directory. This distribution is provided so that a reliable Python environment exists on systems that may not provide for all users.

...

To start the unvinst installation script and install all of the AIX packages, issue the following command:

Panel

See Universal Agent for AIX Installation#AIX Installation Script Parameters and Universal Agent for AIX 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
titleNote

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

...

An entry is added to the system initialization table, /etc/inittab, to start the ubrokerd daemon when the system boots to runlevel 2. The inittab entry is similar to the following:

ubroker:2:once:/opt/universal/ubroker-7.1.0/ubrokerd start

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

Note
titleNote

With the Solaris, HP, and AIX installs, the previous installation directories are removed when the native installer has detected that additional directories or files have not been added to the original installation directories. If they have been modified, the directories will remain and can be reviewed and removed, as desired, by your Administrator.

...

The following table describes the optional parameters that are available in the installation script, unvinst, when installing Universal Agent.

The parameters are grouped into the following categories:

...

Category

...

Description

...

Universal Agent for AIX Installation#Base

...

Used for base install.

...

Universal Agent for AIX Installation#OMS

...

Used for an active OMS configuration.

...

Universal Agent for AIX Installation#UAG

...

Used for an active UAG configuration.

...

Universal Agent for AIX Installation#CLI

...

Used for Universal Controller CLI programs install.

...

Universal Agent for AIX Installation#User Mode

...

Used for user mode installation.

...

Universal Agent for AIX Installation#Third-party

...

Used to manage third-party components.

...

Parameter

...

Description

...

Default

...

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.

...


Html bobswift
<pre>
sh ./unvinst [--user <i>username</i> [--userdir <i>directory</i>] [--create_user {<b>yes</b>|<b>no</b>}] ] [--group <i>group name</i> [--create_group {<b>yes</b>|<b>no</b>}] ] 
             [--keystore {<b>yes</b>|<b>no</b>}] [--convert_opsagent [--opsdir <i>directory</i>] ] [--oms_servers <i>network address</i>] [--oms_port <i>port</i>] 
             [--ac_agent_clusters <i>clusters</i>] [--ac_agent_ip <i>IP address</i>] [--oms_autostart {<b>yes</b>|<b>no</b>}] [--ac_netname <i>ID</i>] 
             [--ac_extension_accept_list <i>list</i>] [--ac_extension_python_list <i>list</i>] [--ac_extension_deploy_on_registration {<b>yes</b>|<b>no</b>}] 
             [--ac_extension_cancel_timeout <i>value</i> {<b>s</b>|<b>m</b>|<b>h</b>|<b>d</b>}] [--ac_process_cancel_timeout <i>value</i> {<b>s</b>|<b>m</b>|<b>h</b>|<b>d</b>}]
             [--uag_autostart <i>yes</i>] [--opscli {<b>yes</b>|<b>no</b>}] [--usermode_install {<b>yes</b>|<b>no</b>} [--unvdir <i>directory</i>]
             [--unvcfgdir <i>directory</i>] [--unvdatadir <i>directory</i>] [--unvport <i>port</i>] [--python {<b>yes</b>|<b>no</b>}]  ]
</pre>


See AIX 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
titleNote

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


This is a silent install. The output from unvinst is written to file install.log in the current directory.

An entry is added to the system initialization table, /etc/inittab, to start the ubrokerd daemon when the system boots to runlevel 2. The inittab entry is similar to the following:

ubroker:2:once:/opt/universal/ubroker-7.2.0/ubrokerd start

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

Note
titleNote

With the Solaris, HP, and AIX installs, the previous installation directories are removed when the native installer has detected that additional directories or files have not been added to the original installation directories. If they have been modified, the directories will remain and can be reviewed and removed, as desired, by your Administrator.

Anchor
AIX Installation Script Parameters
AIX Installation Script Parameters
AIX Installation Script Parameters

The following table describes the optional parameters that are available in the installation 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 AIX installed with the installation script, unvinst, and optional parameters.
 

...

‑create_user
‑‑create_user‑userdir
‑‑userdir‑‑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 this group does not exist, the install creates it.
  • If --group is omitted from unvinst, the default is used.
‑keystore
‑‑keystoreUAG Parameters-c
‑convert
‑‑convert_opsagent‑oms_servers
‑‑oms_servers‑‑uagservers

OMS Parameters‑‑oms_autostart

options.

CLI ParametersUser 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 AIX 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

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

Anchor
--group
--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 accountgroup.
  • 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 AIX 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 Universal Agent for AIX Installation#--usermode_install is yes, there is no default.

ubroker

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

Anchor
-userdir-userdir

Home directory for the created user account specified by Universal Agent for AIX Installation#--user.

  • If this directory does not exist, it is created when the specified user is created.
  • If the user specified by Universal Agent for AIX Installation#--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
Anchor
--group--group

ubroker

‑create_group

Anchor
--create_group
--create_group
‑‑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
-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

Anchor
UAG
UAG
UAG Parameters



-c
‑convert

Anchor
--convert_opsagent
--convert_opsagent
‑‑convert_opsagent

Converts an existing Opswise Automation Center Agent (1.5, 1.6, or 1.7) to a 5.2.0 Agent.

The installation process will invoke a script, opsmerge.sh, 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 Universal Agent 7.2.x.x.



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

ubroker

‑create_group

/home/opswise

‑oms_servers

Anchor
--createoms_groupservers
--createoms_groupservers
‑‑create‑‑oms_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-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

Anchor
UAGUAG
Anchor
--convert_opsagent--convert_opsagent

Converts an existing Opswise Automation Center Agent (1.5, 1.6, or 1.7) to a 5.2.0 Agent.

The installation process will invoke a script, opsmerge.sh, 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 Universal Agent 7.1.x.x.

-d
‑opsdir
‑‑opsdir

If Universal Agent for AIX Installation#--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--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
titleNote

You should always include --oms_servers in unvinst; OMS is the network communications provider between Controller 7.1.x.x and Agent 7.1.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_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.

no

‑uag_autostart

Anchor
--uag_autostart--uag_autostart

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
titleNote

You should always include --oms_servers in unvinst; OMS is the network communications provider between 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_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.

no

-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

‑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 the Universal Automation Center Agent (UAG) Server starts automatically when the Universal Broker is started.UAG OMS is started automatically by Universal Broker when Universal Broker starts.

OMS component definition: The value specified by --uagoms_autostart is set automatically for the UAG OMS AUTOMATICALLY_START and RESTART component definition option.

yes

Anchor
OMSOMS

‑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

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



-U
-usermode_install

Anchor
--usermode_install
--usermode_install
--usermode_install

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 optionsfor a user mode installation, which defines both of the following:

no

Anchor

CLICLI

‑opscli

Anchor
--unvdir
--unvdir
-unvdir
Anchor
unvdir
unvdir
--opscliunvdir

If --

opscli‑‑opscli

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

no

Anchor
User ModeUser Mode
Anchor
--usermode_install--usermode_install

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

no

Anchor
--unvdir--unvdir
Anchor
unvdirunvdir

If Universal Agent for AIX Installation#--usermode_install is set to yes: Specifies the Agent binaries (installation) directory.

(none)

Anchor
unvcfgdirunvcfgdir

If Universal Agent for AIX Installation#--usermode_install is set to yes: Specifies the Agent configuration files directory.

<Universal Agent for AIX Installation#--unvdir>/etc

Anchor
unvdatadirunvdatadir

If Universal Agent for AIX Installation#--usermode_install is set to yes: Specifies the Agent data files directory.

<Universal Agent for AIX Installation#--unvdir>/var

Anchor
unvportunvport

If Universal Agent for AIX Installation#--usermode_install is set to yes: Specifies the Universal Broker port.

(none)

Anchor
Third-partyThird-party
Anchor
pythonpython

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

...

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

A user mode installation, implemented through use of the Universal Agent for AIX 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 AIX Installation#--usermode_install

yes

Universal Agent for AIX Installation#--user

A username that is different than the username specified for any other Agent installation on this machine.

Universal Agent for AIX 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 AIX 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 AIX 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 AIX Installation#--unvdir

Installed

--unvdir

/opt/universal

Agent binaries

--unvcfgdir

/etc/universal

Agent configuration files

--unvdatadir

/var/opt/universal

Agent binaries

Universal Agent for AIX Installation#--unvcfgdir

/etc/universal

Agent configuration files

Universal Agent for AIX Installation#--unvdatadir

/var/opt/universal

Agent data files

...

If security is set to PAM, the pam.conf file under /etc must be modified.

Below is the minimum required PAM service definition to make Universal Agent function:

ucmd

auth

required

/usr/lib/security/pam_aix

ucmd

account

required

/usr/lib/security/pam_aix

Listing Universal Agent for AIX Information

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 AIX, issue the following command:

...

Removing Universal Agent for AIX

System Install Removal

data files

Step 1

Stop the ubrokerd daemon.

Step 2

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

Step 3

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

Panel
Panel
Panel

Anchor
AIX PAM Customization
AIX PAM Customization
AIX PAM Customization

If security is set to PAM, the pam.conf file under /etc must be modified.

Below is the minimum required PAM service definition to make Universal Agent function:

ucmd

auth

required

/usr/lib/security/pam_aix

ucmd

account

required

/usr/lib/security/pam_aix

Listing Universal Agent for AIX Information

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 AIX, issue the following command:

Panel


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


Removing Universal Agent for AIX

System Install Removal


 

Step 1

Stop the ubrokerd daemon.

Step 2

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

Step 3

Using the superuser ID, remove all Universal Agent for AIX 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
</pre>



Step 4

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

Panel
Panel


Html bobswift
<pre>
rmuser ubroker
</pre>



Step 5

Delete the Agent group (ubroker):
 

Panel


Html bobswift
<pre>
rmgroup ubroker
</pre>



User Mode Install Removal

panel

:
 

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
Panel
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>
rmgroup [Usermode Broker group]
</pre>




Note
titleAgent

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.

...