Concurrent License Administrator’s Guide for IBM SPSS Statistics

Before you start

You need your authorization code. The authorization code helps you to get a license for the concurrent license manager. The concurrent license manager controls your concurrent license and allows end users to run SPSS Statistics.

You should have received separate instructions for obtaining your authorization code. If you cannot find your authorization code, contact Customer Service by visiting https://www.ibm.com/products/spss-statistics/support.

To make sure that you set up the concurrent license correctly, follow these steps:

1. Install the concurrent license manager. The concurrent license manager is the utility that will serve up the concurrent licenses to end users. You can install the license manager on any computer on your network. This is typically a server to which desktop computers can connect. See Installing the concurrent license manager for more information.
2. License your product. This action will give the license manager the required information for serving up the licenses. See Licensing your product for more information.
3. Test the concurrent license manager. You should test license manager to make sure it is serving up licenses. See Testing the license manager for more information.
4. Install IBM SPSS Statistics on the local desktop computers. You or your end users will complete the full installation on the desktop computers. During an installation, an end user can specify the computer on which the license manager is running. When an end user tries to launch IBM SPSS Statistics, the product communicates with this license manager to get a license. If a license is available, IBM SPSS Statistics launches. See Installing the product on the local desktop computers for more information.

No administration steps are required for the installation, but if any problems arise, see Administering the concurrent license.

Ghosting

You can ghost the software by installing the license manager and then installing the product on a local desktop that will be used for creating the ghosting image. Ghost the additional computers as needed.

Citrix and Terminal Services

You can install and publish the IBM SPSS Statistics application on your Citrix or Terminal Services Server in the same way that you install and publish other Windows applications.

Mixed licensing

IBM SPSS Statistics has limited support for a mixed licensing environment (a combination of local authorized user licenses and concurrent licenses). In a typical environment, all licenses are handled locally or through the concurrent license manager. For example, if the main product is licensed through the concurrent license manager, add-on modules are also licensed through the concurrent license manager.

The only option for mixed licensing is to license the main product through the concurrent license manager and to license the add-on modules on the end user's computer with licenseactivator. To set up this type of mixed licensing, install IBM SPSS Statistics with a concurrent license. Then use licenseactivator on the end user's computer to license the add-on modules. For more information about licenseactivator, see Using licenseactivator to install a license automatically.

IBM SPSS Statistics does not support the opposite scenario to license the main product locally and to license the add-on modules through the concurrent license manager.

Installing the concurrent license manager

Before end users install IBM SPSS Statistics on their desktop computers, you must install the concurrent license manager. This utility is a continuously executing service or daemon that you will typically install on one computer on your network. (You also have the option of installing on multiple computers, in which case you would set up redundant license managers. For more information, see #Concurrent_License_Administrator_Guide__setting_up_redundant_license_servers.) You do not install the concurrent license manager on the end users' desktop computers.

Whenever an end user starts a concurrent-licensed IBM SPSS application, the application will request a license from the license manager. This utility delivers licenses up to a fixed number of simultaneous end users, determined by the license that you have purchased. After this number has been met, any further requests for licenses are refused. If you find that end users are often being refused licenses, you can contact your sales representative to purchase a license that allows more simultaneous users.

License managers can be downloaded as an eImage.

Multiple operating systems

The platform on which the concurrent license manager is running does not have to match the platform on which the client is running. For example, a Linux license manager can serve up licenses for Windows clients.

Administering the license manager

You administer the license manager using the license manager administrator, which is available only for Windows. Therefore, you need at least one Windows machine on which to install the license manager administrator.

System requirements

The computer on which you install the concurrent license manager must meet the minimum operating system requirements. The license manager does not require a server class machine.

Important: If a firewall is running on the computer on which the license manager is installed, you must open port 5093 for UDP. Otherwise, client computers will not be able to retrieve a license from the license manager. Furthermore, if you are using redundant license manager machines, you must open port 5099 for UDP to enable the license manager machines to communicate with each other.

Upgrading the license manager

If you have a previous version of the license manager installed, you must perform the following steps:

1. Go to the directory in which you installed the old license manager.
2. Copy the lservrc file.
3. Save the lservrc file to a safe location.
4. If any users have checked out commuter licenses, make sure those users check the licenses back in. See Concurrent_License_Administrator_Guide.html#Concurrent_License_Administrator_Guide__configuring_commuter_licenses for information about obtaining a list of checked out licenses.
5. Shutdown the license manager. See #Concurrent_License_Administrator_Guide__starting_and_stopping_the_license_manager for more information.
6. Uninstall the old license manager. See #Concurrent_License_Administrator_Guide__uninstalling_the_license_manager_and_tools for more information.
7. Install the new license manager. For information about installing on Windows, see #Concurrent_License_Administrator_Guide__installing_the_license_manager_and_tools_on_windows. For information about installing on UNIX/Linux, see #Concurrent_License_Administrator_Guide__installing_the_license_manager_on_non-windows_systems. For information about installing on macOS, see #Concurrent_License_Administrator_Guide__installing_the_license_manager_on_macos.
8. Copy the saved lservrc file to the directory in which you installed the new license manager. If you accepted the default location on Windows, check the C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT folder.

Installing the license manager and tools on Windows

1. Insert the concurrent licensing tools DVD/CD into the DVD/CD drive of the network computer on which you want to run the license manager. Copy the archive that contains the license manager and tools for your Windows operating system from the DVD/CD.

   -or-

   If you downloaded an eImage file, use an archive utility such as WinZip to extract all the files in the appropriate eImage.

2. Extract the contents of the archive that contains the license manager and tools.
3. Run setup.exe from the extracted directory and follow the instructions that appear on the screen.
4. You also have the option of installing the license manager administrator and tools on another Windows machine if you want to administer the license manager remotely.

Installing the license manager on non-Windows systems

1. Insert the concurrent licensing tools DVD/CD into the DVD/CD drive of the network computer on which you want to run the license manager. Look for the archive that contains the license manager and tools for your operating system.

   -or-

   If you downloaded an eImage file, go to the location where you downloaded the file.

2. Go to the location where you downloaded your eImage file.
3. Extract the contents of the archive that contains the license manager and tools to the location where you want to install the license manager.
4. Install the license manager administrator on a Windows machine. See #Concurrent_License_Administrator_Guide__installing_the_license_manager_and_tools_on_windows for more information.
5. Refer to #Concurrent_License_Administrator_Guide__starting_and_stopping_the_license_manager for information about starting the license manager.

Installing the license manager on macOS

1. Insert the concurrent licensing tools DVD/CD into the DVD/CD drive of the network computer on which you want to run the license manager. Look for the archive that contains the license manager and tools for your operating system.

   -or-

   If you downloaded an eImage file, go to the location where you downloaded the file.

2. Extract the contents of the archive that contains the license manager and tools to the location where you want to install the license manager.
3. Install the license manager administrator on a Windows machine. See #Concurrent_License_Administrator_Guide__installing_the_license_manager_and_tools_on_windows for more information.
4. Refer to #Concurrent_License_Administrator_Guide__starting_and_stopping_the_license_manager for information about starting the license manager.

Licensing your product

On non-Windows operating systems, you must install the license from the command prompt after installing the license manager.

Installing a license in a virtual environment

If you installed the concurrent license manager in a virtual environment, there are special instructions for licensing. On a virtual machine the hardware is virtual, and the locking code that ties the license manager to the license might change when the virtual machine is restarted. To ensure the license manager works correctly, you need to find a locking code that does not change when the virtual machine is restarted. When you find a stable locking code, you will use it to license the license manager.

Checking the locking code

1. Open a command prompt.
2. Change to the following directory.
   • Windows. If you accepted the default location during installation, the license manager installation directory is C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT.
   • Other platforms. The license manager installation directory.
3. At the command prompt, type echoid (Windows) or ./echoid64 (other platforms).

You will see something like the following in the output:

Locking Code 1 : 4-12A1B

The number that appears immediately before the hyphen (-) is the locking code criteria. The locking code criteria is a number that represents the virtual hardware that is used for the locking code (in this example, it is 4, which represents the OS volume serial ID). The number after the hyphen is the locking code itself (in this example, it is 12A1B).

Following are the possible locking code criteria.

Locking code criteria	Virtual hardware
2	IP address
4	OS volume serial ID
8	Hostname
10	Ethernet card

Confirming that the locking code is stable

1. After checking the locking code, restart the virtual machine.
2. Check the locking code again (see Checking the locking code).
   • If the locking code doesn't change, reboot and check a few more times. If the locking code is stable, you are ready to license (see Licensing the license manager with the new locking code).
   • If the locking code does change, you need to update the locking code (see Updating the locking code).

Updating the locking code

1. In a text editor, open echoid.dat, which you can find in the following directory.
   • Windows. If you accepted the default location during installation, the license manager installation directory is C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT.
   • Other platforms. The license manager installation directory.
2. You will see a single hexadecimal number that represents the current locking code criteria. Change this number to one of the acceptable locking code criteria in hexadecimal format.

Locking code criteria in hexadecimal format	Virtual hardware
0x002	IP address
0x004	OS volume serial ID
0x008	Hostname
0x010	Ethernet card

Licensing the license manager with the new locking code

After you find and update to a stable locking code, there are no further licensing steps that are particular to virtual environments. Use the command prompt to complete installation of the license.

Installing a license from the command prompt

You have two options for installing from the command prompt. You can use licenseactivator to get a license from the Internet automatically, or you can use echoid to get a license manually.

Using licenseactivator to install a license automatically

The computer on which you are installing the license must be connected to the Internet. If it isn't, install the license manually. See Installing a license manually for more information.

1. Log in as the user who installed the license manager.
2. Open a command prompt and change directories to the license manager installation directory. This is the directory in which you installed the license manager, not the directory in which you installed IBM SPSS Statistics. If you accepted the default location on Windows, check the C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT folder.
3. You typically have an authorization code. In the simplest case, you enter the following at the command prompt. See below for more details about the command prompt usage. licenseactivator where is your authorization code.

You should see a message that the license was added successfully. If it wasn't, note the error code and try installing the license manually. See Installing a license manually for more information.

When you use licenseactivator, it licenses the product and writes a log file to its directory. The name of the log file is licenseactivator_<month>_<day>_<year>.log. If any errors occur, you can check the log file for more information. This information is also useful if you contact IBM Corp. for support.

Using licenseactivator with authorization codes

licenseactivator is typically used with one or more authorization codes that you received when you purchased the product. Enter all of the text on one line.

licenseactivator authcode1[:authcode2:...:authcodeN] [PROXYHOST=proxy-hostname][PROXYPORT=proxy-port-number][PROXYUSER=proxy-userid] [PROXYPASS=proxy-password]

Note: Use ./licenseactivator when working with macOS.

• Multiple authorization codes are separated by colons (:).
• The proxy settings are optional, but you may need them if your computer is behind a proxy. Which proxy settings are needed depend on your specific proxy configuration. You might need all of them.

  PROXYHOST

  The server name or IP address of the proxy host

  PROXYPORT

  The port number for connecting to the Internet through the proxy

  PROXYUSER

  If required, the user ID for the proxy

  PROXYPASS

  If required, the password associated with the user ID

Using licenseactivator with license codes

In less common scenarios, IBM Corp. may have sent you a license.

licenseactivator licensecode[:licensecode2:...:licensecodeN]

Note: Use ./licenseactivator when working with macOS.

• Multiple license codes are separated by colons (:).
• When using license codes, licenseactivator does not connect to the Internet, so you do not need to specify proxy information.

macOS-specific licenseactivator features

The following features and setting are specific to running licenseactivator on macOS systems.

Setting a network license

The following example demonstrates setting a network license:

./licenseactivator LSHOST= "mylicserver" COMMUTE_MAX_LIFE=7

Licensing via the activation.properties file

The following example demonstrates using the activation.properties file to license the product.

./licenseactivator -f activation.properties

An activation.properties file template is provided in <installation directory>/Resources/Activation.

Note: Enter ./licenseactivator --help in a Terminal window to display the full list of licenseactivator options.

Installing a license manually

1. Log in as the user who installed the license manager.
2. Open a command prompt and change directories to the license manager installation directory. Note that this is the directory in which you installed the license manager, not the directory in which you installed IBM SPSS Statistics. If you accepted the default location on Windows, check the C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT folder.
3. Get the lock code for the server machine. At the command prompt, type echoid (Windows) or ./echoid64 (other platforms).
4. Send the lock code and your authorization code to IBM Corp. by contacting IBM customer support at https://www.ibm.com/mysupport. IBM Corp. will then provide a license code or a file containing a license code.
5. Use licenseactivator to enter the license code or codes.

Adding a license

You may want to add a license at a later time. The process for adding a license is the same as installing the original license.

Viewing your license

You can view your concurrent license (including the number of users) in the WlmAdmin application. For information about the WlmAdmin application and specifics about viewing the license, see Administering the concurrent license.

Testing the license manager

To make sure the license manager is serving up licenses correctly, you should test it.

1. . If you haven't installed the license manager administrator on another machine, install it on a Windows machine that is not running the license manager you want to test. See #Concurrent_License_Administrator_Guide__installing_the_license_manager_and_tools_on_windows for more information.
2. Start the WlmAdmin application. See #Concurrent_License_Administrator_Guide__starting_the_wlmadmin_application for more information.
3. Add the remote license manager server that you want to test. See #Concurrent_License_Administrator_Guide__adding_a_server for more information.
4. View the licenses on the remote server. See #Concurrent_License_Administrator_Guide__viewing_details_about_a_license for more information.

If you are able to view the license, the license manager is ready for local desktop computers to connect to it. You can proceed with installing the product on local desktop computers. If you are not able to view the license, review the previous steps to ensure the license manager was installed correctly.

Installing the product on the local desktop computers

You have two options for installing the full product locally on an end user's computer. You can manually install on each computer, or you can use an application like Systems Management Server (SMS) to push the installation to the computers running Windows. You also have the option of running a silent installation on macOS.

To manually install on a local desktop

1. Make the installation media available. Download the eImage for the product and extract the files to a shared network drive. If you have physical installation media, make as many copies of the DVD/CD as you need or place it on a shared network drive.
2. Copy the installation instructions and prepare licensing information. Make as many copies of the product installation instructions as you need. The installation instructions are available from the download site or, if you received physical installation media, in the /Documentation/<language>/InstallationDocuments directory on the DVD/CD. Look for the instructions that correspond to your license type. After installation, the end user must enter the IP address or the name of the network computer on which the concurrent license manager is running. Fill out this information in the space provided at the beginning of the instructions before copying them.
3. Distribute the installation materials to end users. Distribute the downloaded file (or network location, or installation DVD/CD), the installation instructions, and the licensing information to end users who can manually install on each computer as needed.

To push to the local desktops running Windows

Because IBM SPSS Statistics installations are compatible with Microsoft Windows Installer (MSI), you can push an installation to the end-user desktop computers.

Pushing an installation to Windows computers

Pushing an installation is a method for remotely distributing software to any number of end users without any user intervention. You can push the full installation of IBM SPSS Statistics to the end-user desktop computers running Windows. The technology that you are using for pushing the installation must support the MSI 3.0 engine or higher.

Overwriting a previous version

If you are going to push to the same directory in which a previous version of IBM SPSS Statistics is installed, the installer will overwrite the existing IBM SPSS Statistics installation. You can optionally push the uninstallation as you push an installation. See Pushing an uninstallation for more information.

Properties for push installations

Following are the properties that you can use for push installations. All properties are case sensitive. Values must be quoted if they contain spaces.

Table 1. Properties for push installations

MSI files

The IBM SPSS Statistics.msi file is located under the Windows\SPSSStatistics\ directory in the extracted contents of the downloaded eImage.

Command line example

The following example is a command line that you could use to push a product installation. Enter all of the text on one line.

MsiExec.exe /i "IBM SPSS Statistics.msi" /qn /L*v logfile.txt INSTALLDIR="C:\Statistics" LSHOST="mylicserver"

Using SMS to push the installation

The basic steps for using Systems Management Servers (SMS) to push IBM SPSS Statistics are:

1. If you downloaded the software, you must first extract the contents of the eImage, then copy the appropriate subdirectory under the Windows\SPSSStatistics\ directory to a directory on a network computer.
2. . Edit the IBM SPSS Statistics.sms file located in the copied directory. Using a text editor, modify the value of CommandLine by adding the appropriate properties. For a list of the available properties, see Properties for push installations. Make sure to specify the correct MSI file in the command line.
3. Create a package from the IBM SPSS Statistics.sms file and distribute the package to the end-user desktop machines.

Using Group Policy or related technology to push the installation

Note: You can download either the '.exe' or '.iso' installer for IBM SPSS Statistics-

When you download the '.exe' installer, refer to the process in this technote to extract the .msi and .mst files that are needed for the push install.

If you download the '.iso', then the .msi and .mst files are saved in the ..\SPSSStatistics\Windows\SPSSStatistics\win64\ directory.

1. If you downloaded the software, you must first extract the contents of the eImage, then copy the appropriate subdirectory under the Windows\SPSSStatistics\ directory to a directory on a network computer.
2. Using an application like ORCA, edit the Properties table in the appropriate IBM SPSS Statistics 30.msi file under the copied folder. ORCA is part of the Windows 2003 Server SDK, which you can find at http://www.microsoft.com/downloads by searching for the SDK. For a list of the properties that you can add to the Properties table, see Properties for push installations. Make sure to use the correct MSI file.
3. Create a package using the edited IBM SPSS Statistics 30.msi file and distribute the package to the end-user desktop computers.

Pushing the installation to a non-English system

You can push to a non-English system without additional specification. However, the installer language (if pushing an interactive installation) will appear in English, the user interface will appear in English, and the help will appear in English. Users can change the user interface language after installation, but localized help will not be available.

You can use the TRANSFORMS property to specify one of the MST files available in the downloaded '.iso' installer file. The MST file will ensure the installer, user interface, and help appear in the specified language. MST files are not available if you downloaded IBM SPSS Statistics. Users will need to manually install the language packs for the localized help and manually change the user interface language in the product.

The TRANSFORMS property is a parameter for MsiExec.exe. The following example uses the TRANSFORMS property to push a French installation. The installer will appear in French, the user interface will appear in French, and French help will be installed. (You can also override the help language with the HELPCHOICE property. See Properties for push installations for more information. ) Enter all of the text on one line.

MsiExec.exe /i "IBM SPSS Statistics 30.msi" /qn /L*v logfile.txt INSTALLDIR="C:\Statistics" LSHOST="mylicserver" TRANSFORMS=1036.mst

Table 2. Language MST Files

Language	MST File
English	1033.mst
French	1036.mst
German	1031.mst
Italian	1040.mst
Japanese	1041.mst
Korean	1042.mst
Polish	1045.mst
Russian	1048.mst
Spanish	1034.mst
Simplified Chinese	2052.mst
Traditional Chinese	1028.mst

Pushing an uninstallation

Note that when you push the uninstall command, the end user loses customizations. If specific users require customizations, you can exclude those users from the distribution and ask them to install the product manually.

If you push an installation of a later version of IBM SPSS Statistics, you may want to uninstall first. You can do this silently by using the push_uninstall.bat file that is included in the extracted eImage files.

The following table lists the uninstall IDs for previous releases.

Table 3. Uninstall IDs for IBM SPSS Statistics

Version	Uninstall ID
28.*	Starting with version 28, use the push_uninstall.bat file to uninstall the product.
27.0.1	{4FEFE042-19D2-47AD-9D27-B24710418A05}
27.0	{8EAD21F8-AD8B-4C6F-ABE6-92357CAB043E}
26.*	{1AC22BAE-DC13-4991-9910-AE3743A4592D}
25.*	{C2D1E17D-CB8A-4742-84FA-1DB5C6A1ABDD}
24.*	{4762AE15-E5A3-43BF-8822-1CFC70FB147A}
23.*	{C3BA73A4-2A45-4036-8541-4F5F8146078B}
22.*	{104875A1-D083-4A34-BC4F-3F635B7F8EF7}
21.*	{1E26B9C2-ED08-4EEA-83C8-A786502B41E5}
20.*	{2AF8017B-E503-408F-AACE-8A335452CAD2}
19.*	{06C43FAA-7226-41EF-A05E-9AE0AA849FFE}
18.*	{C25215FC-5900-48B0-B93C-8D3379027312}
17.0.2	{2ECDE974-69D9-47A9-9EB0-10EC49F8468A}
17.0.1 17.0.0	{46B65150-F8AA-42F2-94FB-2729A8AE5F7E}
16.*	{621025AE-3510-478E-BC27-1A647150976F}

Running a silent installation on macOS computers

A silent, unattended installation does not display a graphical interface and does not require any user intervention.

Use the following command to run a silent installation. On macOS you must run as root or with the sudo command.

sudo installer -pkg IBM\ SPSS\ Statistics.pkg -target /

sudo installer -pkg IBM\ SPSS\ Statistics.pkg -target /
cd /Applications/IBM\ SPSS\ Statistics/Resources/Activation
./licenseactivator LSHOST=[Server Name]

The licenseactivator tool is installed at: /Applications/IBM SPSS Statistics/Resources/Activation.

Disabling Internet connectivity features

After installation, you can use the following command to disable Internet connectivity features (information sharing, error reporting, and welcome screen updates). The command must be run from the /Applications/IBM SPSS Statistics/Resources/Configuration directory (this is the default installation location):

./Configure NO

Administering the concurrent license

The license manager maintains your concurrent license. To administer the license manager itself and to view information about the concurrent licenses that it is maintaining, you can use the WlmAdmin application, which is the main user interface for the license manager administrator. The license manager administrator is installed automatically with the concurrent license manager on Windows. If you are administering a license manager on a non-Windows machine or a remote Windows machine, install the license manager administrator on a separate Windows machine. See #Concurrent_License_Administrator_Guide__installing_the_license_manager_and_tools_on_windows for more information.

Starting the WlmAdmin Application

From the Windows Start menu, choose: [All] Programs > IBM > SPSS License Tools > <version> > Sentinel RMS Server Administration

Adding a server

Before you can administer a license manager, you need to add its server to the WlmAdmin application. You have two options for adding the server.

To manually add a server

1. From the WlmAdmin application menus, choose: Edit > Defined Server List
2. In the Defined Server List dialog, enter the name or IP address of the server on which the license manager is running.
3. Click Add.
4. Click OK.

The server now appears in the Defined Servers lists in the left pane of the WlmAdmin application.

To view a list of servers on the subnet

1. In the left pane of the WlmAdmin application, click the + sign next to Subnet Servers.

A list of license manager servers on your subnet appears. If you can't find a specific server with this method, manually add it as described above.

Obtaining log information

If end users have difficulty checking out licenses, the log files may contain useful information. You can use the LSERVOPTS environment variable and the -f <trace-log-file> and -l <usage-log-file> options to specify that log files should be created. For more information about this environment variable and its options, refer to the SafeNet documentation in the Content directory in the license manager administrator installation directory.

Viewing details about a license

You can view details about licenses that you added either manually or through the License Authorization Wizard.

1. In the left pane of the WlmAdmin application, click the + sign next to the license manager server to see the license(s).
2. Click the name of the license. The right pane displays details about the license. Codes are used to identify the licenses. The first part of the code indicates the feature. The second part indicates the version.

To see the names associated with the feature codes

1. Using a command prompt, change to the directory in which the license manager administrator is installed.
2. Type lsmon.exe <server> (Windows) or ./lsmon64 <server> (other operating systems), where <server> is the name or IP address of the server on which the license manager is running.

The output lists all the features available on the server, grouped by product and version.

Setting up redundant license servers

You can set up multiple, redundant license servers that support the same users. Redundant servers can help prevent any interruption that may occur when a server crashes. Another redundant server can take over the management of the license when the first server crashes.

You will need a special license code to enable the redundancy feature, as described in the following steps. For assistance with creating a redundant license key or any other licensing issue, visit the IBM SPSS License Key Center.

There must be an odd number of servers (at least three of them), and a majority must be running at the same time. For example, if there are three redundant license servers, two of them must be running.

Preparing each redundant license server

1. Install the license manager. See Installing the concurrent license manager for more information.
2. Using a command prompt, change to the directory in which you installed the license manager.
3. Get the lock code for each server machine. At the command prompt, type echoid (Windows) or ./echoid64 (other operating systems).
4. Write down the lock code. You will need the lock code for the next steps.
5. Repeat these steps for each redundant license server.

Activating the redundant licenses

1. Go to the IBM SPSS License Key Center (https://spss.subscribenet.com/control/ibmp/login).
2. Create a concurrent authorization code.
3. After the concurrent authorization code is created, click the code and then scroll down until you see the fields for Lock Code. You will now have the ability to add multiple lock codes to the license key.
4. Using the lock codes from the previous steps, enter the lock codes into the appropriate fields.
5. Click Submit.

Setting up the redundant license server pool

1. . If a license manager is running on any of the redundant license servers, stop the license manager on each computer.
2. From the WlmAdmin application menus, choose: Edit > Redundant License File. This action opens the WrlfTool application.
3. From the WrlfTool application menus, choose: File > New.
4. For each redundant license server, click Add to specify the hostname and IP address of each server.
5. Change the order of the servers to indicate the order in which the redundant license servers are used. The first one in the list is the primary server.
6. Click Add License to add the license(s) that you received from Customer Service or your local office. If you received multiple licenses, be sure to add every one.
7. Click OK.
8. Click Done when you are finished.

Saving the redundant license file

1. From the WrlfTool application menus, choose: File > Save As.
2. Save the redundant license file (lservrlf) to an easily accessible location. You will need to copy the file in the next steps.

Configuring the redundant license servers

1. Copy the redundant license file (lservrlf) to the license manager installation directory on Windows. If you accepted the default location, check the C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT folder. On other operating systems, copy the file directly to the license manager installation directory. There must be at least three redundant license servers.
2. Start the license manager on each redundant license server.

Configuring end-user computers

When the end user installs the product, the user specifies all redundant servers, with the server names or IP addresses separated by a tilde (for example, server1~server2~server3). The setup program then adds the necessary configuration information to the end user's computer. If the product is already installed on the desktop computers, you can perform the following manual steps to add the configuration information.

You can also push an uninstall followed by a new install that defines all the servers. Refer to Pushing an installation to Windows computers for information about pushing installations.

1. Using a text editor, open commutelicense.ini. On Windows, this file is located in the product installation directory on the desktop computer. On macOS, this file is in the <installation directory>/Resources/Activation/ directory.
2. Change the value of DAEMONHOST to the server names or IP addresses separated by a tilde (~). For example:

   DAEMONHOST=server1~server2~server3

3. Save commutelicense.ini.

Configuring commuter licenses

Commuter licenses allow your end users to check out licenses from the license manager, so that they can use the license when not connected to the network. On Windows, commuter licenses are not enabled by default. They are enabled by default on other operating systems. Instructions for actually checking out the commuter license appear in the end user installation instructions. You can restrict the percentage of licenses that are enabled for commuting on the license manager server. It's a good idea to restrict commuter licenses to prevent all the licenses (tokens) from being used up by commuters. After the specified percentage of licenses have been used by commuters, no more will be available until the commuter licenses expire or are checked back in. You can also configure the maximum duration for which an end user can check out a license. The default maximum duration is seven days.

To set the percentage of available commuter licenses

1. Create an LSERVOPTS environment variable on the license manager server. This variable is created during the license manager installation on Windows, so you need to complete this step only for the other operating systems.
2. Edit the value of the LSERVOPTS environment variable to include -com <percentage>, where is a numeric value between 0 and 100 indicating the percentage of licenses that are available for commuting. Specifying 0 disables commuter licenses. This switch is included by default on Windows and is set to 0.
3. Restart the computer on which the license manager is running.

To set the maximum duration for commuter licenses

The maximum length of time a user can check out a commuter license is specified by the CommuterMaxLife setting in the commutelicense.ini file on the desktop computer. On Windows, commutelicense.ini is located in the product installation directory on the desktop computer. On macOS, you must edit the commutelicense.ini file that is located in <installation directory>/Resources/Activation. For Windows and macOS, open commutelicense.ini and look for CommuterMaxLife. Set the value of this option to the maximum number of days for which an end user can check out a commuter license. This should be a number between 1 and 30. You can also set this value when you push the installation. See Pushing an installation to Windows computers for more information.

Note: This functionality works off the date, not the time. For example, if you set the CommuterMaxLife option to one day, then check a license out at 9 a.m., this license does not get checked back in until midnight on the following day. So although CommuterMaxLife is set to one day, the license is actually held for 39 hours.

To obtain a list of checked out licenses from the command line

You can find out which users have checked out licenses.

1. Using a command prompt, change to the directory in which the license manager administrator is installed.
2. Type lsmon <server> (Windows) or ./lsmon64 <server> (other operating systems), where <server> is the name or IP address of the server on which the license manager is running. You can omit the license server name if you want to view checked out licenses for only the localhost server.

To obtain a list of checked out licenses from the WlmAdmin application

You can also view checked out licenses in the WlmAdmin application:

1. In the left pane of the WlmAdmin application, click the + sign next to the license manager server.
2. Click the + sign next to Clients. Clients using the concurrent license are listed. If no clients are listed, no users are using the concurrent license.
3. Select a particular Client to view whether the client has a checked out license. Review the Detailed Information area in the right pane after selection.

Configuring license reservations

You can create a reservation file, which specifies how many licenses are reserved for specific users or groups of users. Users are identified by network IDs or computer names (not IP addresses). For example, you can set up a reservation file that reserves the license for a group of power users. Licenses will always be available for these users. You can also use the reservations to prevent certain users from accessing the license.

Creating a new reservation file

1. From the WlmAdmin application menus, choose: Edit > Reservation File. This action opens the Wlsgrmgr application.
2. From the Wlsgrmgr application menus, choose File > New.

Adding licenses and users to the reservation file

1. From the Wlsgrmgr application menus, choose: Feature > Add.
2. Click Next on the first screen of the wizard.
3. Specify the feature code associated with the license that you want to reserve. Refer to #Concurrent_License_Administrator_Guide__viewing_details_about_a_license for information about getting the feature codes associated with licenses. Also define a specific version, which is entered as it appears in the WlmAdmin application (for example, 160). The version is not optional. Ignore the Capacity controls, because capacity licenses are not supported.
4. Click Next.
5. Specify a name for a group of users. The name is arbitrary, but you should make it descriptive (for example, Sales).
6. Specify the number of licenses that are reserved for the group. Group members can still access all licenses, but the number of licenses you specify will no longer be available for users who are not included in the group. That is, if you have 10 licenses and you reserve five, members of the group have 10 licenses available to them, while other users have only five.
7. On the Members window, click Add to specify a user or computer name associated with the group (do not use IP addresses). If the user or machine is included in the group, that user or machine can use the reserved license. If the user or machine is excluded from the group, that user or machine cannot access the license at all. Specify as many users or machines as needed. Note that groups must be mutually exclusive. Therefore, different groups for the same license cannot contain common users or computers.
8. Click Finish when all users have been added to the group.
9. Add other groups or licenses as needed. You can also modify or delete licenses and groups by right-clicking one and choosing Properties.

Saving the reservation file

1. When finished defining the reservation file, from the menus choose: File > Save As.
2. Save the file to an easily accessible location. You will need to copy the file in the next step.
3. To enable the license server to automatically find the lsreserv file at start up and copy the file to the license manager installation directory on Windows. If you accepted the default location, check the C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT folder. On other operating systems, copy the file directly to the license manager installation directory.
4. If you want the same reservations to apply for all redundant servers, copy the reservation file (lsreserv) to each server.
5. Restart each license manager when finished.

Starting and stopping the license manager

The method for starting the license manager depends on your operating system.

Windows

On Windows machines, the license manager is a System Service. The service is automatically started by default. However, if you need to start it manually:

1. In the Windows Control Panel, double-click Administrative Tools.
2. Double-click Services.
3. Locate Sentinel RMS License Manager for IBM SPSS in the Services list.
4. Right-click the service and choose Start or Stop.

Other operating systems

On other operating systems, the license manager is a daemon service. Complete the following steps to start it manually. You can also configure the license manager to start automatically (instructions follow).

1. Using the command prompt, browse to the directory in which you installed the license manager.
2. Starting. As root, type ./lserv64 & at the command prompt and press Enter.
3. Stopping. As root, type ./lsrvdown64 <hostname> at the command prompt, where <hostname> is the network name of the computer on which the license manager is running. Then press Enter.

Configuring the license manager to start automatically

Windows

1. In the Windows Control Panel, double-click Administrative Tools.
2. Double-click Services.
3. Locate Sentinel RMS License Manager for IBM SPSS in the Services list.
4. Right-click the service and choose Properties.
5. Set the Startup type to Automatic.
6. Click OK.

Other operating systems

1. Add ./lserv64 & to one of the operating system startup files.

Uninstalling the license manager and tools

Windows

1. From the Windows Start menu, choose: Settings > Control Panel.
2. Double-click Add/Remove Programs.
3. Select Sentinel RMS License Manager for IBM SPSS and then click Remove.
4. Click Yes when prompted to remove the license manager.

Other operating systems

1. Using the command prompt, browse to the directory to which you installed the license manager.
2. As root, stop the license manager by typing ./lsrvdown64 <hostname> at the command prompt, where <hostname> is the network name of the computer on which the license manager is running. Then press Enter.
3. Remove the directory where the license manager is installed.

Troubleshooting desktop computers

If the end users' desktop computers are having trouble finding the license manager:

1. Run lswhere (Windows) or ./lswhere64 (macOS) to verify that the desktop computer can find the network computer on which the license manager is running. See Running lswhere for more information.
2. Make sure the license manager service is running on the network computer.
3. Check the appropriate commutelicense.ini file. On Windows, this file is located in the product installation directory on the desktop computer. On macOS, this file is in the <installation directory>/Resources/Activation/ directory. Open commutelicense.ini and make sure DAEMONHOST is set to the correct name or IP address of the computer on which the license manager is running. If you are using redundant servers, this should define all of them. Each name is separated by a tilde (~) character. For example, if the license manager computers are SERVER1, SERVER2, and SERVER3, DAEMONHOST is set to SERVER1~SERVER2~SERVER3.

Running lswhere

You can run lswhere (Windows) or ./lswhere64 (macOS and Linux) from an end user's desktop computer to check which computer is running the concurrent license manager.

1. Using a command prompt, change the current directory to one of the following:
   • Windows. <installation directory>
   • macOS. <installation directory>/Resources/Activation/
2. Type lswhere (Windows) or ./lswhere64 (macOS).

Service and support

To contact IBM Corp. Technical Support, visit http://www.ibm.com/support and submit a case. You will need to register with IBM Corp. Technical Support if you haven't done so previously.

IBM Corp. provides public training seminars for IBM Corp. products on a regular basis. You can also arrange to have training presented onsite. For information on training seminars, visit http://www.ibm.com/training/spss.