Installing Your Licenses |
4 |
![]() |
A license can be checked out by any developer, at any computer on your network and then returned for others to use. A license token is checked out transparently by each user who accesses a product. When two or more users invoke the same application at the same time, they are considered "concurrent."
Depending on your licensing needs, configure your license servers using the criteria described in Section 4.1.1, "Single Independent Server Configuration," Section 4.1.2, "Multiple Independent Server Configuration," and Section 4.1.3, "Redundant Server Configuration." Once you have selected the machine as a redundant license server, that machine cannot be used in a different licensing configuration.
For additional licensing information, refer to Appendix B, "General Licensing Information."
4.1.1 Single Independent Server Configuration
A single independent server administers all product licenses. This scenario is best suited for sites where programmers, the license server, and product servers are all fairly close together on the network. 4.1.2 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. 4.1.3 Redundant Server Configuration
A redundant server configuration enables you to have three servers managing a set of license tokens, in essence acting as one logical server. This configuration requires that a majority of redundant license servers be operative and able to contact each other. If the redundant servers cannot contact each other, none of the license tokens will be available.
4.2 Installing Your Licenses
You can use either a graphical user interface (GUI) or command-line interface to install your WorkShop products, depending on your preference. You can use a GUI by bringing up workshop_install and selecting the Install Licenses button to bring up a Motif interface of the License Installation Tool (lit). If you want to use a command-line interface you will invoke lit_tty.
Prior to installing your licenses, you must also install the license software. Use Chapter 3, "Installing Product Software," to install the license software on each license server. Once you install the FLEXlm licensing software, you can proceed with installing your licenses.
Note - Your CD-ROM name depends on the platform for which you purchased Sun WorkShop products. For SPARC with Solaris, substitute devpro_v5n1_<platform> with devpro_v5n1_sparc
For Intel with Solaris, use devpro_v5n1_intel
4.2.1 Installation Using the Graphical User Interface
Using workshop_install, you can install your licenses with the file the Sun License Center sent you or with the information they provided via fax or telephone. Use the procedures in the section that corresponds to the response you received from the Sun License Center. 4.2.1.1 Email License File Installation
Note - Your CD-ROM name depends on the platform for which you purchased Sun WorkShop products.For SPARC with Solaris, substitute devpro_v5n1_<platform> with
devpro_v5n1_sparcFor Intel with Solaris, use devpro_v5n1_intel
WorkShop software is not nodelocked; therefore, this field is dimmed.
Note - Hostnames and hostids of previously installed servers appear on the screen automatically. After you select the hostnames and hostids, you cannot change them.
4.3.1 Multiple Independent Server Setup
WorkShop software checks the <installation_directory> for licenses, which by default is /opt. The product software automatically looks for the elementary license file relative to where it was installed.
If you're using either a multiple independent or redundant license server configuration, product servers may be served by more than one license server. Each license server is represented by an elementary license file on the product servers. Each product server must contain at least one elementary license file.
After completing the procedures in this chapter, you should be able to invoke your software products. If you are having difficulty running your tools, consult Chapter 5, "Managing Your Licenses," for troubleshooting information and additional license details.