ROSS

PLATFORM
DML Services Installation
Guide for Windows

Version No: 9.3

October 2017
4325 Alexander Drive, Suite 100 • Alpharetta, GA 30022-3740 • www.aptean.com • [email protected]

Copyright © 2017 Aptean. All Rights Reserved. These materials are provided by Aptean for
informational purposes only, without representation or warranty of any kind, and Aptean shall not
be liable for errors or omissions with respect to the materials. The only warranties for Aptean
products and services are those set forth in the express warranty statements accompanying such
products and services, if any, and nothing herein shall be construed as constituting an additional
warranty. No part of this publication may be reproduced or transmitted in any form or for any
purpose without the express written permission of Aptean. The information contained herein may
be changed without prior notice. Some products marketed by Aptean contain proprietary
software components of other software vendors. Aptean and other Aptean products and
services referenced herein as well as their respective logos are registered trademarks or
trademarks of Aptean or its affiliated companies.
Contents
Chapter 1: Overview 1-1
Purpose 1-2
Intended Audience 1-2
Operating System and Database Engine Requirements 1-2
Related IAF Documents 1-2
Chapter 2: Preparing to Install IAF 9.3 DML Services 2-1
Disk Storage Requirements 2-2
Architecture Supported 2-2
System Requirements 2-2
Upgrade Procedure 2-2
Chapter 3: Installing IAF 9.3 DML Services 3-1
Installing IAF 9.3 DML Services 3-2
IAF 9.3 DML Services Upgrade Installs 3-4
Releases and Service Packs 3-4
Installing a Service Pack 3-5
Uninstalling IAF 9.3 DML Services 3-5
Chapter 4: Post-Installation Procedures 4-1
Installing IAF DML Services on Windows 4-2
Installing the Broker Service 4-2
Example 4-2
Removing the Broker Service 4-2
Example 4-2
Installing the Batch Service 4-3
Example 4-3
Removing the Batch Service 4-3
Example 4-3
Installing the Monitor 4-3
GEM_MONITOR Parameters 4-3
Example 4-4
Monitor Database and Log File Name 4-4
Removing the Monitor 4-4

Ross Platform - 9.3

DML Services Installation Guide for Windows Page i
 Example 4-5
Starting the IAF Services 4-5
Starting an IAF Application Server 4-5
Example 4-5
Chapter 5: Licensing IAF 9.3 5-1
Overview 5-2
Licensing Vocabulary and Facts 5-2
Types of Licenses 5-3
Setting Up SLM Licensing 5-3
SLM Utilities on IAF Servers 5-4
Obtaining SLM Host IDs 5-4
Obtaining the IAF Server Host IDs (the Licensed Servers) 5-4
Obtaining the License Server Host IDs 5-5
Configuring IAF to use the Correct License Server or License 5-5
Configuring IAF to use a Grace License 5-6
Configuring IAF to use a License Server 5-7
Registering the IAF Server License 5-8
Removing a License 5-8
NIC Teaming 5-9
License Enforcement and Protection 5-9
Sentinel License Manager for Windows and UNIX 5-9
Sentinel Documentation 5-10
Clients and Licenses 5-10
License Counting Notes 5-11

Grouping For License Counting Purposes, or What Is a "User" 5-12

IAF Licensing Specific SCVs 5-13
GEM_LICENSE_COUNT_NOTIFY 5-13
GEM_LICENSE_DEMO_NOTIFY 5-13
GEM_LICENSE_LOG 5-14
GEM_LICENSE_MODE 5-15
GEM_LICENSE_MONITOR_LOG 5-15
GEM_LICENSE_NOTIFY 5-16
GEM_LICENSE_QUEUE 5-16

Ross Platform - 9.3

DML Services Installation Guide for Windows Page ii
 GEMBASE Licensing Specific Messages 5-17
Appendix A: License Counting Scenarios A-1
Scenario 1 A-2
Scenario 2 A-3
Scenario 3 A-4
Scenario 4 A-5

Ross Platform - 9.3

DML Services Installation Guide for Windows Page iii
 1
Chapter 1: Overview

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 1-1
 Chapter 1: Overview

Purpose
This guide describes the steps to install Aptean DML Services for IAF 9.3 on computers running the
Windows operating system.

Intended Audience
Read this guide if you are responsible for:

l Planning the installation of IAF DML Services

l Installing IAF DML Services

Operating System and Database Engine

Requirements
For information about Operating System and Database Engine requirements for IAF 9.3, see the
Ross Enterprise Software Compatibility Guide, located on the Aptean support Web site at
http://www.aptean.com/support/aptean-customer-support. Search for Ross Enterprise Software
Compatibility Guide in the documentation directories. The guide is updated regularly to include all
hardware and software prerequisites.

Related IAF Documents

The following documents contain information about IAF and are applicable to all operating systems
and database engines:

l IAF User Guide

l IAF System Reference Manual
l IAF Data Manipulation Language Manual

For more information about IAF documentation, see the IAF Documentation Overview.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 1-2
 2
Chapter 2: Preparing to Install IAF 9.3
DML Services

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 2-1
 Chapter 2: Preparing to Install IAF 9.3 DML Services

Disk Storage Requirements

The minimum required free disk space to install and run IAF 9.3 DML Services is 500 MB.

Architecture Supported
IAF 9.3 DML Services has been created to include registration for x64 platforms for Windows.

System Requirements
For information about system requirements for installing IAF 9.3 DML Services, see the Ross
Enterprise Software Compatibility Guide. The guide is updated regularly to include all hardware and
software prerequisites.

Upgrade Procedure
For customers using Oracle:
If you are upgrading to IAF 9.3 from IAF 6.1 or an earlier version, a special upgrade procedure is
necessary due to changes in documentary fields. For details about the upgrade procedure, see the
Guide to using IAF with Oracle.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 2-2
 3
Chapter 3: Installing IAF 9.3 DML
Services

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 3-1
 Chapter 3: Installing IAF 9.3 DML Services

Installing IAF 9.3 DML Services

This section describes the IAF Enterprise Server installation procedure on computers using x64
Windows operating system.
The IAF 9.3 installation kit comes as a Master feature that has the following features:

l IAF Enterprise Server - Default Feature

l IAF Debugger
l IAF Thin Client
l IAF Metadata Merge Tool

This kit can be installed using the complete or custom setup. The complete setup installs the default
features, while the custom setup allows you to select the features to be installed.

1. Execute the Setup_DML_x64_vXXX.msi installer downloaded from the Aptean Support

Web site.

2. In the IAF DML - 9.3 Setup dialog box, click Next.

3. Accept the license agreement and click Next.
4. From the Choose Setup Type dialog box, click Complete or Custom. The Choose Setup Type
dialog box is illustrated in the following figure:

Figure 3-1: Choose Setup Type dialog box

l Complete

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 3-2
 Chapter 3: Installing IAF 9.3 DML Services

Installs all application features for IAF 9.3. The Destination Folder dialog box displays the default
installation folder path, as illustrated in the figure.

Figure 3-2: Destination Folder dialog box

To change the default path, click Browse.

l Custom

Enables you to select specific application features and the location where the features need to be
installed. The following figure illustrates the Custom Setup dialog box:

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 3-3
 Chapter 3: Installing IAF 9.3 DML Services

Figure 3-3: Custom Setup dialog box

To install a particular feature, click to the left of the feature you want to install, and select
one of the following:

l Will be installed on local hard drive - to install the feature.

l Entire feature will be installed on local hard drive - to install the feature with all subfeatures.
l Feature will be installed when required - to install the feature when required
l Entire feature will be unavailable - if you do not want to install a specific feature.

Note: Installing the IAF Enterprise Server feature installs all the listed features in the
Custom Setup list, i.e., IAF Debugger, IAF Metadata Merge Tool, and IAF
Thin Client by default, even if these features are not selected.

5. Click Next.
6. On the Ready to Install dialog box, click Install to begin the installation process.
If you do not have a version of IAF Enterprise Server installed on your computer, the installation
concludes normally. The IAF Installer starts the IAF Services.
Note that IAF 9.3 uses the default port numbers 9114, 9115, and 9116 for the Broker, Batch, and
Monitor services respectively.
For details regarding installing IAF Services, see section Installing IAF DML Services on
Windows on page 4-2.
After the installation process is complete, you will be prompted to read the readme.txt file, which
contains information on program and documentation updates. It is recommended that you read
the file.
7. Click Finish when the process is complete.

IAF 9.3 DML components are installed on your computer.

IAF 9.3 DML Services Upgrade Installs

This section describes the upgrade installs for IAF 9.3 DML Services on Windows platforms.

Releases and Service Packs

As with previous versions of IAF 9.3, Service Packs (SP) will be delivered to the customer base as a
way to provide Service Pack release fixes and new features. Service Packs are cumulative and
contain all fixes to the IAF DML Services product at a time.
Another term that has been associated with the Service Pack methodology in IAF 9.3 is the concept
of Update Installers. In IAF 9.3, every Service Pack release is a full installation of the DML Services
application. There is no static release version of the product for IAF 9.3. When a Service Pack is
released, it is considered as the default release for the IAF DML Services at that time.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 3-4
 Chapter 3: Installing IAF 9.3 DML Services

Installing a Service Pack

If DML Services is already installed on a server, a Service Pack may be applied to update the server
with the latest version of the product. The Service Pack is the same as the installer kit that fully
installs DML Services, but each kit in addition contains the logic to upgrade an existing instance. The
following are the properties of a DML Services Service Pack:

l Service Packs are cumulative and contain all fixes at the time of the release.
l You can only update to Service Packs of higher versions. For example, if you are using Service
Pack 3, you must upgrade to a Service Pack higher than 3.
l Any Service Pack level can be upgraded to a higher Service Pack level.
l Although configuration files may change with the installation of a Service Pack, site specific
information is maintained in the existing configuration.

Uninstalling IAF 9.3 DML Services

Perform the following procedure if you want to remove IAF Enterprise Server for Windows from your
computer:

1. Navigate to the Control Panel.

2. Double-click Add or Remove Programs.
3. Highlight IAF DML 9.3.
4. Click Remove.

IAF 9.3 DML is removed from your computer.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 3-5
 4
Chapter 4: Post-Installation Procedures

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 4-1
 Chapter 4: Post-Installation Procedures

Installing IAF DML Services on Windows

The IAF DML installation procedure installs IAF Services automatically on the ports mentioned in
Installing IAF 9.3 DML Services on page 3-2. However, if multiple instances of the Broker, Batch, or
Monitor are required, the system manager must create additional services. This chapter discusses
the procedure for installing IAF Services manually.
Note that all IAF Services, whether they were added by the installation procedure or by a system
administrator, are started up by default when the Windows system is booted.
To install the IAF Services, you must either run the following commands from the GEM_RUN directory,
or specify the PATH environment variable to include this directory.

Installing the Broker Service

To install the Broker Service, type the following command at the MS-DOS prompt:
gem_broker –install [–l log_level] [–f log_file] [Broker_IPCName]

Where –l log_level indicates the level of the log recording (normal, terse, or verbose), -f log_
file indicates the name of the log file, and Broker_IPCName indicates the IPCName.

Example
gem_broker –install –l verbose –f c:\log\broker tcp,,9317

(The port number is an example, and not the standard port)

Note: The default installation port for the Broker Service in IAF 9.3 is 9314.

Removing the Broker Service

To remove the Broker Service, type the following command at the MS-DOS prompt:
gem_broker –remove Broker_IPCName

Example
gem_broker –remove tcp,,9317 (The port number of the broker service you wish to remove)
The Broker Service is removed, regardless of its state.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 4-2
 Chapter 4: Post-Installation Procedures

Installing the Batch Service

To install the Batch Service, type the following command at the MS-DOS prompt:
gem_batch –install [–l log_level] [–f log_file] [BatchID]

Where –l log_level indicates the level of the log recording (normal, terse or verbose), -f log_
file indicates the name of the log file, and BatchID indicates the batch identification.

Example
gem_batch –install –l verbose –f batch tcp,,9318 (or port number you
wish to assign)

Note: The default installation port for the Batch Service in IAF 9.3 is 9315.

Removing the Batch Service

To remove the Batch Service, type the following command at the MS-DOS prompt:
gem_batch –remove BatchID

Example
gem_batch –remove tcp,,9318 (or port number of the batch service you need to remove)

Installing the Monitor

To install the Monitor Service, type the following command at the MS-DOS prompt:
gem_monitor –install [–p parameter] [-p parameter] [...] [MonitorID]

Where -p parameter indicates one or more of the following parameters and MonitorID indicates
the monitor identification.

GEM_MONITOR Parameters
-b
This parameter specifies the IAF batch-id to use. If this parameter is not specified, the default batch-
id is selected from the IAF SCV GEM_DEFAULT_BATCH or the TCP/IP service bat930. The TCP/IP
service name is IAF version dependent, e.g. bat 930 for IAF version 9.3, bat900 for IAF version 9.0,
bat810 for IAF version 8.1, bat800 for IAF version 8.0, bat730 for IAF version 7.3, etc.
-f
This parameter specifies the log file name. If this parameter is not specified, no log file will be created.
-l
This parameter indicates the level of log recording (normal, terse, or verbose).

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 4-3
 Chapter 4: Post-Installation Procedures

-r
This parameter specifies the Oracle home directory to be used. If this parameter is not specified, the
home directory is selected from the registry.
-s
This parameter specifies the Oracle SID to use. If this parameter is absent, the SID is selected from
the registry.
-w
This parameter specifies the number of seconds the IAF monitor has to wait before processing the
monitor database. If this parameter is not specified, the monitor waits for 30 seconds. This parameter
is added to the command line so that other database services have a chance to start before GEM_
MONITOR accesses them.

Example
gem_monitor -install -s ORCL -r c:\ORANT -w 45 -b 9318 9319 (or the port numbers you
wish to monitor, respectively)

Monitor Database and Log File Name

Previously, the SCVs GEM_MONITOR_DATABASE and GEM_MONITOR_LOG defined the IAF
monitor database and log file names, respectively. For Windows x64 platforms, since monitors run as
x64 services, those filenames have been modified slightly.
The SCVs values in the registry are used as the basis for the real filenames. For example, if GEM_
MONITOR_DATABASE is set to
c:\Ross\soft\IAF\Dml\930\gem_monitor.dat
then the real monitor database file is
c:\Ross\soft\IAF\Dml\930\gem_monitor_9314.dat
assuming that the TCP/IP port number for this monitor is 9314. Similarly, the real monitor log file will
also have the TCP/IP port number appended to the value in the registry. For example:
c:\Ross\soft\IAF\Dml\930\log\gem_monitor_9314.log

Removing the Monitor

To remove the Monitor Service, type the following command at the MS-DOS prompt:
gem_monitor –remove MonitorID

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 4-4
 Chapter 4: Post-Installation Procedures

Example
gem_monitor –remove tcp,,9316 (or the monitor you need to remove)

Starting the IAF Services

You can start IAF Services using any of the following methods:

l Reboot your system

l Start the services from the Services Applet in the Windows Control Panel. Select the service you
wish to start, and click the Start button.

Starting an IAF Application Server

This section describes starting an IAF application server.
The kit provides two methods to start application servers:

l Automatic - which allows the server to auto start using the autostart.txt file in the
$\Ross\Soft\IAF\Dml\930\startup folder, which is populated with the appropriate
<server>.res files.
l Manually

Example
Perform the following steps to manually start application servers:

1. Open a new MSDOS console session.

2. At the DOS prompt, change directory into the run subdirectory of the IAF install directory, which
you specified in the installation process.
3. At the DOS prompt, type the following:

gem_server_startup [drive:\path\] <server>.res [broker_IPCname]

[drive:\path\]<server>.res is a complete file specification of the server resource file. Note

that the folder path to <server>.res is optional. If the file is in the same directory as the gem_
server_startup program, you do not have to specify a folder path. You can directly refer to the
server resource file. For example,
gem_server_startup <server>.res tcp,,broker_port

where broker_port is the broker_id you specified when you started the broker service as specified
above.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 4-5
 5
Chapter 5: Licensing IAF 9.3

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-1
 Chapter 5: Licensing IAF 9.3

Overview
The licensing subsystem in IAF 9.3 for all Windows platforms is provided by SafeNet’s Sentinel RMS
License Management System. All IAF 9.3 installations require Sentinel License Server(s) to manage
license counting. While the IAF servers may be on any platform, the Sentinel License Management
(SLM) servers are Windows based computers requiring Win32 and/or X64 architecture.
For SLM licensing in IAF 9.3, the Ethernet physical address (MAC address) is used to license a
server. For redundancy within a server, multiple physical addresses can be provided for a server. For
more information about how to license your server, see the section Obtaining SLM Host IDs on
page 5-4. This section provides information about licensing IAF on Windows platforms.

Licensing Vocabulary and Facts

When dealing with licensing, you need to know and understand the specific vocabulary used in this
context. Understand the following concepts before continuing:

l License Servers – These are the computers that the SLM license server runs on. SLM servers
can exist as stand alone servers or in a license pooled configuration that provides failover and
redundancy. With IAF 9.3, all SLM license servers must run on Win32 or X64 Windows
platforms.

Note: The term server may be slightly inappropriate in this context, since the SLM
license service is a relatively lightweight application.

l Licensed Servers – These are the actual computers that run IAF and request licenses from the
SLM License Servers.
l License Pooling – License pooling is a feature provided by Sentinel that allows licenses to be
pooled among an odd number of License Servers, so that failover and redundancy can be
provided. License Servers must be in odd numbers (such as 3, 5, 7, etc) in order to have a valid
license pool. For more information, see the Sentinel Administrators Guide.
Each license pool is issued one license, which is shared among all the License Servers in the
pool.
l On a Windows platform, the same computer can be a License Server and the Licensed Server.
Any IAF 9.3 server can be configured as the SLM license server.
l A single license pool can contain both X64 and Win32 License Servers.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-2
 Chapter 5: Licensing IAF 9.3

Types of Licenses
SLM licensing includes two types of licenses - Server Licenses and Grace Licenses.

l Server Licenses – Server licenses are actual production licenses that are loaded into the SLM
license service. Server licenses define:

o Servers that are valid license servers (the servers running SLM)
o The computers that are to be licensed (the IAF servers)
o The licenses and counts associated with those licenses
o Expiry dates and other properties of a license as applicable to a contract.

l Grace Licenses – A grace license, also known as a local license, is a temporary license that may
be provided by the Aptean Licensing or Support departments in certain cases. Grace licenses do
not require a SLM license server. Attempting to load grace licenses to a license server results in
an error. A grace license must reside on the IAF server that provides licensing.

Setting Up SLM Licensing

Note: Before setting up SLM Licensing, read the Sentinel documentation available with the IAF
distribution kit or at the Aptean Support Web site. The Sentinel License Manager System
Administrator’s Help is available in HTML format in the \documentation directory with
the IAF 9.3 distribution kit, and on the Aptean Support documentation download site.

Perform the following steps to install SLM:

1. Obtain the SLM Host Ids for the license servers and the servers you intend to license. For more
information, see the section Obtaining SLM Host IDs on the next page.
2. If you have not obtained a SLM license for your IAF 9.3 system, contact Ross licensing 1-855-
411-2783 to obtain the license.
3. If you have not reviewed Sentinel documentation, review the Installing the Sentinel RMS
Developer Kit Server document and the Sentinel RMS Administration document.
4. Install the Sentinel RMS license server by following the instructions provided in the Installing the
Sentinel RMS Developer Kit Server document. The Sentinel kit is located in the $Gem_
Root\Download\Sentinel folder on your IAF server. Install the Sentinel RMS license server
using the Setup.exe file provided in the folder.
5. Install your license file by following the instructions included in the Readme file.

Your system should now be licensed and ready for production.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-3
 Chapter 5: Licensing IAF 9.3

SLM Utilities on IAF Servers

License utilities provided for SLM are included in the $GEM_ROOT\license directory in your IAF 9.3
installation. This section contains a brief list of available tools and their features. For more information
on each utility, see the Sentinel licensing documentation. Usage of the tools is consistent across
Windows and Unix platforms.

l echoid - Get a Computer's Locking Code

l echouid - Get a License Upgrade Lock Code
l ipxecho - Display the IPX Network Address
l loadls - Install the License Server as a Windows service
l lslic - Install/Delete a License Code
l lsmon - Monitor License Server Transactions
l lsrvdown - Shut Down the License Server
l lsusage - Display the Sentinel LM Usage Log File
l lswhere - Display a List of License Servers
l WlmAdmin - Administer License Management Activities

Obtaining SLM Host IDs

To obtain your Server license from Aptean licensing, you require the host IDs for the SLM License
servers. Additionally, you need the IAF 9.3 servers to be licensed. These host IDs will be the
Ethernet physical address for the network cards in the servers.

Obtaining the IAF Server Host IDs (the Licensed Servers)

You can use any of the following methods for obtaining your Host IDs that need to be provided to
Aptean Licensing.

l Use the Show Hostid command at a DML Prompt>.

l Use the print %targetid command at a DML Prompt>.
l Use the echoid tool provided by Sentinel when installing SLM as follows:

1. Echoid.exe is located in the $GEM_ROOT\license folder in IAF 9.3 installations.

2. Edit echoid.dat file in that directory. Make sure the value is changed to 0x010, not the
default 0x3FF.
3. At the command prompt execute: echoid –d

The Ethernet Address(es) listed in the results of this command should be provided to licensing.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-4
 Chapter 5: Licensing IAF 9.3

l Use the platform specific to find the MAC address

o Use ipconfig /all from a command prompt on Windows

o Use ifconfig –a as root on Solaris

o Use lanscan as root on HP-UX

o Use netstat –ia as root on AIX

The Physical Addresses of the cards listed by this command should be provided to licenses.

Note: It is not necessary to send ALL Ethernet physical addresses to Aptean Licensing in order
to license a Server. Many of today’s servers can have 4 or more network cards and it is
unnecessary to have them all included. In many cases, two addresses in a machine
allows for sufficient redundancy.

Obtaining the License Server Host IDs

You need to provide Aptean Licensing with the Host IDs for your SLM License Server. If IAF 9.3 is to
be located on the same server as a License Service, you can directly provide the Host ID information
as discussed in the section Obtaining the IAF Server Host IDs (the Licensed Servers) on the previous
page. If your License Server is not located on an IAF server, you can obtain the Host ID using one of
the following methods:

l Use the echoid tool provided by Sentinel when installing SLM.

1. Edit the echoid.dat file in the folder. Make sure the value is changed to 0x010, from the
default 0x3FF.
2. At the command prompt, execute echoid –d.

The Ethernet Address(es) listed in the results of this command should be provided to Aptean
licensing.

l Use ipconfig /all from a command prompt.

The Physical Addresses of the cards listed by this command should be provided to licenses.

Configuring IAF to use the Correct License

Server or License
For licensing in IAF 9.3 to work correctly, the kernel must be configured to point to the correct license
server or grace license.
In order to have DML-Runtime identify the License Server(s), you need to specify where the license
servers are. Environmental variables are used to control the behavior of the IAF kernel. The relevant
GEMBASE SCVs are:

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-5
 Chapter 5: Licensing IAF 9.3

l GEM_LSHOST
This SCV is used for making available to the kernel, the list of License Servers that are available
in a license pool. This SCV can be set to a space separated list of License Server host names or
IP addresses.
l GEM_LSFORCEHOST
This SCV can be set to force the use of a single license server host name or IP address. This
SCV overrides GEM_LSHOST SCV.
l GEM_LSFORCEPORT
This SCV can be used in combination with the GEM_LSFORCEHOST SCV. When specified, it
sets the port number to connect on the license server computer. This would only be necessary if
the default port was modified on the license server that is being contacted.

Note: It is required that either GEM_LSFORCEHOST or GEM_LSHOST be set for IAF to

work correctly. If neither SCV is set, the kernel does not work as expected
and exits.

If you need to use the software tools available with Sentinel (lslic.exe, lsmon.exe, etc), you
require two environmental variables. It is necessary to set one or more of these environmental
variables in the Windows Command Prompt or Unix Shell you are using.

l LSHOST – Overridden by GEM_LSHOST when using IAF

l LSFORCEHOST – Overridden by GEM_LSFORCEHOST when using IAF

See the Sentinel RMS documentation for more information on the LSHOST and LSFORCEHOST
environment variables.

Configuring IAF to use a Grace License

If you are configuring IAF to use a grace license, the license file provided by Aptean
Licensing/Support must be located in the $GEM_ROOT\license folder. The file must always have
the name gembase.lic. A license server is not required in this configuration. However, if any
license servers are installed and running, they do not cause any problems as long as they are not
referenced.
To specify a Grace license for IAF 9.3, you must set:
GEM_LSFORCEHOST NO-NET

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-6
 Chapter 5: Licensing IAF 9.3

Entries in a grace license file should be as follows (the text is wrapped):

10 DML-RUNTIME 9.3 LONG NORMAL STANDALONE EXCL INFINITE_KEYS INFINITE_
KEYS 5 MAY 2008 10 SEP 2008 NiL SLM_CODE DEMO NiL NiL Ni NiL NiL 15_MINS
WiXq1uvTFcCOpCsFDIx9fzTsvEFJ3GfXlBYsboZ2O33j4ZS5J8sqNDooMrbQzAhBfj
#

10 IAF 9.3 LONG NORMAL STANDALONE EXCL INFINITE_KEYS INFINITE_KEYS 5 MAY

2008 10 SEP 2008 NiL SLM_CODE DEMO NiL NiL Ni NiL NiL 15_MINS
o2bpQdTDcJmMuaeLI:zCVTcSa6kT7iEr4v1dQRLkCZfvDJMg2nX3DGmCeNt9pJ0Q3K
#

Configuring IAF to use a License Server

SLM production licenses are issued as network licenses. This means that with production licenses,
the license file provided by Aptean Software Licensing/Support is only used to register the license
with a license server(s) and is not subsequently used. After obtaining a production license, an
administrator must use the LSLIC.exe utility to register the license with the license server as
described in the next section. After the license has been registered, one of the following scenarios
must be used.

l GEM_LSFORCEHOST Licence_Server_machine
l GEM_LSHOST License_Server1 License_Server2 License_Server3
(This option is applicable if you are using a license pool)

Do not use GEM_LSHOST if only one computer is listed. Even though this may work, it is possible that
there could be several seconds overhead while trying to locate another server.
Entries in a Server license file should be as follows (the text is wrapped):

10 DML-RUNTIME 9.3 LONG NORMAL NETWORK EXCL 20_KEYS INFINITE_KEYS 1 JAN

2005 31 DEC 2007 APP_SHR SLM_CODE 0_NO_ENCRYPTION NON_COMMUTER NO_
GRACE NO_OVERDRAFT ND_LCK NON_REDUNDANT 00031F12010,0003EE74010
0000F47A010,0000EE7D010,0003B2D3010 NiL NO_HLD NiL 15_MINS
WgbJchm9DfW:X7v,u,hA3W0pU4D3bUmM:wNaYkrSV238WBgmJDMCyaTa1jvEmyR4LKrMQq9
XMX:LoW,GYLKYOdLd

10 DML-DEVELOPMENT 9.3 LONG NORMAL NETWORK EXCL 1_KEYS INFINITE_KEYS 1

JAN 2005 31 DEC 2007 APP_SHR SLM_CODE 0_NO_ENCRYPTION NON_COMMUTER NO_
GRACE NO_OVERDRAFT ND_LCK NON_REDUNDANT 00031F12010,0003EE74010
0000F47A010,0000EE7D010,0003B2D3010 NiL NO_HLD NiL 15_MINS
zKZ9Tab,hCYjyEDh5HtAL6,amNCE7TTHRdzHxPj7bRLWtfpWTQe7dltWQGC6JFXu36EBXSwZo
KzAoyBKh9kk1Ef5

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-7
 Chapter 5: Licensing IAF 9.3

Registering the IAF Server License

A customer, on receiving the Sentinel LM license file, registers the license with an SLM license
server. The easiest way to register a license with the Sentinel LM license server is to use the
lslic.exe utility available in the $GEM_ROOT\license folder.
For other methods to register a license, see the SLM Administration documentation. If you are using a
license pool, see the relevant section in the SLM Administration guide for specific instructions. Use
the following command to register licenses contained in a license file:
lslic –F filename.ext

In this case, filename.ext is the name of the file that contains the licenses to be registered. Note
that -F contains an uppercase F, not a lowercase f. -F registers a license permanently. “-f” registers
a license for only until the service is restarted.
For example:
lslic –F gembase.lic

lslic –F c:\ross\soft\gem\930\license\your_license.lic

Removing a License
To remove a specific license:
lslic –d licensename version

Note that licensename is case sensitive and that all IAF license names are in uppercase.
Examples:
lslic –d GEMBASE-RUNTIME 9.3

lslic –d DML-DEVELOPMENT 9.3

lslic –d DML-REPORTS 9.3

lslic –d IAF 9.3

lslic –d IAF-MOBILE 9.3

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-8
 Chapter 5: Licensing IAF 9.3

NIC Teaming
Since IAF licensing is tied to the MAC address on a server, licensing servers may appear to be
complicated. NIC teaming in a server can be accomplished in many ways depending on the hardware
platform (including differences in hardware between vendors), operating system and network
configuration. For a more detailed discussion on NIC teaming, see http://en.wikipedia.org/wiki/Link_
aggregation.
The MAC addresses that are available to the licensing software on the box depends on the level
where the NIC teaming occurs. The following procedure describes how to license your teamed cards
correctly:

1. Configure your server with the desired network configuration.

2. Use the Sentinel echoid.exe tool described earlier in this guide to obtain the MAC
Addresses/Host IDs provided to the licensing software by the operating system.
3. Provide the MAC Addresses/Host IDs to the Aptean licensing department, to be included in the
license.

Changing the teaming configuration for the NICs on a server can, in some cases, lead to different
MAC addresses being provided to the licensing software (and any other application running on the
computer). Since this can occur, it is possible to invalidate the IAF license of a server when you
reconfigure teaming. If this occurs, request a new license with the updated information.

License Enforcement and Protection

Sentinel License Manager for Windows and UNIX
IAF 9.3 uses the Sentinel RMS License Manager on the Windows,
HP-UX: HPUX Itanium, AIX and SUN platforms. With a few notable exceptions, this change has no
affect on GEMBASE running on other platforms or other licensing software. A notable exception is as
follows:
In order to invoke a local database while running GCWpro, you must now have a DML-RUNTIME
license. Also, while a local database is invoked, GCWpro behaves the same as character-cell
applications have traditionally behaved in regards to licenses. That is, a DML-RUNTIME license is
required to obtain access to the database, a DML-REPORTS license is required in order to perform a
reporting function and a DML-DEVELOPMENT license is required to perform a development function.
No licenses are required so long as no local databases have been invoked.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-9
 Chapter 5: Licensing IAF 9.3

Sentinel Documentation
The Sentinel licensing manuals are placed on your system when installing IAF 9.3 and the Sentinel
RMS product. All system administrators should read this documentation. Read the documentation or
at least skim over it at your first available opportunity.

Clients and Licenses

The following license policy is implemented in IAF:

l Concurrent user license counting

DML requires concurrent user counting and consumes the following three licenses as needed:

1. DML-RUNTIME

Note: For Smart Client, multiple instances running on a computer requires only one
DML-RUNTIME license, even if multiple tabs are open for each instance.

2. DML-DEVELOPMENT
3. DML-REPORTS

l Non-concurrent license counting

Two separate non-concurrent licenses are used for non-concurrent license counting:

o IAF
All IAF products require the presence of an IAF license. This license does not require
concurrent user counting. Only the presence of this license is checked; it is not counted.
o IAF-MOBILE
This license is required to use the IAF Mobile product in Data Collection and shop floor
management. Only the presence of the license is checked; it is not counted.

Separate license features can be present in your license file for each IAF feature enabled. Each IAF
feature can have its own separate expiry date, its own separate maximum user limit, or be marked as
being a temporary DEMO/TEST license.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-10
 Chapter 5: Licensing IAF 9.3

The available license features are documented in the table below:

Table 5-1 License Counting Diagram

DML-
Client Vs License DML-RUNTIME DML-REPORTS IAF-MOBILE IAF
DEVELOPMENT
Char Cell Count Note 1 Count Note 2 Count Note 2
Thin Client Count Note 1 Count Note 2 Count Note 2
GCW Pro Count Note 3 Count Note 2 Count Note 2
MM Tool
iBrowser Count Note 1
Connect Required
Broker Manager
Batch Manager
Security Count Note 1
Manager
Developer Studio Count Note 1
IAF Mobile Required
Smart Client Count Note 1 Required

License Counting Notes

1. If a DML-RUNTIME license cannot be obtained, databases cannot be invoked.

2. DML-REPORTS and DML-DEVELOPMENT are optional licenses that are counted only if the
client executes DML reporting and development features respectively. These licenses are
requested and counted only for so long as the client is actively reporting or developing, then they
are released.
3. GCWpro does not check for or count a license unless it is used to access a local database. If a
GCWpro client attempts to invoke a local database, a request is made for a DML-RUNTIME
license. If the DML-RUNTIME license cannot be reserved, the local database cannot be invoked.
When a local database is opened (invoked), GCWpro requests and counts a DML-RUNTIME
license.

Reporting functions and development functions executed while a local database is invoked also
request and count DML-REPORTS and DML-DEVELOPMENT licenses respectively. However, all
licenses (including the DML-RUNTIME license) are released after the last local database is finished.
The following examples demonstrate how to compute the count for each client type.
Example 1: Each GEMBASE character-cell user, GEMBASE thin client user and GEMBASE
GCWpro with local database user consumes a DML-RUNTIME license feature. If a DML-RUNTIME
feature cannot be obtained, the database cannot be invoked.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-11
 Chapter 5: Licensing IAF 9.3

If a Gembase reporting or development activity is initiated, a DML-REPORTS or

DMLDEVELOPMENT license feature is optionally consumed, but only for the duration of the
reporting or development activity. In the case of GEMBASE GCWpro with local database access, it
is the Windows PC on which GCWpro is run that must be licensed. In the case of GEMBASE Thin
Client, it is the system on which the thin server runs that must be licensed.
Example 2: Each iBrowser client checks for an IAF license feature. Since iBrowser also uses a type
of thin server, a UI server, each iBrowser user will consume one DML-RUNTIME feature.

Grouping For License Counting Purposes, or

What Is a "User"
Sentinel can group users for license counting purposes by any combination of three criteria: HOST,
USER and DISPLAY.
IAF sets each Thin Client, GCWpro, user's HOST to the hostname of the client machine, USER to
the user’s username on the server system, and DISPLAY is set to a unique eight hexadecimal
character product installation "token" that permits the same user on the same client system to be
consistently counted as a single user even in the presence of VPN, NAT, Masquerading firewalls.
The thin server counts DML-RUNTIME, DML-REPORTS, and DML-DEVELOPMENT licenses. The
BROKER counts the client at application open time and releases the client at application close or
disconnect time.
IAF users are grouped by their hostname and TCP/IP port number. The BROKER checks the IAF
license on the client's behalf. The BROKER checks the IAF client at application open time.
GEMBASE sets each Fat Client's HOST to the IP address of the client system, USER to the
username from the application connect string, and DISPLAY to the client’s IPC port number. So by
default, each Fat Client connection is counted separately. The BROKER counts the
DML-RUNTIME license on the client's behalf. The BROKER counts the client at application open
time (or database invoke time) and releases the client at application close or disconnect time (or
database finish time).
Character cell licensing has been updated to count licenses similar to GTC and GCWPro. For every
character cell, connection for a "user/desktop" combination counts as a single license consumed.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-12
 Chapter 5: Licensing IAF 9.3

IAF Licensing Specific SCVs

GEM_LICENSE_COUNT_NOTIFY
The setting of this SCV determines whether or not GEMBASE notifies END USERS of impending
license exhaustion. This SCV can be set to T[RUE], F[ALSE], Y[ES], N[O], or to a number. T[RUE]
and Y[ES] cause end user impending license exhaustion warning messages to be enabled and for
those messages to begin to be displayed when 90% of the maximum user count for a license has
been utilized. FALSE and NO cause end user impending license exhaustion warning messages to be
disabled. Setting this SCV to a number causes end user impending license usage exhaustion
warnings to be enabled starting when number percent of the maximum user count for a license has
been utilized.
Note that impending license exhaustion warning messages are always sent to the license log (if
enabled) regardless of the setting of this SCV. For logging purposes, this SCV determines when, not
if, such messages will be logged. If this SCV is not set, end users will receive impending license
exhaustion warning messages when 90% of the maximum user count for a license has been utilized.
When running in thin client/server mode, this SCV is negotiated with the thin client. /LOCK may be
appended to the SCV value to prevent the thin client from being able to override the thin server's SCV
value.
Examples:
GEM_LICENSE_COUNT_NOTIFY=YES
GEM_LICENSE_COUNT_NOTIFY=NO
GEM_LICENSE_COUNT_NOTIFY=80

GEM_LICENSE_DEMO_NOTIFY
The setting of this SCV determines whether or not GEMBASE notifies END USERS that they are
running a DEMO/TEST license. DEMO/TEST licenses are only available on platforms on which
GEMBASE uses the FLEXlm licensing system. This SCV can be set to T[RUE], F[ALSE], Y[ES], N
[O], 1, or 0. T[RUE] and Y[ES] cause end user demo license notification messages to be enabled.
FALSE and NO cause end user demo license notification messages to be disabled. If this SCV is not
set, the default is TRUE.
Note that regardless of the setting of this SCV, GEMBASE displays the word "DEMO" with bold and
blink attributes in the upper right-hand portion of the banner next to the time whenever the time is
displayed in the upper right-hand portion of the banner. The word "DEMO" is also included in both the
stock "DML>" prompts (i.e., "DEMO-DML>" and the "GEMBASE Finished" message that
GEMBASE displays as it exits (i.e., "GEMBASE DEMO Finished"). When running in thin
client/server mode, this SCV is negotiated with the thin client. /LOCK may be appended to the SCV
value to prevent the thin client from being able to override the thin server's SCV value.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-13
 Chapter 5: Licensing IAF 9.3

Examples:
GEM_LICENSE_DEMO_NOTIFY=NO
GEM_LICENSE_DEMO_NOTIFY=YES

GEM_LICENSE_LOG
This SCV is applicable to all licensed platforms, regardless of which underlying licensing software is
in use. The setting of this SCV determines whether or not licensing related actions and errors are
logged. This SCV can contain a comma-separated list of keywords. Valid keywords are:
T[RUE], F[ALSE], Y[ES], N[O], 1, 0, M[ONITOR], F[ILE] {:|=}file-specification, L[EVEL]{:|=}logging-
level.
The FILE=file-specification keyword causes logging messages to be sent to the file specified in 'file-
specification.' This file must be writeable by the user in order for any logging to this file to take place.
If the FILE keyword is specified by itself without any other keywords, the TRUE keyword is implied.
Place single quotes (FILE='filespecification') or double quotes (FILE="file-specification") around the
file-specification if it contains either commas or spaces. The file specification must not contain colon
(":"), equal sign ("="), single quote ("'") or double quote ('"') characters.
The LEVEL=logging-level keyword determines how detailed the license log is to be.
One of the following logging levels can be specified: FATAL, SEVERE, ERROR, TERSE,
WARNING, INFORMATIONAL,VERBOSE, SUCCESS, or INTENSE.
FATAL causes the least amount of logging to take place. INTENSE causes the most logging to take
place. If the logging level is not specified, the default logging level is WARNING.. If the LEVEL
keyword is specified by itself without any other keywords, the TRUE keyword is implied. Please note
that the INTENSE logging level outputs a large amounts of text to the log. This is not recommended
for normal day-to-day logging.
The MONITOR keyword, if specified, causes logging messages to be sent to the GEMBASE
MONITOR and logged centrally in a single licensing log file. If the MONITOR keyword is specified by
itself without any other keywords, the TRUE keyword is implied. See the description of the GEM_
LICENSE_MONITOR_LOG SCV for details.
The TRUE keyword enables logging for this client. If specified all by itself without any other
keywords, it causes logging to be performed via the monitor with the default logging level of
WARNING. YES or any odd numeric value is synonyms for TRUE.
(This is standard GEMBASE true/false SCV logic.)
The FALSE keyword disables logging for this client. NO or any even numeric value are synonyms for
FALSE. If both the FILE and MONITOR keywords are specified, the license log messages are sent
to both locations.
If this SCV is not set, the logging level is set to WARNING and license log messages are sent to the
monitor.
The keyword list may be enclosed within parenthesis for clarity.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-14
 Chapter 5: Licensing IAF 9.3

Examples:
GEM_LICENSE_LOG=YES

GEM_LICENSE_LOG=NO

GEM_LICENSE_LOG=(FILE:license_log.log, MONITOR, LEVEL=INTENSE)

GEM_LICENSE_MODE
Setting this SCV causes GEMBASE to request the specified license at GEMBASE startup time and
hold onto that license until GEMBASE exits. This SCV can and should be set when the user knows in
advance that s/he will be performing a series of actions which all require a DML-REPORTS license or
DML-DEVELOPMENT license and which must not fail for lack of a license before all the actions have
been completed (and the user has exited GEMBASE.) If both DML-REPORTS and DML-
DEVELOPMENT licenses will be needed, then specify DML-DEVELOPMENT.
GEMBASE features that require a DML-REPORTS license also operate successfully when the user
already holds a DML-DEVELOPMENT license. You may set this SCV to one of the following values:
DML-DEVELOPMENT, DML-REPORTS, or DML-RUNTIME.
Note however, that interactive IAF sessions (such as character-cell and thin client) always request
and hold a DML-RUNTIME license in addition to any other license that they may request and release.
Therefore, one would usually set this SCV to either DML-REPORTS or DML-DEVELOPMENT. Also,
the "DML-" portion of the license name may be omitted if desired. When running in thin client/server
mode, this SCV is negotiated with the thin client. /LOCK may be appended to the SCV value to
prevent the thin client from being able to override the thin server's SCV value.
Examples:
GEM_LICENSE_MODE=DEVELOPMENT

GEM_LICENSE_MONITOR_LOG
This SCV is applicable to all licensed platforms, regardless of which underlying licensing software is
in use. The setting of this SCV determines the location of the GEMBASE MONITOR licensing log
file. If this SCV is not set, the default monitor licensing log file location is GEM_ROOT\log\gem_
license_monitor_service_log.log on the Windows platforms and
GEM_ROOT/log/gem_license_monitor_service_log.log on UNIX platforms where
service is the monitor service name (or port number if it doesn't have a name in the services file).
Note that this SCV is read by the GEMBASE MONITOR and needs to be visible in the monitor's
environment in order for the monitor to see it.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-15
 Chapter 5: Licensing IAF 9.3

GEM_LICENSE_NOTIFY
This SCV is applicable to all licensed platforms, regardless of which underlying licensing software is
in use. The setting of this SCV determines whether or not GEMBASE notifies END USERS of
impending license expiration. This SCV can be set to T[RUE], F[ALSE], Y[ES], N[O], or to a number.
T[RUE] and Y[ES] cause end user license expiration warning messages to be enabled and for those
messages to begin to be displayed to end users 30 days prior to the license's expiration date. FALSE
and NO cause end user license expiration warning messages to be disabled. Setting this SCV to a
number causes end user license expiration warnings to be enabled starting number days prior to
license expiration.
Note that license expiration warning messages are always sent to the license log (if enabled) starting
30 days prior to license expiration regardless of the setting of this SCV.
If this SCV is not set, end user license expiration warnings are enabled and begin to be displayed to
end users 30 days prior to license expiration. When running in thin client/server mode, this SCV is
negotiated with the thin client. /LOCK may be appended to the SCV value to prevent the thin client
from being able to override the thin server's SCV value.
Examples:
GEM_LICENSE_NOTIFY=NO

GEM_LICENSE_NOTIFY=YES

GEM_LICENSE_NOTIFY=10

GEM_LICENSE_QUEUE
This SCV can be set to T[RUE], F[ALSE], Y[ES], N[O], 1 or 0. The setting of this SCV determines
whether or not GEMBASE waits for the requested license to become available. If this SCV is set to a
TRUE value and a requested license is not available at this time it is requested, then GEMBASE
silently waits indefinitely for the license to become available before continuing. The default behavior
is for GEMBASE to return an error if the license is not immediately available. When running in thin
client/server mode, this SCV is negotiated with the thin client. /LOCK may be appended to the SCV
value to prevent the thin client from being able to override the thin server's SCV value.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-16
 Chapter 5: Licensing IAF 9.3

GEMBASE Licensing Specific Messages

The most common licensing messages that you will consistently see on all platforms for which
GEMBASE is licensed are:
“Your license-name license will expire at midnight on dd-mmm-yyyy”
GEM_LICENSE_NOTIFY=YES and your license-name license key will expire soon. Contact Aptean
licensing administration to obtain a new license key before dd-mmm-yyyy. This is a strictly
informational message. To disable this message, set GEM_LICENSE_NOTIFY=NO.
“Your license-name license will expire at midnight TONIGHT”
GEM_LICENSE_NOTIFY=YES and your license-name license key will expire tonight. Immediately
contact Aptean licensing administration to obtain a new license key. This is a strictly informational
message. To disable this message, set GEM_LICENSE_NOTIFY=NO.
“Your license-name license will expire at midnight TOMORROW night”
GEM_LICENSE_NOTIFY=YES and your license-name license key will expire tomorrow night.
Immediately contact Aptean licensing administration to obtain a new license key. This is a strictly
informational message. To disable this message, set GEM_LICENSE_NOTIFY=NO.
Your license-name license has expired.
Your license-name license key has already expired. Contact Ross Systems licensing administration
to obtain a new license key. Depending on which license has expired, this message is likely fatal.
Licensed number of limit license-name users exceeded
All the available license-name licenses are already in use by other users.
“license-name license request failed.”
IAF was unable to obtain a license-name license for some reason. One or more additional messages
with specific error codes always accompany this message. See the other message(s) for details. If
you are using Thin Client or GCWpro, you may need to expand the message window at the bottom of
the screen in order to see the other messages.
“Your license-name license usage (count users of limit) exceeds nn percent”
GEM_LICENSE_COUNT_NOTIFY is set and you have exceeded nn percent license-name usage.
You may be getting close to your limit. This is a strictly informational message
“Queued waiting for license-name license…”
GEM_LICENSE_QUEUE=YES and the license-name was not immediately available. Most likely all
the available license-name licenses are already in use by other users. You are now in the queue
waiting for a license-name license to become available.
“license-name license lost; reconnect attempt nn of nn...”
Your connection to the license server has been temporarily lost. GEMBASE will try nn times to
reconnect to the license server.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page 5-17
 A
Appendix A: License Counting Scenarios

Ross Platform - 9.3

DML Services Installation Guide for Windows Page A-1
 Appendix A: License Counting Scenarios

Scenario 1
Each client computer running GTC consumes 1xDML-RUNTIME license, regardless of the number
of GTC instances or the USERNAMEs used.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page A-2
 Appendix A: License Counting Scenarios

Scenario 2
Each client computer running Smart Client DmlDesktop consumes 1xDML-RUNTIME license,
regardless of the number of DmlDesktops or the USERNAMEs used.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page A-3
 Appendix A: License Counting Scenarios

Scenario 3
Each client computer running iBrowser clients consumes 1xDML-RUNTIME license for each
iBrowser client.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page A-4
 Appendix A: License Counting Scenarios

Scenario 4
In this scenario, Client computer #1 consumes 2x DML-RUNTIME licenses; one for running GTC,
and one for running Smart Client DmlDesktop. Client computer #2 consumes 3xDML-RUNTIME
licenses; one for each iBrowser user.

Ross Platform - 9.3

DML Services Installation Guide for Windows Page A-5