02sflm6 Install Users

Standard Floating License
Manager
Installation and User’s Guide
SFLM Version 6.0
SILVACO International April 2004

4701 Patrick Henry Drive, Bldg. #2
Santa Clara, CA 95054
Telephone: (408) 567-1000
FAX: (408) 496-6080
Standard Floating License Manager
Installation and User’s Guide
Copyright 2004
SILVACO International
4701 Patrick Henry Drive, Building #2
Phone: (408) 567-1000

FAX: (408) 496-6080
E-Mail: support@silvaco.com
Internet: www.silvaco.com
ii SILVACO International
Notice
The information contained in this document is subject to change without notice.

SILVACO International MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF FITNESS
FOR A PARTICULAR PURPOSE.
SILVACO International Inc. shall not be liable for errors contained herein, or for incidental or
consequential damages in connection with the furnishing, performance, or use of this material.
This document contains proprietary information, which is protected by copyright. All rights are
reserved. No part of this document may be photocopied, reproduced, or translated into another
language without the prior written consent of SILVACO International.
Simulation Standard, ATHENA, Analog Alliance, Legacy, Manufacturing Tools, Automation Tools, SFLM,
VICTORY, Ranger3D, Nomad, VYPER, SmartSpice, PSTATS, UTMOST IV, Measure, DISCOVERY,
MERCURY, Optolith, TCAD Driven CAD, TonyPlot3D, RESILIENCE, Flash, ATHENA, Interpreter,
Interactive Tools, DeckBuild, DevEdit, ANALOG EXPRESS, CELEBRITY, SSuprem3, ATLAS, ATLAS
Interpreter, Luminous2D/3D, MC Implant, S-Pisces, TonyPlot, FastLargeSignal, SmartStats, Ferro,
DevEdit3D Interpreter, Quantum2D/3D, SDDL, Circuit Optimizer, MaskViews, TFT2D/3D, Radiant,
SSuprem4, Elite, FastBlaze, Mocasim, Silicides, MC Depo/Etch, FastNoise, Clarity, Blaze/Blaze3D,
Device3D, Frontier, TwinSim, MixedMode2D/3D, VCSELS, Maverick, Envoy, Giga2D/3D, FastGiga,
Guardian, Scout, FastMixedMode, Laser, Dragon, Expert, Spirit, Beacon, Savage, Harm, Zenith, Vision,
Gateway, Scholar, SN, UTMOST, UTMOST II, UTMOST III, UTMOST IV, PROMOST, SPAYN,
ExpertViews, UTMOST IV, Fit, FastSpice, Twister, Blast, MixSim, SmartLib, TestChip, Promost-Rel,
RelStats, RelLib, Ranger, LISA, QUEST, EXACT, CLEVER, STELLAR, HIPEX-RCR, HIPEX-Net,
HIPEX-RC, Connecting TCAD to Tapeout, SmartCell, SmartCore, SmartModel, and UTMOST IV Spice
Modeling are trademarks of Silvaco International.
© 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, and 2004 by
SILVACO International Inc.
SILVACO International iii

Reader Comments
We welcome your evaluation of this manual. Your comments and suggestions help us to improve our
publications. If you have any responses to the questions below, please let us know. Please write us with
your observations, complaints, bug reports, suggestions, or comments.
• Is this manual technically accurate?
• Are the concepts and wording easy to understand?
• Is the size of this manual convenient for you?
• Do you consider this manual to be readable?
Please add any additional relevant comments.
Send your comments to:
SILVACO International
Attn: Technical Publications
4701 Patrick Henry Drive, Building #2
FAX: (408) 496-6080
E-mail: support@silvaco.com
You can also browse our web page at www.silvaco.com
iv SILVACO International
Table of Contents
Chapter 1:
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1: What’s New in SFLM6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2: Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.3: Overview of SFLM6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.3.1: License Server Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.3.2: License Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.4: Customer Environment Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.4.1: Setting The Path To The Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.4.2: Choosing A Single License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.4.3: Choosing Multiple License Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.4.4: Redundant Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.5: Virtual Private Networks (VPNs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Chapter 2:
Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1: Online Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2: Offline Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Chapter 3:
License Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1: Automatic Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2: Install Locally Saved License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Chapter 4:
The Administration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1: Install New License(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2: Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.3: Re-Register License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.4: Setup Redundant Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.4.1: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.4.2: Setting Up Redundant Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.5: Customize Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.5.1: Verbose Logging/Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.6: Synchronize Server Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.7: Send Test Log Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Chapter 5:
The Reports Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1: List Installed License File(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.2: Show Active User(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.3: Show Valid License(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
SILVACO International TOC-1

Standard Floating License Manager Installation and User’s Guide
Chapter 6:
Support Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Chapter 7:
SFLM6 and SFLM4 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.1: SFLM4 and SFLM6 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.2: License Server ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.3: Upgrading an SFLM4 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.4: User Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Chapter 8:
Frequently Asked Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
TOC-2 SILVACO International

Chapter 1:
Overview
This chapter introduces the license management software SFLM and identifies the particular
operating systems and platforms on which it is supported. An initial introduction to how SFLM6 works
is provided as the reader may be unfamiliar with its principles of operation. The following chapters
provide a step-by-step guide through the first time user installation to show the typical screens that
the installer will face.
1.1: What’s New in SFLM6

The Standard Floating License Manager (SFLM) 6.0 is a major upgrade to previous versions. The key
points are summarized below:
• SFLM6 incorporates a web based front end, and can use either Netscape or Internet Explorer.
• License files are no longer linked to the hostid (in the case of Solaris and HPUX systems) or to a
security HASP key (in the case of Windows or RedHat Linux systems).
• License files are now linked to information derived from the server machine hardware. This
information is sent to the SFLM database through the process of registration, and a license file is
then generated.
• SFLM6 supports Multiple Server Redundancy.
• Multiple license servers may now exist on one system and an application may connect to them to
obtain the license(s) it requires.
1.2: Supported Platforms

SFLM6 currently supports the platforms shown in Table 1-1 which describes the machine platform, the
Operating System (OS) and the acronym used in this manual.
Platform Operating System Keyword
SPARC Solaris 8 and 9 Solaris
HP 9000 HPUX 11.0 HP
x86 RedHat 7.3 and 9.0 Linux
x86 Microsoft Windows 2000 2000
x86 Microsoft Windows XP XP
Table 1-1: Supported Platforms for SFLM 6
SFLM6 uses the web browser that is supported on each platform, Internet Explorer (IE) 6.0 and
Netscape 4.6.
1.3: Overview of SFLM6

The later chapters of this manual describe in detail the installation process of SFLM6, but before we
begin, it is useful to examine a basic overview of the new installation process. This chapter gives a
general overview of the installation process, which consists of a two stage process of “Server
Registration” and “License Installation”.
SILVACO International 1-1

1.3.1: License Server Registration

The first stage is called Registration (also called Activation) and is a means by which a unique
description of the machine acting as a license server is generated and saved in the online SFLM
database. This stage is described in more detail in Chapter 2: “Registration”.
Figure 1-1 shows a simple flowchart of the registration process. Upon entering a password the
registration process is started and the software gathers information about the customers computer e.g.
computer name, hostid, etc. This information, together with the users name and contact information,
would then be transmitted via either http (if online registration is chosen) or by E-mail (if offline
registration is chosen) to the license database. Registration is a process that basically delivers a
unique machine ID number to the SFLM database so that a license can be keyed to it.
Note: The online registration requires that the browser is able to access the www internet.
Figure 1-1: SFLM6 Registration Flowchart
1-2 SILVACO International

Overview
1.3.2: License Installation

When all the registration information is received a license file will be generated and keyed to the
user’s specific machine. The user will then be informed by Silvaco that their license is ready and it can
be obtained by the customer either automatically or by E-mail.
The automatic route is the most convenient as SFLM6 will contact the online SFLM license database
and request a license to be transmitted via http. This license file will be saved locally on the users
machine and no further contact is required.
Note: The online registration requires that the browser is able to access the www internet.
The alternative offline route is to send the license file by E-mail, floppy disk or some other means and
the user then would use a file browser to find this file and load it with their web browser.
Figure 1-2: SFLM6 License File(s) Flowchart

THE SFLM6 license servershould now be able to issue licenses to applications. The following Chapters
give a more detailed graphical illustration of how a user would install the SFLM6 license manager, but
it essentially still follows the two flowcharts shown in Figures 1-1 and 1-2.

1.4: Customer Environment Settings

1.4.1: Setting The Path To The Software
On Windows this is not an issue as the shortcut to start the SFLM6 server contains the path.
On Unix and Linux machines an environment variable must be set in the terminal. The two most
common Unix terminal shells are the C-shell and the Bourne-Again (Bash) shell. In these cases the
following changes are needed:
For C-Shell users the following should be added to their .cshrc file:
set path = ( $path /<vendordir>/bin )
For Bash users the following should be added to their .profile file:
PATH="/<vendordir>/bin:$PATH"
export PATH
Note: /<vendordir> is the path to the top directory of the vendor's installed software.
1.4.2: Choosing A Single License Server

How does an application know the name of the license server from where it is supposed to get a
license?
There are two ways the application will know this; either using a global setting in the installation, or
from a local users environment settings.
Global Setting for All Users

When an application is executed it will look at the contents of the file /<vendordir>/var/
sflm_monitord.cf to find the SFLM server. This file is created during the initial SFLM installation
process, and contains the name of the machine where the installation was run. By default, all the
vendor applications run from the /<vendordir>/ location will use the machine in /<vendordir>/var/
sflm_monitord.cf as the license server. In nearly all installations this will be correct and should be left
alone.
To change the global SFLM setting the system administrator has two choices; either simply edit the
file sflm_monitored.cf and replace the existing server name with the new machine name, or reform the
full SFLM installation again with the environment variable SFLM_SERVERS set to the chosen
machine. For instance on Unix C-shell terminals this would be:
setenv SFLM_SERVERS "sflmserver"

sflm -install
Local Settings for Individual Users

Individual users may choose a particular license server by creating the environment variable
SFLM_SERVERS in their user environment, and giving it the name of their chosen server. This
setting will override the global setting that was created.

Overview
How to Set the SFLM_SERVERS Environment Variable

C-shell Unix and Linux users should add the following to their .cshrc file:
setenv SFLM_SERVERS "sflmserver"
Bash shell Unix and Linux users should add the following to their .profile file:
SFLM_SERVERS="sflmserver"
export SFLM_SERVERS
Windows users should right click on “My Computer”, select "Properties", click on the "Advanced" tab,
and then click on the "Environment Variables" tab. A screen should appear that will allow the setting
of environment variables.
Note: The name "sflmserver" is the machine name of the new license server.
1.4.3: Choosing Multiple License Servers

If the network contains multiple license servers, the user can change the SFLM_SERVERS
environment variable to access all of them. For instance on Unix C-shell:
setenv SFLM_SERVERS "machineA machineB machineC"
The application in this case will first attempt to get a license from machineA, if it fails it will try
machineB and finally machineC.
Note:
1. It is important that spaces exist only between machine names. No spaces are allowed within one
machine name.
2. Each machine has a full SFLM installation which is stand alone. This is not a redundant server
setup.
3. All the servers need to undergo the Registration process.
1.4.4: Redundant Server Setup

If the license server is set up for redundant servers the user should first set up the single server setup
described above. Then one further change is necessary.
The SFLM_SERVERS environment variable should be changed to the three machines set up for
redundancy each separated by the | sign e.g. for Unix C-shell:
setenv SFLM_SERVERS "MachineA|machineB|MachineC"
Note: All the redundant servers need to undergo the Registration process and the license file is specifically generated by the
vendor to allow redundant servers.

Note: No spaces should be present in the SFLM_SERVERS variable.
1.5: Virtual Private Networks (VPNs)

VPNs are becoming very popular today as they allow workers to remain at home while still connected
to the office network through their own internet connection.
To enable SFLM with a VPN setup the ports 3162 and 111 must be open in both directions. These
ports are registered to the SFLM software and are used by it only.
Remote users connected to the internet will be able to access office SFLM servers if these two ports
remain open.

Chapter 2:
Registration
This Chapter describes how the user installs the SFLM software, and how the process of machine
registration is performed using a web browser. This step must be performed by all new users of SFLM6
The first step for all users is to obtain the SFLM6 software from the software vendor, unpack it onto
their machine and install it. Instructions for unpacking the software will be supplied with the software
delivery. After unpacking the software, SFLM must be installed on the machine designated as the
license server.
After unpacking, SFLM6 must be started on the license server.
The SFLM6 installation is performed from a command line on Solaris, HPUX and Linux RedHat
operating systems. As the root user, the following command should be executed:
/<installdir>/bin/sflm -install
where <installdir> is the installation directory where the software was unpackaged.
On Windows platforms InstallShield will take care of this first step, but the user does need to have
administration rights.
Note: Starting the SFLM6 software is the only step that requires either root or Administrator privileges. The rest of the
registration may be from a regular user account.
On all platforms, the user will be prompted to provide a unique password. Some of the web pages for
SFLM6 affect how the license server functions, and therefore we have elected that before they can be
accessed the original password must be given. All other pages which are standard reports will be
accessible to users without this password.
Note: The SFLM password is only for protecting certain SFLM pages; it is not an existing system password.
After installation, the user should bring up a web browser (either Netscape or Internet Explorer) and
type in:
http://servername:3162
in the address bar. Here "servername" is the hostname or machine name of the computer where "sflm -
install" or InstallShield was run.
Note: The web browser does not need to be run on the license server machine. After the “sflm -install”, the user may use any
machine to run the browser, but the "servername" MUST be the machine where "sflm -install" was performed.
When the web browser pops up it should display a page similar to the one shown in Figure 2-1. This is
the beginning of a wizard that will guide the user through the process of registration.
At anytime you may click on “Help” in the browser to provide more information about the current
page.

Note: Existing Silvaco users can unpack the new SFLM6 software on top of their existing SFLM4 installation.
Figure 2-1: Set Password Dialog

The first step is to enter the SFLM6 password that was typed in during the initial software
installation. After entering the password, the wizard proceeds to the next screen shown in Figure 2-2
where the user should decide if they are registering either Online or Offline. If the machine has
access to the internet, in other words if the web browser can access www pages, it is highly
recommended that they choose Online registration. Offline registration should only be chosen if the
machine has no access to the world wide web.
Note 1: For online registration, it is the machine running the web browser that needs access to the internet and not the license
server where SFLM6 was installed.

Registration
Note 2: No direct access to the internet is needed. The machine running the browser can reside behind a firewall as long as
the proxy configuration is set properly.
Figure 2-2: Register License Server Dialog

2.1: Online Registration

When Online registration is chosen the next web page in the installation is shown in Figure 2-3. The
user needs to fill out all 4 fields on this page and select the appropriate vendor name from the software
vendor list at the bottom of the web page.
At this point SFLM6 will also have gathered together the set of machine credentials that will uniquely
describe the server machine. Upon clicking on the Next button all this information will be transmitted
to the central SFLM database automatically via http. This information shall be used to generate the
customers license file and to send it to the appropriate E-mail address. All information is strictly
confidential and secure.
Note: Online registration is available only if the browser can access pages on the www internet.
Figure 2-3: Register Online Dialog

Registration
If this page is completed correctly Figure 2-4 should be displayed. By clicking “Next” on this page you
will complete the process of registration and should show the web page in Figure 2-5. The server "Code
Name" is the equivalent hostid of the server machine that will appear in your license file.
Figure 2-4: Activate Server Dialog

Figure 2-5: Registration Complete Dialog

Registration is now complete and a page similar to Figure 2-6 will appear when you click on “OK”. The
user should now wait until their software vendor informs them that a license file(s) is ready for them
to retrieve.

Registration
Figure 2-6: Main SFLM Home Page

2.2: Offline Registration

When an Offline registration is chosen then we must assume that the user can not access the web
from the server machine or from any other machine on the network. In this case clicking on Offline
registration will result in a web page similar to that shown in Figure 2-7.
Figure 2-7: Offline Registration Dialog

The user must take the Machine Credentials, MachineID and MachineKey information and somehow
send it to their software vendor. Possible means are by E-mail (if by E-mail, it should be sent to the
vendor account manager), floppy disk, and so forth.
For example, the key parts of the page shown in Figure 2-7 that must be sent are:

Registration
Machine Credentials:
0ID0_u8g9WH0xAT19QHq6fgjZN8ilKeR3TlKInBKUa6czYWdr4qU8oxxH7BYpHPoFJySTw2Z+PRA9
X5Zp/3JROFIcTw3w63w//8D1plBHJdSLKN7QJBfWPdkAvtmCAdmwnRohaADq9IHozLSa2LuhPE6q
/vjnjnwWkFJZPG0n9MQroOOuuCjqMmymfEgZpgngb7Sdbs5n5UeOnehjb0NvWQ0PfXI61vMej8zY
OdhWWN48xSWi6vqPoPiDzlpjuPD7IbYter+y4j+hJIGUzZm/W9vOi/moafqWN22MK0C8kknsX6+0
TFaZ6jtgDm+Cs9rki8KGmgB9M6i0V9RGmg6xO9joVPk/7GY96GXjnXOF6/UEk/L9fLHqyDTXerzN
sI6RiTL9+IZDdH0pU9kKoiT4NeV0RWeNcbVT0zGnTaAMPUHeIJuUNKpkllM5Wac8jhcM9MJFMzCk
BY05j1WRIzpq3rA8X0N3I4FZUdyg84dfcEtaVooyW/6oehQdEoyvoTnjZuhe
MachineID shangrila-8327a8e8-fef15c09
MachineKey X7S7 T9C9 4JE0 G17G PZNU WFZ4
At this point clicking “Next” will show the page in Figure 2-8 which cannot be completed at this point.
The Code Name and Activation Code will be issued on receipt of the registration data above. When the
user receives this information they need to return to this page (the Offline registration section) and
enter the Code Name and Activation code.
The user can return to this page at a later date by opening the main SFLM home page (http://
servername:3162), clicking on “Admin”, clicking “Re-register License Server”, clicking “Register
Offline”, and finally “Next”.
When the user enters the codename and activation code they will see a screen similar to Figure 2-5
that lets the user know that the activation was successful. They should click “OK” on this screen to
complete the SFLM activation. The SFLM system is now ready to accept license files.

Figure 2-8: Code Name and Activation Code Dialog

Chapter 3:
License Installation
After registration is completed successfully, the software vendor will inform the user that a license file
is ready. The customer may obtain their license file our Automatic update feature, or they may
receive their license as an E-mail attachment. In either case, the user should then return to their web
browser and open:
http://servername:3162
Click on the “Install New License(s)” option (shown in Figure 2-6) to display Figure 3-1. The
Automatic Update or an Install Saved File options can be chosen from this screen.
Figure 3-1: Install New License Dialog

3.1: Automatic Update

This option will download your license file directly through the web. When you click on this button the
image in Figure 3-2 should appear, and if you accept this then the image in Figure 3-3 will be shown.
Once this is complete the server will be able to distribute licenses. By returning to the Home page,
shown in Figure 2-6, and clicking on “Show Valid License(s)” a list of all available licenses will be
displayed.
Note: The Automatic upload is available only if the browser can access pages on the www internet.
Figure 3-2: Automatic Update Dialog

License Installation
Figure 3-3: Automatic Update Accepted Dialog

3.2: Install Locally Saved License File

This option is designed for those users who had to register their machine offline. Typically these users
would be sent a license by E-mail or floppy disk, which should be saved to their hard disk. Clicking on
this option will open the page in Figure 3-4 where you will be asked to browse to the saved file and load
it.
Figure 3-4: Install Locally Saved License File Dialog

Once this is complete the server will be able to distribute licenses. By returning to the Home page,
shown in Figure 2-6, and clicking on “Show Valid License(s)” a list of all available licenses will be
displayed.

Chapter 4:
Administration Page
The Administration page is accessed by clicking the Admin link on the SFLM home page, shown in
Figure 2-6, contains the main features of SFLM6 which can be customized by the user. Before these
pages can be accessed the user will be prompted to provide a password: this would have been entered
by the user as described at the start of Chapter 2.
There are seven Admin features which shall be described in the following sections.
4.1: Install New License(s)

This feature would be accessed if a new license file is ready to be installed. As an example, if a user
purchases additional licenses of a product, the vendor would first create a new license file, inform the
user, and then the user would use this feature to install the new license file.
4.2: Change Password

When SFLM was first installed on the license server machine, as described at the start of Chapter 2,
you were prompted to enter a password. This page allows you to change this password. First enter the
original or current password, then enter your new chosen password and then re-enter this password to
confirm it.
If you have forgotten your password for the SFLM server you need to reset it outside the web front end.
You will need to be the root or administrator user, on the machine where SFLM was originally
installed, within a Unix shell or DOS window.
/<installdir>/bin/sflm -set-password
You will be prompted to set a password. This operation may be conducted while the SFLM server is
active without causing any problems.
4.3: Re-Register License Server

If the hardware within the license server machine changes, then the machine credentials that identify
that machine as the license server may also change. This may affect the operation of the license server.
This option should be accessed in this event to re-register the machine credentials and reactivate the
license server.
Note: You may need a new license file generated by the vendor if the re-registration process assigns a different codename to
your server. Your codename is shown in the machine IDs list at the bottom of the SFLM webpage http://
servername:3162. For example, in Figure 3-4 it is 0SSMID10001820. This will depend on the extent of the changes on
your machine.
4.4: Setup Redundant Servers

4.4.1: Overview
This feature is available to prevent engineering downtime if for any reason the SFLM6 server or its
machine crashes. If this occurs, applications will hang, all current jobs will be paused and no licenses
can be issued until the server is restarted or the machine is repaired. Although all jobs shall continue

once the license server is restarted, this can be a significant management issue. The SFLM6 redundant
server system is one method to ensure that this problem does not result in any engineering downtime.
The system requires that a minimum of 3 machines be designated and installed as redundant license
servers. The same license file is installed on each machine, and each machine is set up to be the
primary, secondary or tertiary server. When an application requests a license it will attempt to contact
the primary license server in normal system operation.
If it cannot contact the primary server (the machine may have failed) it will then attempt to contact
the secondary server. Users will experience a short pause until the secondary server takes over.
The redundant system requires that at least 2 machines are alive and communicating at any given
time. The SFLM servers communicate to each other on license usage, and when the primary machine
returns to the system it will then take over the license control.
Note: This system is only available to software vendor applications that are SFLM6 compliant and is not backwardly
compatible to older SFLM4 applications. Please contact your vendor to find which of their software versions are SFLM6
compliant.
4.4.2: Setting Up Redundant Servers

This feature is on a “per request” basis, so you will first need to contact your software vendor account
manager and request this licensing option.
There are 4 steps to set up redundancy.
1. Run "sflm -install" as described before on all three machines.
2. Bring up a web browser on each machine, type in the URL http://machinename:3162/" (where
machine is the hostname of the machine), and then go through the registration procedure that will
be initiated. Then wait to be contacted by your vendor.
3. Your vendor will inform you when your license file is ready to be downloaded. When you receive
this message open your web browser at "http://machine:3162/" and click on "Install new
License(s)". Download the license file from your vendor and install it with the web browser.
Note: This license file must be installed on all the chosen redundant servers one at a time.
4. When steps (1-3) are completed, open your web browser at "http://machine:3162/", click on “Admin”
and then "Setup Redundant Servers". The screen shown in Figure 4-1 should appear. To add a
server, type in the SFLM server name of each machine chosen to be a redundant server and click
“Add” (The SFLM server name is shown at the bottom of the web browser). The order that servers
are shown in the Server list will decide which is primary, which is secondary and so on. The order
may be changed at any time by first selecting a server from the list and then using the control
buttons on the right hand side (Move to Top, Move Up, Move Down, Move to Bottom, Delete). If
communication is broken with a server this will be shown on the Redundant Groups line by a line
drawn through the name of the server for which communication has been lost.
Note: Step 4 must be performed on each of the redundant servers. The servers will then be able to communicate with each
other and this will be displayed in the bottom of the web browser SFLM6 page on the line "Redundant Groups".

Administration Page
Note: The environment for each user then needs to be changed to specify the redundant server names. Please refer to
Section 1.4.4:“Redundant Server Setup” for more information.
Figure 4-1: Set Up Redundant Servers
4.5: Customize Logging

Any action that SFLM6 performs, such as a license check out or check in, can be logged to a file for later
reference. Such information can be of great use to users who wish to study license usage rates for
different products, or to examine any warnings or errors that are produced. All the necessary data will
be in this file.
To access this feature, first click on “Admin” and then “Customize Logging” and the page shown in
Figure 4-2 should appear. This page controls two log locations; one in the system log (e.g. /etc/
syslog.conf on Solaris machines) and one in a user-defined file.
The default system log level is "notice" for both, but they may be set independently of each other. A
description of available logging levels is given at the bottom of this page.

Figure 4-2: Customize Logging
Master Log Level

Controls minimum logging level for both the system log and the user log.
System Log Level

The pull down menu allows the logging level to be changed from the default "Notice". Note that the
minimum log level is controlled by the Master log level.
Filename
The user may define a file to save the SFLM messages into. The default is no user logging file and so it
is set to "(null)".
Log Level
This pull down menu controls the individual logging level for the user defined log file. Note that the
minimum log level is controlled by the Master log level.

Administration Page
4.5.1: Verbose Logging/Messaging

By default, this is "off". Switching this to "Yes" will result in a much longer description of the SFLM
output which is normally not required.
All the defaults may be restored by clicking on the “Reset Form” button, and the user may save any
changes by clicking on the “Save Changes” button.
Table 4-1: Logging Levels in SFLM 6
Off No logging is performed.
Emergency A panic condition.
Alert A condition that should be corrected immediately.

Examples of this include:
Errors contained in the license file(s) will be reported. This could occur if the file
has been corrupted or if it has been edited (which is not allowed).
SFLM is installed on a system not specified in the license file.
System clock has been changed.

License(s) close to expiration will be reported.
License(s) that will only be active at a time in the future.
SFLM server exits.
Server is low on memory.
Critical Critical conditions.

Examples of this include:
Hardware failure such as a hard disk error.
Memory corruption.
Error Errors.
Examples of these include:
Cannot get MAC address.
Unable to register program.
SFLM installation failure.
Warning Warning messages. Typically non fatal.

Examples include:
Unterminated string received by server.
Obsolete license(s).
Notice Conditions that are not error conditions, but that may require special handling.
Examples include:
Notice that verbose mode is turned on.
Attempt(s) to connect to a port.
The machine identification has changed perhaps due to new hardware.
Server status is in the process of being cleared.
Reading of a particular license file.

Table 4-1: Logging Levels in SFLM 6
Informa- Informational messages.

tion Examples of these include:
License check out and in. This information contains the
username, machine name, product name and process ID.
Other requests that can be safely ignored.
Debug Messages that contain information normally of use only when debugging a pro-
gram.
4.6: Synchronize Server Time

A logical clock is kept by the SFLM server software which can sometimes stray from the local system
clock. This option will synchronize the logical time with a clock at your vendor. Only access this feature
if the times are 1 hour or more apart.
4.7: Send Test Log Message

SFLM6 logs license requests and license release info as detailed in the customized logging section. The
user may send a test message with this particular option to establish that the logging customizing has
succeeded.

Chapter 5:
Reports Page
The reports page is accessed by clicking the reports link on the home page (see Figure 2-6), and gives
the user access to 3 different reports which provide detailed information that the license administrator
may require.
5.1: List Installed License File(s)

SFLM6 allows multiple license files to be loaded concurrently. This report shows a table where each
row gives a report on an individual license. The columns report the license filename, the license ID
number and the current status of the license.
1. The license filename gives the current location of the license file on the license
server machine.
2. The license ID is a unique identifier for the license that your vendor has provided.
If you contact your vendor regarding licensing or general support then you should
know this license ID number before you contact them.
3. The status column will report the active and expired machine IDs that are found
in that license file. These IDs identify the machine(s) where the license may be
installed.
5.2: Show Active User(s)

This option will generate information on licenses that are currently checked out from the SFLM server.
A table will be produced that has four columns; username, job number, host name and product name.
The total number of jobs will also be given which represents the sum of all licenses that are currently
checked out by current users.
1. User name will be the username of someone who has checked out a license from SFLM.
2. Each time an application is run the operating system assigns an ID to that job. Job
number will be the process ID number of the application on a particular machine.
3. The Host is the hostname or machine name where an application is running.
4. The Product information contains the license code for a product and the name of that
product.
5.3: Show Valid License(s)

This option will generate a table which contains a complete list of all licensed applications. This list is
derived from all the license files that have been installed on the server. Each row of this table is
dedicated to one application and gives three columns of information; license information, product
information and user information.
1. License information shows total licenses of that product and the number of unused
licenses still available.
2. Product information shows the product license code and the product name.
3. User information shows a list of users who have checked out a license for that
particular product. Users are identified by their login name, the process ID for the
job and the machine name where the application is running.

[This page intentionally left blank.]

Chapter 6:
Support Utilities
The support utilities are intended to be used whenever the license server has a problem and will not
issue a license to a user request. It is not a part of the general operation of the SFLM license server.
Four utilities are available that report information, and may be used to find what the problem is; list
environment variable, redundant server status, server resource usage and server status & version.
The information from these 4 options should be supplied to your vendor if or when it is requested.
They are accessible through the web interface to your license server.


Chapter 7:
SFLM6 and SFLM4 Compatability
7.1: SFLM4 and SFLM6 Applications

A common occurrence will be the existence of networks that have a mixture of SFLM4 and SFLM6
applications that need to be used. An SFLM4 application is a product that was compiled with the
libraries that correspond with an SFLM4 license server. An SFLM6 application is a product that was
compiled with the libraries that correspond with an SFLM6 license server. This section will explain
how the two will interact on one system.
If an SFLM4 license server is running on the system it will only be able to serve SFLM4 applications
and will NOT be able to serve licenses to SFLM6 applications.
If an SFLM6 license server is running on the system it will be able to serve both SFLM4 and SFLM6
applications.
7.2: License Server ID

SFLM4 used either the hostid (from Solaris and HPUX operating systems) or a HASP key (dongle) to
tie (or key) the license to a particular server. SFLM6 now uses an online registration process to provide
a virtual hostid for all platforms.
7.3: Upgrading an SFLM4 Installation

SFLM software is organized so that it can be unpacked on top of an existing SFLM4 installation. If the
SFLM4 server is already running, installing the SFLM6 version on the same machine will first
terminate the SFLM4 server, and then install the SFLM6 software.
The SFLM6 software has pre-prepared license files to ensure that there is no downtime for existing
customers. After registering their server online, they should receive an immediate response from
Silvaco informing them that their license file is ready to download.
7.4: User Environments

Silvaco programs that have been linked with SFLM4 libraries all used an environment variable
SFLM_SERVER to identify the name of the license server.
This variable, although still supported by SFLM6, has been superceded by SFLM_SERVERS because
it can support multiple servers, as described in Section 1.4:“Customer Environment Settings”.
In cases where there is a mixture of both older SFLM4 and SFLM6 applications both variables need to
be set.
Note: The same is true on Windows platforms, except that on this platform there are two files called var/sflmserver and var/
sflmservers that contain the name of the license servers.


Chapter 8:
Frequently Asked Questions
How do I bring up the web front end to SFLM?

Before the web front end can be brought up, the SFLM application software must first be installed. On
Unix, this is done by running the command:
sflm -install
as root on the license server machine. Then the user can open a web browser (e.g. netscape or internet
explorer), and for the URL you should type:
http://server:3162/
and replace the name "server" with the hostname of the machine where "sflm -install" was executed.
The web front end should now appear.
What version of SFLM do I have?

To find the version of SFLM on your machine run the command:
sflm -WVs
If the version reported back for the rpc.sflmserverd is less than 6.0.0.R you need to upgrade.
What is registration?
SFLM6 no longer requires a hostid or a hardware dongle to be on the license server machine. Instead,
SFLM will give your machine a unique "virtual dongle" identification. To ensure that this number is
unique it must be compared with the database of all virtual dongle IDs kept by your vendor. This can
be done automatically if you are online, otherwise you need to send this information via E-mail to your
vendor. This process is called "registration".
What is activation?
Once a virtual dongle has been registered, and it is confirmed that it is unique, the license server can
be made active, that is it will now accept license files. When this is done online the user will have
nothing to do, it is done in the background. If the registration was offline the user must enter an
activation code sent back by your vendor.
What should I choose - online or offline registration?

Choose online registration if the web browser is able to access the internet. If access to the internet is
blocked you must register offline.

I have forgotten my password, what should I do?

You can reset your password outside the web front end. You will need to be root on the machine where
SFLM was originally installed and then run the command:
sflm -set-password
You will be prompted to set a password. This operation may be conducted while the SFLM server is
active without causing any problems.
When I run an application I cannot get a license, what should I do?

Make sure the license server is still alive. The SFLM software is designed to automatically start itself
if, for any reason, it should be forced to close by any other program. You can check if the SFLM is
running with the web front end. Click on “Reports” and then on “List Installed License Files”. The
table that is displayed will tell you if the server is running.
If SFLM is not running you will need to restart it from the command prompt. As root (or administrator)
run the command:
sflm -start
How do I find out who has checked out a particular product license?
Open the web front end and click on “Reports”, then click the option “Show Active Users”.
What are redundant servers?

Sometime either a machine or a network is unreliable, and when a user tries to open an application,
the application will be unable to contact the license server to get a license. The SFLM redundant server
system is one method to get around this problem. The system requires that a minimum of 3 machines
to be designated and installed as redundant license servers. The same license file is installed on each
machine, and each machine is set up as primary, secondary or tertiary servers. When an application
requests a license it will attempt to contact the primary license server; if it cannot contact the primary
server it will then attempt to contact the secondary server and so on. The redundant system requires
that at least 2 machines are alive and communicating at any given time. The SFLM servers
communicate to each other on license usage, and when the primary machine returns to the system it
will then take over the license control. When installed, the system will be opaque to the user.
How do I set up redundant servers?

Step 1:
First, request redundancy from your vendor account manager and when this is done proceed to step 2.
Step 2:
Run "sflm -install" on all three machines.
Step 3:
Bring up a web browser on each machine, type in the URL "http://machine:3162/" (where machine is
the hostname of the machine), and then go through the registration procedure that will be initiated.
Then wait to be contact by you vendor.

Frequently Asked Questions
Step 4:
Your vendor will inform you when your license file is ready to be downloaded. When you receive this
message, open your web browser at "http://machine:3162/" and click on “Install new License(s)”.
Download and install the license file that your vendor has created on the primary license server
machine (this license file should list the machine credentials of the 3 machines chosen as license
servers).
Step 5:
When the above are completed open your web browser at "http://machine:3162/" and go to "Setup
Redundant Servers". Use the "Add Server" field to add each server individually to the Server List.
What can cause me to need to re-register?

The unique description of your machine is linked to many things, such as the machine name, disk
number, mac address, etc. Typically changing one piece of hardware, e.g. the hard disk, will not require
re-registration. A number of hardware changes are necessary before re-registration will be required.
How can I reset the SFLM?

Some situations may occur infrequently where the active users report shows a license checked out for
an application that you know has been terminated. To free this license, you can either wait one hour
for SFLM to automatically remove this phantom license check out, or perform a manual reset of the
server.
To manually re-start SFLM the user needs to login as root (on Unix/Linux) or Administrator
(Windows), open a command terminal or DOS window, and run:
/<installdir>/bin/sflm -stop
/<installdir>/bin/sflm -start


02sflm6 Install Users

Uploaded by

Copyright:

Available Formats

02sflm6 Install Users

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02sflm6 Install Users

Uploaded by

Copyright:

Available Formats

Standard Floating License

SILVACO International April 2004

Phone: (408) 567-1000

The information contained in this document is subject to change without notice.

SILVACO International iii

SILVACO International TOC-1

TOC-2 SILVACO International

1.1: What’s New in SFLM6

1.2: Supported Platforms

Platform Operating System Keyword

SPARC Solaris 8 and 9 Solaris

HP 9000 HPUX 11.0 HP

x86 RedHat 7.3 and 9.0 Linux

x86 Microsoft Windows 2000 2000

x86 Microsoft Windows XP XP

Table 1-1: Supported Platforms for SFLM 6

1.3: Overview of SFLM6

SILVACO International 1-1

1.3.1: License Server Registration

Figure 1-1: SFLM6 Registration Flowchart

1-2 SILVACO International

1.3.2: License Installation

Figure 1-2: SFLM6 License File(s) Flowchart

SILVACO International 1-3

1.4: Customer Environment Settings

set path = ( $path /<vendordir>/bin )

1.4.2: Choosing A Single License Server

Global Setting for All Users

setenv SFLM_SERVERS "sflmserver"

Local Settings for Individual Users

1-4 SILVACO International

How to Set the SFLM_SERVERS Environment Variable

setenv SFLM_SERVERS "sflmserver"

1.4.3: Choosing Multiple License Servers

setenv SFLM_SERVERS "machineA machineB machineC"

1.4.4: Redundant Server Setup

setenv SFLM_SERVERS "MachineA|machineB|MachineC"

SILVACO International 1-5

Note: No spaces should be present in the SFLM_SERVERS variable.

1.5: Virtual Private Networks (VPNs)

1-6 SILVACO International

SILVACO International 2-1

Figure 2-1: Set Password Dialog

2-2 SILVACO International

Figure 2-2: Register License Server Dialog

SILVACO International 2-3

2.1: Online Registration

Figure 2-3: Register Online Dialog

2-4 SILVACO International

Figure 2-4: Activate Server Dialog

SILVACO International 2-5

Figure 2-5: Registration Complete Dialog

2-6 SILVACO International

Figure 2-6: Main SFLM Home Page

SILVACO International 2-7

2.2: Offline Registration

Figure 2-7: Offline Registration Dialog

2-8 SILVACO International

SILVACO International 2-9

Figure 2-8: Code Name and Activation Code Dialog