Documente Academic
Documente Profesional
Documente Cultură
Engineered Software
Page
Network Installation
Guide
Overview
Feb. 2011
Version 2009a
Commuter Licensing
10
11
12
15
Overview
Network Requirements
Engineered Software uses the SafeNet Sentinel RMS software locking system with a USB dongle key to
distribute and control network licenses of its products. The Sentinel RMS Server software will run on
Windows XP, Windows Vista, Windows 7, Windows Server 2003/2003R2 and Windows 2008/2008R2
Server. Standard system requirements for the operating system should be sufficient to run the server
software.
Neither SafeNet nor Engineered Software support Sentinel RMS on computers with more than one
network interface card (NIC).
Neither SafeNet nor Engineered Software support Sentinel RMS on a virtual hardware system.
It is highly recommended the license server have a static IP address assigned to it.
The Sentinel RMS Server uses UDP port numbers 5093, 5094, and 5099, which have been registered to
SafeNet Inc. These UDP ports must be open for communications to the license server from all clients.
Windows 2003 server SP2/Windows 2008 may have closed ports by default so you will need to
verify them.
Network Installation
Complete network installation consists of two parts, each described in detail on the following pages.
Configure the License Server: This involves selection of a computer on the network to host the
license, the hardware key, installation of license server software, and exchanging codes with
Engineered Software to obtain the proper license file.
Install the Software on Client Workstations: Workstations may be configured using the default
setup directly from the Installation CD/downloaded media or from a network location. The IP
address of the License Server must be entered during the setup on each workstation.
Primary license administration is provided thru the use of the WlmAdmin tool which is described later in
this document, and found on the installation CD/downloaded media at \SERVER\CLIENT TOOLS
Commuter licensing is provided for PIPE-FLO Professional, PIPE-FLO Stock, and PIPE-FLO
Compressible. Client tools are available to enable users to checkout licenses to run the Software when
they are not connected to the network. These tools are described later in this document, and found on
the Installation CD/downloaded media at \SERVER\CLIENT TOOLS.
Additional administration tools and optional server configuration settings are available to manage
and monitor license usage. Instructions on how to use these tools can be found on our knowledge base
at http://www.eng-software.com/kb/item.aspx?article=1435
Page 2
Page 3
All license holders are issued a hardware key. If the key is lost, so are the programs licensed to that key.
DO NOT LOSE THE KEY. We will not reissue for a lost key. The cost to order a new key is the same as the initial cost of the number of network
licenses purchased.
Create a new mail message to unlock@eng-software.com. For clarity, use the subject line, PIPEFLO Network License Locking Codes
c) Include your product serial number(s) and company name in the body of the message.
d) Paste the codes from LOCKINGCODES.TXT into the message or include the file in the message as
an attachment.
e) After receiving the message with your locking codes, Engineered Software will send back a license
file that you will use in the next step.
g) Copy the file license.txt from the email received to the server tools folder you copied over previously.
( C:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\Servertools)
h) From the same directory, run WLMADMIN.EXE to install the new licenses to your license server.
Engineered Software Network Configuration & Installation Guide
Page 4
Browse under Subnet Servers, right-click on the name of the license server. Choose Add Feature -> from
a file -> to Server and its File. Select the file LICENSE.txt.
i) To view license availability, under WLMADMIN.EXE choose View/Refresh all. You should see the
PROF/COMP or STOCK license depending on the PIPE-FLO program purchased. Further detail on
working with WlmAdmin is provided later in this document.
3. Remove previous licenses (Upgrade customers only)
a) From your Sentinel RMS Server directory run the file
\SERVER\SERVERTOOLS\LICENSECLEANER.EXE and specify the path to your LSERVRC file located
in your Sentinel LM directory. By default, the path to the Sentinel LM (version 8.0.x or older) directory is
C:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS Server\WinNT. For RMS version 8.0.5
default path is C:\Windows\system 32 for the new RMS software)
b) For these changes to take effect, restart the Sentinel RMS Server software.
Win/XP/2003/Vista/7/2008, find the Sentinel RMS service in your services control panel. Select it,
choose Stop, and when the process completes, choose Start.
c) An alternate method to remove the previous license is to locate the LSERVRC, open it with notepad
and delete the previous license then save the file. To use this method you will need to stop the
Sentinel RMS service first then restart it after editing the file
Page 5
Windows Vista users: Refer to the following knowledge base articles for known issues with PIPE-FLO on the Windows
Vista and Windows 7 operating systems.
http://kb.eng-software.com/questions/180/ For Windows Vista
http://kb.eng-software.com/questions/342/ For Windows 7
The required feature license is found, but the version is not current.
Page 6
Code -2
Multiple versions of the required feature license are installed on the server. Remove
licenses from a previous version.
Code 9395199 No more licenses available on the license server.
For more troubleshooting assistance, refer to our Knowledge Base at the following articles:
http://www.eng-software.com/kb/item.asp?ID=1341
http://www.eng-software.com/kb/item.aspx?article=1408
http://www.eng-software.com/kb/item.aspx?article=1451
Page 7
Software Installation
1. Place the Program CD into the drive or browse to the downloaded media.
2. Run the program SETUP.EXE and follow the installation prompts that appear on your screen.
3. The Setup program will install all required files to your computer. It will also add the Overtime program to
the PIPE-FLO group in your Start Menu with links to start the program.
If you are adding the Overtime Feature to your existing PIPE-FLO Professional, you will need to install a
new PIPE-FLO license to your license server following the steps below. If you purchased your
OVERTIME with your PIPE-FLO then the OVERTIME feature is included in the license file already.
Follow the adding License procedure on pages 3 -5 substituting the Overtime Feature upgrade
Network License Locking Codes for the subject line when submitting the locking codes.
Page 8
Commuter Licensing
Commuter licensing is provided only for PIPE-FLO Professional, PIPE-FLO Stock, and PIPE-FLO
Compressible. It is not available for PUMP-FLO.
The most common use of commuter licensing is when a user of your network needs to use the Software
program on a portable computer that is not connected to the network.
The WCommute and WRCommute utilities are found on the Installation CD or downloaded media in the
path SERVER\CLIENT TOOLS. If you choose to allow users to check out Software licenses, you will
need to copy it to an available location on your network or copy the client tools folder to the user
workstations.
Checking out Licenses
To check out an authorization, the computer must be attached to the local network and have access to a
license server containing an available Software license. After checking out an authorization, the user
may disconnect the computer from the network and continue to run the Software.
A remote user (not attached to the local network) can also obtain an authorization by sending a commuter
locking code to a local user, who checks out the authorization. The local user then forwards the
authorization via email to the remote user to enable the Software on his computer.
Restricting Commuter Licensing
Commuter licensing uses up the same license tokens as other types of licensing. If you want to restrict
the percentage of license tokens on a specific license server that can be used by commuter licensing
authorizations, use the com option when you start the license server. (See Optional Server
configuration later in this document for details on license server startup options.) This makes sure that
commuter licensing doesnt use up all of the license tokens needed by other users of the Software on the
network.
Commuter Licensing Authorization Check in Policy
When checking out an authorization, the user requests authorization for a specific number of days (the
default is 30 days). The authorization expires after that many days, and the License Server
automatically recovers the license without any action by the user.
You may choose to instruct the local user not to bother checking the authorization in after returning. On
the other hand, if you are in danger of running out of license tokens for the Software, you may want to
encourage local users always to check authorizations back in as soon as possible.
Note that the commuter licensing user must check an authorization back into the same license server
from which the authorization was checked out.
Note: A remote commuter authorization cannot be checked back into the license server, and will
always remain checked out for the full number of days requested.
Page 9
Page 10
A remote user generates a commuter locking code for the remote computer, and sends the
commuter locking code to a local user who has access to the Software license.
The local user checks out a remote commuter authorization, and sends it to the remote user.
Note: A remote commuter authorization cannot be checked back into the license
server, and will remain checked out for the full number of days requested.
Getting a Remote Commuter Locking Code
1. On the remote computer, run the WRcommute utility. Within Windows Explorer, navigate to the
wrcommute.exe file and double-click the file to run it.
2. Click the Get Locking Code tab. You see the commuter locking code for the current computer.
3. Send the commuter locking code as an E-mail message to the local user who can check out the
authorization for you. Type an E-mail address in the E-mail address and click Send.
4. If wrcommute is unable to create the E-mail, save the locking code to a file and include the file in an Email message to the local user.
Checking out a Remote Commuter Authorization
1. On the local computer, follow steps 1-4 in the previous section Checking out a License on the Local
Area Network
2. Select the Check out authorization for remote machine check box and click Check Out.
3. Enter the commuter locking code received from the remote user. You can select Enter the locking
code for remote machine and type it in the text box or paste from the clipboard. You can also Get
locking code string for remote machine from a file.
4. Click OK. You see the Remote Commuter Licensing dialog box.
5. Send the commuter locking code as an E-mail message to the remote user. Type an E-mail address
in the E-mail address and click Send.
6. If wcommute is unable to create the E-mail, save the locking code to a file and include the file in an Email message to the local user.
Installing a Remote Commuter Authorization
1. On the remote computer, run the WRcommute utility.
2. Click the Install Remote Authorization Code tab.
3. Enter the remote authorization code received from the local user. You can select Enter remote
authorization code and type it in the text box or paste from the clipboard. You can also get remote
authorization code from a file.
Page 11
To always show the license servers you have defined (see below), select the Discover defined
servers on startup check box.
To automatically discover and display the license servers on your subnet, select Discover subnet
servers on startup check box. Be sure to select Save these preferences to a file to save your
choices.
Show client library error handler messages to pass license management error messages from
SentinelLM through to WlmAdmin.
Broadcast Interval to select the number of seconds between broadcasts to the network to
discover license servers.
Timeout Interval to select the number of seconds at which WlmAdmin will stop trying to contact a
license server. If you have a large network or a slow one, you might want to increase this number
if you find WlmAdmin has difficulty retrieving information from license servers.
Page 12
3. Once a license server is defined, you can add more or select a server and click Remove to
remove it from the list.
4. Click OK to return to the main WlmAdmin screen.
To Discover All License Servers on Your Network Subnet
Go to the left-hand pane of the main WlmAdmin window and double-click Subnet Servers. WlmAdmin
will broadcast to the network to discover all license servers and display them here.
To Refresh the Network Display
Right-click on Defined Servers or Subnet Servers and select Refresh to tell WlmAdmin to display new
information on that group of license servers. You may also select Refresh All from the View menu to
refresh the display for all license servers shown.
To See Information on a License Server
Click the name of a license server in the left-hand pane of the main window. In the right-hand pane of the
display, you see the IP or IPX address of the computer containing the license server and its host name.
To Add or Remove a License Server from the Defined Server List
Right-click the name of a license server in the left-hand pane of the main window. From the menu, select
Add to Defined List or Remove from Defined List.
To Shut Down a License Server
Right-click the name of a license server in the left-hand pane of the main window. From the menu select
Shutdown Server.
To Add a License Code to the License Server from the Keyboard
1. Right-click the name of a license server in the left-hand pane of the main window. From the menu
select Add Feature. To add the license by typing in the license code, select From a String.
2. Type the license code in the License code box.
3. If this is a redundant license code, enter the token distribution criteria in the Distribution criteria
box in this format: Server1:tokens1^Server2:tokens2... where Server is an IP address, IPX
address, or host name of the computer containing a redundant license server and tokens is the
number of license tokens to be allocated to that redundant license server. Note that all
Server:tokens arguments must be separate with a ^ symbol.
4. To permanently add the license code to the license server license file as well as temporarily
adding it to the license server memory (only in effect until the license server is rebooted), select
the Add feature to servers file check box.
5. Click Add.
To Add a License Code to the License Server from a File
1. Right-click the name of a license server in the left-hand pane of the main window. From the menu
select Add Feature. Select From a File and To Server (to add the license code temporarily to
the license server memory, only in effect until the license server is rebooted) or To Server and
its File (to add the feature both temporarily to the license server memory and permanently to its
license file).
2. Now select the license code file from the standard file selection window.
Page 13
Page 14
1-360-292-4060
Fax:
1-360-412-0672
solutions@eng-software.com
Web:
http://www.eng-software.com
Technical support is available Monday through Friday from 7:30 a.m. to 4:30 p.m. Pacific Time.
(Excluding recognized U.S. holidays).
When contacting Engineered Software for support, please gather the following information beforehand
(You may want to print out a copy of this page and fill out the information.):
Program Name:
Program Serial Number: (Found on installation CD or program About dialog):
License Server Operating System (Type, Version):
Workstation Operating System (Type, Version):
Error Message received (Code, number, etc): __________________________________
If there is any additional information that you can think of to add, please do so. The more information we
have, the quicker we will be able to help you.
Installation Tips
To reduce downtime for your users run the getcode.bat file prior to uninstalling the existing Sentinel
LM/RMS server or license file. That way you can have the new license file already prior to starting the
installation procedure.
Install the new license before installing the new client software. The license is backwards compatible so
your clients will be able to continue to run their existing version until you are able to upgrade them.
Page 15