...
Step 1 | From the Stonebranch Customer Portal, download the Agent product distribution file that is appropriate for your platform (for instructions, see Product Distribution File Download). |
|---|---|
Step 2 | Install the Agent. For details, see Universal Agent for UNIX Installation. |
Step 3 | If you are installing the Agent on AIX or Linux, you must review and perform PAM customization: If you are upgrading the Agent on an Intel-based Solaris system, you must follow the update procedure described below (See Upgrading Universal Agent for Intel-Based Solaris Systems). |
Step 4 | Verify that the Agent is installed and running. If the Agent is configured to communicate with a Controller, verify that the Controller shows the Agent as being online (see Verifying Universal Agent Installation). |
...
| Note | ||
|---|---|---|
| ||
During a UNIX system mode install upgrade, the installation logic creates .archive directories (if they do not already exist) under the If you take your own configuration or component definition file backups prior to upgrading a Universal Agent install, be sure to save them outside of the |
| Anchor | ||||
|---|---|---|---|---|
|
Overview
In versions 7.5.x.x and earlier, all Universal Agent components (on Intel-based Solaris systems) were built on a 32-bit, little-endian Solaris Intel machine. With the release of 7.6.x.x, we have transitioned to a more robust 64-bit, little-endian Solaris Intel machine.
Implications of the Change
This transition, while offering numerous benefits, also means that the persistent data stored on disk by the components from previous releases is no longer compatible with the new release. Specifically, the binary format used for persistent data in earlier versions does not align with the new 64-bit architecture.
The following components are affected:
- OMS Server: creates message data files (in binary format) and persists them to disk to ensure message reliability. These files are not designed to be portable. See OMS Server Message Database.
- UAG: creates a job file (in binary format) for each task and persists it to disk until the task is completed.
Pre-Upgrade Steps
Before starting the pre-upgrade steps, ensure the Solaris Intel machine being upgraded is not executing any tasks. Verify that there are no tasks in either Queued or Running status, as any such tasks will be lost and cannot be recovered.
- Restart the Universal Broker by running
/opt/universal/ubroker/ubrokerd restart - Once the broker restarts, both OMS and UAG will process the persistent data written to disk. Do not move on to the next step until you see message
UNV6312Iin/var/opt/universal/log/unv.logandOPSAGT029Iin/var/opt/universal/uag/logs/agent.log - Suspend any Agents running on the Solaris Intel machine being upgraded.
- Suspend the OMS server running on the Solaris Intel machine being upgraded. This may not be necessary if the OMS server is on a different system.
- Stop the Universal Broker by running
/opt/universal/ubroker/ubrokerd stop - Delete any
.datafiles in/var/opt/universal/spool/oms - Delete any
_jobfiles in/var/opt/universal/uag/cache
Performing the Upgrade
After completing the above pre-upgrade steps, you may proceed with the standard upgrade process detailed in the previous section. Upon successful upgrade, make sure to Resume the suspended Agent(s) and OMS server.
| Anchor | ||||
|---|---|---|---|---|
|
...