test

Sun WorkShop Quick Install

Choosing a License Server Configuration

This release of Sun WorkShop supports the following types of licenses:

There are the following possible license server configurations:

Note -

Personal Edition (node-locked) licenses can use a single independent or a redundant server configuration.

For examples of license server configurations, see Chapter 1 in Sun WorkShop Installation and Licensing Reference.

Personal Edition and Floating Licenses

This release of Sun WorkShop supports a node-locked (Personal Edition) license, where the licensed software only runs on the machine (the node) to which the software is locked. The machine where the licensed software is installed is the application server, and the machine running the license daemons is the license server. With a node-locked license, the license server and the application server might be the same machine, and only one user can run the application on the machine at any one time.

With a floating license, developers can access licensed software simultaneously over the network through FLEXlm license manager software. When two or more users invoke the same software product at the same time, they are considered concurrent users. The concurrent user license model makes software available to any user on any computer on a network because licenses are floating and not tied to a specific machine. FLEXlm license manager software monitors and controls access to the software. A license can be checked out by any developer on the network and then returned for others to use. A license is checked out transparently by each user who accesses the licensed software.

Single Independent Server Configuration

A single independent server administers all software licenses. This scenario is suited for sites where programmers, the license server, and application servers are close together on the network. The single independent server configuration is the default and the easiest to install and administer.

Multiple Independent Server Configuration

When you use two or more servers independently, you create a multiple independent server configuration. Using this configuration, you indicate a number of rights to use (RTUs) for each server, and users can obtain a license token from any one of the servers. This scenario is most common for medium to large software development environments distributed over a network.

Distributing the total number of license tokens among multiple license servers increases the likelihood that at least some license tokens will always be available; any license tokens served by computers that are offline are unavailable until those machines are returned to the network.

Redundant Server Configuration

A redundant server configuration enables you to have three servers acting as one logical server managing a set of license tokens. This configuration requires that two of the redundant license servers be operative and able to contact each other. If the redundant servers cannot contact each other, none of the license tokens are available.

At any point, one of the redundant servers is the master server, the one that actually issues license tokens with a heavier processing load. If the master server is unavailable, then the next available peer in the configuration becomes the master server.

Note -

Once you have selected the machine to be used as a redundant license server, that machine cannot be used in a different licensing configuration.

The main advantage of redundant servers is an increased likelihood that if any tokens are available, then all tokens are available. The cost is increased installation and maintenance complexity.