This article describes how to upgrade an existing Sun Update
Connection - Enterprise installation to a higher version. The system dependency
server (SDS), proxy SDS, console, CLI, and agents must all use the same version.
The agent for each channel must be upgraded. A channel is the operating
system version and the hardware architecture of one or more managed hosts: for example, a Solaris 10 Operating System (Solaris OS) distribution on the x86
architecture or a Linux RHEL WS 3.0 distribution on the AMD64 architecture.
The upgrade process usually takes between 5 and 10 minutes for each channel.
The amount of time depends on the type of system used by the local host and the
environment. Before you perform the upgrade, stop or complete outstanding jobs
running and then back up your current installation and files.
Backing Up Your Current Installation
The Sun Update Connection - Enterprise backup.sh
script backs up the databases and saves the following information:
Rules
File settings
Encryption keys
Scripts
Vendor credentials
Note: Do not run the backup script while you have jobs running.
Stop any outstanding and running jobs, or wait for them to complete.
Close all consoles.
Log in to the SDS as superuser.
Change to the /install directory.
# cd /usr/local/uce/install
Run the backup script.
# ./backup.sh
The backup script performs the following tasks:
Stops the Sun Update Connection - Enterprise applications.
Verifies that the local system is the system dependency server.
Saves the data in the following directories and files under backup names:
/usr/local/uce/server/public/* -- Universal rules and components
/usr/local/uce/server/private/* -- Local rules and components
/usr/local/uce/engine/*/bin -- Setting files and encryption keys
/usr/local/uce/install/* -- Application installers, restore and support scripts
Backs up the databases and saves the backup files in a tar
file. The file name includes the year, month, day, hour, and
minute that the backup is created.
Restarts the Sun Update Connection - Enterprise applications.
Complete the following checklist for jobs in the Status window:
Stop all jobs that are running on the host, or wait until the jobs are completed.
Wait for running CLI and API commands to finish.
Verify that the agent application on the managed hosts is not busy with any task.
Verify that the agent application on the managed hosts is up and running.
Exit from all consoles.
Upgrading Your Components
To upgrade your existing Sun Update Connection - Enterprise 1.0.x software to a newer version, upgrade the following components in order:
Upgrade the System Dependency Server
Upgrade the console, CLI, and proxy SDS
Upgrade the agents, either by using the console or by manually running the script on each host
Note: Before you start the upgrade, verify that you do not have any jobs, CLI, or API commands running.
Upgrade the System Dependency Server
Log in to the SDS as superuser.
Upgrade the SDS.
Download the Sun Update Connection - Enterprise 1.0.x
tar bundle, extract it to a temporary directory, and execute the
./ezInstall script.
The ./ezInstall script starts
the installation program.
Follow the onscreen prompts to install the new version of the Sun Update Connection - Enterprise software.
A warning message similar to the following is displayed.
Found existing license file. Would like to use an alternative license file?
If you are using your existing license, select No and then press Enter to continue.
Provide information to complete the upgrade.
The ezInstall script completes the upgrade as follows:
Checks your connection to the SDS and configures ports
Upgrades the SDS
Upgrades the knowledge base and the dependency manager
Prepares files for the installation of the agents, the console, the CLI, and the proxy SDS
When the upgrade process completes, a confirmation message is displayed.
Press Enter to exit the ezInstall script.
Upgrade the Console, CLI, and Proxy SDS
The ezInstall script saves the installation tar files
in the /install directory.
Change to the /install directory.
# cd /usr/local/uce/install
Copy the console-mmdd.tar.gz file to the console system.
Expand the contents of the console tar file.
# tar xPfzv console-mmdd.tar.gz
The uce_console directory is created.
Start the console installer program.
# ./uce_console/Install
To run the non-graphical, non-interactive installation, which is faster, use the -i flag.
The console upgrade is installed.
(Optional) Repeat this procedure to install the CLI.
The CLI tar file is called cli-mmdd.tar.gz.
(Optional) Repeat this procedure to install the proxy SDS. The proxy
SDS tar file is called
proxy-mmdd.tar.gz.
Start the new console.
# uce_console
Upgrade the Agents by Using the Console
A new agent is created during the upgrade process called
agentmmdd.tar.gz. You must upgrade
the agent RPM or PKG software for each channel. You can use the console to upgrade all of
your agents, or you can upgrade each agent manually, as shown here.
Change to the /install directory.
# cd /usr/local/uce/install
Expand the contents of the agent tar file.
# tar xPfzv agent-mmdd.tar.gz
Start the console.
# uce_console
Log in as admin user.
In the Hosts section of the console, select a channel.
Select package or RPM in the Components List.
For a Solaris channel, right-click Local/Local PKGs in the Components List, then choose Add from the Local menu.
For a Linux channel, right-click Local/Local RPMs in the Components List, then choose Add from the Local menu.
The Add Software window opens.
Browse to the new version of the agent software.
For example, UCE_-version-release/rpms/sun-uce-agent*.rpm.
Select the file that matches the platform of the managed hosts.
Note: After the agent is uploaded, it will not
appear in the Local PKG or Local RPM list when the console is in standard mode (uce_console).
Click Apply.
Wait until the software is successfully uploaded to the local knowledge base.
Close the Add Software window.
The agent software is added to the knowledge base, but it is not visible in the Components list.
Repeat steps 5 through 10 for each active channel.
Log out of the console.
Restart the console in upgrade mode.
# uce_console -update_director_mode true
The login window opens.
Log in as the admin user.
The Update window opens.
Update the agents for each channel.
From the Hosts list, select hosts of a single channel.
From the Components list, select the version of the agent software that matches the updated SDS.
Click Install.
The Installing window opens and shows the status of the installations.
Wait until the status icon in the Installed column is a
checkmark in a green circle. This process might take several
minutes for each agent.
Repeat these steps for each active channel.
When you have upgraded each of the agents, close the console.
Start the console in standard mode.
# uce_console
Check that all agents are up and listed as connected in the Hosts list.
Back up the new Sun Update Connection - Enterprise data.
# cd /usr/local/uce/install
# ./backup.sh
Save the backup files for both the previous version and the latest version in a safe place.
Upgrade the Agents Manually
If you do not want to use the console to perform the agent upgrades,
you can manually upgrade the agent on each managed system.
Copy the agent tar file to the managed node.
Expand the contents of the agent tar file.
Change to the /uce_agent directory.
# cd uce_agent
Install the agent.
# ./Install
Note: The -i flag is supported for silent install.
Unless otherwise licensed, code in all technical manuals herein (including articles, FAQs, samples) is provided under this License.
Print-friendly Version
