Specifications

Chapter 14. License and serial number servers 155
򐂰 License - A logical function that enables one System z CP for a zPDT system. Multiple
CPs require multiple licenses. The token functions provide licenses.
򐂰 License Monitor - A web browser interface that displays information about Sentinel Keys
and clients using them. It is accessed at port 7002 on a Linux system running a license
server.
򐂰 License Server - A network-accessible service that manages and dispenses zPDT
licenses from a token. It operates as a Linux daemon and is automatically started (after
zPDT is installed) when Linux is booted. A “local” zPDT installation internally accesses the
license server via internal TCP/IP. Remote license servers are accessed via network
TCP/IP.
򐂰 USB Server - A driver provided by SafeNet to access tokens on USB ports. It operates as
a Linux daemon and is installed when zPDT is installed.
򐂰 Server Configuration File - A file (in XML format) used by the Sentinel Key Server to obtain
networking and logging parameters. It is located at:
/opt/safenet_sentinel/common_files/sentinel_keys_server/Sntlconfigsrvr.xml
򐂰 Client Configuration File - A file (in XML format) used by zPDT to obtain parameters to
access both a License Server and (possibly) a UIM server. It is located at:
/usr/z1090/bin/sntlconfig.xml
򐂰 Heartbeat - The periodic accessing by zPDT of the license(s) managed by a license
server. If the heartbeat is missed, the zPDT license is revoked.
򐂰 Time Cheat - The Sentinel Key (token) records the current date and time each time the key
is accessed. If the Linux system clock contains a time earlier that the last recorded time in
the token, the license is unusable.
򐂰 Token Serial Number - The license information in the token contains a unique serial
number assigned by IBM. This serial number may be used as the basis for the System z
CP serial number in some cases.
򐂰 UIM or Unique Identification Manager - This is a server (or local function of zPDT) that
helps maintain unique enterprise-wide System z serial numbers for zPDT systems. The
license server and the UIM server (or local function) are separate but parallel functions.
򐂰 Identification - A serial number and instance number, as stored by the System z STIDP
instruction. (The instance number is similar to an LPAR number on a larger System z.)
򐂰 Serial Number - A value between 1 and 65535 (four hex digits). The serial number is
assigned by the UIM function to the base Linux and used by zPDT to provide the System z
serial number.
򐂰 Instance Number - A number between 1 and 255 assigned to each zPDT instance on a
base Linux machine. Each zPDT instance must operate under a different Linux userid and
the instance number is assigned to the userid. The instance number is used in the same
manner as the LPAR number on a larger System z.
򐂰 Data Base - A file containing UIM information. The files are not directly editable. There are
two types of databases. One exists in every Linux zPDT machine, and the other exists in a
UIM server (if this is used). The local database (on a zPDT client) is located at:
/usr/z1090/uim/uimclient.db
򐂰 UIM Server - A centralized service that maintains unique zPDT serial numbers for multiple
zPDT machines within an enterprise. Clients access the server through TCP/IP. The
server runs under a normal Linux userid (and not under root).
򐂰 UIM Client - Each Linux machine running zPDT has a client function. In a local operation,
a remote UIM server might not be involved. The UIM client could operate solely from the
local UIM database.