Special Licensing Needs

Use the following information to accommodate any special licensing needs you may have. For details on using FLEXnet, refer to the Macrovision website at:

http://www.macrovision.com/support/by_catagory/Software_Licensing.shtml

Using FLEXnet Options

An options file enables the license administrator to control the security parameters of FLEXnet. Specifically the license administrator can:

Creating an Options File

Use the desired options listed below to create the options file using any text editor. Ideally, you should keep the options file in the same directory as your license.lic file. Also, add the pathname to the options file in the license.lic file as the fourth field on the VENDOR line for agileesofd as shown in the following example. (Remember to use the backslash ('\') character if the file contains wrapped lines.)

 VENDOR agileesofd /iccap2008/licenses/vendors/agileesofd \
/iccap2008/licenses/agileesofd.opt

You can include comments in your options file by starting each comment with a pound sign '#'. Everything in the options file is case-sensitive. Be sure that user names and feature names, for example, are entered correctly. The available options are:

Use the following steps to create and use an options file. Details about each step located in Installing Licenses:

1	Create an options file with your required options.

2	Modify your license.lic file so that the VENDOR or DAEMON line points to this option file as shown in this example:

VENDOR agileesofd /iccap2008/licenses/vendors/agileesofd \
/iccap2008/licenses/agileesofd.opt

3	Start up your license server (lmgrd) that is pointing to your license file. You must stop it first if it is running. It's important that a message is displayed or recorded in the FLEXnet log verifying the license manager is using the options file.

4	Set AGILEESOFD_LICENSE_FILE to point to your license server.

5	Run IC-CAP.

Updating the License File

If you have been running FLEXnet and receive updated codewords from Agilent EEsof, you can add the new licenses to the FLEXnet environment as follows:

1	Replace the existing license.lic files on the license servers and clients with the new license.lic file.

2	On the primary server, run lmutil lmreread. This causes the lmgrd on the primary server to re-read the license.lic file and update all of the other lmgrd processes on the network.

3	After you have done this, you can run lmutil lmstat -a to verify that the license servers have received the new license information.

If this does not work, you may need to stop all of the lmgrd processes on your network and then restart them as described in the section Installing Licenses.

Merging Multiple Vendor Licenses

When you are running FLEXnet-licensed products from multiple vendors, you have three ways to prevent licensing conflicts during installation:

Each lmgrd can only read a single license file. With the first option you will have more license servers to monitor. With the third option you have only one server but multiple lmgrds to administer.

Your product's license file(s) define the license server(s) by hostname and hostid in the SERVER line(s) in the license file.

If you have two or more products whose license servers run on the same node (as specified by the SERVER lines in the license files), you may be able to combine the license files into a single license file.

More precisely, you can combine two license files under the following conditions:

Some possible reasons license files may not be compatible are:

If your license files are compatible as described above, then you can combine license files and run a single lmgrd, as described in Combining License Files from Multiple Vendors. If the license files are not compatible, then you must keep the license files separate and run separate copies of lmgrd for each license file, as described in the section, Using Separate License Files on the Same Server Node.

Combining License Files from Multiple Vendors

If your license files are compatible, you can combine them using any text editor. To combine license files, merge all of the compatible license files into one file, then edit out the extra SERVER lines so that only one set of SERVER lines remains. Write out this data, and you have your combined license file.

If you combine license files from multiple vendors, it is a good idea to keep a copy of the combined license file in each vendor's default license file location. This way, your users can avoid having to set AGILEESOFD_LICENSE_FILE, because each package finds its license information in the default place. On UNIX, you can do this with a symbolic link from each default location to the location of the combined license file.

FLEXnet Version Component Compatibility

When you combine license files for two different FLEXnet-licensed products, the products may not use the same version of FLEXnet. FLEXnet is designed to handle this situation. There are two basic compatibility rules for FLEXnet:

From these two compatibility rules come the simple rules for selecting which version of administration tools to use:

For specific application programs, you can use either the new or the old version (with the assumption that the vendor daemon for that application is at least as new as the application).

Using Separate License Files on the Same Server Node

You must run a separate copy of lmgrd for each license file. When you run multiple copies of lmgrd, there are two details to remember:

When running client programs (such as a licensed application), you can set the AGILEESOFD_LICENSE_FILE environment variable to point to multiple license files. For example, you may have a license file from vendor ABC and a license file from vendor XYZ with incompatible servers. You can place the license file from vendor ABC into:

/user/flexnet/abc.lic

and the license file from vendor XYZ into:

/user/flexnet/xyz.lic

then set the AGILEESOFD_LICENSE_FILE environment variable to point to both of them. The syntax is as follows:

AGILEESOFD_LICENSE_FILE=27000@server1;27000@server2;27000@server3

Note that each path is separated with a semi-colon.

AGILEESOFD_LICENSE_FILE can point to only one license file for FLEXnet v1.x applications.

Redundant License Servers

You can set up a redundant or backup license server(s), in case a primary server is unavailable. If your license.lic file has the maximum number of SERVER lines (three), you have a redundant license server configuration. The license setup is identical to a single SERVER configuration, with the exception that no licenses will be available until a majority of the license servers are running. That is, if you have three SERVER lines, at least two must be up and running before any licenses will be available for checkout. Be sure that the FLEXnet software is loaded and running on each server.

Controlling License Path Settings

The lmutil utility provides the lmpath function which allows direct control over FLEXnet license path settings. You can use lmpath to add to, override, or get the current license path set in the registry. This enables you to change or view path settings without locating individual settings in the Windows registry on the PC or in the FLEXnet registry (.flexlmrc) on UNIX.

The lmutil utility is located in $ICCAP_ROOT/licenses/bin. This location must be in your PATH, or use the following command before running the utility:

cd $ICCAP_ROOT/licenses/bin

The usage for this function is:

lmutil lmpath {-status | -add | -override} {vendor_name |
all} license_path_list

where

-status displays the current license path settings.

-add appends license_path_list to the front of the current license-path settings or creates the list of license-path settings, if it doesn't exist, initializing it to license_path_list. Duplicates are discarded.

-override overrides the existing list of license-path settings with the contents of license_path_list. If license_path_list is the null string, "", the specified list is deleted. For example:

lmutil lmpath -override agileesofd ""

Deletes the value of AGILEESOFD_LICENSE_FILE from the registry.

lmutil lmpath -override vendor2 ""

Deletes the value of VENDOR2_LICENSE_FILE from the registry.

lmutil lmpath -override all ""

Deletes the value of LM_LICENSE_FILE from the registry.

vendor is a string naming a particular vendor daemon name. Affects the value of vendor_LICENSE_FILE. For example, use agileesofd to affect AGILEESOFD_LICENSE_FILE.

all refers to all vendor daemons. Affects the value of only LM_LICENSE_FILE.

license_path_list is the new path setting(s). On UNIX, this is a colon-separated list, and on Windows it is a semi-colon-separated list. If license_path_list is the null string, "", then the list is deleted for the specified vendor. Though you can enter specific license file names, you gain flexibility by entering only a path without a file name. This will include all *.lic files in the same location.

Checking the Status

Before you change license path settings, Agilent recommends that you display the current settings. To display the settings, enter the following commands:

lmutil lmpath -status

The following example status listing is from UNIX and is similar to a Windows listing:

lmpath - Copyright (C) 1989-2004 Macrovision Corporation. All rights reserved. Known Vendors: _____________ agileesofd: /iccap2006icenses/license.lic:/iccap2008/licenses/license.lic _____________ Other Vendors: ______________ /usr/local/flexlm/licenses/license.lic

Changing License Path Settings

When adding or overriding path settings, lmpath sets the FLEXnet entry in the Windows registry on the PC, or changes the file $HOME/.flexlmrc on UNIX. Here are examples of how license settings may appear in each registry:

UNIX:

 AGILEESOFD_LICENSE_FILE = /iccap2002/licenses:/iccap2008/licenses

Windows:

Registry location:

My Computer\HKEY_LOCAL_MACHINE\Software\Agilent\ICCAP_2008

Registry license path setting:

AGILEESOFD_LICENSE_FILE        REG_SZ        C:\ICCAP_2008\licenses

To change license path settings, enter the appropriate command in a Command Prompt on Windows, or a terminal window on UNIX. You can adapt the following examples which change path settings for AGILEESOFD_LICENSE_FILE:

lmutil lmpath -add agileesofd <new_lic_path1>:<new_lic_path2>

lmutil lmpath -add agileesofd C:\<new_lic_path1>;C:\<new_lic_path2>

lmutil lmpath -override agileesofd <new_lic_path>

lmutil lmpath -override agileesofd C:\<new_lic_path>