Pivotal - Reference r10 r10SP1 PLM

...................................
....
Pivotal® License Manager r1.0
and r1.0 Service Pack 1
Reference
December 2006
.....
Pivotal® License Manager r1.0 and r1.0 Service Pack 1 Reference
Second Edition
December 12, 2006
PROPRIETARY NOTICE
Copyright © 1997-2006 Pivotal Corporation. All rights reserved.
Pivotal®, the Pivotal logo and the Pivotal family of products are registered trademarks and/or trademarks of Pivotal Corporation.
All rights reserved.
Microsoft is a registered trademark of Microsoft Corporation.
Oracle is a trademark or a registered trademark of Oracle Corporation. HP/UX is a trademark or registered trademark of Hewlett
Packard Corporation. Sun, Sun Microsystems, SPARC, and Solaris are used under license and are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license
and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products
bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. Vaultus is a registered
trademark of Vaultus Mobile Technologies, Inc. ("Vaultus"). The BlackBerry and RIM families of related marks, images and
symbols are the exclusive properties of and trademarks or registered trademarks of Research in Motion - used by permission.
Red Hat and the Red Hat Shadowman logo are registered trademarks of Red Hat, Inc. Linux is a registered trademark of Linus
Torvalds. All other trademarks are the property of their respective owners.
Intersolv® is a registered trademark of DataDirect Technologies, © Copyright 1994-1998. All Worldwide Rights Reserved.
JRun® is a registered trademark of Macromedia, Inc.
Portions of this software are copyrighted by Rogue Wave Software, Inc. © Copyright 2002. Portions of this software are
copyrighted by JSockets® © Copyright 1998, Caribou Lake Software, Inc. Portions of this software were developed by
openwddx.org.
This product includes software developed by Logica by whom copyright and know-how are retained, all rights reserved.
Copyright (c) 1996-2001 Logica Mobile Networks Limited.
The source code, object code, and documentation in the com.oreilly.servlet package is copyrighted and owned by Jason Hunter.
© Copyright 2001 by Jason Hunter. All rights reserved.
RightFax® is a registered trademark of the AVI Corporation.
Java®, Hotspot Performance Engine®, Java API for XML Processing (JAXP) and all Java-based trademarks and logos are
trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
Unicode is a registered trademark of Unicode, Inc.
Intellisync, and the Intellisync logo are trademarks of Intellisync, Inc. that may be registered in some jurisdictions.
Interactive Intelligence Customer Interaction Center is the registered trademark of Interactive Intelligence Inc. U.S. and foreign
patents pending.
All other company or product names appearing in this guide are for identification only and may or may not be trademarks or
registered trademarks of their respective holders.
Pivotal Customer Relationship Management Software is licensed and subject to the conditions and limitations of the Pivotal
License.
The information herein is the property of Pivotal and any misuse or abuse will result in economic loss. DO NOT COPY UNLESS
YOU HAVE BEEN GIVEN SPECIFIC WRITTEN AUTHORIZATION FROM PIVOTAL.
CONFIDENTIAL INFORMATION
This document is provided for limited and restricted purposes in accordance with a binding contract with Pivotal. The
information herein includes trade-secrets and should all be considered confidential.
DISCLAIMER
THE INFORMATION IN THIS DOCUMENT WILL BE SUBJECT TO PERIODIC CHANGE AND UPDATING. PLEASE
CONFIRM THAT YOU HAVE THE MOST CURRENT DOCUMENTATION. THERE ARE NO WARRANTIES OF ANY KIND,
EXPRESS OR IMPLIED, PROVIDED IN THIS DOCUMENTATION, OTHER THAN THOSE EXPRESSLY AGREED UPON IN
THE APPLICABLE PIVOTAL CONTRACT, ERRORS AND OMISSIONS EXCEPTED.
For additional information, contact:

Head Office Europe
Pivotal Corporation Pivotal Corporation Limited
#600-858 Beatty Street Wilson House, Fenian Street
Vancouver, BC Dublin 2
Canada V6B 1C1 Ireland
Telephone: 604-699-8000 Telephone: 353-1-662-9333
Fax: 604-699-8001 Fax: 353-1-662-9334
Web address: http://www.pivotal.com
. . . . . . . . . . . . . . . . . . . . . . . . . . . Contents
........
....
About This Guide
Chapter 1 Introducing License Management
License Management Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Out-of-the-box License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
License Server System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Deploying the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Chapter 2 Setting Up License Management
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Setting Up License Management without Redundant Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Setting up the License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Installing Sentinel RMS Development Kit Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Installing Pivotal License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Oracle Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Specifying details of the Pivotal License Manager user account . . . . . . . . . . . . . . 2-7
Generating the Locking Code for the License Server Computer. . . . . . . . . . . . . . . . . . . . . . 2-8
Requesting for a Production License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Configuring the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Specifying the License Server Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Copying the License Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Adding the License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Setting Up eRelationship Systems for License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Specifying Licensing Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Pre-r5.9 Service Pack Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Managing User Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Assigning Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Unassigning User Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Unassigning LAN or Satellite User Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Unassigning Mobile Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Setting Up License Management with Redundant Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Recommendations for Setting Up the Redundant License Server Cluster . . . . . . . . . . . . . 2-20
Setting Up Redundant License Server Computers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Generating the Locking Code for Each Redundant License Server Computer . . . . . . . . . . 2-21
Requesting for a Redundant Production License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Copying the Redundant Production License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Setting Up the Leader License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
.....
Dec 12 2006 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference iii
Contents
Copying the lservrlf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Setting up eRelationship Systems for License Management . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Using an Emergency License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Using the License File with Additional Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Uninstalling Sentinel RMS Development Kit Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Uninstalling Pivotal License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Chapter 3 Troubleshooting
Do’s and Don’ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Do’s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
License Server Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Oracle Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Pivotal eRelationship Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Don’ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Error Messages Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Pivotal License Manager Log Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Appendix A Non-Production License Files
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Obtaining New Non-Production License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Using the Downloaded Non-Production License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Appendix B Production License File Request: Sample Format
Requesting for a Production License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Sample Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Index
.....
iv Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference Dec 12 2006
. . . . . . . . . . . . . . . . . . . .About
. . . . . This
. . . . Guide
......
....
................................
Scope
This guide provides information for license management and
associated tasks.
................................
Audience
This guide is written for system administrators responsible for
setting up and administering Pivotal license management.
................................
Prerequisites
You should have experience setting up and administering Pivotal
eRelationship systems. You should also have experience
administering Windows 2003 Server computers.
................................
Pivotal Product Guides,
Technical Support, and
Education Services
You can access a wide variety of information about Pivotal
products on the Internet at: http://www.pivotal.com.
Documentation updates, product guides, technical support and

education services are available from the Pivotal Customer Portal at
http://eservice.pivotal.com or from the Pivotal Partner
Portal at http://epartner.pivotal.com. You will require a
valid user name and password to access these sites. Contact
SupportReadiness@cdcsoftware.com for logon information.
Contact Pivotal Global Technical Support at

http://www.pivotal.com/services/
global_support.asp.
.....
Dec 12 2006 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference v
About This Guide:
Pivotal Product Guides, Technical Support, and Education Services
Contact the Pivotal Education Services Group at

http://www.pivotal.com/services/education_services.asp.
Send questions, comments or suggestions related to documentation to

Documentation@cdcsoftware.com.
.....
vi Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference Dec 12 2006
...................................
....
Introducing License Management
1
.....
Dec 12 2006 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference 1-1
1 Introducing License Management:
License Management Terminology
License Management Terminology
Activated users
Activated users are the named users who are assigned a license to access an
eRelationship system.
Emergency license file
An interim license file that can be used when a license server computer is replaced owing
to problems such as a hardware malfunction. Contact Pivotal Global Technical Support
for an emergency license file.
License file
A file that stores information about licensing such as the total number of licenses that can
be assigned to users. The license file must be added to the license server. The license file
is used by the license server to track the number of available licenses that can be assigned
or unassigned.
License server
A Windows Server 2003 computer with Sentinel RMS Development Kit Server and
Pivotal License Manager installed.
License server pool
A cluster of redundant license servers.
Locking code
A code generated specifically for a computer. Use the echoid.exe to generate the
locking code specific to the Ethernet address and the NetBIOS name of the license server
computer.
Named users
Users added to the Users table in eRelationship.

.....
1-2 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference Dec 12 2006
Introducing License Management:
Overview 1
Production license file
A license file to be used for a Production System. Depending on the licensing agreement,
the production license file allows only a specified number of licenses to be assigned to
users.
Overview
Pivotal Lifecycle Engine r5.9 enforces license management. Only named and activated
users are granted access to eRelationship systems. Named users are the users added to the
Users table in eRelationship. Activated users are the named users who are specifically
assigned a license to access an eRelationship system. For license management, you
require a Windows Server 2003 computer as the license server with the following
installed:
• Sentinel RMS Development Kit Server
• Pivotal License Manager
Information about licensing such as the total number of licenses that can be assigned to
users is stored as encrypted data in a license file. The license server uses the license file
and tracks the number of available licenses that can be assigned or unassigned.
................................
Out-of-the-box License Files
Table 1-1 lists the out-of-the-box license files in the License Files folder on the Pivotal
r5.9 License Management CD-ROM.
Table 1-1 Out-of-the-box license files
License File Type of eRelationship System and Environment
Pivotal.Customization Customization System in a production environment
Pivotal.Demo Demo System for demonstration purposes
Pivotal.Demo.Mobile Mobile Demo System for demonstration purposes
Pivotal.Dev.Custom Customization System in a development environment
Pivotal.Dev.Master Development Production System in a development

environment
Pivotal.Dev.Offline Offline System in a development environment
Pivotal.Offline Offline System in a production environment
Each license file listed in Table 1-1 grants access to only 5 named and activated users.
The Pivotal.Demo license file, when used along with the Pivotal.Demo.Mobile
license file, grants access to 7 named and activated users, of which 2 licenses can be used
for mobile users.
For a Production System, you need to request for a production license file. For more
information, see Requesting for a Production License File on page 2-9.
.....
Overview
Note: The out-of-the-box license files for non-production systems provided on the
Pivotal r5.9 License Management CD-ROM expire on December 31, 2006. For more
information about obtaining new non-production license files and associated
procedures, see Non-Production License Files on page A-1.
................................
License Server System Requirements
Table 1-2 lists the system requirements for the license server.
Table 1-2 System requirements for the license server
Component Requirements Comments

1
Operating system One of the following :
• Windows Server 2003
(Standard or Enterprise
Edition) Service Pack 1 Note: Do not host the
and IIS 6.0 license server on a virtual
• Windows Server 2003 machine.
(Standard or Enterprise
Edition) Release 2 and
IIS 6.0
Processor speed 2 GHz Minimum recommended

hardware requirement.
RAM 512 MB Minimum recommended

hardware requirement.
Hard disk space 140 MB free hard disk Minimum recommended
space hardware requirement.
1. 64-bit operating systems are not supported.
................................
Deploying the License Server
Figure 1-1 on page 1-5 shows a license server in a master, satellite, and mobile
deployment. .....
Introducing License Management:
Overview 1
Figure 1-1 License server in a master and satellite deployment with mobile systems
If the master and satellite systems are on the same domain, you can set up a single license
server as shown in Figure 1-1. If the master and satellite systems are on different or
non-trusted domains, set up separate license servers for each system. Decide the number
of license server computers depending on the requirements of your deployment scenario.
Figure 1-2 on page 1-6 shows a master and satellite system with separate license servers.
.....
Overview
Figure 1-2 Master and satellite systems with separate license servers
Depending on the deployment scenario, set up license servers with or without

redundancy. For more information, see Setting Up License Management without
Redundant Servers on page 2-5 or Setting Up License Management with Redundant
Servers on page 2-19.
If you are upgrading from previous versions of Lifecycle Engine and Applications/CMS,
see the Pivotal Lifecycle Engine r5.9 Upgrade and Migration Guide and the Pivotal
Applications/CMS r5.9 Upgrade and Migration Guide.
Note: It is recommended that you install Pivotal SyncStream r5.9 Service Pack 1
before deploying mobile systems.
.....
...................................
....
Setting Up License Management
2
.....
2 Setting Up License Management:
Overview
Overview
This chapter details the procedures to install license management software and manage
user licenses for Pivotal eRelationship systems.
For information about prerequisite tasks and system requirements for the license server
computer see Chapter 1, Introducing License Management.
Figure 2-1 on page 2-3 and Figure 2-2 on page 2-4 provide an overview of license
management tasks. Each task is linked to the section with relevant information.
.....
Setting Up License Management:
Overview 2
Start
Yes Redundant License Servers?

Go to A
No
on the license server
Install Sentinel RMS Development Server
Install Pivotal License Manager
Generate the locking code
Request for the production license file
Specify the license server computer

Copy the production license file
Add the production license file
Master/Satellite Mobile or Master/Satellite? Mobile
on the parent system

Specify licensing details for the
eRelationship system
Specify licensing details for the Specify the e-mail address and HTTP
eRelationship system Message Server for the mobile user
Assign licenses Assign mobile license
Start synchronization
Yes End
Pivotal r5.9 Service Pack 1 applied?
No
on the mobile computer

Install mobile license
Figure 2-1 Setting up license management without redundant servers

.....
Overview
Set up the redundant license server cluster
on each license server

Install Sentinel RMS Development Server
Install Pivotal License Manager
Generate the locking code
Request for a redundant production license file
on the leader license server

Copy and paste the redundant production license file
Set up the leader license server
on each license server

Copy and paste the lservlf file
Set up the eRelationship system
Go to B
Figure 2-2 Setting up license management with redundant servers

.....
Setting Up License Management without Redundant Servers 2
Setting Up License Management without

Redundant Servers
This section details the procedures to set up license management without redundant
servers for a Pivotal Lifecycle Engine r5.9 deployment.
To set up license management without redundant servers
1 Set up the license server

a) Install Sentinel RMS Development Kit Server
b) Install Pivotal License Manager
2 Generate the license server computer’s locking code
3 Request for a production license file
4 Configure the license server
5 Set up eRelationship systems for license management
a) Specify licensing details
b) Assign licenses
................................
Setting up the License Server
This section details the procedure to set up the license server. Do not use a virtual image
to set up the license server. For more information about system requirements for the
license server, see License Server System Requirements on page 1-4. To set up the license
server, install the following:
Installing Sentinel RMS Development Kit Server

Install Sentinel RMS Development Kit Server on the computer designated as the license
server.
To install Sentinel RMS Development Kit Server
1 On the computer designated as the license server, log on as the administrator.

2 Insert the Pivotal r5.9 License Management CD-ROM into the CD-ROM drive.
3 Open Windows Explorer, and browse the folders on the Pivotal r5.9 License
Management CD-ROM.
4 Open the License Server folder and double-click setup.exe.
5 In the Sentinel RMS Development Kit Server - InstallShield Wizard window,
click Next.
.....
Setting Up License Management without Redundant Servers
6 Accept the license agreement and click Next.

7 Type the user name and organization. Select the option to install the application for
all users or only the logged on user, and then click Next.
8 The destination folder to which Sentinel RMS Development Kit Server will be
installed is displayed as C:\Program Files\Common Files\SafeNet Sentinel.
The destination folder cannot be changed. Click Next.
9 Select the Complete option to install all components and then click Next.
10 Click Install to begin the installation.
11 Click Finish when the installation is complete.
Sentinel RMS Development Kit Server is installed.
Installing Pivotal License Manager

Install Pivotal License Manager on the same license server computer where Sentinel
RMS Development Kit Server is installed.
Before installing Pivotal License Manager, do the following:

• On the license server computer:
• Create a domain account with a user name and password to run Pivotal
License Manager.
• Grant the user Log on as a batch job and Log on as a service security
policy rights. Assign these security policy rights either by adding the user to
the IIS_WPG group or by using the Local Security Settings window. If
you add the user to the IIS_WPG group, verify that the group is assigned
the required security policy rights.
• On the SQL or Oracle Server, add the user to the RelationshipAdmin group or
grant write access rights to the Business Module and Enterprise Data databases. For
more information about the RelationshipAdmin group, see the Pivotal Lifecycle
Engine r5.9 Deployment Guide.
Oracle Environment
If eRelationship is deployed in an Oracle environment, it is recommended that the license
server computer has a complete Oracle Client installation. Ensure that the tnsnames.ora
file has the Oracle instance name used for the eRelationship deployment. On the license
server computer, if you do not select the complete Oracle Client installation option,
install the Oracle Client and the OLE DB Provider for Oracle. If you use the Oracle 9i
Client, ensure to use the Oracle 9i Provider for OLE DB 9.2.0.7.0.
If you use the Oracle 10g Release 1 Client, ensure to use the Oracle 10g Provider for
OLE DB 10.1.0.4.0.
.....
To install Pivotal License Manager1
1 On the computer designated as the license server, log on as the administrator.

2 Insert the Pivotal r5.9 License Management CD-ROM into the CD-ROM drive.
The setup program runs automatically. If the setup program does not start
automatically, navigate to the PLM folder on the Pivotal r5.9 License Management
CD-ROM and double-click the setup.exe file.
3 In the Pivotal License Manager r1.0 - InstallShield Wizard dialog box, click
Next.
4 Accept the license agreement and click Next.
5 Select either of the following:
• Complete and then click Next to install Pivotal License Manager to the default
directory.
• Custom and then click Next if you want to change the directory to which
Pivotal License Manager is installed.
• Click Change to specify the directory.
• Type the name of the folder in the Folder name box, or browse to the
destination folder.
• Click OK.
• Click Next.
6 Type the domain name, user name, and password of the user account under which
Pivotal License Manager is to be run, and then click Next.
Ensure that the user account has write access rights to the Business Module and
Enterprise Data databases. You can also specify the domain name, user name, and
password in the Internet Information Services (IIS) Manager window after
installing Pivotal License Manager. For more information, see To specify details of
the Pivotal License Manager user account on page 2-8.
7 Click Install.
8 Click Finish when the installation is complete.
Pivotal License Manager is installed. The installation also creates a PLicenseManager

virtual directory under the Default Web site in Internet Information Service (IIS).
Integrated Windows Authentication is used for the PLicenseManager virtual
directory.
Specifying details of the Pivotal License Manager user account

During the installation of Pivotal License Manager, if the domain name, user name, and
password of the user account to run Pivotal License Manager were not specified, follow
the procedure detailed here.
1. Ensure to apply the related Pivotal service packs. For more information about installing the service
packs, see the release notes.
.....
To specify details of the Pivotal License Manager user account
1 On the license server computer, click Start and then click Run.
2 Type inetmgr in the Run dialog box.
3 In the Internet Information Services (IIS) Manager window, expand the name of
the license server computer, and then expand Application Pools.
4 Right-click the PLicenseManager application pool and select Stop.
5 Right-click the PLicenseManager application pool and select Properties.
6 In the PLicenseManager Properties dialog box, click the Identity tab.
7 Select Configurable and type the user name and password in the User Name and
Password boxes. Type the user name in the format domain\username.
8 Click OK.
9 Right-click the PLicenseManager application pool and select Start.
The domain, user name, and password are specified for the Pivotal License Manager user
account.
To ensure that Pivotal License Manager is properly installed
>> On the license server computer where Pivotal License Manager is installed, open a
Web browser and type the following URL in the Address box:
http://<computername>/PLicenseManager/PlicenseManager.dll?default
If Pivotal License Manager is properly installed, the following text is displayed in the
browser window:
<?xml version="1.0" ?>
<PLicenseManager>This default message was produced by the Internet
Server DLL Wizard. Edit your CPLicenseManagerExtension::Default()
implementation to change it.</PLicenseManager>
For information about troubleshooting the installation of Pivotal License Manager, see
Chapter 3, Troubleshooting.
................................
Generating the Locking Code for the
License Server Computer
To obtain a production license file, provide the locking code of the license server
computer to Pivotal Global Technical Support. Generate the locking code for the license
server computer by using the Sentinel Host Locking Code Information Utility
(echoid.exe). By default, the echoid.exe utility is located in the \Program
Files\Pivotal\SyncStream\Licensing folder.
.....
To generate the license server computer’s locking code
1 Open a Command Prompt window, and change directory to the folder with the
echoid.exe utility.
2 At the command prompt, type echoid.exe.

3 Copy the locking code displayed in the Command Prompt window.
The locking code generated is specific to the Ethernet address and the NetBIOS name of
the license server computer.
It is not recommended to change the license server computer. If a different computer is

designated as the license server, run the echoid.exe utility again and submit a new
request for a license file. For more information about requesting for a production license
file, see Requesting for a Production License File on page 2-9.
................................
Requesting for a Production License File
Send the license server computer’s locking codes to Pivotal Global Technical Support
along with your request for a production license file. Based on the number of licensed
users, Pivotal Global Technical Support will send you a production license file.
To request for a production license file
1 Log on to the Pivotal Global Technical Support Web site at:

http://login.pivotal.com.
2 Create a new Support Incident.

3 Provide relevant information in all mandatory fields. Additionally:
• Select License Request from the Type drop-down list.
• Provide the:
• License server computer’s locking code
• Number of LAN licenses required
• Number of mobile licenses required
• Locking codes and number of licenses for each satellite system with a
separate license server
• Locking codes for redundant license servers, if any
4 Click Save.
After your support incident request has been logged and processed, you will receive the
required production license files from Pivotal Global Technical Support.
Note: To obtain additional licenses for a Production System, contact Pivotal Global
Technical Support for a new license file. For more information about using the
additional license file, see Using the License File with Additional Licenses on page
2-25.
.....
................................
Configuring the License Server
To configure the license server, specify the license server computer and the license files.
To configure the license server
1 Specify the license server computer

2 Copy the license files
3 Add the license files
Specifying the License Server Computer

Use the WlmAdmin tool to specify the license server computer.
To specify the license server computer
1 On the license server, click Start, point to Programs, then point to Pivotal, and then
select License Server.
2 In the WlmAdmin window, expand the list under Subnet Servers.
3 The name of the license server computer is listed under Subnet Servers. If the name
of the computer is not displayed, select Defined Server List from the Edit menu.
4 In the Defined Server List dialog box, type the name of the computer designated as
the license server, click Add and then click OK.
The name of the license server computer is listed under Subnet Servers.
Copying the License Files

Out-of-the-box license files are located in the License Files folder on the Pivotal r5.9
License Management CD-ROM. For more information about the out-of-the-box license
files, see Table 1-1 on page 1-3. The out-of-the-box license files expire on 31 December,
2006. For more information about obtaining new non-production license files and
associated tasks see Appendix A, Non-Production License Files.
Note: To obtain a license file for a Production System, contact Pivotal Global
Technical Support. Mention the license server computer’s locking code along with your
request for the production license file. For more information, see Generating the
Locking Code for the License Server Computer on page 2-8 and Requesting for a
Production License File on page 2-9.
Copy the following to a folder on the license server:

• License files from the Pivotal r5.9 License Management CD-ROM.
• Production license files received from Pivotal Global Technical Support.
.....
Setting Up eRelationship Systems for License Management 2
Adding the License Files

Use the WlmAdmin tool to add license files to the license server.
To add license files
1 On the license server, click Start, point to Programs, point to Pivotal, and then
3 Right-click the name of the license server computer, select Add Feature, point to
From a File, and then select To Server and its File.
4 Browse to the location of the license file and click Open.
The feature name and the version of the license file are listed under the license server
computer name. Repeat steps 1 to 4 for each license file.
Setting Up eRelationship Systems for License

Management
Depending on the deployment scenario, before you set up an eRelationship system for
licensing, install the required software and create eRelationship systems.
If you are upgrading from previous versions of Lifecycle Engine or Applications/CMS,

see the Pivotal Lifecycle Engine r5.9 Upgrade and Migration Guide and the Pivotal
Applications/CMS r5.9 Upgrade and Migration Guide.
To set up eRelationship systems for license management
1 Specify licensing details

2 Assign licenses
Specifying Licensing Details

For each eRelationship system specify the licensing details such as the name of the
license server computer and the license file. You can assign licenses only after the
licensing details are specified for each eRelationship system.
Specify the license file for the master system or the satellite system.
Note: If you have installed Pivotal SyncStream r5.9 Service Pack 1, you do not need
to specify the license file for a mobile system or install a mobile license file on the
mobile computer. However, you need to assign a mobile license for the mobile user
from the main system.
.....
Setting Up eRelationship Systems for License Management
To specify licensing details for a master or satellite system
1 On the administrative computer, click Start, point to Programs, point to Pivotal,

and then click eRelationship Enterprise Manager.
2 In the Servers pane of the Pivotal eRelationship Enterprise Manager window,
expand the appropriate server listed under Data Synchronization, and then select
the eRelationship system.
3 Right-click the eRelationship system name and select System Properties.
4 In the Licensing area on the System tab of the Properties dialog box:
a) Type the name of the license server computer in the License Server box.
Use the format:
http://<Server Name>:<Port No>
where:
Server Name is the name of the license server computer with Sentinel RMS
Development Kit Server and Pivotal License Manager installed.
Port No is the port number for the PLicense Manager virtual directory.
If the default Web site for the PLicense Manager virtual directory does not use
80 as the TCP Port, type the port number.
If HTTPS protocol is used, type https instead of http. If the port number is not
443, type the port number. Use the format:
https://<Server Name>:<Port No>
b) Click Connect to connect to the license server.
c) Select the license file from the License File drop-down list.
d) Click Set License File to set the license file for the eRelationship system.
5 Click OK.
The license file is specified for the eRelationship system.
The following text is displayed in the Licensing area of the System tab in the Properties
dialog box:
• License File set
The text is displayed when the license file is successfully set for an eRelationship
system.
• License file already set
The text is displayed if the license file has been already set for an eRelationship
system.
• The current License File is set
The text is displayed if you close and open the Pivotal eRelationship Enterprise
Manager window after the license file is set for an eRelationship system, and when
the connection to the license server is successful.
.....
Setting Up eRelationship Systems for License Management 2
Note: For an eRelationship system, when the license file already specified is a
production license file, you cannot specify a non-production license file. However, to
specify a production license file when the license file already specified for an
eRelationship system is a non-production license file, first unassign all licenses. For
more information about unassigning licenses, see Unassigning User Licenses on page
2-17.
Pre-r5.9 Service Pack Releases

If you have not installed Pivotal SyncStream r5.9 Service Pack 1 on the mobile
computer, follow these additional steps to specify licensing details for a mobile system.
Before you specify the license file for a mobile system, do the following:
• Add the production license file and the mobile license file to the license server.
For more information about adding license files, see Adding the License Files on
page 2-11.
• Verify if the mobile system is:
• Able to access the same network as the parent eRelationship system and the
license server computer.
• Connected to the parent eRelationship system.
Note: Installing Pivotal SyncStream r5.9 Service Pack 1 on a mobile computer also
automatically installs the Pivotal.Mobile license file. You do not require any
separate license file for mobile systems, and do not need to perform the steps
documented in this section. However, on the main system, ensure to assign a license to
the mobile user. For more information about assigning licenses, Assigning Licenses on
page 2-16.
To specify licensing details for a mobile system
1 On the computer where the parent eRelationship system is defined:

a) Click Start, point to Programs, point to Pivotal, then click eRelationship
Enterprise Manager.
b) In the Servers pane of the Pivotal eRelationship Enterprise Manager window,
expand a server under Data Synchronization and select the eRelationship
system.
c) Follow the steps detailed in To specify licensing details for a master or satellite
system on page 2-12 for a production license file.
d) In the Users pane of the Pivotal eRelationship Enterprise Manager window:
• Specify the e-mail address and HTTP server for the mobile user. For more
information about specifying user properties see the Pivotal eRelationship
Enterprise Manager r5.9 Help.
• Select the mobile user and assign the mobile license. For more information,
see Managing User Licenses on page 2-15.
2 Start synchronization for the mobile user. For more information, see the Pivotal
eRelationship Enterprise Manager r5.9 Help.
.....
Setting Up eRelationship Systems for License Management
3 On the mobile computer, after the mobile system has been successfully received and
processed:
a) Log on with administrator rights.
b) Open Windows Explorer, and browse to the Pivotal\SyncStream folder.
c) Double-click SysMgr.exe.
d) In the Servers pane of the Pivotal eRelationship Enterprise Manager window,
expand the server under Data Synchronization and select the mobile system
name.
e) Right-click the mobile system name and select System Properties.
f) In the Licensing area on the System tab of the Properties dialog box:
• If a new mobile system has been successfully received and processed, the name
of the license server computer is displayed in the License Server box and the
name of the mobile license file is displayed in the License File box.
• If the mobile system has not been received:
• Type the name of the license server computer in the License Server box.
Type the name of the license server computer in the format
http://<Server Name>:<Port No>
where:
Server Name is the name of the license server computer
Port No is the port number for the PLicense Manager virtual directory.
If the default Web site for the PLicense Manager virtual directory does not
use 80 as the TCP Port, type the port number.
If HTTPS protocol is used, type https instead of http. If the port number is
not 443, type the port number. Use the format:
https://<Server Name>:<Port No>
• Click Connect to connect to the license server.
• Select the license file that was specified for the parent eRelationship system
from the License File drop-down list.
4 Click Install Mobile License in the Licensing area on the System tab of the
Properties dialog box.
5 Click OK.
The license is set for the mobile system and the text Mobile License Installed is
displayed in the Licensing area of the System tab in the Properties dialog box.
After the license has been set for a mobile system, if you close and open the Pivotal
eRelationship Enterprise Manager window, the text Connected is displayed in the
Licensing area.
.....
Managing User Licenses 2
Managing User Licenses

Use Pivotal eRelationship Enterprise Manager to assign or unassign licenses.
If you have started the DSM for a specific eRelationship system, and you want to assign
or unassign licenses for users of another eRelationship system, ensure you stop the DSM
before assigning or unassigning licenses.
Note: You cannot use a mobile system to assign or unassign licenses; use either the
master or parent satellite system. Assign user licenses before you begin
synchronization.
To assign or unassign licenses for an eRelationship system, ensure that:

• You are added as a user to the RelationshipAdmin Group.
For more information about the RelationshipAdmin Group, see the Pivotal
Lifecycle Engine r5.9 Deployment Guide. If you are not a part of the
RelationshipAdmin Group, add yourself to the Users table in eRelationship.
To add yourself to the Users table, start Windows Access and log on to the
eRelationship system. For more information, see To be added as a user to an
eRelationship system on page 2-15.
• You are granted db_owner rights to the Business Module and Enterprise Data
databases.
• For deployments in a SQL Server environment, the PLicenseManager user is
granted write access rights to the Pivotal Business Module and Enterprise Data
databases. This step is not required if the PLicenseManager user is part of the
RelationshipAdmin Group. The PLicenseManager user account is used to run the
PLicenseManager virtual directory.
• The eRelationship system is defined, the FilePath specified, and *.rdf files
restored. Complete the tasks detailed in Chapter 2, Planning for Deployment in the
Pivotal Lifecycle Engine r5.9 Deployment Guide.
To be added as a user to an eRelationship system
1 On the administrative computer where the eRelationship system is defined, click

Start, point to Programs, point to Pivotal, and then click eRelationship.
2 In the Pivotal Login dialog box:
a) Select the eRelationship system from the System drop-down list.
b) Click OK.
3 Click Yes in the confirmation box to add yourself as a user to the eRelationship
system.
You are automatically added as a user to the eRelationship system.

.....
................................
Assigning Licenses
Depending on whether a user is a LAN, satellite user, or a mobile user, you can assign
licenses to a single user or multiple users. You can also assign licenses to a group or
multiple groups.
Before assigning licenses to users or groups for the eRelationship system:

• Restore the eRelationship system.
If you are upgrading to a Pivotal Lifecycle Engine r5.9 deployment, see the Pivotal
Lifecycle Engine r5.9 Upgrade and Migration Guide.
• Specify the license file for the eRelationship system.
For more information about specifying the license file, see Specifying Licensing
Details on page 2-11.
• Connect to the eRelationship system.
For information about connecting to an eRelationship system, see the Pivotal

eRelationship Enterprise Manager Help for r5.9 Service Pack 1 or r5.9.
• Specify the e-mail address and HTTP server for mobile users and synchronizing
systems.
For information about specifying the e-mail address and the HTTP server, see the
Pivotal eRelationship Enterprise Manager Help for Pivotal SyncStream r5.9 Service
Pack 1 or Pivotal SyncStream r5.9.
To assign licenses to users or groups

then click eRelationship Enterprise Manager.
expand a server under Data Synchronization and select the eRelationship system.
3 In the Users pane, click the Users option to display the list of users.
If you want to assign licenses to groups, click the Groups option in the Users pane.
4 In the User ID or Group ID column:
• Select the user or group name. To select multiple users or groups, do one of the
following:
• Press SHIFT for contiguous selection
• Press CTRL for non-contiguous selection
• Right-click the selected users or groups, and then select one of the following:
• Assign License for a LAN or satellite user or group
• Assign Mobile License for a mobile user or mobile group
5 Click Yes in the confirmation box if you have selected multiple users or groups.
Licenses are assigned to the selected users or groups.

.....
Managing User Licenses 2
Warning! If you select a large number of users or groups, the time taken to assign
licenses will be significantly longer than the time taken to assign licenses to a smaller
number of users or groups.
The icon is displayed in the License column for any user with an assigned license.
If all members of a group are assigned a license, the icon is displayed in the License
column. If only some members of a group are assigned a license, the icon is
displayed in the License column.
The number of available licenses displayed in the Available Licenses box changes
depending on the number of licenses assigned or unassigned. Ensure that the number of
licenses you assign does not exceed the number of licenses displayed in the Available
Licenses box, or else an error message is displayed.
The number of available mobile licenses displayed in the Available Mobile Licenses
box changes depending on the number of licenses assigned or unassigned. Ensure that the
number of assigned mobile licenses does not exceed the number of available mobile
licenses displayed in the Available Mobile Licenses box, or else an error message is
displayed. Assigning a mobile license also decrements the number of available licenses.
................................
Unassigning User Licenses
You can unassign single or multiple user licenses. You can also unassign single or
multiple group licenses. When all licenses are unassigned, the number displayed in the
Available Licenses box in the Users pane of the Pivotal eRelationship Enterprise
Manager r5.9 window, will be the same as the number displayed in the Total Licenses
box. This section details the following procedures:
• Unassigning LAN or Satellite User Licenses
• Unassigning Mobile Licenses
If you have started the DSM for a specific eRelationship system, and you want to
unassign licenses for users of another eRelationship system, ensure to stop the DSM
before unassigning licenses.
Unassigning LAN or Satellite User

Licenses
You can unassign single user, multiple user, group, or multiple group licenses. If you
unassign a license for the DSM user, the DSM will be stopped. Before unassigning the
satellite user license, stop synchronization for the satellite user using the Stop
Synchronization command in Pivotal eRelationship Enterprise Manager. For more
information about stopping synchronization, see the Pivotal eRelationship Enterprise
Manager Help for Pivotal SyncStream r5.9 Service Pack 1 or Pivotal SyncStream r5.9.
.....
To unassign user or group licenses

then click eRelationship Enterprise Manager.
expand a server under Data Synchronization and select the eRelationship system.
3 In the Users pane, click the Users option to display the list of users.
If you want to unassign licenses to groups, click the Groups option in the Users
pane.
• Select the user or group name. To select multiple users or groups, do one of the
following:
5 Right-click the selected users or groups, and then select Unassign License.
Licenses are unassigned, and the or icons are not displayed in the License
displayed in the License column. The number of available licenses displayed in the
Available Licenses box changes depending on the number of licenses assigned or
unassigned.
Unassigning Mobile Licenses

Before you unassign mobile licenses, ensure that you are a member of the
RelationshipAdmin group.
Before unassigning the mobile user license, stop synchronization for the mobile user
using the Stop Synchronization command in Pivotal eRelationship Enterprise Manager.
For more information about stopping synchronization, see the Pivotal eRelationship
Enterprise Manager Help for r5.9 Service Pack 1 or r5.9.
To unassign mobile licenses
1 Stop mobile synchronization for the mobile user on the parent system.
For more information about stopping mobile synchronization see the Pivotal
eRelationship Enterprise Manager Help for Pivotal SyncStream r5.9 Service Pack 1
or Pivotal SyncStream r5.9.
2 Unassign licenses for mobile users or groups on the parent system.
For more information about unassigning licenses for mobile users or groups, see To
unassign mobile user or group licenses on the parent system on page 2-19.
.....
Setting Up License Management with Redundant Servers 2
To unassign mobile user or group licenses on the parent system
1 On the computer where the parent system is defined, click Start, point to Programs,
point to Pivotal, then click eRelationship Enterprise Manager.
2 In the Pivotal eRelationship Enterprise Manager window, expand a server under
Data Synchronization and select the eRelationship system.
3 In the Users pane, click the Users option to display the list of users. If you want to
unassign group licenses, select the Groups option in the Users pane.
a) Select the mobile user or group name. To select multiple users or groups, do one
of the following:
b) Right-click the selected users or groups and click Unassign License.
c) Click Yes in the confirmation box if you have selected multiple users or groups.
Licenses are unassigned, and the or icons are not displayed in the License
displayed in the License column.
After unassigning licenses for mobile users, you can initialize the child system on the
mobile computer. For more information about initializing the child system on the mobile
computer, see the Pivotal eRelationship Enterprise Manager Help for Pivotal
SyncStream r5.9 Service Pack 1 or Pivotal SyncStream r5.9.
Setting Up License Management with Redundant

Servers
A license server pool consists of a number of redundant license servers on separate
computers. You can designate one of these license server computers as the active license
server or the leader, and the other license servers as backup license servers or followers.
The redundant server deployment is configured for fail-over settings and not
load-balancing. Use Network Load Balancing Manager to set up the cluster. This
section details how to set up license management for a Pivotal Lifecycle Engine r5.9
deployment with redundant servers. It is presumed that you are familiar with tasks such
as network load balancing, setting up clusters, and other administrative procedures. To
set up license management with redundant servers, ensure that:
• The number of license server computers in the license server pool is an odd number.
For example you can have either three, five, or seven license server computers.
• At least more than half the number of license server computers are always functional
and connected to the network so that requests to the license server pool are serviced.
For example, if you have five license servers, at least three or more license server
computers should be functional and connected to the network.
.....
Setting Up License Management with Redundant Servers
• Virtual images are not used to set up license server computers.

• Each license server computer meets the minimum specified system requirements.
For more information, see License Server System Requirements on page 1-4.
• The Sentinel RMS Development Kit Server License Manager service is always
functional on all redundant license server computers within a license server pool.
If the service is not functional, remove the license server computer from the license
pool.
To set up license management with redundant servers
1 Set up the license server cluster and specify details for each license server computer
2 Set up each license server computer
3 Generate the locking code for each license server computer
4 Request for a redundant production license file from Pivotal Global Technical
Support
5 Copy the redundant production license file
6 Set up the leader license server
7 Copy and paste the lservrlf file on each license server
8 Set up eRelationship systems for license management
................................
Recommendations for Setting Up the
Redundant License Server Cluster
Determine the number of license server computers you want to set up. For each
redundant license server computer in the cluster:
• Specify the static Internet Protocol (IP) address.
Also specify the subnet mask.
• Select Unicast as the cluster operation mode.
• Determine and specify the priority for each license server computer.
Assign 1 as the Priority (unique host identifier) to the leader license server
computer. Assign priority 2, 3, and so on in sequence to the other follower license
server computers in the license server pool.
• Reserve a dedicated IP configuration for the virtual address for the cluster.
Type this virtual IP address for each license server computer while defining Host
Parameters.
• Ensure that the:
• Initial host state is set to Started.
• Filtering mode is specified as Single host for the cluster port rule.
.....
................................
Setting Up Redundant License Server
Computers
Set up each redundant license server computer in the license server pool by installing:
For more information about installing Sentinel RMS Development Kit Server, see
Installing Sentinel RMS Development Kit Server on page 2-5.
For more information about installing Pivotal License Manager, see Installing
Pivotal License Manager on page 2-6.
To verify if you have successfully installed Pivotal License Manager, open a browser
window and type the following URL in the Address box:
http://<virtual IP address>/PLicenseManager/
PlicenseManager.dll?default
If you have successfully installed Pivotal License Manager, the following text is
displayed in the browser window:
<?xml version="1.0" ?>
<PLicenseManager>This default message was produced by the Internet
Server DLL Wizard. Edit your CPLicenseManagerExtension::Default()
implementation to change it.</PLicenseManager>
................................
Generating the Locking Code for Each
Redundant License Server Computer
Generate the locking code for each license server computer in the license server pool. For
more information about generating the locking code, see Generating the Locking Code
for the License Server Computer on page 2-8.
................................
Requesting for a Redundant Production
License File
To request for a redundant production license file, contact Pivotal Global Technical
Support. Also specify the:
• Number of redundant license servers.
• Locking codes for the leader license server computer and follower license server
computers. Provide the locking codes in the order of priority beginning with the
locking code for the leader, first follower, second follower, and so on.
To request for the redundant production license file, use the procedure detailed in
Requesting for a Production License File on page 2-9.
.....
Setting Up License Management with Redundant Servers
................................
Copying the Redundant Production
License File
Copy the redundant production license file received from Pivotal Global Technical
Support to a folder on the leader license server. It is recommended that you copy the
redundant production license file to the directory where you installed Sentinel RMS
Development Kit Server.
................................
Setting Up the Leader License Server
Use the WlmAdmin utility on the leader license server to specify the leader and follower
license servers. Use WRlfTool to create the lservrlf file. You must place the
lservrlf file on each redundant license server computer.
Note: Before you set up the leader license server and create the lservrlf file, stop
the Sentinel RMS Development Kit License Manager service for each license server.
To set up the leader license server
1 On the leader license server, click Start, point to Programs, point to Pivotal, and
then select License Server.
2 In the WlmAdmin window, click Edit and then select Redundant License File.
3 In the WrlfTool window, click File and then select New.
a) In the Redundant Servers area of the lservrlf - WrlfTool window, click Add
Server.
b) In the Add Server to Pool dialog box:
• Type the Host Name of the leader license server computer in the Host
Name box. Use the NetBIOS name as the Host Name. For example, if the
leader license server’s computer name is leader, type leader in the Host
Name box.
• Type the static IP address in the IP/IPX Address box.
• Click OK.
c) Repeat steps a and b for each redundant license server in the cluster.
Add each redundant license server to the list according to the specified order of
priority for the cluster. For example, if the priority of the license server computer is
specified as 2, complete step a and step b for the first follower license server only
after you have specified the details of the leader license server computer.
Ensure that the list of displayed redundant license servers in the lservrlf - Wrlf Tool
window is the same as the order and priority of redundant license servers defined in
the cluster. To change the order, select the displayed host name and address of the
license server computer and click Move Up or Move Down.
.....
d) In the Redundant Licenses area of the lservrlf - WrlfTool window, click Add
License.
• In the Add Redundant License dialog box, select the Read License(s)
from file option.
• Click Browse to navigate to the folder with the redundant production
license file received from Pivotal Global Technical Support.
• Select the redundant production license file and click Open.
• Click OK.
• Click Done in the Edit License window.
e) Click File and select Save As to save the lservrlf file to a destination folder.
You can also type a different name for the lservrlf file. Click Save.
f) Click File and select Exit to close the lservrlf - WrlfTool window.
4 Click File and click Exit to close the WlmAdmin window.
Redundant license servers are defined and the lservrlf file is created in the specified
destination folder.
................................
Copying the lservrlf File
Use the lservrlf file as the redundant license file for each redundant license server in
the license server pool. Copy the lservrlf file and paste it in the \Program
Files\Common File\SafeNet Sentinel\Sentinel RMS Development Kit
Server\Win NT folder on the leader license server and on every follower license server.
................................
Setting up eRelationship Systems for
License Management
Before setting up eRelationship systems for license management, start the Sentinel RMS
Development Kit License Manager service for each redundant license server according to
the specified order of priority. For example, first start the service for the leader license
server, then the first follower license server, and so on.
To set up eRelationship systems for license management, see Setting Up eRelationship

Systems for License Management on page 2-11.
Note: While specifying licensing details for the eRelationship system, type the virtual
IP address of the cluster in the License Server box. Also, select the name of the
redundant production license file from the License File drop-down list.
.....
Using an Emergency License File
Using an Emergency License File

If you replace the license server owing to a hardware malfunction or other problems, set
up another license server computer and request for a new production license file. Contact
Pivotal Global Technical Support for an emergency license file that you can use in the
interim. To request for an emergency license file, use the procedure detailed in
Requesting for a Production License File on page 2-9. Also state the reason why you
require an emergency license file.
To use the emergency license file
1 Set up the new license server computer.

For more information about setting up the license server computer, see Setting up the
License Server on page 2-5. It is recommended that you use the NetBIOS name of
the old license server computer for the new license server computer. This will ensure
minimal impact on connecting eRelationship systems.
2 Configure the license server.
Copy the emergency license file to a folder on the license server. Use the
WlmAdmin tool to add the emergency license file to the license server.
For more information about configuring the license server, see Configuring the
License Server on page 2-10.
3 Connect all eRelationship systems.
a) On the administrative computer, click Start, point to Programs, point to
Pivotal, then click eRelationship Enterprise Manager.
b) In the Pivotal eRelationship Enterprise Manager window, expand a server
under Data Synchronization and select the eRelationship system.
c) Right-click the selected eRelationship system and then click Connect.
The eRelationship system is connected.
Ensure to specify licensing details for the eRelationship system if you have:
• Changed the NetBIOS name of the license server computer
• Used a different IP address for the license server computer
For more information about specifying licensing details for an eRelationship system, see
Specifying Licensing Details on page 2-11.
Note: It is recommended that you do not assign or unassign licenses when an

emergency license file is specified as the license file for an eRelationship system. Do
not configure and send new mobile systems using an emergency license file.
.....
Using the License File with Additional Licenses 2
Using the License File with Additional Licenses

If you require additional licenses, contact Pivotal Global Technical Support. Use the
procedure detailed in Requesting for a Production License File on page 2-9 and request
for a production license file. Mention the number of additional licenses required,
including the number of mobile licenses.
To use the license file with additional licenses
1 Lock all users out of the eRelationship system:

c) Right-click the selected eRelationship system and then click System
Properties.
d) In the Properties dialog box, click Lock in the Locking System area.
Users are locked out of the eRelationship system.
2 Stop the Data Synchronization Manager (DSM).
c) Right-click the selected eRelationship system and then click Stop.
The DSM is stopped.
3 Stop the PLicenseManager application pool.
a) On the license server computer, click Start and then click Run.
b) Type inetmgr in the Run dialog box.
c) In the Internet Information Services (IIS) Manager window, expand the
name of the license server computer, and then expand Application Pools.
d) Right-click the PLicenseManager application pool and select Stop.
The PLicenseManager application pool is stopped.
4 Copy the additional license file to any folder on the license server.
5 Use the WlmAdmin tool and add the additional license file to the license server.
a) On the license server, click Start, point to Programs, point to Pivotal, and then
b) In the WlmAdmin window, expand the list under Subnet Servers.
c) Expand the list under the license server computer.
d) Right-click the name of the production license file, and select Remove Feature.
.....
Using the License File with Additional Licenses
e) Right-click the name of the license server computer and select Add Feature,
point to From a File, point to To Server and its File.
f) Browse to the location of the additional license file, select the additional license
file and click Open.
g) Click OK.
h) Click File in the main menu of the WlmAdmin window and then click Exit.
The additional license file is added to the license server. The feature name and
version of the additional license file will be the same as that of the production license
file removed in step d on page 2-25.
6 Start the PLicenseManager application pool.
d) Right-click the PLicenseManager application pool and select Start.
The PLicenseManager application pool is started.
7 Connect the eRelationship systems.
8 Unlock the eRelationship system:
c) Right-click the selected eRelationship system and then click System
Properties.
d) In the Properties dialog box, click Unlock in the Locking System area.
The eRelationship system is unlocked.
9 Start the DSM.
c) Right-click the selected eRelationship system and then click Start.
The DSM is started.
You can now assign the additional licenses.

.....
Uninstalling Sentinel RMS Development Kit Server 2
Uninstalling Sentinel RMS Development Kit

Server
Uninstall Sentinel RMS Development Kit Server from the Control Panel or use the
Pivotal r5.9 License Management CD-ROM.
To uninstall Sentinel RMS Development Kit Server
1 On the license server computer, log on as the administrator.

2 Uninstall Sentinel RMS Development Kit Server
Using the Pivotal r5.9 License Management CD-ROM:
a) Insert the Pivotal r5.9 License Management CD-ROM into the CD-ROM drive.
b) Browse the contents of the Pivotal r5.9 License Management CD-ROM and
open the License Server folder.
Using the Control Panel:
a) Click Start, point to Settings, and click Control Panel.
b) Double-click Add/Remove programs in the Control Panel window.
c) Select Sentinel RMS Development Kit Server from the list of currently
installed programs in the Add/Remove Programs dialog box.
d) Click Change and proceed to step 3.
3 In the Sentinel RMS Development Kit Server - InstallShield dialog box, click
Next.
4 Click the Remove option and then click Next.
5 Click Remove.
6 Click Finish when the process is complete.
Sentinel RMS Development Kit Server is uninstalled.
Uninstalling Pivotal License Manager

Uninstall Pivotal License Manager from the Control Panel or use the Pivotal r5.9
License Management CD-ROM.
To uninstall Pivotal License Manager
1 On the license server computer, log on as the administrator.

2 Uninstall Pivotal License Manager
Using the Pivotal r5.9 License Management CD-ROM:
a) Insert the Pivotal r5.9 License Management CD-ROM into the CD-ROM drive.
.....
Uninstalling Pivotal License Manager
b) Browse the contents of the Pivotal r5.9 License Management CD-ROM and
open the PLM folder.
c) Double-click the setup.exe file.
d) In the Pivotal License Manager r1.0 (v1.0.0100) - InstallShield or Pivotal
License Manager r1.0 - InstallShield dialog box, click Next.
e) Click the Remove option and then click Next.
f) Click Remove.
g) Click Finish when the process is complete.
From the Control Panel:
a) Click Start, point to Settings, and click Control Panel.
b) Double-click Add/Remove programs in the Control Panel window.
c) Select Pivotal License Manager r1.0 (v1.0.0100) or Pivotal License Manager
r1.0 - InstallShield from the list of currently installed programs in the Add/
Remove Programs dialog box.
d) Click Remove.
e) Click Yes in the confirmation box.
Pivotal License Manager is uninstalled.
.....
...................................
....
Troubleshooting
3
.....
3 Troubleshooting:
Do’s and Don’ts
Do’s and Don’ts

This section provides a brief list of do’s and don’ts for license management.
................................
Do’s
License Server Computer

• Use only Windows 2003 with IIS 6.0 as the license server computer.
• Ensure that the license server computer is on the same or trusted domain as the
• If the Primary Domain Controller for the domain is on a Windows 2003 Server,
force IIS to use Windows NT LAN Manager (NTLM) as your authentication
mechanism if you want to use Integrated Windows authentication only.
Alternatively, set the Service Principal Name for the HTTP service to the domain
user account that the PLicenseManager application pool is running under.
• Assign each license server computer a static IP address. If you do not assign a static
IP address, use only the NetBIOS name to resolve possible different IP addresses
allocated dynamically.
• Install both Sentinel RMS Development Kit Server and Pivotal License Manager on
the machine designated as the license server.
• Before installing Pivotal License Manager:
• Create a domain account with a user name and password to run Pivotal
License Manager. This user can be a service user that is running other
Pivotal services such as the PRAC and PRS users.
• Grant the user Log on as a batch job and Log on as a service security
policy rights. Assign these security policy rights either by adding the user to
the IIS_WPG group or by using the Local Security Settings window. If you
add the user to the IIS_WPG group, verify that the group is assigned the
required security policy rights.
• Verify if the following IIS Settings are set for the PLicenseManager Application
Pool:
• Disable all recycling properties
• Disable idle time-out
• Integrated Windows Authentication
• Identity is set to Configurable with user name specified in the format
domain\username
• Web Service Extensions set to Allowed Status for the Pivotal License
Manager
• In an Oracle environment, use a complete Oracle Client installation for the license
server computer. Ensure that the tnsnames.ora file has the Oracle instance name
used for the eRelationship deployment. On the license server computer, if you do not
.....
Troubleshooting:
Do’s and Don’ts 3
select the complete Oracle Client installation option, install the Oracle Client and the
OLE DB Provider for Oracle. For more information, see Oracle Environment on
page 2-6.
• Consider having more than one license server computer when there are a large
number of users or there are network limitations.
• Install separate license server computers when the master and satellite systems:
• are on different domains
• are on non-trusted domains
• cannot communicate to the same license server owing to network
restrictions.
• Copy the license files to any specific folder designated for the same.
• If you have not installed Pivotal SyncStream r5.9 Service Pack 1, add the production
license file and the mobile license file to the license server. For more information
about adding the license files, see Adding the License Files on page 2-11.
SQL Server
• If the SQL Server is in a different domain compared to the domain of the license
server computer, ensure that the ODBC connection defined contains the fully
qualified computer name of the SQL Server.
• For the Business Module and Enterprise Data databases, grant administrator rights to
the user assigning licenses.
Oracle Server
• If the Oracle Server is in a different domain compared to the domain of the license
server computer, ensure that the ODBC connection defined contains the NetBIOS
computer name of the Oracle Server.
.....
3 Troubleshooting:
Do’s and Don’ts
Pivotal eRelationship Enterprise Manager

• It is recommended that you install Pivotal SyncStream r5.9 Service Pack 1 before
deploying mobile systems.
• Before you specify the license file for a mobile system, and if you have not installed
the Pivotal SyncStream r5.9 Service Pack 1:
• Add the production license file and the mobile license file to the license
server.
• Ensure the mobile system is able to access the same network as the parent
eRelationship system and the license server computer.
• Verify if the mobile system is connected to the parent eRelationship
system.
• Assign licenses on the master system. Assigning licenses from the main system will
ensure that changes do not get rejected, and will prevent any delay in sending the
licensing information down to the satellites replicas.
• If the satellite and master system use different license server computers, ensure that
the license assigned to a user on a master system is synchronized to the satellite
system.
• Unassign all licenses before specifying a production license file when the license file
already specified for an eRelationship system is a non-production license file.
• Unassign all licenses before changing the license file for an eRelationship system.
However, you do not need to unassign licenses when you use an emergency license
or an additional license file.
• Use the Replicate feature to take a backup of the eRelationship databases if you
want to create copies of the eRelationship system that are not for backup or recovery
purposes and if a different license file will be used. The Replicate feature will not
store licensing information of the eRelationship system.
• Use the Backup feature if you want to retain the licensing information of the
eRelationship system for backup and restoration purposes.
.....
Troubleshooting:
Do’s and Don’ts 3
................................
Don’ts
• Do not use a virtual machine for the license server computer.
• Do not install the Sentinel RMS Development Kit Server and the Pivotal License
Manager on a Windows Domain Controller.
• Do not lock down the C:\ drive of the license server computer. Sentinel RMS
Development Kit Server can be installed only on the C:\ drive.
• Do not start synchronization without assigning a license to the DSM user and also
specifying the:
• e-mail address of the DSM user
• name of the HTTP server.
• Do not create a license server pool with an even number (2, 4, 6, and so on) of
license server computers. A license server pool must have an odd number (3, 5, 7,
and so on) of license server computers.
• When assigning licenses to a group, do not assign more licenses than the number of
available licenses or the operation will fail.
• Do not specify a non-production license file for an eRelationship system when the
license file already specified is a production license file.
• Do not forget to import the licensing.rtr when you perform an upgrade to
Pivotal Lifecycle Engine r5.9. For more information, see the Pivotal Lifecycle
Engine r5.9 Upgrade and Migration Guide.
.....
3 Troubleshooting:
Frequently Asked Questions
Frequently Asked Questions

This section provides answers to a few frequently asked questions.
Should I have a license server for every eRelationship system?
No. A license server can service more than one eRelationship system. Add the license
files to the license server. Also use Pivotal eRelationship Enterprise Manager and specify
the name of the license server computer and the license file for each eRelationship
system.
For more information about configuring the license server, see Configuring the License
Server on page 2-10.
For more information about specifying the name of the license server computer and the
license file for each eRelationship system, see Setting up eRelationship Systems for
License Management on page 2-23.
Must I use a production license file for a Production System?
If you have a Production System, ensure to use a production license file. To request for a
production license file, see Requesting for a Production License File on page 2-9.
When will the out-of-the-box, non-production license files provided on the Pivotal r5.9 License
Management CD-ROM expire?
The out-of-the-box license files provided on the Pivotal r5.9 License Management
CD-ROM will expire on 31 December, 2006. For more information about the
out-of-the-box license files, see Out-of-the-box License Files on page 1-3. For more
information about obtaining new non-production license files, see Appendix A,
Non-Production License Files.
What must I do to obtain new non-production license files?
You can download new non-production license files from the Pivotal Customer and
Partner Portals. For more information, see Obtaining New Non-Production License Files
on page 4-2.
Can I use a demo, non-production license file for more than one eRelationship system?
Yes, you can use a non-production license file for more than one eRelationship system.
However, ensure to use a production license file for a Production System.
.....
Troubleshooting:
Frequently Asked Questions 3
When is it advisable to have more than one license server computer?
It is advisable to have a separate license server for each master or satellite system when
the master and satellite systems:
• are on different domains
• are on non-trusted domains
• cannot communicate to the same license server owing to network restrictions.
I generated the locking code for a license server computer and requested for a production license file. Can
I add the production license file to a different license server computer?
No, you cannot add the production license file to a different license server computer. The
production license file is based on the locking code that is specific to the Ethernet address
and NetBIOS name of the license server computer. If you change the NetBIOS name or
use another license server computer, generate the locking code again and request for a
new production license file. For more information about generating the locking code, see
Generating the Locking Code for the License Server Computer on page 2-8. For more
information about requesting for a production license file, see Requesting for a
Production License File on page 2-9.
How many license server computers comprise a license server pool?
A license server pool must consist of an odd number of license server computers. For
example, the number of license server computers must be 3, 5, 7, and so on.
Can the license server computer be hosted on a virtual machine?
No, the license server computer must not be hosted on a virtual machine.
Can I install Sentinel RMS Development Kit Server on a D:\ drive?
No. You can install Sentinel RMS Development Kit Server only on a C:\ drive.
Do I need to reassign licenses when I use a license file with additional licenses?
No, you do not need to reassign licenses when using the additional license file. See Using
the License File with Additional Licenses on page 2-25.
.....
3 Troubleshooting:
Errors
Errors
This section details a few of the common errors that you might encounter for license
management.
Assigned License Icon Is Not Displayed

Possible Cause The import of the licensing.rtr was not successful during an upgrade to Pivotal
Lifecycle Engine r5.9.
Resolution Import the licensing.rtr. For more information, see the Pivotal Lifecycle Engine r5.9
Upgrade and Migration Guide.
HTTP Status 401

Possible Causes • In the URL, you typed an IP address instead of the NetBIOS name of the license
server computer.
• The Service Principal Name or the Windows NT LAN Manager (NTLM), were not
set or specified.
Resolution • In the URL, type the NetBIOS name of the license server computer.
Specify either the Service Principal Name or NTLM. For more information about
specifying the Service Principal Name, see To specify the Service Principal Name on
page 3-8.
To specify the Service Principal Name
Obtain the Setspn.exe file from Microsoft Corporation. Copy the Setspn.exe file to a
folder on the Primary Domain Control computer. The Microsoft Windows Server 2003
version of the Setspn.exe command-line tool is also available in the Windows Server
2003 Support Tools that are included on the Microsoft Windows Server 2003 CD-ROM.
To use Setspn.exe
1 On the Primary Domain Control computer, open a command prompt window.

Change directory to the folder with the Setspn.exe.
2 At the command-prompt, type the following command and press ENTER.
setspn.exe -a http/<netbios machine name> DomainName\UserName
where:
<netbios machine name>
At the command-prompt, type the following command and press ENTER.
setspn.exe -a http/<fully qualified domain name>
DomainName\UserName
where:
<fully qualified domain name> is the full name of the license server.
.....
Troubleshooting:
Errors 3
To obtain the full computer name, right-click My Computer on the Desktop and
then select Properties. Click the Network Identification tab in the System
Properties dialog box. The Full computer name is displayed. For example, if the
machine name is picmac, and the domain is corporate.pivotal.local, type the
fully qualified domain name as picmac.corporate.pivotal.local.
The name of the license server is specified.
If you have installed Pivotal r5.9 products on the same computer as the license
server, or IIS is not set to use NTLM, you could continue to obtain repeated prompts
for user name and password, or receive a HTTP 401 error when trying to test the
installation of Pivotal License Manager. For more information about specifying
NTLM, see To specify NTLM on page 3-10.
HTTP Status 404

Possible Causes • The Default Web site is stopped.
• The license server computer is not accessible.
Resolution • Restart the Default Web site.

• On the license server computer, grant the user Log on as a batch job and Log on as
a service security policy rights. Assign these security policy rights either by adding
the user to the IIS_WPG group or by using the Local Security Settings window. If
you add the user to the IIS_WPG group, verify that the group is assigned the
• Ensure that the license server computer is available on the network.
HTTP Status 500 <all ranges>

Possible Causes • The Plicense Manager Application pool is not started.
• The user account set to run Pivotal License Manager is not granted the Logon as a
batch job security policy right, or has not been added to the IIS_WPG group.
Resolution • Start the Plicense Manager Application pool.

Hr = 0xC00C0240
Possible Causes • A time-out has occurred.
• The license server computer is locked.
• Pivotal License Management and Sentinel RMS Development Kit Server is not
installed properly.
.....
3 Troubleshooting:
Errors
Resolution • Reinstall Pivotal License Management and Sentinel RMS Development Kit Server.
• Restart the license server computer.
Repeated Prompts for Authorization

Possible Cause If Internet Information Services (IIS) has not been set to use NTLM, you could
continue to obtain repeated prompts for user name and password, or receive a HTTP
401 error when trying to test the installation of Pivotal License Manager. For more
information about specifying NTLM, see To specify NTLM.
Resolution To specify NTLM
1 Open a Command Prompt window, and change directory to the

C:\Inetpub\Adminscripts or the equivalent folder for the PLicenseManager
virtual directory.
2 Type the following command and press ENTER:
cscript adsutil.vbs set w3svc/NTAuthenticationProviders "NTLM"
To verify if you have specified the setting correctly, type the following at the
command prompt and press ENTER:
cscript adsutil.vbs get w3svc/NTAuthenticationProviders
The text NTAuthenticationProviders : <STRING> "NTLM" is displayed if you have

correctly specified the NTLM setting.
Service Unavailable Error

Possible Causes • The PLicenseManager application pool is not started.
• The user account used to install and run Pivotal License Manager:
• has not been added to the IIS_WPG group.
• is not granted Logon as Batch and Logon as Service security policy rights.
Resolution • Add the user to the IIS_WPG group.

• Grant the user Logon as Batch and Logon as Service security policy rights if the
IIS_WPG group is not already granted the same security policy rights.
• Ensure that the PLicenseManager application pool is started.
Test for Pivotal License Management Installation

Returns a Service Unavailable Error
Possible Cause The user account set to run Pivotal License Manager is not granted the Logon as a batch
job or Log on as a service security policy rights, or has not been added to the IIS_WPG
group.
.....
Troubleshooting:
Errors 3
Resolution • Start the Plicense Manager Application pool.
Unable to Connect to the License Server

Possible Causes • Network problems.
• Insufficient network privileges.
• Firewall restrictions.
• The PLicenseManager site is not added to the list of trusted sites in Internet
Explorer.
Resolution • Resolve network problems and grant sufficient privileges to the user logged on to the
license server.
• Define an exception to the license server computer in the firewall settings.
• Add the PLicenseManager site to the list of trusted sites in Internet Explorer.
Unable to Start the Mobile DSM

Possible Causes • The user is not assigned a valid mobile license.
• The installation of Pivotal SyncStream r5.9 Service Pack 1 failed to install the
mobile license file on the mobile computer, or the mobile license file is corrupted.
• If Pivotal SyncStream r5.9 Service Pack 1 has not been installed, the mobile license
may not have been installed on the mobile computer.
Resolution • Assign the user a valid mobile license. For more information about assigning
licenses, see Assigning Licenses on page 2-16.
• Install Pivotal SyncStream r5.9 Service Pack 1 on the mobile computer.
Install the mobile license on the mobile computer only if you have chosen not to apply
the Pivotal Lifecycle Engine r5. 9 related service packs. For more information about
installing the mobile license, To specify licensing details for a mobile system on page
2-13.
Unable to Start Synchronization

Possible Cause The most common cause for being unable to start synchronization that is related to
licensing is that the DSM user has not been assigned a license or has not been assigned a
valid e-mail address and HTTP server name has not been specified.
Resolution Assign a valid license and specify a valid e-mail address and the HTTP server name for
the DSM user.
.....
3 Troubleshooting:
Errors
Unable to Unassign a Mobile License

Possible Cause Synchronization has not been stopped for the mobile user.
Resolution Stop synchronization for the mobile user and then unassign the mobile license.
Unable to Unassign a Satellite License

Possible Cause Synchronization has not been stopped for the satellite user.
Resolution • Stop synchronization for the satellite user before unassigning the license.
• Ensure that there are no network problems between the license server computer and
the master and satellite systems.
................................
Error Messages Displayed
DSM cannot connect to the system. Check the

relation.err file for errors
Possible Causes • You have not specified the DSM user.
• The DSM user does not have administrator rights to the eRelationship databases.
• The FilePath is not specified or is incorrect.
• If an ANM Server is specified, the DSM may be unable to connect to the ANM
Server.
Resolution • Assign a DSM user.

• Assign a valid e-mail address for the DSM user.
• Grant the DSM user administrator rights to the eRelationship databases.
• Specify the FilePath.
• Verify the Distributed COM User group identities for the DSM and ANM servers.
• Verify if the accounts set to run the DSM and ANM servers have enough rights to
run the servers.
• Ensure the ANM server computer can be located on the network and has the Pivotal
ANM service installed.
The [SetProduction] call to the License Server

failed: ADO Connection Exception Frame
Possible Cause The user account set to run the Pivotal License Manager does not have sufficient rights to
access the Business Module and Enterprise Data databases.
Resolution Grant the user account write access to the Business Module and Enterprise Data
databases.
.....
Troubleshooting:
Errors 3
The [SetProduction] call to the License Server

failed (2147483647) ADO Connection Exception
Frame
Possible Causes • You have attempted to assign the licenses after an upgrade from Pivotal SyncStream
r5.7 to Pivotal SyncStream r5.9 SyncStream, while Pivotal Applications/CMS
remains at r5.7.
• COM registration problems on the license server machine for the MDAC
components or Oracle client components.
Resolution Import the licensing.rtr. For more information, see the Pivotal Lifecycle Engine r5.9
Upgrade and Migration Guide.
The [GetFeatures] call to the License Server

failed:(-2147024809) Cannot open
ServerXMLHTTP object: Hr = 0x80070057
Possible Cause Registration problems of MSXML4
Resolution You may not have used the To Server and its File option in the WlmAdmin tool to add
the license file.
To add license files
1 On the license server, click Start, point to Programs, point to Pivotal, and then
3 Right-click the name of the license server computer, select Add Feature, point to
From a File, and then select To Server and its File.
4 Browse to the location of the license file and click Open.
computer name. Repeat steps 1 to 4 for each license file.

failed: (1610612737) Cannot connect to Server:
Hr = 0x80070005
Possible Causes • The Internet Explorer Enhanced Security Configuration Windows Component is
installed and enabled.
• Firewall restrictions.
Resolution • Add the PLicenseManager site to the list of trusted sites in Internet Explorer.
• Do not specify any firewall setting restriction for the license server computer.
• Remove the Internet Explorer Enhanced Security Configuration Windows
Component.
.....
3 Troubleshooting:
Errors
To remove the Internet Explorer Enhanced Security Configuration

Windows Component
1 Click Start, click Settings, and then select Control Panel.

2 In the Control Panel window, click Add or Remove Programs.
3 In the Add or Remove Programs dialog box, click Add/Remove Windows
Components.
4 In the Windows Components Wizard, clear the Internet Explorer Enhanced
Security Configuration check box.
5 Click Next.
6 Click Finish.
The Internet Explorer Enhanced Security Configuration Windows Component is
removed.

failed: (1610612735) Unable to connect to Pivotal
License Manager HTTP Error: Status = 401
Possible Causes • IIS is not set to use NTLM.
• Pivotal r5.9 products are installed on the same computer as the license server.
Resolution Specify NTLM. For more information, see To specify NTLM on page 3-10.
The [InstallMobileLicense] call to the local

library failed:(18) License Server:Feature not
available: Access Denied:0x12
Possible Causes The Pivotal.Demo.Mobile license file was not added to the license server computer.
Resolution In addition to adding the Pivotal.Demo file, also add the Pivotal.Demo.Mobile
license file to the license server computer. For more information about adding license
files, see Adding the License Files on page 2-11.
username - The [AssignLicense] call to the

License Server Failed: (1879048196) The user
has already assigned a license!
Possible Cause This error may occur when two eRelationship systems using the same non-production
license file have duplicate GUIDs in the DatabaseId or MasterSourceDatabaseId flag in
the RSys_System_Flags table of the eRelationship system's Enterprise Data database.
This issue will not occur if the license file used is a production license file for a
Production System.
Resolution New GUIDs must be generated. Only the MasterSourceDatabase ID must be changed.
.....
Troubleshooting:
Errors 3
For Offline and Production systems, the GUIDs of the Enterprise Data database must be
changed.
To change the GUIDs of an Enterprise Data database

and then click eRelationship Enterprise Manager.
expand the appropriate server listed under Data Synchronization, and then select
the eRelationship system.
3 Right-click the eRelationship system name and select System Properties.
4 Right click the system name and select Replicate To File.
5 Select Save Enterprise Data, specify the desired output file and click Save.
6 After the replication is complete, right click the system name and select Restore
System.
7 Select Restore Enterprise Data, specify the file just created in step 6 and click
Restore.
8 If necessary, restart synchronization.
In the case of a Customization System, it is necessary to change the GUIDs of a Business

Module (which is the Enterprise Data of a Customization system). Manually change the
GUIDs in the Business Module database.
To change the GUIDs of a Business Module database
1 Click Start, point to Programs and then click Microsoft Visual Studio.
2 Select Create GUID from the Tools menu.
3 Choose Registry Format. A new GUID is generated.
4 Ensure that eRelationship Enterprise Manager is not connected to the eRelationship
system.
5 Stop msync.exe.
6 Use the following SQL to update the Database ID value:
USE BM
Update RSys_System_Flags
Set Rn_Value = 'newGuid'
where Rn_Flag = 'MasterSourceDatabaseId'
Substitute the new GUID created in Visual Studio (minus the curly braces) for newGuid
and the name of the Business Module database for Business Module.
7 Generate a second new GUID in Visual Studio.
.....
3 Troubleshooting:
Errors
8 Use the following SQL to update the MasterSourceDatabase ID value:

USE BM
Update RSys_System_Flags
Set Rn_Value = 'newGuid'
Where Rn_Flag = 'MasterSourceDatabaseId'
9 Substitute the second GUID created in Visual Studio (minus the curly braces) for the
new GUID and the name of the Business Module database for Business Module.
You are trying to assign more licenses (1) than

the number of licenses available on the license
server (0)
Possible Causes • The license server computer was specified for the eRelationship system but Pivotal
eRelationship Enterprise Manager failed to retrieve the licensing information. 0 is
also displayed in the Total Licenses, Available licenses, Total Mobile Licenses
and Available Mobile Licenses boxes in the Users pane of the Pivotal
eRelationship Enterprise Manager window.
• Network connectivity problems.
• IIS settings not verified.
Resolution • Resolve network connectivity problems.

• Verify settings for the license server computer. For more information, see Do’s on
page 3-2 and Don’ts on page 3-5.
................................
Pivotal License Manager Log Errors
This section documents a few of the errors that are logged to the Pivotal License
Manager log file. The log file is located in the C:\Program
Files\Pivotal\SyncStream\Logs folder.
NativeError = 11 (or 17)
SQLMessage = 08001
Possible Causes • The SQL Server was shut down.
• There is no network connection to the SQL Server.
Resolution • Start the SQL Server.

• Restart the Sentinel RMS Development Kit Server License Manager service.
.....
Troubleshooting:
Errors 3
hr = 0x70000002 [The user has no license

assigned. Please ask your administrator to
assign a license.]
Possible Causes • This may happen because of sharing non-production license files between
eRelationship systems with the same MasterSourceDatabase IDs, even though you
assigned a license for the user.
• Similar GUIDs exist for both the eRelationship systems.
Resolution Ensure to assign different MasterSourceDatabase IDs.
Note: You need to change the GUID only for eRelationship systems that use
non-production license files. Ensure to change the GUID only once. Also make sure
you change the GUID before you perform any licensing settings or assignments.
hr = 0x70000004 [The user has already assigned

a license!]
Possible Causes • This may happen if two or more eRelationship systems share the same license file
and they have the same MasterSourceDatabase ID.
• A synchronizing system has different license servers for the main and the satellite
systems. You may see this message on the license servers for either the satellite or
main systems. This cause does not require any resolution.
• Similar GUIDs exist for both the eRelationship systems.
Resolution Ensure to assign different MasterSourceDatabase IDs.
hr = 0x7000000C [SAFENET::Cannot initialize

the VLS library]
Possible Cause The mergemodule containing the files required for the Safenet client library were not
installed or the installation failed.
Resolution Check the following location: C:\Program Files\Common Files\Pivotal

Shared\SentinelLM. If the files do not exist or are not the right version (8.0.4) re-install
Pivotal License Manager.
hr = 0x70000015 [The automatic request to

assign licenses for all users failed. Contact your
administrator.]
Possible Causes • The failover mechanism failed to re-assign licenses for all users at start up.
• Sentinel RMS Development Kit Server License Manager service may be stopped.
• The license file has not been added to the license server.
.....
3 Troubleshooting:
Errors
Resolution • Start the Sentinel RMS Development Kit Server License Manager service.
• Use the WlmAdmin tool and add license files to the license server. For more
information see Adding the License Files on page 2-11.
hr = 0x7000001F [The Pivotal Key sent in request

does not match the License File.]
Possible Causes • There is a mismatch between information in the current license file and the
• The license file was changed without first unassigning licenses for users and then
setting the new license file for the current eRelationship system.
• A GUID change occurred after some licenses were assigned.
Resolution • Stop synchronization and unassign licenses for all users. Specify the new license file
for the current eRelationship system. See Using the License File with Additional
Licenses on page 2-25.
• All licensing information must be cleared from the eRelationship system. Contact
Pivotal Global Technical Support for more information.
hr = 0x70000022 [The Production Key has an

invalid format.]
Possible Cause Information in the RSys_System_Flags table may have been inadvertently changed .
Resolution Specify the license file for the eRelationship system again. For more information, see
Specifying Licensing Details on page 2-11.
Safenet error = 0xC8001006

Possible Cause All license codes are in use. You require a license file with a larger number of license
codes.
Resolution • If you are using a shared non-production, demo license file between the
eRelationship systems, acquire a license file with larger number of license codes or
unassign more licenses from one of the eRelationship systems.
• Contact Pivotal Global Technical Support for a license file with a larger number of
license codes.
Safenet error = 0xC8001008

Possible Cause Unable to contact the license server computer.
Resolution Ensure that the license server computer is functioning and connected to the network.
.....
Troubleshooting:
Errors 3
Safenet error = 18
Possible Cause Unable to find the requested license file.
Resolution • Verify if the correct license file is added to the license server computer.
• Restart the license server computer.
Safenet error = 88
Possible Cause An attempt to install a mobile license from a terminal server session was made.
Resolution Do not install the mobile license from a terminal server session.
.....
...................................
....
Non-Production License Files
A
.....
Dec 12 2006 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference A-1
A Non-Production License Files:
Overview
Overview
The out-of-the-box license files for non-production systems provided on the Pivotal r5.9
License Management CD-ROM expire on December 31, 2006. For more information
about the out-of-the-box license files for non-production systems provided on the Pivotal
r5.9 License Management CD-ROM, see Out-of-the-box License Files on page 1-3.
This appendix provides information about obtaining and using the new non-production
license files.
Obtaining New Non-Production License Files

Download new non-production license files from the Pivotal Customer or Partner
Portals.
To obtain the new non-production license files
1 Log on to the Pivotal Customer or Partner Portals at:

http://login.pivotal.com.
2 Click Product Downloads, and then click License Keys.

3 Download the required non-production license files.
Note: The non-production license files downloaded from the Pivotal Customer and
Partner Portals will expire within 12 months from the date of download.
The following section details how to use the downloaded non-production license files.
Using the Downloaded Non-Production License

Files
Follow the procedure in this section to remove the reference to the out-of-the-box license
file and add the downloaded non-production license files to the license server computer.
Note: For an eRelationship system, if for example, you choose to replace the
out-of-the-box Pivotal.Dev license file with the downloaded
Pivotal.Dev.Offline license file, ensure to unassign licenses for all users
before following the procedures in this section.
.....
A-2 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference Dec 12 2006
Non-Production License Files:
Using the Downloaded Non-Production License Files A
To use the downloaded non-production license files
1 Disconnect the eRelationship system that currently uses the out-of-the-box license
file.
b) In the Pivotal eRelationship Enterprise Manager window, expand the server
c) Right-click the selected eRelationship system and then click Disconnect.
The eRelationship system is disconnected.
2 Stop the PLicenseManager application pool.
d) Right-click the PLicenseManager application pool and select Stop.
The PLicenseManager application pool is stopped.
3 Stop all Pivotal services.
a) Click Start, point to Settings, and then click Control Panel.
b) In the Control Panel window, double-click Administrative Tools, and then
select Services.
c) In the Services window, select the Pivotal service such as the Pivotal Active
Notification Manager service, right-click the service and then select Stop.
The Pivotal service is stopped.
4 Close all Pivotal client applications.
5 Use the WlmAdmin utility to remove the reference to the out-of-the-box license file
from the license server.
a) On the license server computer, click Start, point to Programs, point to
Pivotal, and then select License Server.
c) Expand the list under the license server computer.
d) Right-click the name of the production license file, and select Remove Feature.
The reference to the out-of-the-box license file is removed from the license server.
This does not delete the file. After removing the reference to the file using the
WlmAdmin tool, open Windows Explorer and browse to the location of the
out-of-the-box license file and delete it.
6 Copy the new downloaded license file to the same location on the license server
computer as the old out-of-the-box license file.
7 Use the WlmAdmin utility to add the downloaded license file to the license server.
a) On the license server computer, click Start, point to Programs, point to
Pivotal, and then select License Server.
.....
Dec 12 2006 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference A-3
A Non-Production License Files:
Using the Downloaded Non-Production License Files

c) Right-click the name of the license server computer, select Add Feature, point
to From a File, and then select To Server and its File.
d) Browse to the location of the downloaded license file and click Open.
computer name.
8 Restart the PLicense Manager application pool.
d) Right-click the PLicenseManager application pool and select Start.
The PLicenseManager application pool is started.
9 Reconnect the eRelationship system.
10 Start all Pivotal Services.
a) Click Start, point to Settings, and then click Control Panel.
b) In the Control Panel window, double-click Administrative Tools, and then
select Services.
c) In the Services window, select the Pivotal service such as the Pivotal Active
Notification Manager service, right-click and then select Start.
The Pivotal service is started.
11 Start all Pivotal client applications.
12 If you have a synchronization environment, start the Pivotal Data Synchronization
Manager.
a) Right-click the selected eRelationship system and click Start.
The Pivotal Data Synchronization Manager is started.
The eRelationship system uses the downloaded license file.

.....
A-4 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference Dec 12 2006
...................................
....
Production License File Request:
B
Sample Format
.....
Dec 12 2006 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference B-1
B Production License File Request: Sample Format:

Request for a production license file for a Production System. For more information, see
Requesting for a Production License File on page 2-9.
................................
Sample Format
To request for a production license file, use the sample format provided in Table B-1.
Listing B-1 Production License File Request: Sample Format
Locking code for license server on the master system

Locking Code:
LAN licenses for license server on master system:<>

Mobile licenses for license server on master system:<>
Locking code for license server1 on Satellite System1

Locking Code:
LAN licenses for license server1 on Satellite System1:<>

Mobile licenses for license server1 on Satellite System1:<>
Locking code for license server1 on Satellite System2

Locking Code:
LAN licenses for license server1 on Satellite system2:<>

Mobile licenses for license server1 on Satellite system2:<>
Redundancy required:
Number of redundant servers:<>
Locking code for redundant license server1:
Locking Code: xx-xxxxx
.....
B-2 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference Dec 12 2006
Index
...................................
....
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
expiry, license files 4-2
A
add license files 2-11 F
assign licenses 2-13, 2-16, 3-4
filtering mode 2-20
Available Licenses box 2-17
Available Mobile Licenses box 2-17 I
IIS_WPG group 3-2
C Install Mobile License 2-14
copy license files 2-10
E L
leader license server 2-22
error
License column 2-17
ADO Connection Exception Frame 3-12, 3-13
License File box 2-14
assigned license icon is not displayed 3-8
Cannot connect to Server license files
Hr = 0x80070005 3-13 adding 2-11, 2-24, 2-25
Cannot initialize the VLS library 3-17 additional licenses 2-25
Cannot open ServerXMLHTTP object copying 2-10
Hr = 0x80070057 3-13 downloaded 4-2
DSM cannot connect to the system 3-12 downloaded, obtaining 4-2
Hr = 0xC00C0240 3-9 emergency 1-2, 2-24
HTTP Status 401 3-8 expiry 4-2
HTTP Status 404 3-9 non-production 4-2
HTTP Status 500 3-9 out-of-the-box 1-3
License Server Feature not available 3-14 out-of-the-box, expiry 4-2
repeated prompts for authorization 3-10 production, requesting for 2-9
Safenet error = 0xC8001006 3-18 redundant production, requesting for 2-21
Safenet error = 0xC8001008 3-18 license keys 4-2
Safenet error = 18 3-19 license management
Safenet error = 88 3-19 with redundant servers 2-19
service unavailable 3-10 without redundant servers 2-5
The automatic request to assign licenses for all license server
users failed 3-17 deployment 1-5
The Pivotal Key sent in request does not match setting up 2-5, 2-21
the License File 3-18 License Server box 2-12, 2-14
The Production Key has an invalid format 3-18 licenses
The user has already assigned a license 3-14, assigning 2-16
3-17 available 2-17
Unable to connect to Pivotal License Manager available mobile 2-17
HTTP Error unassigning 2-17, 2-18
Status = 401 3-14 licensing.rtr 3-5
unable to connect to the license server 3-11 locking code 2-8, 3-7
unable to start synchronization 3-11
unable to start the mobile DSM 3-11 M
unable to unassign a mobile license 3-12
mobile licenses 2-18
unable to unassign a satellite license 3-12
.....
Dec 12 2006 Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference i
Index A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
N T
NetBIOS 3-2 tnsnames.ora 3-2
non-production license files 4-2
U
P unassign licenses 2-17, 3-4, 4-2
Pivotal License Manager 2-6 Unicast 2-20
PLicense Manager virtual directory 2-14 user licenses
PLicenseManager user account 2-15 LAN or satellite, assigning 2-16
Primary Domain Controller 3-2 LAN or satellite, unassigning 2-17
production license file 1-3, 2-9 mobile, assigning 2-16
mobile, unassigning 2-18
R
redundant servers 2-19
V
request virtual machine 3-5
production license file, sample format 5-2
W
S Windows Domain Controller 3-5
Sentinel RMS Development Kit Server 2-5 Windows NT LAN Manager 3-8
Service Principal Name 3-8 WlmAdmin utility 2-11, 2-22, 4-3
Set License File 2-12 WrlfTool 2-22
.....
ii Pivotal License Manager r1.0 and r1.0 Service Pack 1 Reference Dec 12 2006

Pivotal - Reference r10 r10SP1 PLM

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pivotal - Reference r10 r10SP1 PLM

Uploaded by

Copyright:

Available Formats

...................................

For additional information, contact:

Copying the lservrlf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Documentation updates, product guides, technical support and

Contact Pivotal Global Technical Support at

Contact the Pivotal Education Services Group at

Send questions, comments or suggestions related to documentation to

License Management Terminology

Emergency license file

License server pool

A cluster of redundant license servers.

Users added to the Users table in eRelationship.

Table 1-1 Out-of-the-box license files

License File Type of eRelationship System and Environment

Pivotal.Customization Customization System in a production environment

Pivotal.Demo Demo System for demonstration purposes

Pivotal.Demo.Mobile Mobile Demo System for demonstration purposes

Pivotal.Dev.Custom Customization System in a development environment

Pivotal.Dev.Master Development Production System in a development

Pivotal.Dev.Offline Offline System in a development environment

Pivotal.Offline Offline System in a production environment

Table 1-2 System requirements for the license server

Component Requirements Comments

Processor speed 2 GHz Minimum recommended

RAM 512 MB Minimum recommended

1. 64-bit operating systems are not supported.

Depending on the deployment scenario, set up license servers with or without

Yes Redundant License Servers?

Generate the locking code

Request for the production license file

Specify the license server computer

Master/Satellite Mobile or Master/Satellite? Mobile

on the parent system

on the mobile computer

Figure 2-1 Setting up license management without redundant servers

Set up the redundant license server cluster

on each license server

Install Pivotal License Manager

Generate the locking code

Request for a redundant production license file

on the leader license server

on each license server

Set up the eRelationship system

Figure 2-2 Setting up license management with redundant servers

Setting Up License Management without

To set up license management without redundant servers

1 Set up the license server

Installing Sentinel RMS Development Kit Server

To install Sentinel RMS Development Kit Server

1 On the computer designated as the license server, log on as the administrator.

6 Accept the license agreement and click Next.

11 Click Finish when the installation is complete.

Sentinel RMS Development Kit Server is installed.

Installing Pivotal License Manager

Before installing Pivotal License Manager, do the following:

1 On the computer designated as the license server, log on as the administrator.

Pivotal License Manager is installed. The installation also creates a PLicenseManager

Specifying details of the Pivotal License Manager user account

To specify details of the Pivotal License Manager user account

To ensure that Pivotal License Manager is properly installed

2 At the command prompt, type echoid.exe.

It is not recommended to change the license server computer. If a different computer is

To request for a production license file

1 Log on to the Pivotal Global Technical Support Web site at: