New Functionality in the 1.1 Release

This section covers the following functionality:

• Installing the SDS and Agent in Zones

• Patching in Zones

• Adding Solaris Software With a Script

Installing the SDS and Agent in Zones

The SDS should only be installed in one zone on a system, either a global or non-global zone. The agent can be installed on any zone. The installer does not have to know on which zone it is installed.

If you are planning to install an agent in a non-global zone, an agent must also be installed in the global zone (CR 6511890)

Before determining where to install the agent, consider the following Solaris zone patching rules:

• When an agent is installed in a sparse zone, it is not possible to install packages or patches which require updates to the /usr directory. This is because the /usr directory is designed to be read-only in a sparse zone and is shared with the global zone.

• Some patches installed in the global zone will also affect the local zones.

Patching in Zones

The zones hierarchy displays as a group and members of the group, for example if HostA has two non-global zones, it is displayed as HostA_zone_group [3]. Expand HostA_zone_group [3] to see the two non-global zones. The SDS automatically creates the group HostA_zone_group [3] and populates it with with registered agents from all of the zones on the system.

Before patching Solaris zones, you should be familiar with how zones are designed to work. An update can be installed in a non-global zone without being installed in a global zone, and vice versa. When patching to zones, some patches will not install in non-global zones (sparse or full) and others will. Some patches that are installed in the global zone do not affect non-global zones directly, but others do affect non-global zones. Within the constraint of the update itself. The packaging of the component defines whether it needs to be in the global zone or not. Under zones, there is just one instance of the Solaris OS, which means that usually components belonging to the OS runtime (kernel, services) must be updated in the global zones. The update meta-data, but not the bits, is propagated to the non-global zones.

See CR 6533814.

Adding Solaris Software With a Script

The directory change impacts the CLI procedures that are used for Solaris software. In this procedure, you will use a script from the Sun Connection CLI application to upload Solaris software. Use this procedure if you are unfamiliar with Solaris commands and having trouble unpacking the PKGs or tarring the directories.

Before You Begin

Install the latest Sun Connection CLI.

The script is located at /opt/SUNWuce/cli/bin/uce_cli.sh.

To Upload Solaris Software With CLI

1. Change to the following directory by typing:

   cd /opt/SUNWuce/cli/bin/

2. Type the following command:

   uce_cli -upload_files -D OS-version_architecture -T file1[,file2] -u admin

   Where the file1 and file2 are absolute pathnames.

3. Type a password for the Sun Connection admin user.

4. For the channel, type the number of the distribution-architecture, according to the displayed list of Available Channels, to which the packages you want to upload belong.

5. At the prompt Would you like all found components to be added under specific category?, type y to put the packages in a user-defined category, and then at the Category name prompt, type the name of the category.

   If the category does not yet exist in the Sun Connection components list, it will be created. If you type n, the packages are added under a default category in the components list.

   uce_cli.sh will tar the Solaris package directories. Then it uploads the tarballs to the knowledge base. Sun Connection recognizes them as Solaris packages and enables you to deploy them as PKGs.