SimSci®

SIM4ME® FlexNet™ 11.13

License Server
Administrator Guide

December 2015
All terms mentioned in this documentation that are known to be trademarks or service marks have been
appropriately capitalized. Schneider Electric Software, LLC. cannot attest to the accuracy of this
information. Use of a term in this documentation should not be regarded as affecting the validity of any
trademark or service mark.
ActiveFactory, ArchestrA, ARPM, AssayCentral, Autonomous, Avantis, Avantis.PRO, Connoisseur,
CrudeManager, CrudeSuite, DATACON, DATAPREP, DT Analyst, DYNSIM, DYNSIM Power, Esscor,
EYESIM, Factelligence, FactorySuite, FactorySuite A², Foxboro, Foxboro Evo, FSIM Plus, HEXTRAN,
Hot Links, I/A Series, IMPACT, IMServ, InBatch, InControl, Industrial Portal, IndustrialSQL Server,
InFusion, INPLANT, InSQL, IntelaTrac, InTouch, IPact, Invensys, Logic Validator, MBM, NETOPT,
PIPEPHASE, PRO/II, PROVISION, QI Analyst, ROMeo, SCADAlarm, SIM4ME, SimCentral, SimSci,
SimSci-Esscor, Skelta, Skelta BPM.NET, Skelta Sharepoint, Skelta Sharepoint Accelerator, Spiral
Software, SuiteVoyager, TACITE, Tactical Batch, The Simulator, TRISIM Plus, VISUAL FLARE,
VISUAL FLOW, VISUAL FLOW SUITE, VISUAL NETWORK, Visual Solutions, VOYAGER,
WindowMaker, WindowViewer, Wonderware, Wonderware InTouch, and ZI ZHI are trademarks of
Schneider Electric SE, its subsidiaries and affiliated companies.
© 2015 by Schneider Electric Software, LLC. All rights reserved.
No part of this documentation shall be reproduced, stored in a retrieval system, or transmitted by any
means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written
permission of Schneider Electric Software, LLC. No liability is assumed with respect to the use of the
information contained herein.
Although precaution has been taken in the preparation of this documentation, Schneider Electric
Software, LLC assumes no responsibility for errors or omissions. The information in this documentation
is subject to change without notice and does not represent a commitment on the part of Schneider Electric
Software, LLC. The software described in this documentation is furnished under a license agreement.
This software may be used or copied only in accordance with the terms of such license agreement.
ArchestrA, Avantis, DYNSIM, EYESIM, Foxboro, Foxboro Evo, I/A Series, InBatch, InduSoft,
IntelaTrac, InTouch, PIPEPHASE, PRO/II, PROVISION, ROMeo, Schneider Electric, SIM4ME,
SimCentral, SimSci, Skelta, SmartGlance, Spiral Software, VISUAL FLARE, WindowMaker,
WindowViewer, and Wonderware are trademarks of Schneider Electric SE, its subsidiaries, and affiliated
companies. An extensive listing of Schneider Electric Software, LLC trademarks can be found at:
http://software.schneider-electric.com/legal/trademarks/. All other brands may be trademarks of their
respective owners.
Schneider Electric Software, LLC
26561 Rancho Parkway South
Lake Forest, CA 92630 U.S.A.
(949) 727-3200
http://software.schneider-electric.com/
1 INTRODUCTION .........................................................................................................................................1
1.1 ABOUT THIS MANUAL AND THE INSTALL PROGRAM ..............................................................................................1
1.2 TERMS AND DEFINITIONS...............................................................................................................................1
1.3 ABOUT SIMSCI ...........................................................................................................................................2
1.4 TECHNICAL SUPPORT ....................................................................................................................................2
1.5 AUTHORIZED SIMSCI TECHNICAL SUPPORT CENTERS..............................................................................................3
1.6 DOWNLOADSOFTWARE ................................................................................................................................3
2 FLEXNET PUBLISHER 11.13 LICENSE SERVER OVERVIEW..............................................................................5
2.1 PREREQUISITES ..........................................................................................................................................5
2.2 IPASSI FNP 11.13 LICENSE SERVER DEBUG LOG FILE (IPASSI.LOG) ....................................................................5
3 SET UP IPASSI FLEXNET 11.13 LICENSE SERVER ON A MACHINE ...................................................................6
3.1 INSTALLATIONSTRATEGIES .............................................................................................................................6
3.1.1 No FNP or FLEXlm License Server Present .......................................................................................6
3.1.2 Foreign FLEXlm or FNP License Server Present ................................................................................6
3.1.3 IPASSI FLEXlm or FNP License Server Present ..................................................................................6
3.2 INSTALL IPASSI FNP 11.13 LICENSE SERVER ON A MACHINE .................................................................................7
3.3 CONFIGURE AND INSTALL THE TEMPORARY LICENSE F ILE ........................................................................................8
3.4 REQUEST A PERMANENT LICENSE FILE ............................................................................................................. 10
3.5 CONFIGURE AND INSTALL THE PERMANENT LICENSE FILE ...................................................................................... 11
3.5.1 Active Temporary License File Exists ............................................................................................. 11
3.5.2 Valid Permanent File License Exists with Identical Server Line........................................................ 11
3.5.3 Valid Permanent File License Exists with a Different Server Line..................................................... 11
4 MAINTAIN THE IPASSI FNP 11.13 LICENSE SERVER .................................................................................... 13
4.1 RECONFIGURE THE IPASSI FNP 11.13 LICENSE SERVER ...................................................................................... 13
4.2 RESTART THE SERVER TO RE‐READ THE LICENSE FILE ........................................................................................... 13
4.3 STATUS OF THE IPASSI FNP 11.13 LICENSE SERVER .......................................................................................... 14
4.4 CHECK IF THE FNP LICENSE SERVER IS READY.................................................................................................... 14
5 CUSTOMIZE FNP LICENSING POLICY .......................................................................................................... 17
5.1 USE THE LICENSE SERVER OPTIONS FILE .......................................................................................................... 17
5.2 COMMANDPARAMETERS ............................................................................................................................ 17
5.3 DEFINE USER AND HOST GROUPS .................................................................................................................. 18
5.3.1 Case Sensitivity in Names ............................................................................................................ 18
5.3.2 Create and Use Groups ................................................................................................................ 19
5.3.3 GROUP Command ....................................................................................................................... 19
5.3.4 HOST_GROUP Command ............................................................................................................. 19
5.4 DEFINE LICENSING POLICY ........................................................................................................................... 20
5.4.1 BORROW_LOWWATER Command ................................................................................................ 20
5.4.2 EXCLUDE Command .................................................................................................................... 20
5.4.3 EXCLUDEALL Command ............................................................................................................... 21
5.4.4 EXCLUDE_BORROW Command .................................................................................................... 21
5.4.5 INCLUDE Command ..................................................................................................................... 22
5.4.6 INCLUDEALL Command ................................................................................................................ 22
5.4.7 INCLUDE_BORROWCommand ..................................................................................................... 23
5.4.8 MAX Command ........................................................................................................................... 23
5.4.9 MAX_BORROW_HOURSCommand .............................................................................................. 23
5.4.10 RESERVE Command ................................................................................................................ 24
6 UNINSTALL IPASSI FNP 11.13 LICENSE SERVER........................................................................................... 25

7 FNP STANDARD AND TOKEN LICENSE SECURITY FAQS ............................................................................... 26

1 Introduction

1.1 About this Manual and the Install Program

This document provides information for the license administrator to:
• Install the IPASSI FlexNet Publisher 11.13 License Server application on a machine
(Section 3)
• Manage the IPASSI FlexNet Publisher 11.13 License Server (Section 4)
• Customize the IPASSI FlexNet Publisher 11.13 licensing policy (Section 5)
• Get help from SimSci Technical Support (Section Technical Support )
• Find contact information for Authorized SimSci Technical Support Centers in
several countries
• Uninstall IPASSI FNP 11.13 License Server (Section 6)

1.2 Terms and Definitions

FLEXNET SERVER This term refers to the FlexNet Publisher process, not to the machine on
which the FNP license server runs. The FNP license server does not have
to run on a network server machine or a f ile server machine. The
administrator can restart the FNP license server without rebooting the
machine on which the FNP license server runs.
An FNP license server maintains the FNP license f ile and handles
requests for FNP licenses.
TOKEN SERVER A license server similar to a FlexNet Publisher license server. The only
difference is in the license f ile. While the FlexNet license server
manages the standard FlexNet license f ile, the TOKEN license server
maintains the TOKEN license f ile and handles requests for TOKEN
licenses. Almost all the instructions for the IPASSI FlexNet license
servers are applicable to their TOKEN counterparts.
FLEXNET DAEMON This term refers to the generic FlexNet Publisher daemon LMGRD.EXE.
The vendor‐specif ic daemon for SimSci is IPASSI.EXE. These two f iles
comprise the execution part of the FNP license server.
FLEXNET CLIENT This term refers to the FNP‐licensed application. The client part of the
FNP security is embedded in the application, and serves as a medium
through which the application communicates with the FNP license
server for validation. The FNP server and client can co‐exist on the
same machine.
Figure 1 illustrates the FlexNet Publisher client‐server relationship.

Chapter 1 1
 Figure 1 FLEXnet Client‐Server Relationship

1.3 About SimSci

For more than forty years, SimSci has been a leader in the development and deployment of
process simulation software, services, and complete solutions for oil and gas production,
hydrocarbon and specialty chemical processing and refining, and fossil and nuclear power.
Benefit from products that minimize capital requirements, optimize facility performance,
maximize ROI, and produce assets for:
• Plant engineering design and simulation
• Integrated process engineering
• Pipeline production analysis, asset model management
• Operational analysis, optimization, process control
• Dynamic simulation, operator training
• Design, operate and optimize a safe and profitable plant subject to ever more
stringent market and regulatory constraints.
SimSci software solutions are indispensable tools in solving these three increasingly
complex challenges simultaneously. SimSci is a business unit of Invensys Process Systems,
owned by Invensys, plc.

1.4 Technical Support

SimSci and its agents around the world provide technical support and service for our
products. If you have any questions regarding the use of the program or the interpretation
of output produced by the program, contact your local SimSci representative for advice or
consultation.
When calling one of the Technical Support Centers, be prepared to describe your problem
or the type of assistance required. To expedite your call, complete the following steps
before calling Technical Support:
• Have the installation program and all provided documentation available.
• Determine the type of operating system you are using.

Chapter 1 2
 • Determine the amount of free disk space available on the disk which the product is
installed.
• Note the exact actions you were taking when the problem occurred, as well as the
steps you took leading up to that point.
• Note the exact error messages that appear on your screen, as well as any other
symptoms.
Both new and experienced users will benefit significantly from attending one of SimSci's
regularly scheduled training courses. If you would like to obtain a list of courses available,
or if you have any questions please call your nearest SimSci Technical Support office or
visit our web site at www.simsci.com.

1.5 Authorized SimSci Technical Support Centers

Support Tel/Internet Support Center Tel/Internet
Center
USA
800‐746‐7241 KOREA +82 2 2090‐0822
[email protected] [email protected]

CANADA
800‐746‐7241 SINGAPORE +65 6829 0201
[email protected] [email protected]

EUROPE &
AFRICA +44 (0) 1925 811469 MEXICO 01‐800‐466‐2255
[email protected] [email protected]

MIDDLE
EAST +966 3 8010382 VENEZUELA +58 212 267 5868
[email protected] [email protected]

JAPAN
+813 6450‐1095 (PES/DYNSIM) BRASIL +55112844 0213/291
+813 6450 1096 (ROMeo) [email protected]
[email protected]

CHINA
+86 21 53559555 x5859 AUSTRALIA/ NEW +1‐800‐746‐7241
[email protected] ZEALAND [email protected]

See iom.invensys.com under the Support tab for Center updates.

1.6 Download Software

As long as the license administrator has a valid SimSci Electronic Software Distribution
(ESD) user account, the user can download the license security programs and utilities
from the ESD web site. These are the steps to follow:
1. The administrator opens the web page http://www2.simsci.com/sim4me/support/
updates.stm
2. The administrator clicks the Sign In link.
3. The administrator enters the user name and password

Chapter 1 3
 4. The administrator clicks the Product Hub button.
5. Check License Security on the left side and all license security downloads will
display.
6. The administrator clicks the item to download.

Chapter 1 4
2 FlexNet Publisher 11.13 License Server Overview

FlexNet Publisher (FNP) is an advanced version of FLEXlm. FNP provides floating or concurrent
licensing to network client software applications, rather than machine specific licensing.
This design greatly benefits both users and license administrators. With the FNP
technology, the end‐user can also borrow a license to run the application offline, that is,
when the end‐user's machine is not connected to the network. In addition, license
administrators can configure the FNP license server options file to create a custom
licensing policy that best serves their unique licensing needs.
The FNP license server and the FNP‐licensed application can run on the same machine, or
the server can run on a different machine from that of the application. The machine on
which the server runs can be a different hardware platform than, or can run a different
Windows operating system from, the machines that run the FNP‐licensed application.
IPASSI FlexNet Publisher 11.13 is a FlexNet Publisher 11.13 license management system that
SimSci has customized to secure SimSci software applications. SimSci developed, in
addition to the general FNP functionalities, the utilities FNP1113CHECKOUT.EXE and
TKN1113CHECKOUT.EXE to allow the end‐users to borrow the 11.13 FNP standard licenses
and TOKEN licenses respectively for offline use.

2.1 Prerequisites
FNP 11.13 is a client‐server based license management system. To set up the system, the
license administrator first selects a machine to host the FNP 11.13 License Server. The
IPASSI FNP 11.13 License Server machine must meet three conditions.
• The machine must run a Win32 or higher operating system.
• The machine must be able to communicate with all the machines that run
FNP‐licensed SimSci applications.
• The machine must not have another copy of IPASSI FLEXlm or IPASSI FNP License
Server running alongside the FNP 11.13 License Server to be installed.
Only one instance of an FNP or FLEXlm server from the same vendor can run
simultaneously. If a legacy server from the same vendor is to continue running in
production, the license administrator should find another machine on which to host the
new FNP 11.13 license server. Any machine can host the FNP license server, as long as the
machine meets these requirements.
The IPASSI FNP 11.13 License Server machine should be configured for high availability and
performance to ensure that application machines have easy and constant access to the
IPASSI FNP licenses.

2.2 IPASSI FNP 11.13 License Server Debug Log File (IPASSI.LOG)
To enhance security, the 11.13 License Server runs on the Local Service account instead of
Local System account, since the former has lower privilege. Because of this, the license
server does not have write access to its default install location, C:\Program Files
(x86)\IPASSI\FNP1113. Therefore, the license server debug log file directory is now

Chapter 2 5
defaulted to C:\Users\Public\Public Documents\SimSci. When reconfiguring the log file
folder, please make sure that the license server has write access to the new log file
directory.

Chapter 2 6
3 Set up IPASSI FlexNet 11.13 License Server on a Machine

3.1 Installation Strategies

To set up an FNP License Server, the administrator first selects a machine that meets the
previously mentioned prerequisites and then installs the FNP License Server on the
machine.
Note that the IPASSI FNP TOKEN License Server is identical to the FNP License Server,
except that the TOKEN license server manages TOKEN licenses instead of the standard
FNP licenses. Therefore, all instructions that apply to the FNP License Server apply to the
FNP TOKEN License Server too.
Depending on whether there is already a version of the FNP/FLEXlm server installed on
the machine, the administrator chooses one of the following three ways to install the
IPASSI FNP 11.13 License Server.

3.1.1 No FNP or FLEXlm License Server Present

If there is no FNP or FLEXlm license server from any vendor currently installed on the
selected machine to host the IPASSI FNP 11.13 License Server, the administrator can safely
install the IPASSI FNP 11.13 License Server on the machine.

3.1.2 Foreign FLEXlm or FNP License Server Present

If there is one or more FNP or FLEXlm license server from another vendor but none from
SimSci currently installed on the machine, the administrator can safely install the IPASSI
FNP 11.13 License Server on the machine. This is because FNP or FLEXlm servers from
different vendors can coexist on the same machine without causing any problem.
However, SimSci recommends that the IPASSI FNP 11.13 License Server be installed to a
unique file system location, so that it works independently of any existing FNP or FLEXlm
servers. Also, the license administrator needs to ensure that no two or more license servers
are trying to use the same port for their lmgrd processes.

3.1.3 IPASSI FLEXlm or FNP License Server Present

If there is an IPASSI FNP or FLEXlm license server already installed on the machine, and it
is required to continue providing service, the administrator should not install the IPASSI
FNP 11.13 License Server on the machine. The administrator should find another machine
that can host the new IPASSI FNP 11.13 License Server to avoid conflict. This is because
only one instance of an FNP or FLEXlm license servers from the same vendor can run at a
time.
When upgrading an existing license server in production to FNP 11.13, the administrator
should temporarily stop the production license server to test the new FNP 11.13 License
Server. After the new FNP 11.13 License Server is working properly, the administrator can
continue to uninstall the old license server.

Chapter 3 6
3.2 Install IPASSI FNP 11.13 License Server on a Machine
During the installation process, the Setup utility asks for the user's name, company's name
and address, the product, phone and fax numbers, and e‐mail address. The administrator
should have this information ready before starting the installation procedure.
1. From Windows Explorer, the administrator opens either the FNP 11.13 LICENSE
SERVER INSTALL CD or the folder on the local or network drive that contains the
IPASSI FNP 11.13 License Server installation program.
2. The administrator browses to the root of the folder and double‐clicks SETUP.EXE.
The Setup program starts and the Setup Welcome dialog box appears.
3. The administrator clicks the Next button. The Customer Information dialog box
appears.
4. The administrator enters the requested information. The company name, fax
telephone number, and e‐mail address are required. All other entries are optional.
The information entered in this dialog box appears automatically on the Permanent
License Request Form for FNP 11.13, in the IPASSI.TXT file. This is the document
that the administrator submits to SimSci to request a permanent license file.
5. The administrator clicks the Next button, and then confirms all the provided
customer information is correct, and clicks the Next button to commit.
6. The Destination Folder dialog box appears. The administrator selects the
destination directory in which the FNP 11.13 License Server application files will be
installed. The default target location for this is C:\PROGRAM FILES (x86)\.The
administrator should make sure not to select a location that overlaps with other
applications, especially with other license server folders. To change the destination
directory, the administrator clicks the Browse button and specifies the desired
directory.
7. The administrator clicks the Next button to commit the install to the selected target
destination.
8. The administrator clicks the Install button. The Setup utility starts copying files and
displays the installation progress indicator.
9. The administrator clicks the Cancel button at any time to cancel the installation.
After the file transfer is complete, the Setup Complete dialog box appears.
10. After reading the message on the dialog, the administrator clicks the Finish button
to complete the installation.
After the IPASSI FNP 11.13 License Server is installed successfully, two shortcut icons
appear in the Start menu, as shown in IPASSI FNP 11.13 Icons in the Start Menu.

Chapter 3 7
 Figure 2 IPASSI FNP 11.13 Icons in the Start Menu
The IPASSI FNP 11.13 Folder icon allows the license administrator to directly open the
IPASSI FNP 11.13 License Server folder in Windows Explorer. This folder contains the
IPASSI FNP 11.13 License Server files, among them are:
• the generic daemon LMGRD.EXE
• the SimSci vendor daemon IPASSI.EXE
• the permanent license request form IPASSI.TXT
• the server options file IPASSI.OPT
• the management tool LMTOOLS.EXE
The lmtools.exe shortcut icon gives direct access to launch the major FNP license server
management tool LMTOOLS.EXE. The administrator uses this utility to manage and
configure the IPASSI FNP 11.13 License Server.

3.3 Configure and Install the Temporary License File

After the administrator receives a valid temporary license file IPASSI.LIC from SimSci, he
or she needs to configure this file for it to work on the license server machine. These are
the steps to follow.
1. From the Start menu, the administrator selects the IPASSI FNP 11.13 Folder icon
to open the license server folder in Windows Explorer.
2. The administrator copies the IPASSI.LIC file to this folder.
3. The administrator opens the IPASSI.LIC file in a text editor, such as Notepad.
4. The administrator edits the SERVER line in this file so that the second entry on this
line is the name or IP address of the FNP 11.13 License Server machine. Example:
SERVER [FNPSERVERMACHINENAME] ANY
5. The administrator adds an LMGRD port number to the end of the SERVER line, if
necessary. This step is required if the license administrator needs the license server
to always use the same port number. Otherwise, this step is optional. Example:
SERVER [FNPSERVERMACHINENAME] ANY 27000

Chapter 3 8
 6. The administrator adds an IPASSI port number to the end of the VENDOR line, if
necessary. This step is required if the license server is always to use the same port
for IPASSI.EXE. Otherwise, this step is optional. Example:
VENDOR IPASSI PORT=4567
7. The administrator saves and closes the IPASSI.LIC file.
8. The administrator selects the lmtools.exe shortcut to launch the LMTOOLS.EXE
utility.

Figure 3 Launch of Server Utility Program ‐ lmtools.exe

9. On the Service/License File tab, the administrator chooses the IPASSI FNP 11.13
SERVICE.

Chapter 3 9
 10. The administrator selects the Start/Stop/Reread tab, as shown below.

Figure 4 Start/Stop/Restart Tab

11. If the server is running, the administrator can stop and restart the server, or can
click the ReRead License File button to use the new license. If the server is not
running, the administrator clicks the Start Server button to start the IPASSI FNP
11.13 License Server and activate the temporary license file.

3.4 Request a Permanent License File

The installation process puts the document Permanent License Request Form for FNP
11.13 into the file IPASSI.TXT under the FNP1113 folder. To obtain a permanent license
file, the administrator must complete this form and send it to SimSci Technical Support.
In turn, SimSci sends the administrator a permanent IPASSI FNP 11.13 license file.
Specific steps include:
1. The administrator selects the IPASSI FNP 11.13 FOLDER shortcut to open the
folder, as shown in Figure 2.
2. The administrator opens the IPASSI.TXT file in any text editor application, such as
Microsoft Notepad. The information that the administrator entered during the
installation process appears on the form. The administrator edits the file, if
necessary, to ensure that all the information is correct and as complete as possible.
The administrator should not change anything in the section labeled FOR IPASSI
USE ONLY.
3. In the Product for which license is requested field, the administrator enters any
subcomponents as necessary, such as a data historian.
4. The administrator emails or faxes the completed form to SimSci, using the email
address or the fax number on the form.

Chapter 3 10
3.5 Configure and Install the Permanent License File
After the permanent license file is available, the administrator selects one of the following options
to start using the file, depending on the status of the existing license files:

3.5.1 Active Temporary License File Exists

If the license server is running on temporary licenses, and all the licenses are to be
replaced by the licenses in the permanent license file, these are the steps to follow:
1. The administrator simply removes the temporary license file and copies over
the permanent license file.
2. The administrator stops the IPASSI FNP 11.13 License Server using LMTOOLS.EXE.
3. The administrator restarts the IPASSI FNP 11.13 License Server using LMTOOLS.EXE.

3.5.2 Valid Permanent File License Exists with Identical Server Line
If the license server has an existing valid permanent license file, and the SERVER line in
this file is identical to the one in the new permanent license file, then the administrator
may want to combine them into one permanent license file. These are the steps to follow:
1. The administrator stops the IPASSI FNP 11.13 License Server using LMTOOLS.EXE.
2. The administrator opens the existing permanent license file in any text editor.
3. The administrator opens the new permanent license file in the text editor in
another window.
4. From the new file, the administrator copies the whole content of the new
permanent license file, except the SERVER line and the VENDOR lines.
5. In the existing license file, the administrator pastes the copied material to the end
of the file.
6. The administrator saves and closes both license files.
7. The administrator restarts the IPASSI FNP 11.13 License Server using LMTOOLS.EXE.

3.5.3 Valid Permanent File License Exists with a Different Server Line
If the server machine already has an existing valid permanent license file, but the SERVER
line in this file is not identical to the one in the new permanent license file, the
administrator cannot combine them into one permanent license file. Below are the steps
to follow to use both the existing and new permanent license files:
1. The administrator copies the new permanent license file to the FNP1113 folder,
giving the new license file a name that differs from the name of the existing license
file and has the .LIC extension name. The unique file name prevents overwriting
the existing license file. The .LIC extension allows the server to use the file the next
time the server starts.

Chapter 3 11
 2. The administrator reconfigures the IPASSI FNP 11.13 Service to use the additional
license files by setting the Path to the License File field in the Config Services tab to
the FNP1113 folder, not to a specific file, as shown in Figure 5.
3. When the FNP 11.13 License Server starts with this configuration, it uses all the valid
license files (.LIC files) that reside in the Path to the License File folder.

Figure 5 Config Services Tab

Finally, the administrator may need to configure the permanent license file to have the
same LMGRD and IPASSI port numbers as does the temporary license file, as described in
section Configure and Install the Temporary License File. After that the license server can
restart for the license files to take effect.

Chapter 3 12
4 Maintain the IPASSI FNP 11.13 License Server

After the license administrator successfully installs the IPASSI FNP 11.13 License Server on
a license server machine and a license file that is valid for the machine is available in the
FNP 11.13 License Server folder, the IPASSI FNP 11.13 License Server is ready to launch and
handle licensing requests from the users.
During the service period, the license administrator may have to update the license files or
reconfigure the license server. When such a need arises, the license administrator can use
the LMTOOLS.EXE utility to make the change, which is available on the Start menu
through the shortcut, as described in section 3.2.

4.1 Reconfigure the IPASSI FNP 11.13 License Server

The FNP license server has three components: the daemon, the license file, and the server
log file. The FNP 11.13 License Server installation program automatically configures these
three components. SimSci generally does not recommend that license administrators
reconfigure the server or change the service name from IPASSI FNP 11.13 License Service.
However, if a reconfiguration is ever necessary, the Config Services tab has all the controls
to perform the task. In Config Services tab, the administrator can specify the paths to the
following:
• the LMGRD.EXE file
• the license file IPASSI.LIC
• the debug log file IPASSI.LOG
The tab has two additional options: Start Server at Power Up and Use Services. When the
Use Services checkbox is available and selected, the Start Server at Power Up checkbox is
enabled. When the Start Server at Power Up checkbox is selected, the IPASSI FNP 11.13
License Server automatically starts every time the machine starts. However, the server
does not start automatically if something else prevents server from starting, such as an
invalid or missing license file. After the administrator reconfigures the service using the
LMTOOLS.EXE utility, the administrator clicks the Save Service button to saves the
changes.

4.2 Restart the Server to Re‐Read the License File

Whenever the license file changes, the administrator may stop and restart the server to
make the changes take effect. The controls on the Start/Stop/Reread tab serve this
purpose.
For instance, after the administrator replaces a temporary license file with a permanent
one, the administrator must stop and start the server, or re‐read license file, to activate the
permanent file. Section 3.5 describes how to manage the permanent FNP license files.
To stop the IPASSI FNP 11.13 server, the administrator clicks the Stop Server button, as
shown in Figure 4. However, if one or more licenses from this server are currently

Chapter 4 13
borrowed, the administrator must check the Force Server Shutdown checkbox before
clicking the Stop Server button.
To start the server, there must be a valid license file from SimSci as specified in the Path to
the license file field on the Config Services tab of the LMTOOLS.EXE.
The administrator can make changes to the license file take effect without stopping and
restarting the server, merely by clicking the Reread License File button.

4.3 Status of the IPASSI FNP 11.13 License Server

The Server Status tab allows the license administrator to monitor the IPASSI FNP 11.13
Server and the current license usage status. The license administrator clicks the Perform
Status Enquiry button shown in Server Status.

Figure 6 Server Status

The name and path of the active license file appears at the bottom of this window.

4.4 Check if the FNP License Server is Ready

The most reliable way to determine whether the IPASSI FNP 11.13 License Server is
servicing is to examine the license server debug log file IPASSI.LOG. By default, this log
file resides in the license server directory: C:\Users\Public\Documents\SimSci.
If the log file is not available in this folder, the administrator can find the actual location
of the file in the registry, LMGRD_LOG_FILE, as shown below.

Chapter 4 14
 Figure 7 Location of FNP 11.13 License Server Log File
Once the license server log file is found, the administrator opens the file in a text editor,
such as Notepad, scrolls down to the last server starting session, and searches for any error
message. The sample in Server Log File Showing Normal Starting Session shows that the FNP
11.13 server started without a problem.

Figure 8 Server Log File Showing Normal Starting Session

Chapter 4 15
If no error message appears in the FNP 11.13 License Server log file, the server is working
correctly. If there is any error message in the starting session in the log file, the
administrator has to resolve the problem before end‐users can request licenses.
For example, if the administrator tries to start the FNP 11.13 License Server with a license
file that is not intended for the license server machine, the server gives an authentication
error message. The administrator should either install the license and FNP 11.13 License
Server on the machine for which the license was generated, or ask SimSci to issue a license
file for this machine.
Another possible problem can be that the licenses have expired. The license expiration
date can be found in the license file IPASSI.LIC. If the licenses have expired, the
administrator must ask the SimSci sales representative to renew the license.
SimSci technical support can help resolve errors and problems that the administrator
cannot resolve. The administrator should have the license file and license server log file
available for the SimSci technical support staff, to speed up the troubleshooting process.

Chapter 4 16
5 Customize FNP Licensing Policy

The FNP license administrator can customize the FNP license usage by establishing the
rules in the FNP License Server options file. The options file allows the license
administrator to control various operating parameters of the FNP License Server so that
the licensing policy can be as secure or as open as the license administrator prefers. Some
common reasons for the license administrator to create rules in the options file are:
• To allow certain users to obtain or borrow licenses
• To prevent certain users from obtaining or borrowing licenses
• To reserve licenses for certain users

5.1 Use the License Server Options File

The FNP License Server uses only one options file and the default name for IPASSI FNP
11.13 License Server is IPASSI.OPT. If the options file has the default name and the file
resides inside the IPASSI FNP1113 SERVER folder along with the LMGRD.EXE and
IPASSI.EXE, the administrator does not have to do anything more for the license server
to use the file. When the IPASSI FNP License Server starts, it automatically reads the
options file and applies the rules in this file to its licensing activities.
However, if the options file does not use the default file name, or the file resides in a folder
other than the one where the LMGRD.EXE and IPASSI.EXE are, then the administrator
must explicitly specify location information about the options file in the FNP license file.
The administrator edits IPASSI.LIC, and defines the fully qualified path of the options
file on the VENDOR line:
VENDOR IPASSI OPTIONS="C:\PROGRAM FILES\IPASSI\FNP1113\OPTIONS.OPT"
If there are any spaces in the path or file name, they must be wrapped with the double
quotes.
Changes made to the options file do not take effect until the administrator restarts the
FNP License Server.
The administrator can create and edit the ASCII options file with any text editor, such as
Notepad. Each line in the file represents one licensing option rule. Comments in the
options file start with the pound sign (#).

5.2 Command Parameters

Section 5.3 and 5.4 describe the commands that appear in the options file. These
commands take one or more of the following parameters.
PRODUCT_CODE This parameter is the code of the application to which the rule applies.
The license f ile def ines the product codes. For instance, the product
code PRO/II is 500.
ENTITY This parameter is the name of a USER, HOST, GROUP, or HOST_GROUP.
These are the humans or machines to which the rule applies.

Chapter 5 17
 A USER is a person, identif ied by network name, who can request
licensing actions through any HOST in the network.
A HOST is a machine in the network, through which one or more USERs
can request licensing actions. A HOST is identif ied by network name or
IP address. The administrator can use wildcards to apply a rule to a
range of IP addresses.
A GROUP is a collection of one or more USERs.
A HOST_GROUP is a collection of one or more HOSTs.
TYPE This parameter def ines the type of entity to which the rule applies. The
TYPE is one of USER, HOST, GROUP, or HOST_GROUP.
LIST This parameter is a list of one or more entities, separated by spaces.
Most commands use both the TYPE and LIST parameters. The TYPE
parameter def ines the type of entities that can appear in the LIST. For
example, the following command requires that the entity OPERATORS be
a group.
EXCLUDE 500 GROUP OPERATORS
This command requires that the entity ARECIBO be a host.
INCLUDE 200 HOST ARECIBO
The server ignores any command that are improperly formed, or for
which the items in the LIST parameter are not the same kind of entity
as the TYPE parameter.
USER_LIST This parameter is a list of two or more users. No host names may appear
in the user list.
HOST_LIST This parameter is a list of two or more hosts. No user names may appear
in the host list.
NUM_LIC This parameter def ines the number of licenses to which the rule
applies.

5.3 Define User and Host Groups

Rules apply to individual users, to individual host machines, and to groups of users or host
machines. To apply rules to groups of users or machines, the administrator must define
groups.

5.3.1 Case Sensitivity in Names

By default, the rules in the options file treats user names and host names with case‐
sensitivity. Before defining any user groups or host groups, the administrator may make
choose to make the user names and host names case‐insensitive.

Chapter 5 18
The GROUPCASEINSENSITIVE command must be the first command in the options file.
The syntax of the command is:
GROUPCASEINSENSITIVE OFF|ON
Examples of the command are:
GROUPCASEINSENSITIVE OFF
The first example sets case‐insensitivity off, meaning that the options file considers case
when it applies rules to entities. To apply a rule to four users named Claire, claire, ClaIre and
CLAIRE, the administrator must name each user explicitly.
GROUPCASEINSENSITIVE ON
The second example sets case‐insensitivity on, meaning that the options file does not
consider case when it applies rules to entities. If the administrator applies a rule to the
user named Claire, the same rule applies to the users claire, ClaIre and CLAIRE.

5.3.2 Create and Use Groups

Users are identified by their user names, which are the names by which the network
knows them. To set a rule for more than one user name, the administrator can create a
GROUP, and then apply the rule to all users in the GROUP at once.
Hosts are identified by their machine names or IP addresses, which are the identifiers by
which the network knows them. To set a rule for more than one host name, the
administrator can create a HOST_GROUP, and then apply the rule to all hosts in the
HOST_GROUP at once.

5.3.3 GROUP Command

The GROUP command creates a group of users. The syntax of the command is:
GROUP GROUP_NAME USER_LIST
The options file can contain more than one command for a single GROUP. The first
command defines the group and adds users. Subsequent commands add more users to the
group.
Examples of the command are:
GROUP OPERATORS HWEILIN MAFALDA
GROUP OPERATORS SACAJAWEA
The first GROUP command defines the group OPERATORS, and then adds the two users
HWEILIN and MAFALDA to the group. The second command adds the user SACAJAWEA to
the group.
EXCLUDE 500 GROUP OPERATORS
This EXCLUDE rule prohibits the users HWEILIN, MAFALDA and SACAJAWEA from using the
application with product code 500.

5.3.4 HOST_GROUP Command

The HOST_GROUP command creates groups of host machines. The syntax of the command
is:

Chapter 5 19
 HOST_GROUP HOST_GROUP_NAME HOST_LIST
The options file can contain more than one command for a single HOST_GROUP. The first
command defines the group and adds hosts. Subsequent commands add more hosts to the
host group. Examples of the command are:
HOST_GROUP PACIFIC TOKYO
HOST_GROUP PACIFIC SEATTLE 242.07.611.23 AUCKLAND
The first rule defines the host group PACIFIC, and then adds the host TOKYO to the host
group. The second command adds the hosts SEATTLE, 242.07.611.23 and AUCKLAND to
the host group.
EXCLUDE 500 HOST_GROUP PACIFIC
This EXCLUDE rule prohibits all users, on all four hosts in the PACIFIC host group, from
using the application with product code 200. The administrator does not have to apply
this rule to individual users on those machines.

5.4 Define Licensing Policy

The administrator can define a licensing policy by writing rules that allow, restrict or
forbid license actions to particular entities.

5.4.1 BORROW_LOWWATER Command

This rule sets the number of licenses that cannot be borrowed for a given application. The
purpose of the command is to guarantee that there is always a pool of licenses that are
available for online users. The syntax of the command is:
BORROW_LOWWATER FEATURE TYPE LIST NUM_LIC
Examples of the command are:
BORROW_LOWWATER 500 * * 1
This command sets one license for the application with product code 500 that no entity
can borrow.
BORROW_LOWWATER 200 GROUP OPERATORS 5
This command sets FIVE licenses for the application with product code 200 that no
member of the group OPERATORS can borrow.

5.4.2 EXCLUDE Command

This rule prohibits one or more entities from using the license.
The EXCLUDE command overrides the INCLUDE command. If an entity appears in both
INCLUDE commands and EXCLUDE commands for a given license, the entity is prohibited
from using the license. The syntax of the command is:
EXCLUDE PRODUCT_CODE TYPE LIST
Examples of the command are:
#FIRST DEFINE THE GROUP ENGINEERS
GROUP ENGINEERS CYNISCA THAIS STEPHEN.GORDON
#

Chapter 5 20
 #PREVENT THE USERS CYNISCA, THAIS AND STEPHEN.GORDON FROM
# USING THE PRO/II LICENSE FROM ANY MACHINE ON THE NETWORK.
EXCLUDE 500 GROUP ENGINEERS
#
#PREVENT THE USER JERGHIZ.KHAN FROM USING THE PRO/II LICENSE
# FROM ANY MACHINE ON THE NETWORK.
EXCLUDE 500 USER JERGHIZ.KHAN
#
#PREVENT ANY USER LOGGED IN TO A HOST WITH AN IP ADDRESS IN THE
# RANGE 123.123.123.0 THROUGH 123.123.123.255 FROM USING THE
# LICENSE FOR THE APPLICATION WITH THE CODE 200.
EXCLUDE 200 HOST 123.123.123.*
In this example, the two EXCLUDE statements combine to create a list of four users who are
forbidden to use the PRO/II license.
These commands together allow all other users, as long as they are not on the excluded IP
addresses, and they are not a member of the ENGINEERS group, and they are not
JERGHIZ.KHAN, to use the PRO/II license.
The administrator might have added JERGHIZ.KHAN to the group ENGINEERS, and then
would not have had to write a separate rule for JERGHIZ.KHAN. However, the
administrator may want to write a rule that applies to CYNISCA, THAIS and
STEPHEN.GORDON but not to JERGHIZ.KHAN. To allow this, the license administrator
chose to handle JERGHIZ.KHAN as a special case.

5.4.3 EXCLUDEALL Command

This rule prohibits one or more entities from using any licenses that this license server
handles. The EXCLUDEALL command overrides the INCLUDEALL command. If an entity
appears in both INCLUDEALL commands and EXCLUDEALL commands for a given license,
the entity is prohibited from using the license. The syntax of the command is:
EXCLUDEALL TYPE LIST
Examples of the command are:
EXCLUDEALL USER WALLADAH.ALMUSTAKFI
This command prohibits the user WALLADAH.ALMUSTAKFI from using any licenses that
this license server handles.
EXCLUDEALL HOST CHAOS
This command prohibits any user on the machine CHAOS from using any licenses that this
license server handles.
EXCLUDEALL HOST_GROUP ZOMBIES
This command prohibits any user on any machine in the host group ZOMBIES from using
any licenses that this license server handles.

5.4.4 EXCLUDE_BORROW Command

This rule prohibits one or more entities from borrowing licenses for a given product. The
EXCLUDE_BORROW command overrides the INCLUDE_BORROW command. If an entity
appears in both INCLUDE_BORROW commands and EXCLUDE_BORROW commands for a

Chapter 5 21
given license, the entity is prohibited from borrowing the license. The syntax of the
command is:
EXCLUDE_BORROW PRODUCT_CODE TYPE LIST
An example of the command is:
EXCLUDE_BORROW 500 USER CELESTINA.GIULIA JUNKO.KAMISHIMA
This command prohibits the users CELESTINA.GIULIA and JUNKO.KAMISHIMA from
borrowing licenses for the application with product code 500. These users can still use the
application through online licenses.

5.4.5 INCLUDE Command

This command allows an entity to request licensing actions for an application. An entity
that does not appear in an INCLUDE statement is not allowed to request licensing actions
for the application.
The EXCLUDE command overrides the INCLUDE command. If an entity appears in both
INCLUDE commands and EXCLUDE commands for a given license, the entity is prohibited
from using the license. The syntax of the command is:
INCLUDE PRODUCT_CODE TYPE LIST
Examples of the command are:
INCLUDE 500 USER GRACE.MAKUTSI AIGONG.CHEN
This command allows the users GRACE.MAKUTSI and AIGONG.CHEN to request licensing
actions for the application with product code 500.
INCLUDE 500 USER FREYJA.NJÖRÐRSDOTTIR
INCLUDE 500 GROUP TRAINERS
INCLUDE 500 HOST HONGMAO
These three commands allow the user FREYJA.NJÖRÐRSDOTTIR to use the PRO//II license
from any machine on the network, allow all members of the user group TRAINERS to use
the PRO/II license from any machine on the network, and allow all users logged in to the
host machine HONGMAO to use the PRO/II license. At the same time, these commands deny
the use of the PRO/II license to everyone who is not FREYJA.NJÖRÐRSDOTTIR or a
TRAINER or logged in to the host HONGMAO.

5.4.6 INCLUDEALL Command

This command allows an entity to use all licenses that this license server handles. The
EXCLUDEALL command overrides the INCLUDEALL command. If an entity appears in both
INCLUDEALL commands and EXCLUDEALL commands for a given license, the entity is
prohibited from using the license. The syntax of the command is:
INCLUDEALL TYPE LIST
Examples of the command are:
INCLUDEALL USER JANE.EYRE
This command allows the user JANE.EYRE to request licensing actions for any application
that this license server handles.
INCLUDEALL HOST_GROUP DRILLSITES

Chapter 5 22
This command allows all users on all hosts in the host group DRILLSITES to request
licensing actions for any application that this license server handles.

5.4.7 INCLUDE_BORROW Command

This rule allows one or more entities to borrow licenses for a given product. An entity that
does not appear in an INCLUDE_BORROW statement may not borrow licenses for the
application.
The EXCLUDE_BORROW command overrides the INCLUDE_BORROW command. If an entity
appears in both INCLUDE_BORROW commands and EXCLUDE_BORROW commands for a
given license, the entity is prohibited from borrowing the license. The syntax of the
command is:
INCLUDE_BORROW PRODUCT_CODE TYPE LIST
An example of the command is:
INCLUDE_BORROW 500 GROUP TRAINEES VISITORS
This command allows all members of the user groups TRAINEES and VISITORS to borrow
licenses for the application with product code 500.

5.4.8 MAX Command

This command limits usage for a group or user. The syntax of the command is:
MAX NUM_LIC PRODUCT_CODE TYPE LIST
Examples of the command are:
MAX 6 200 HOST ILOCANO
This command allows no more than SIX users logged in to the host ILOCANO to request
licensing actions at one time for the application with product code 200.
MAX 2 * USER HILDEGARD.VONBINGEN
This command allows the user HILDEGARD.VONBINGEN to request no more than TWO
licenses at a time for any application.
MAX 1 500 USER ALL_USERS
This command allows each user to checkout no more than one seat of the PRO/II (500)
license.

5.4.9 MAX_BORROW_HOURS Command

The license certificate for an application specifies the maximum period of time for which
any user can borrow a license for the application. This command changes the maximum
period. The syntax of the command is:
MAX_BORROW_HOURS PRODUCT_CODE NUM_HOURS
The new time period must be shorter than that specified in the license certificate. If two or
more MAX_BORROW_HOURS commands appear in the options file, only the last one applies
to the application.
An example of the command is:

Chapter 5 23
 MAX_BORROW_HOURS 200 24
This command allows an entity to borrow a license, for no more than 24 hours, for the
application with product code 200.

5.4.10 RESERVE Command

This command reserves a number of licenses for a specific entity. The syntax of the
command is:
RESERVE NUM_LIC PRODUCT_CODE TYPE LIST
Examples of the command are:
RESERVE 1 500 USER MATEKONI
This example reserves ONE license seat of the application with product code 500 for the
exclusive use of user MATEKONI.
RESERVE 5 200 HOST 242.07.611.23
This example reserves FIVE license seats of the application with product code 200 for any
users on host machine 242.07.611.23.
RESERVE 25 200 GROUP SALESTEAM
This example reserves TWENTY‐FIVE license seats of the application with product code 200
for all members of the user group SALESTEAM.
Reserved licenses are dedicated to the named entity. Even when that user, host or group is
not actively using the licenses, the licenses are not available to anyone else.

Chapter 5 24
6 Uninstall IPASSI FNP 11.13 License Server
When the IPASSI FNP 11.13 License Server installed on the machine is no longer needed, the
administrator may want to uninstall it by following the steps below.
1. The administrator uses LMTOOL.EXE to shut down the IPASSI FNP 11.13 License
Server.
2. The administrator opens the Control Panel and selects Add/Remove Programs.
3. The administrator selects the IPASSI FNP 11.13 License Server and then clicks the
Remove button, as shown in Add/Remove Programs.

Figure 9 Add/Remove Programs

4. Windows displays the question shown in Confirmation Dialog.

Figure 10 Confirmation Dialog

5. The administrator clicks the Yes button to remove the IPASSI FNP 11.13 License
Server, or clicks the No button to keep the server installed.
6. After the administrator uninstalls the IPASSI FNP 11.13 License Server, the FNP 11.13
License Server folder may still contains a few remaining files, such as IPASSI.LIC
and IPASSI.LOG. The administrator may want to back up these files for future
references.
7. The administrator deletes the IPASSI FNP 11.13 License Server folder from the
machine.

Chapter 6 25
7 FNP Standard and TOKEN License Security FAQs

Q: Can I install and run two or more FNP or FLEXlm servers from different vendors
at the same time on the same machine?
A: Yes, the same machine can host two or more copies of FNP or FLEXlm servers, each
from a different vendor. However, SimSci highly recommends that all the servers be
installed into different locations on the hard drive, so they do not interfere with one
another.
Q: Can I install and run two or more FNP or FLEXlm servers from SimSci at the
same time on the same machine?
A: The same machine can host two or more copies of SimSci FNP or FLEXlm servers.
However, only one version can be active at a time. For example, you can install IPASSI
FLEXlm 9.5 server and the FNP 11.13 server in different locations on the same machine, but
you can run only one of them at a time.
Q: Can the IPASSI FNP License Server manage both standard FNP standard
licenses and TOKEN licenses?
A: Yes, the FNP License Server can handle both types of licenses at the same time.
Q: How can I allow application machines to have access to the FNP License Server
while the firewall on the license server machine is active?
A: To allow other machines to have access to the FNP License Server while the firewall is
turned on, follow these steps:
1. Open the license file for editing
2. Edit the SERVER line to add an available port number:
SERVER HOST HOSTID [PORT]
Example
SERVER IPS‐SOL07 0002B303DF80 27000
3. Edit the VENDOR line to add an available port number:
VENDOR VENDOR PORT=[PORT]

Example:
VENDOR IPASSI PORT=4571
4. Open the Windows Firewall utility, as shown in Windows Firewall Utility, and
select the Exceptions tab.

Chapter 7 26
 Figure 11 Windows Firewall Utility
5. Check the checkboxes for IPASSI.EXE and LMGRD.EXE, thus making them
exceptions to the firewall.
The value of the environment variable IPASSI_LICENSE_FILE on the application
machine must include the LMGRD.EXE port number, such as 27000@IPS‐SOL07. The
LMGRD.EXE port number is the number you just set on the SERVER line in the license file.
Q: How do I prevent users on other machines from shutting down the FNP License
Server?
A: To deny users on other machines the ability to shut down the FNP License Server,
follow these steps:
1. Run the LMTOOLS utility.
2. Select the START/STOP/REREAD tab.
3. Select the FNP License Server.
4. Stop the server.
5. Click the Advanced settings button. The utility displays the Start/Stop Server Options
on the left side of the window, as shown in Disable FLEXnet Server Shut Down
Remotely.

Chapter 7 27
 Figure 12 Disable FLEXnet Server Shut Down Remotely
6. Check the Restrict lmdown to work only from node where lmgrd is running
checkbox.
7. Click the Start Server button.
With these settings, only users on this machine can shut down the FNP license server
while users on other machines do not have the capability.
Q: How do I find the system information about the FNP license server machine?
A: The System Settings tab on FNP utility program LMTOOLS.EXE shows the machine
system information, including the host ID and the Ethernet address. Exploring server system
information shows an example of LMTOOLS.EXE System Settings tab display.

Chapter 7 28
 Figure 13 Exploring server system information
The second item on the SERVER line in your license file must be the same as the value in
the Computer/Hostname field or the IP Address field of the System Settings tab.
Q: How can I improve FNP licensing performance over a wide‐area network?
A: To speed up the initial connection time between the FNP License Server and the FNP
Clients over a wide‐area network, you must specify the port numbers for the FNP license
server, both on the server and on the application machines.
On the server machine, follow the steps described in section 3.3 to set the port numbers in
the FNP license file. This establishes a port number for the application servers to request.
Default lmgrd.exe port range is 27000‐27009.
On every application machine, the user edits the IPASSI_LICENSE_FILE environment
variable to include the LMGRD port number in its value. Example: 27000@FNPSERVER. That
way the Client machines now know exactly which port on the Server machine to use when
trying to connect to the FNP License Server.
Q: How can I set a longer time for the initial connection attempt over a slow wide‐
area network?
A: Every application machine has the environment variable FLEXLM_TIMEOUT. This
variable determines the amount of time a FNP‐licensed application uses when it tries to
connect to a license server. Possible settings range from 0 through 2147483647
microseconds. The user can set the environment variable to a value larger than the default
setting of 100000 microseconds.
Q: When I request help, what information should I have ready to give the SimSci
Technical Support staff?

Chapter 7 29
A: For fast support, you should provide the following:
• A screenshot of any FNP or TOKEN licensing security error message that the
SimSci application displays
• The FNP license file IPASSI.LIC
• The FNP License Server log file IPASSI.LOG

Chapter 7 30
Invensys Systems, Inc.
26561 Rancho Parkway South
Lake Forest, CA 92630
United States of America
http://iom.invensys.com

Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys Representative.
Email: [email protected]
Website: http://support.ips.invensys.com