Technical article 104850

Differences between the new OpenServer 5 and old licensing schemes

OpenServer 5.0.0

Written · Last revised

Problem

How is the new SCO OpenServer 5.0.0 licensing different from previous releases?

Solution

The differences between the old serialization/branding scheme and the new scheme employed in the SCO OpenServer Release 5 line of products can be summarized as follows:

Release       Type of License          When Licensing Occurs
-------       ---------------          ---------------------
pre-5.0.0     file "branding"          installation
5.0.0         dynamic request          runtime
              fulfillment

Thus the old scheme, which might be aptly called "installation licensing", works by stamping or "branding" files at install time, activating them for all future runtime use. In contrast, the new scheme, "runtime licensing", works by creating a license database independently of the licensable binaries, which are never branded or touched. This database is created when the License Manager is run on behalf of the licensable product, but the binaries corresponding to these licenses are not really activated using the licenses _until they run_.

When a licensable binary is run, the binary requests a license
of the license demon, which obtains this license from its
license database, effectively passing it to the binary.  This
dynamic activation of the binary occurs each time a copy of it
is run, until the user limit, or some other policy-enforced
limit for this product, is reached.
A natural consequence of this scheme is that "licensing" a
product through the License Manager (creating the licenses)
is independent of installing the product through the Software
Manager.  It is not the responsibility of the licensing subsystem
to check that the corresponding product is installed, or even to
check that the license information being entered _corresponds
to a valid product_.  (However, currently the License Manager
only lists installed products as selections to which licensing
options may be applied; this is to reduce confusion over the
new idea of having licenses on a system without the corresponding
software, as well as to maintain consistency with the behavior
of ScoAdmin clients, in which actions/options are applied to
specific selected objects.  This restriction will be lifted in
future releases, when License Servers are implemented as
discussed in item 1 below.)  These characteristics are desirable
for two reasons:
1. It enables the concept of a License Server to be implemented
on SCO OpenServer Release 5. (NOTE: This has not been actually
implemented yet).  The scheme will facilitate this by allowing
licenses for various products to be kept on a single machine
for check-out by various license clients running the
corresponding installed software.
2. It gives developers of licensable products more freedom
in defining different versions of their products, with minimal
modification of the product files, _and_ of the media packaging
of the products.  Thus, developers have the flexibility to
create different licenses for different versions of their
product, with little or no impact on their source/distribution
files.  Any of these licenses may be accepted by the License
Manager, and any of the associated software components may be
allowed to install via the Software Manager from the "master"
media.  This makes the administration of installable software
more flexible for system administrators, and simpler for the
vendor.  It is then the task of the Policy Manager to determine
that the installed product is also properly licensed.

Furthermore, they also have the flexibility to modify the way in which their products are activated (for example, to allow a Desktop version of the product to run on a Server-based operating system) independently of the product files as well. They need only modify the policies associated with these product versions (currently through the Policy Manager API).

From the Xinuos technical article database, record 104850. Reproduced with permission. The original is at www.sco.com/ta/104850, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.