JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Packaging and Delivering Software With the Image Packaging System in Oracle® Solaris 11.2
Oracle Technology Network
Library
PDF
Print View
Feedback
search filter icon
search icon

Document Information

Using This Documentation

Chapter 1 IPS Design Goals, Concepts, and Terminology

Chapter 2 Packaging Software With IPS

Chapter 3 Installing, Removing, and Updating Software Packages

Chapter 4 Specifying Package Dependencies

Chapter 5 Allowing Variations

Chapter 6 Modifying Package Manifests Programmatically

Chapter 7 Automating System Change as Part of Package Installation

Chapter 8 Advanced Topics For Package Updating

Avoiding Conflicting Package Content

Renaming, Merging and Splitting Packages

Renaming a Single Package

Merging Two Packages

Splitting a Package

Obsoleting Packages

Preserving Packaged Editable Files that Migrate

Preserving Unpackaged Files

Moving Unpackaged Files on Directory Removal

Packaging the Directory Separately

How to Preserve a Directory After Content Uninstall

Sharing Content Across Boot Environments

Existing Shared Content in Oracle Solaris

Delivering Content to a Shared Area

How to Enable Your Application to Use a Shared Area

How to Migrate Unshared Content to a Shared Area

Delivering a File That Is Also Delivered by Another Package

Delivering Multiple Implementations of an Application

Attributes of Mediated Links

Specifying Mediated Links

Best Practices for Mediated Links

Chapter 9 Signing IPS Packages

Chapter 10 Handling Non-Global Zones

Chapter 11 Modifying Published Packages

Appendix A Classifying Packages

Appendix B How IPS Is Used To Package the Oracle Solaris OS

Delivering Multiple Implementations of an Application

You might want to deliver multiple implementations of a given application with the following characteristics:

Oracle Solaris 11 delivers multiple implementations of several different applications, such as Java and Python. To specify which implementation is available from a common directory such as /usr/bin, and to enable an administrator to easily change that selection, use a mediated link.

A mediated link manages multiple implementations of an application in a single image. A mediated link is a symbolic link with mediator attributes set (see Attributes of Mediated Links). Software that is packaged with a link action that has mediator attributes is a participant in a mediation. The mediation participant that is available from a common directory such as /usr/bin is called the preferred version. The preferred version in a mediation is determined in one of the following ways:

Specified in the package manifest

You can specify a version (mediator-version) or a versioned implementation (mediator-implementation) for each participant in the mediation. You can specify an overriding priority in case of conflicts (mediator-priority).

Selected by the system

If a participant in the mediation has a priority specified, the participant with the highest value priority is selected as the preferred implementation.

If no participant in the mediation has a priority specified, and a participant has a version specified, the participant with the highest value version is selected as the preferred implementation.

If no participant in the mediation has a priority or version specified, an arbitrary participant is selected as the preferred implementation. If the mediator-implementation of the selected participant includes a version string, the participant with the highest value version string for that mediator-implementation is selected as the preferred implementation.

Specified by an administrator

An administrator can set the preferred implementation by using the pkg set-mediator command. See Specifying a Default Application Implementation in Adding and Updating Software in Oracle Solaris 11.2 .

If only one instance of a particular mediation is installed in an image, then that instance is automatically selected as the preferred implementation of that mediation. If the preferred implementation is set by a system administrator after package installation, installing additional participants in this same mediation does not change the preferred implementation set by the administrator.