Product licensing User Guide

version 1.5.1

el
ekt
robi
t.
com
 Product licensing User Guide

Elektrobit Automotive GmbH

Am Wolfsmantel 46
91058 Erlangen, Germany
Phone: +49 9131 7701 0
Fax: +49 9131 7701 6333
Email: [email protected]

Technical support

Support URL

https://www.elektrobit.com/support

Legal notice
Confidential and proprietary information

ALL RIGHTS RESERVED. No part of this publication may be copied in any form, by photocopy, microfilm,
retrieval system, or by any other means now known or hereafter invented without the prior written permission
of Elektrobit Automotive GmbH.

All brand names, trademarks and registered trademarks are property of their rightful owners and are used only
for description.
Copyright 2020, Elektrobit Automotive GmbH.

Page 2 of 87
 Product licensing User Guide

Table of Contents
Modification history ............................................................................................................................... 7

1. Typography and style conventions ......................................................................................... 9

2. Overview .................................................................................................................................. 11
2.1. Target groups ............................................................................................................................. 11
2.2. Maintenance license model ........................................................................................................ 11
2.3. License bundles ......................................................................................................................... 12
2.3.1. Single user or evaluation license ...................................................................................................... 12
2.3.2. Floating license ............................................................................................................................. 12
2.3.3. Dongled license ............................................................................................................................ 13
2.3.4. Hardware license .......................................................................................................................... 13

2.4. License file details ..................................................................................................................... 13

2.4.1. Reading the FlexNet Publisher license file ......................................................................................... 14
2.4.2. Reading the Hardware license file .................................................................................................... 15
2.4.3. Reading the legacy floating license file set ......................................................................................... 16
2.4.4. Reading the legacy dongle license file ............................................................................................... 17

2.5. License activation ...................................................................................................................... 18

2.5.1. General information on license activation ........................................................................................... 18
2.5.2. License Administrator user interface ................................................................................................. 18

3. Using the EB licensing portal ............................................................................................... 20

3.1. Overview .................................................................................................................................... 20
3.1.1. Login to the EB licensing portal ....................................................................................................... 20
3.1.2. Password lost ............................................................................................................................... 20

3.2. Profile administration ................................................................................................................. 21

3.3. Account administration .............................................................................................................. 21
3.3.1. Managing allocation accounts .......................................................................................................... 22
3.3.1.1. Creating an allocation account ...................................................................................................... 23
3.3.1.2. Adding an allocation account ........................................................................................................ 23
3.3.1.3. Adding allocation account members ............................................................................................... 24
3.3.1.4. Assigning permissions to account members ..................................................................................... 25
3.3.1.5. Switching to an allocation account ................................................................................................. 25
3.3.1.6. Verifying a transferred order .......................................................................................................... 26

3.4. License administration ............................................................................................................... 27

3.4.1. Searching licenses ........................................................................................................................ 27
3.4.2. Accessing your licenses ................................................................................................................. 28
3.4.3. Transferring licenses to an allocation account ..................................................................................... 30
3.4.4. Splitting licenses between allocation accounts .................................................................................... 31

4. The licensing project on EB Command ................................................................................ 34

Page 3 of 87
 Product licensing User Guide

5. Single user or evaluation licenses ........................................................................................ 35

5.1. Activating single user or evaluation licenses ............................................................................ 35
5.1.1. Installing the EB Client License Administrator tool ................................................................................ 36
5.1.1.1. Installing for Microsoft Windows ..................................................................................................... 36
5.1.1.2. Installing for Linux ....................................................................................................................... 37
5.1.2. Activating a single user or evaluation license online ............................................................................. 37
5.1.2.1. Activating on Microsoft Windows .................................................................................................... 37
5.1.2.2. Activating on Linux ...................................................................................................................... 38
5.1.3. Activating a single user or evaluation license offline ............................................................................. 39
5.1.3.1. Activating on Microsoft Windows .................................................................................................... 39
5.1.3.2. Activating on Linux ...................................................................................................................... 40

5.2. Returning a single user or evaluation license ........................................................................... 42

5.2.1. Returning a single user or evaluation license online ............................................................................. 42
5.2.1.1. Returning on Microsoft Windows .................................................................................................... 42
5.2.1.2. Returning on Linux ...................................................................................................................... 42
5.2.2. Returning a single user or evaluation license offline ............................................................................. 43
5.2.2.1. Returning on Microsoft Windows .................................................................................................... 43
5.2.2.2. Returning on Linux ...................................................................................................................... 44

5.3. Upgrading a single user or evaluation license .......................................................................... 46

5.3.1. Upgrading a single user or evaluation license online ............................................................................ 47
5.3.1.1. Upgrading on Microsoft Windows ................................................................................................... 47
5.3.1.2. Upgrading on Linux ..................................................................................................................... 47
5.3.2. Upgrading a single user or evaluation license offline ............................................................................ 48

5.4. Repairing a broken license ........................................................................................................ 48

5.4.1. Repair on Microsoft Windows .......................................................................................................... 49
5.4.2. Repair local liceses on Linux ........................................................................................................... 49

5.5. Removing an expired license .................................................................................................... 50

5.5.1. Removing on Microsoft Windows ...................................................................................................... 50
5.5.2. Removing on Linux ........................................................................................................................ 50

6. Floating licenses ..................................................................................................................... 52

6.1. Activating floating licenses ........................................................................................................ 52
6.1.1. Installing the EB Server License Administrator tool .............................................................................. 53
6.1.2. Activating a floating license online .................................................................................................... 54
6.1.3. Activating a floating license offline .................................................................................................... 55

6.2. Returning a floating license ....................................................................................................... 57

6.2.1. Returning a floating license online .................................................................................................... 57
6.2.2. Returning a floating license offline .................................................................................................... 57

6.3. Upgrading a floating license ...................................................................................................... 59

6.3.1. Upgrading floating license online ...................................................................................................... 60
6.3.2. Upgrading a floating license offline ................................................................................................... 60

6.4. Removing an expired floating licenses ...................................................................................... 61

Page 4 of 87
 Product licensing User Guide

6.5. Repairing a floating license ....................................................................................................... 61

6.6. Using floating licenses on a client machine .............................................................................. 62
6.6.1. Configuring a license server in client application .................................................................................. 62
6.6.2. Manual setup ............................................................................................................................... 63

7. Dongled licenses ..................................................................................................................... 64

7.1. Prerequisites when using dongled licenses .............................................................................. 64
7.2. Downloading license files from the Order History page ............................................................ 64
7.3. Retrieving dongle serial number and customer ID .................................................................... 66

8. Hardware licenses ................................................................................................................... 67

8.1. Downloading license files from the Search Licenses menu ....................................................... 67
8.2. Finding the EB hardware serial number .................................................................................... 69

9. Partner licenses for EB tresos Studio .................................................................................. 70

9.1. Overview .................................................................................................................................... 70
9.2. Background information ............................................................................................................ 70
9.2.1. Restrictions for partner licenses ....................................................................................................... 70
9.2.2. Restrictions for partner customers .................................................................................................... 70

9.3. Using partner licenses ............................................................................................................... 70

9.3.1. Using a partner license as a partner ................................................................................................. 70
9.3.2. Using a partner license as a partner customer .................................................................................... 71

9.4. Retrieving the provider-ID .......................................................................................................... 72

9.5. Use of the signature tool ........................................................................................................... 73
9.6. Software redistribution .............................................................................................................. 73

10. Legacy licenses .................................................................................................................... 74

10.1. Overview .................................................................................................................................. 74
10.2. Background information .......................................................................................................... 74
10.2.1. Legacy dongled licenses ............................................................................................................... 74
10.2.2. Legacy floating licenses ................................................................................................................ 74

10.3. Accessing your legacy licenses .............................................................................................. 74

10.3.1. Accessing legacy floating licenses .................................................................................................. 74
10.3.2. Accessing legacy dongled licenses ................................................................................................. 77

11. License server configuration ............................................................................................... 78

11.1. Overview .................................................................................................................................. 78
11.2. Transferring floating licenses from lmgrd to lmadmin ............................................................. 78
11.3. Login to the license server ...................................................................................................... 79
11.4. Importing a license file ............................................................................................................ 80

Page 5 of 87
 Product licensing User Guide

11.5. Verifying the license file import ............................................................................................... 81

11.6. Configuring the EB vendor daemon ......................................................................................... 82
11.7. Verifying the EB vendor daemon ............................................................................................. 84
11.8. Verifying your licenses ............................................................................................................. 85
11.9. Testing the license server with lmgrd command line utility ..................................................... 86

Page 6 of 87
 Product licensing User Guide
Modification history

Modification history
Version Description

1.5.1 Fixed version incompatibility of lmgrd.exe and lmutils, which resulted in an error when us-
ing lmgrd as license server or the commmand line tools installed in the x64 directory of the
license administrator.
1.5.0 Upgrade FlexNetPublisher V11.17.2 to V11.19.1.
Upgrade from Visual Studio 2017 to Visual Studio 2022
1.4.3 Upgrade FlexNetPublisher to V11.17.2.
Linux Client Administrator:
Local trusted storage install
Activation tool
Command line utilities
Documentation enhancements.
1.4.2 Fix for vendor daemon crash.
Flexera identified an issue in FNP 11.16 which causes the EB vendor daemon to crash. A
workaround has been integrated to the EB licensing toolkit.
1.4.1 lmflex.exe command line utility provides license source information:
from client trusted storage
from unserved license file
from server trusted storage including server name
from served license file including server name
Added license repair documentation.

Documentation enhancements.
1.4.0 Upgrade FlexNetPublisher V11.14.1.1 to V11.16.5.1.
Upgrade from Visual Studio 2015 (vc140) to Visual Studio 2017 (vc141).
1.3.0 Simplified Dongle License File handling.
64 bit License Activation Utilities.

Upgrade from Visual Studio 2010 (vc100) to Visual Studio 2015 (vc140)

Introduced FlexNet license-repair function

Deep link to related order in Elektrobit Customer Portal license notification email.

Delete expired licenses without return to FlexNet Operations Cloud via context menu.
Deleted Information about the 32 Bit Vendor Daemon.

Page 7 of 87
 Product licensing User Guide
Modification history

Version Description
Deleted chapter 11.2 and 11.2.1.

Renamed chapter 11.3.

Added chapter 11.9 "Testing the license server with lmgrd command line utility".

First version with Linux-Client support.

NOTE 32 bit License Activation Utility discontinued!

The latest version with 32 bit support is release 1.2.4!

1.2.4 Upgrade FlexNetPublisher V11.13.1.3 to V11.14.1.1.

Removed confusing ESD related menu options from the customer portal.

Added EB Command links to the customer portal.

Added license return/upgrade sections.

Added Maintenance license model description.

Added Order-Notification email description.

Added license file description.
1.2.2 Added legacy license chapter.
Updated license server chapter.
1.2.0 Display unique machine-ID in user interface.
Upgrade FlexNetPublisher V11.12.0.0 to V11.13.1.4.

Upgrade from Visual Studio 2008 SP1 (vc9) to Visual Studio 2010 (vc10)
1.1.0 Service release to resolve floating license server restart and reread license issue.

1.0.0 Initial version based on FlexNet Publisher V11.12.0.0

Page 8 of 87
 Product licensing User Guide
Chapter 1. Typography and style conventions

1. Typography and style conventions

NOTE Meta information about the editorial guidelines

The following examples contain meta information about this document and are not instruc-
tions on how to write.

The signal word WARNING indicates information that is vital for the success of the configuration.

WARNING Source and kind of problem

What can happen to the software?

What are the consequences of the problem?

How does the user avoid the problem?

The signal word NOTE indicates important information on a subject.

NOTE Important information

Gives important information on a subject

The signal word TIP provides helpful hints, tips and shortcuts.

TIP Helpful hints

Gives helpful hints

Throughout the documentation you find words and phrases that are displayed in bold, italic, or monospaced
font.

To find out what these conventions mean, see the following table.

All default text is written in Arial Regular font.

Font Description Example

Arial italics to emphasize new or important terms The basic building blocks of a configuration are
module configurations.
Arial boldface for GUI elements and keyboard keys 1. In the Project drop-down list box, select
Project_A.
2. Press the Enter key.
Monospaced font for user input, code, and file directo- The module calls the BswM_Dcm_Re-
(Courier) ries questSessionMode() function.

Page 9 of 87
 Product licensing User Guide
Chapter 1. Typography and style conventions

Font Description Example

For the project name, enter Project_Test.
Square brackets to denote optional parameters; for insertBefore [<opt>]
[] command syntax with optional para-
meters
Curly brackets {} to denote mandatory parameters; for insertBefore {<file>}
command syntax with mandatory pa-
rameters
Three dots … to indicate further parameters; for insertBefore [<opt>…]
command syntax with multiple para-
meters
A vertical bar | to indicate all available parameters; allowinvalidmarkup {on|off}
for command syntax in which you se-
lect one of the available parameters

Page 10 of 87
 Product licensing User Guide
Chapter 2. Overview

2. Overview
This document describes the steps which are required to activate a license with a FlexNet Operations On Cloud
(FNOC) activation code as well as the configuration steps required to use a file-based license in combination
with a dongle.

2.1. Target groups

The Product licensing user guide provides information for users who want to use a product license of Elektrobit
Automotive GmbH. The target group includes both first time users and experienced users of EB products.

The chapter 11, License server configuration is aimed at network administrators and server administrators. It
provides information on how to install a floating network license server.

2.2. Maintenance license model

Most EB software products are sold according a maintenance based license model. All licenses except leased-,
concept- and evaluation-licenses are perpetual. The maintenance period controls the access to newer product
releases. During a valid maintenance period, any new release of a software can be used with the same license.
Software versions which are released beyond the maintenance period can't be used. To use a release which
was created after the maintenance end date, a software maintenance renewal has to be purchased.

In figure 2.1, Maintenance Period, the following restrictions are shown:

Release 2.0 up to Release 3.1 can be used with the license that was purchased in 05/2015 which includes
on year maintenance (up to 04/2016).
Release 1.0 can't be used because a newer version was already available at the purchase date. If access
to earlier versions is required, EB sales back-office can assist.
Release 3.2 can't be used because the maintenance period has ended before Release 3.2 was available.

Page 11 of 87
 Product licensing User Guide
Chapter 2. Overview

Figure 2.1. Maintenance Period

2.3. License bundles

Depending on the product you have ordered, you receive one of the following licensing bundles:

2.3.1. Single user or evaluation license

Login credentials to the EB licensing portal via email notification
Single user license activation code via email notification and via EB licensing portal
EB Client License Administrator tool via EB Command delivery
For information about the setup of single user or evaluation licenses, see chapter 5, Single user or evaluation
licenses.

2.3.2. Floating license

Login credentials to the EB licensing portal via email notification
Floating license activation code via email notification and via EB licensing portal
EB Server License Administrator tool including the EB vendor daemon via EB Command delivery
FlexNet Publisher lmadmin license server installer via EB Command delivery
EB_SERVER_CONFIG.lic license file to configure the EB vendor daemon via EB Command delivery
For information about the setup of floating licenses, see chapter 6, Floating licenses

Page 12 of 87
 Product licensing User Guide
Chapter 2. Overview

2.3.3. Dongled license

Login credentials to the EB licensing portal via email notification
Hardware dongle
Dongle driver via EB Command delivery
License file from the EB Licensing Portal
Dongle serial number (see section 7.3, Retrieving dongle serial number and customer ID).
Only for legacy licenses:
License file via EB licensing portal (for more information, see chapter 10, Legacy licenses)
For information about the setup of dongled licenses, see chapter 7, Dongled licenses.

2.3.4. Hardware license

Login credentials to the EB licensing portal via email notification
License file via EB licensing portal.
The board ID and serial number can be found on your EB device (for more information, see section 8.2,
Finding the EB hardware serial number).
For information about the setup of hardware licenses, see chapter 8, Hardware licenses.

2.4. License file details

Below find more information about the internal structure of EB license files.

Page 13 of 87
 Product licensing User Guide
Chapter 2. Overview

2.4.1. Reading the FlexNet Publisher license file

FlexNet Publisher license files are used for dongle-based licenses and for COMPOSITE based licenses starting
with ACG7.3.

Figure 2.2. FlexNet Publisher license file

No. Description

1 With the Entitlement-ID the corresponding order can be found in the EB licensing portal order
history.
2 The date-based version feature of FlexNet Publisher is used to specify the maintenance end
date. In this example, the maintenance ends on Dec. 31, 2016.
3 A license file can contain numerous license features.
4 A license can be permanent (i.e. perpetual) or if it is an evaluation-, concept- or leased license,
a license end date can be specified.
5 The serial number of the WibuKey dongle is used as HOSTID. In case of using a native Flex-
era dongle, the HOSTID is specified as HOSTID=FLEXID=sn where sn specifies the Flexera
dongle serial number.
6 A node-locked license is uncounted. Multiple instances of an application can be used on the
machine where the corresponding dongle is connected. The license checkouts are not counted
(contrary to floating licenses).

Page 14 of 87
 Product licensing User Guide
Chapter 2. Overview

2.4.2. Reading the Hardware license file

Hardware license files are used for EB hardware devices like an EB 6100 or an EB 5200.

Figure 2.3. Hardware license file

No. Description

1 Device board ID (HostID), see also section 8.2, Finding the EB hardware serial number.
2 Device serial number, see also section 8.2, Finding the EB hardware serial number.
3 Entitlement name, find your entitlement in the order history in the EB licensing portal.
4 Multiple license features are included in one license file.
5 Each license feature has a subscription end date related to the maintenance period, see also
section 2.2, Maintenance license model.

Page 15 of 87
 Product licensing User Guide
Chapter 2. Overview

2.4.3. Reading the legacy floating license file set

For ACG4, ACG6 and up to ACG7.2 a combination of an EB proprietary license file for the client application
and a FlexNet Publisher license file for the license server is used.

Figure 2.4. License file for floating server

Figure 2.5. License file for client machines

No. Description

1 The COMPOSITE-ID of the server is calculated by the lmcomposite.exe command line utility. It
must be provided to EB before a license can be issued.
2 The license feature protecting the client license file.
3 Floating licenses are permanent (i.e. perpetual).
4 Number of available floating licenses.
5 License feature for unattended builds.
6 License feature which is requested by clients from the floating server.

Page 16 of 87
 Product licensing User Guide
Chapter 2. Overview

2.4.4. Reading the legacy dongle license file

For ACG4, ACG6 and up to ACG7.2 an EB proprietary license file syntax is used for node locked licenses.

Figure 2.6. Legacy node-locked (dongle) license file

No. Description

1 The user code (UC) contains the dongle number. In this case the dongle number is 219842
(without the leading D). The number is equal to the EB delivery number.
2 Maintenance end date, see also section 2.2, Maintenance license model.
3 List of license features (EB tresos Studio + ACG modules).

Page 17 of 87
 Product licensing User Guide
Chapter 2. Overview

2.5. License activation

2.5.1. General information on license activation
The license administrator tools communicate with the FlexNet Operations On Cloud license server and
transfer a license from the FlexNet Operations On Cloud license server to your server or client machine.
Activation-based licenses are managed by the FlexNet Operations On Cloud service.
A license is stored in a secured file on the customer's machine. This so called trusted storage is protected
against several manipulation attempts such as rollback of the machine's clock, backup and restore on
different machines, and usage in virtual environments.

Two different license activation tools are provided:

EB Server License Administrator (for floating licenses)
EB Client License Administrator (for single-user and evaluation licenses)

2.5.2. License Administrator user interface

Figure 2.7. License Administrator user interface

No. GUI item Type Description

1 Activate button Click for online license activation.

Page 18 of 87
 Product licensing User Guide
Chapter 2. Overview

No. GUI item Type Description

2 Return button Click for online license return.

3 Repair button Click for online license repair.
4 Upgrade button Click for online license upgrade.
5 Number of Licenses text box Enter the number of floating licenses you want to acti-
vate. For single-user licenses the number is always 1.
6 Activation Code text box Enter the activation code to activate a license or
choose a license from the list of already activated li-
censes to return the license.
7 Create Activation Request ... button Click to create an offline activation request file.
8 Create Return Request ... button Click to create an offline return request file.
9 Process Activation ... button Click to process offline activation or return response
files.
10 Status section The status of the activation process is displayed.
11 DNS Name section The machine DNS name is displayed.
12 Machine ID section The unique machine identifier is displayed.
13 Clear Log button Click to clear all messages shown in the status section.

Choose the appropriate activation tool depending on your license model in EB Command. For more information
on EB Command, see chapter 4, The licensing project on EB Command. For more information on the activation
tools, see chapter 5, Single user or evaluation licenses and chapter 6, Floating licenses.

Page 19 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

3. Using the EB licensing portal

3.1. Overview
Licenses of Elektrobit Automotive GmbH (EB) products are managed by an online software delivery service
that helps you manage and stay current with your EB licenses.

The EB licensing portal provides you with the following features:

Profile administration, see section 3.2, Profile administration
Account administration, see section 3.3, Account administration
License administration, see section 3.4, License administration
Email notifications when your account or your order is updated

3.1.1. Login to the EB licensing portal

Your login credentials are provided by email. You receive a login-ID which consists of your email address and
a token to set your password.

To log in, use your email address as login-ID and your customized password on the EB licensing portal:
https://elektrobit.flexnetoperations.com

3.1.2. Password lost

If you forgot your password, use the Password Finder to request a new password:
https://elektrobit.flexnetoperations.com/control/elkb/password

Figure 3.1. EB licensing portal login

Page 20 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

3.2. Profile administration

On the Your Profile page you can perform the following actions:
Configure your account member address.
Configure your permissions if you have the permission Admin Privileges. For more information on permis-
sions, see section 3.3.1.4, Assigning permissions to account members.

Figure 3.2. Your Profile page

3.3. Account administration

Your customer account is provided by EB. At least one account administration member is set up in your account
per default. Additional account members can be added by EB or any other account member with account
administrative privileges.

In larger companies, licenses are normally associated to specific departments or subsidiaries. Licenses for
partner customers may also be associated to a specific customer account. Use allocation accounts for these
use cases.

Page 21 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

3.3.1. Managing allocation accounts

STEP Managing allocation accounts

Prerequisite:

■ The permission Account Administration must be activated. For more information,

see section 3.2, Profile administration.

Step 1
Log in to the EB licensing portal, see section 3.1.1, Login to the EB licensing portal.

Step 2
Create an allocation account, see section 3.3.1.1, Creating an allocation account.

Step 2.1
Add additional allocation accounts if needed, see section 3.3.1.2, Adding an allocation
account.

Step 3
Add members to an allocation account, see section 3.3.1.3, Adding allocation account
members.

Step 4
Assign permissions to allocation account members, see section 3.3.1.4, Assigning per-
missions to account members.

Step 5
Switch to an allocation account, see section 3.3.1.5, Switching to an allocation account.

Step 6
Move licenses to an allocation account.

Step 6.1
Transfer licenses to an allocation account, see section 3.4.3, Transferring licenses to
an allocation account.

Step 6.2
Split licenses between allocation accounts, see section 3.4.4, Splitting licenses be-
tween allocation accounts.

Step 7
Verify the successful transfer of an order, see section 3.3.1.6, Verifying a transferred or-
der.

Page 22 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

3.3.1.1. Creating an allocation account

STEP Creating an allocation account

Prerequisite:

■ The permission Account Administration must be activated. For more information,

see section 3.2, Profile administration.

NOTE Delete an allocation account

If you want to delete an allocation account, contact the Product Sup-

port and Customer Care Team.

Step 1
In the EB licensing portal, browse to View Groups.

Step 2
Click Create New Allocation Account.

Figure 3.3. The View Groups page

Example: In the screenshot below, the main account is ElektrobitTesting and two allocation accounts EB CIS-
I and EB CIS-T are already available.

3.3.1.2. Adding an allocation account

STEP Adding an allocation account
Step 1
Enter an allocation account in the Name text box, e.g. EB CIS-T.
Step 2
You can also provide a note for the new account in the Note text box.

Page 23 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

Step 3
Check the Download and Transfer/Split Orders check boxes. The Admin check box is
checked by default. Make sure that the Move HostDevice check box is unchecked.

Step 4
As an account administrator, you are included automatically as a member in the newly
created allocation account.

Step 5
Click Add Allocation Account to create the new allocation account.

Figure 3.4. The Add Allocation Account page

3.3.1.3. Adding allocation account members

STEP Adding allocation account members
Step 1
Check that you are already included in the new allocation account as administrator.
Step 2
Click Add New Member to add account members and set the intended permissions.

Figure 3.5. Add an allocation account

Page 24 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

NOTE Transfer of licenses

Each account member that has the permission Transfer & Split Orders is able to transfer
a license back to the main account.

3.3.1.4. Assigning permissions to account members

You can assign the following permissions to members of your allocation account and to yourself:
Admin Privileges: enables to change account settings, see section 3.3, Account administration.
Download Privileges: enables to download license files, see section 3.4, License administration.
Transfer & Split Orders: enables to transfer licenses and to split multiple licenses, see section 3.4, License
administration.
Move Host & Device: this permission is not supported.

STEP Assigning permissions to account members

Step 1
In the EB licensing portal, browse to Account Members under Administration.
Step 2
Select or unselect a check box in the permission column to assign or unassign a permis-
sions from an account member.

Figure 3.6. Account member administration

3.3.1.5. Switching to an allocation account

If you are a member of multiple accounts, you can switch the account, e.g. to verify that an order was transferred
successfully.

STEP Switching to an allocation account

Step 1
Click the Switch Account button at the top of the EB licensing portal.

Page 25 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

Figure 3.7. The Switch Account button

Step 2
Select the allocation account you want to verify, afterwards you are logged in to the allo-
cation account

Figure 3.8. Select an allocation account

3.3.1.6. Verifying a transferred order

STEP Verifying a transferred order
Step 1
Switch to the account with the transferred order. For more information, see sec-
tion 3.3.1.5, Switching to an allocation account.
Step 2
Browse to the order history of the selected allocation account.

Figure 3.9. Order history of the allocation account

Step 3
The previously transferred order is now visible within the allocation account. Only account
members of the allocation account can see this license from now on.

Page 26 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

Step 4
To see the license, point to the Actions button on the right side of the order line and click
License(s).

Step 5
If you accidentally assigned a license to the wrong allocation account you can transfer the
license back to the main account. Make sure to switch to the correct allocation account
before you transfer the license back. For more information on switching accounts, see
section 3.3.1.5, Switching to an allocation account.

Step 6
Follow the same procedure as used to transfer the license to the allocation account, see
section 3.4.3, Transferring licenses to an allocation account.

3.4. License administration

On the EB licensing portal you can do the following license-related tasks:
Search licenses, see section 3.4.1, Searching licenses.
Access your licenses, see section 3.4.2, Accessing your licenses.
Transfer licenses to a different allocation account, see section 3.4.3, Transferring licenses to an allocation
account.
Split licenses between allocation accounts, see section 3.4.4, Splitting licenses between allocation ac-
counts.

3.4.1. Searching licenses

On the Search Licenses page you can perform the following actions:
Search for your licenses using different search criteria.
To search for a license, use the Find Licenses section and click Search Licenses.
Filter your search results.
To filter your search results, use the option buttons and text boxes in the Filter By section.
Download all your file-based company licenses in a single ZIP archive.
To download all file-based company licenses, click Download All Licenses.

Page 27 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

Figure 3.10. Search Licenses page

NOTE Search function only for associated licenses

Only licenses that are already associated are shown in the search result. Associated li-
censes are already activated on a specific machine or a license file was generated for a
specific dongle. Browse to the affected order to generate your license file or to retrieve your
activation codes.

NOTE Restricted download of multiple licenses

You can download a subset of licenses with the Download button at the bottom of the page.
However, only licenses which are shown according to your search criterion and have their
check box activated are included in the ZIP archive.

Example: If your search criterion has provided 50 results but on the result screen you have
configured to show only 25 results on a page, only these 25 results are included in the
ZIP archive.

3.4.2. Accessing your licenses

STEP Accessing your related licenses

For information on how to access legacy licenses, see section 10.3, Accessing your lega-
cy licenses.

Step 1
Browse to the Order History page.

Step 2
Point to the Actions button on the right side of the related order line.

Page 28 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

Step 3
In the context menu, click License(s).

Figure 3.11. Order History page

Within the order-related license overview page you can do the following:
Download individual license files for each dongled license catalog items.
To download an individual file, click Download to the right of the dongled license.
Retrieve activation codes for single user or floating license catalog items.
Activation codes are shown for single user or floating licenses.
Download all selected licenses as a ZIP archive.
To download all selected licenses, click the Download button on the bottom of the list.

Figure 3.12. Download license on the Order History page

Page 29 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

NOTE ZIP archives do not contain activation codes

Activation codes are not included in the ZIP archive since these codes must be entered into
the appropriate license administrator tool. You can find your activation codes also in the
automatically created order notification email. You find an email history in Recent Email
Notifications.

3.4.3. Transferring licenses to an allocation account

You can perform a license transfer only on a whole order. If you want to split a license pool, see section 3.4.4,
Splitting licenses between allocation accounts.

WARNING You can only transfer licenses from EB tresos AutoCore Generic 7.3 and high-
er

If you try to transfer a legacy license, an error occurs. For more information on legacy
licenses, see chapter 10, Legacy licenses.

STEP Transferring licenses to an allocation account

Prerequisite:

■ To perform this task, you need the permission Transfer & Split Orders.

Step 1
Browse to the Order History page.

Step 2
Point to the Actions button on the right side of the affected order line.

Step 3
In the context menu, click Transfer to transfer a license to an allocation account.

Figure 3.13. Transfer License

Step 4
Select the target allocation account in the To Account: drop-down list box.

Page 30 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

Figure 3.14. Select target allocation account

Step 5
Click Submit to save your selection.

Step 6
You can verify the transfer in the Order Detail view of the Order History under Alloca-
tions.

Figure 3.15. Transfer verification

3.4.4. Splitting licenses between allocation accounts

WARNING You can only split licenses from EB tresos AutoCore Generic 7.3 and higher

If you try to split legacy licenses, an error occurs. For more information on legacy licenses,
see chapter 10, Legacy licenses.

STEP Splitting licenses between allocation accounts

Prerequisite:

■ To perform this task, you need the permission Transfer & Split Orders.

Step 1
Browse to the Order History page.

Page 31 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

Step 2
Click the appropriate order to show a list of included line items.

Figure 3.16. Select order

Step 3
In the Order Detail view, point to the Actions button on the right side of a line item.

Step 4
In the context menu, click Split to split the license.

Figure 3.17. The Order detail view

Step 5
Select the target allocation account in the To Account: drop-down list box.

Step 6
Select the number of licenses to transfer in the Quantity to Allocate: drop-down list box.
Step 7
Click Submit to complete the split and transfer operation.

Page 32 of 87
 Product licensing User Guide
Chapter 3. Using the EB licensing portal

Figure 3.18. Split licenses

NOTE Split licenses only on line-item level

You can only split licenses on line-item level since each line item may
have a different number of available licenses.

Step 8
You can verify the license split in the Order Detail view of the Order History under Allo-
cations.

Figure 3.19. License split overview

Page 33 of 87
 Product licensing User Guide
Chapter 4. The licensing project on EB Command

4. The licensing project on EB Command

Several components are available on the EB Command customer portal:

https://command.elektrobit.com

List of components:

Microsoft Windows EB Client License Administrator setup file

Linux EB Client License Administrator setup archive
Microsoft Windows EB Server License Administrator setup file
WibuKey WkRuntime dongle driver setup file (FLEXID-10)
Sentinel HASP4 dongle driver setup file (FLEXID-9)
FlexNet Publisher License Administration Guide (fnp_LicAdmin.pdf)
EB Product licensing User Guide (LicensingUserGuide.pdf)
FlexNet License Server setup file for 64-bit (lmadmin-x64)

Figure 4.1. The EB Command licensing project

Page 34 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

5. Single user or evaluation licenses

5.1. Activating single user or evaluation licenses
Single user and evaluation licenses are provided via FlexNet Operations On Cloud activation codes. You can
find the activation codes either in the order notification email or in Order History of the EB licensing portal.

NOTE Using remote desktop or terminal server sessions is not possible

The Single-User or Evaluation license is not allowed to be used on remote desktop or

terminal server sessions. This usage is technically prohibited. Choose the floating license
for remote desktop or terminal desktop sessions instead.

STEP Activating single user or evaluation licenses

Prerequisite:

■ The EB Client License Administrator tool is downloaded from EB Command and in-
stalled. For more information on EB Command, see chapter 4, The licensing project
on EB Command. For information on how to install the EB Client License Administrator
tool, see section 5.1.1, Installing the EB Client License Administrator tool.

Step 1
Obtain your activation code from the EB licensing customer portal or from the order notifi-
cation email. For more information, see chapter 2, Overview.

Step 2
Activate your license with the EB Client License Administrator Tool.
For online activation, see section 5.1.2, Activating a single user or evaluation license on-
line.
For offline activation, see section 5.1.3, Activating a single user or evaluation license of-
fline.

Step 3
Start the application.

Page 35 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

5.1.1. Installing the EB Client License Administrator tool

STEP Installing the EB Client License Administrator tool

5.1.1.1. Installing for Microsoft Windows

Prerequisite:

■ Download the EB_Client_License_Administrator_Setup.exe tool from EB Command:

https://command.elektrobit.com

Step 1
Run EB_Client_License_Administrator_Setup.exe.

Step 2
Select the destination folder.

Step 3
Optionally create a Start menu entry.

Step 4
Optionally create a desktop shortcut.

Step 5
Select the default option Use License Activation Codes. For more information, see chapter 5, Single user
or evaluation licenses.

Figure 5.1. Use activation codes

Page 36 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Step 6
Click Install to begin the installation.

5.1.1.2. Installing for Linux

Prerequisite:

■ Download the EB_Client_License_Administrator_Linux.tar.gz tool from EB Command:

https://command.elektrobit.com
■ Install Linux Standard Base (LSB).

Step 1
Open a command line terminal.

Step 2
Unarchive the downloaded file EB_Client_License_Administrator_Linux.tar.gz.

Command: # tar zxvf EB_Client_License_Administrator_Linux.tar.gz

Step 3
Change directory to eb_license.

Command: # cd eb_license

Step 4
Run install_eb_license_tools.sh with root rights.

Command: # sudo bash install_eb_license_tools.sh

5.1.2. Activating a single user or evaluation license online

STEP Activating a single user or evaluation license online

5.1.2.1. Activating on Microsoft Windows

Step 1
Run the EB Client License Administrator tool from the Start menu or click the desktop shortcut.

Step 2
Enter an activation code in the Activation Code text box.

Page 37 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Figure 5.2. Online client license activation

Step 3
Click Activate.

Step 4
Verify the license activation in the Status section.

Step 5
Your license is ready to use.

5.1.2.2. Activating on Linux

Step 1
Open a command line terminal.

Step 2
Change directory to location where the EB_Client_License_Administrator_Linux has installed. Usually /usr/
local/share/FNP/service64/[Version]/.
Command: # cd /usr/local/share/FNP/service64/11.19.1/

Step 3
Activate the code using ebactutil.sh.
Command: # ./ebactutil.sh -activate "YOUR-CODE-FORA-EBPR"

Page 38 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Step 4
Verify the activation using ebactutil.sh.
Command: # ./ebactutil.sh -view

Step 5
Your license is ready to use.

5.1.3. Activating a single user or evaluation license offline

STEP Activating a single user or evaluation license offline

5.1.3.1. Activating on Microsoft Windows

Step 1
Run the EB Client License Administrator tool from the Start menu or click the desktop shortcut.

Step 2
Enter an activation code in the Activation Code text box.

Figure 5.3. Offline client license activation

Page 39 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Step 3
Click Create Activation Request ....

Step 4
Save the activation request file and move it to a machine with internet access.

Step 5
On the machine with internet access, log in to the EB licensing portal.

Step 6
Browse to Offline License Handling.

Figure 5.4. Processing the activation request file

Step 7
Click Browse... to load your previously created activation request file.

Step 8
Click Process to process your offline license activation request and save the activation response file.

Step 9
Move the activation response file to your client machine where you created the activation request.

Step 10
On your client machine, click Process Activation ... to load and process the activation response file.

Step 11
Verify the license activation in the Status section.

Step 12
Your license is ready to use.

5.1.3.2. Activating on Linux

Step 1
Open a command line terminal.

Page 40 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Step 2
Change directory to location where the EB_Client_License_Administrator_Linux has installed. Usually /usr/
local/share/FNP/service64/[Version]/.
Command: # cd /usr/local/share/FNP/service64/11.19.1/
Step 3
Generate the activation request using ebactutil.sh.
Command: # ./ebactutil.sh -activate "YOUR-CODE-FORA-EBPR" -gen ~/activation_re-
quest.xml
Step 4
Move the request to a machine with internet access.

Step 5
On the machine with internet access, log in to the EB licensing portal.

Step 6
Browse to Offline License Handling.

Figure 5.5. Processing the activation request file

Step 7
Click Browse... to load your previously created activation request file.

Step 8
Click Process to process your offline license activation request and save the activation response file.

Step 9
Move the activation response file to your client machine where you created the activation request.

Step 10
Process the activation request using ebactutil.sh.
Command: # ./ebactutil.sh -process ~/activation_request_response.xml

Step 11
Verify the activation using ebactutil.sh.

Page 41 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Command: # ./ebactutil.sh -view

Step 12
Your license is ready to use.

5.2. Returning a single user or evaluation license

5.2.1. Returning a single user or evaluation license online
5.2.1.1. Returning on Microsoft Windows
STEP Returning a single user or evaluation license online
Step 1
Run the EB Client License Administrator tool from the Start menu or click the desktop
shortcut.
Step 2
Select the line that shows the license you want to return.

Figure 5.6. Online client license return

Step 3
Click Return.

Step 4
Your license is successfully returned and its seat is available again for new license activa-
tion.

5.2.1.2. Returning on Linux

Step 1
Open a command line terminal.

Page 42 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Step 2
Change directory to location where the EB_Client_License_Administrator_Linux has installed. Usually /usr/
local/share/FNP/service64/[Version]/.
Command: # cd /usr/local/share/FNP/service64/11.19.1/
Step 3
Return the license using ebactutil.sh.
Command: # ./ebactutil.sh -return "YOUR-CODE-FORA-EBPR"

Step 4
Verify the license is not stored in local trusted storage anymore using ebactutil.sh.
Command: # ./ebactutil.sh -view

Step 5
Your license is successfully returned and its seat is available again for new license activation.

5.2.2. Returning a single user or evaluation license offline

5.2.2.1. Returning on Microsoft Windows
STEP Returning a single user or evaluation license offline
Step 1
Run the EB Client License Administrator tool from the Start menu or click the desktop
shortcut.
Step 2
Select the line that shows the license you want to return.

Figure 5.7. Offline client license return

Step 3
Click Create Return Request ....

Page 43 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Step 4
Save the return request file and move it to a machine with internet access.

Step 5
On the machine with internet access, log in to the EB licensing portal.

Step 6
Browse to Offline License Handling.

Figure 5.8. Processing the return request file

Step 7
Click Browse... to load your previously created return request file.

Step 8
Click Process to process your offline license return request file.

Step 9
Save the generated license return response file.

NOTE License return response file

The license return response file contains the license return confirma-
tion. It is not needed further on.

Step 10
Your license is successfully returned and its seat is available again for new license activa-
tion.

5.2.2.2. Returning on Linux

STEP Returning a single user or evaluation license offline
Step 1
Open a command line terminal.

Page 44 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Step 2
Change directory to location where the EB_Client_License_Administrator_Linux has in-
stalled. Usually /usr/local/share/FNP/service64/[Version]/.
Command: # cd /usr/local/share/FNP/service64/11.19.1/
Step 3
Generate the return request using ebactutil.sh.
Command: # ./ebactutil.sh -return "YOUR-CODE-FORA-EBPR" -gen ~/re-
turn_request.xml

Step 4
Move the request file to a machine with internet access.

Step 5
On the machine with internet access, log in to the EB licensing portal.

Step 6
Browse to Offline License Handling.

Figure 5.9. Processing the return request file

Step 7
Click Browse... to load your previously created return request file.

Step 8
Click Process to process your offline license return request file.

Step 9
Save the generated license return response file.

Page 45 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

NOTE License return response file

The license return response file contains the license return confirma-
tion. It is not needed further on.

Step 10
Your license is successfully returned and its seat is available again for new license activa-
tion.

5.3. Upgrading a single user or evaluation license

If you have purchased a subscription renewal of your single user license or your evaluation period was extend-
ed, then you can upgrade your license so that the new maintenance end date is applied to your current license.

Page 46 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

5.3.1. Upgrading a single user or evaluation license online

5.3.1.1. Upgrading on Microsoft Windows
STEP Upgrading a single user or evaluation license online
Step 1
Run the EB Client License Administrator tool from the Start menu or click the desktop
shortcut.
Step 2
Select the line that shows the license you want to upgrade.

Figure 5.10. Online client license upgrade

Step 3
Click Upgrade.

Step 4
Your license is successfully upgraded.

5.3.1.2. Upgrading on Linux

STEP Upgrading a single user license online is a two step operation
Step 1
Return your license online.
For online return, see section 5.2.1.2, Returning on Linux

Step 2
Activate your license online.
For online activation, see section 5.1.2.2, Activating on Linux

Page 47 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

5.3.2. Upgrading a single user or evaluation license offline

STEP Upgrading a single user license offline is a two step operation
Step 1
Return your license offline.
For offline return, see section 5.2.2, Returning a single user or evaluation license offline

Step 2
Activate your license offline.
For offline activation, see section 5.1.3, Activating a single user or evaluation license of-
fline

5.4. Repairing a broken license

A license might get invalid or broken e.g. after hardware defects and repair. A broken license could be recovered
in many cases. If the license repair does not succeed, please contact EB customer support.

Page 48 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

5.4.1. Repair on Microsoft Windows

STEP Repair a single user or evaluation license online on Microsoft Windows
Step 1
Run the EB Client License Administrator tool from the Start menu or click the desktop
shortcut.
Step 2
Select the line that shows the broken license you want to repair.

Figure 5.11. Online client license repair

Step 3
Click Repair.

Step 4
Your license might be recoverd.

5.4.2. Repair local liceses on Linux

NOTE License repair in virtual environments

The license repair in virtual environments is not supported. If the license repair is needed
in such environments, please contact EB customer support.

Step 1
Open a command line terminal.

Step 2
Change directory to location where the EB_Client_License_Administrator_Linux has installed. Usually /usr/
local/share/FNP/service64/[Version]/.
Command: # cd /usr/local/share/FNP/service64/11.19.1/

Page 49 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Step 3
Try to repair local licenses using ebactutil.sh.
Command: # ./ebactutil.sh -localrepair

5.5. Removing an expired license

5.5.1. Removing on Microsoft Windows
To remove an expired license without returning the license to the FlexNet Operations Cloud, click the right
mouse button on the expired license line and select Delete Expired License.

Figure 5.12. Removing an expired license

NOTE Context Menu

The context menu to delete an expired license is only available if the license is already
expired!

5.5.2. Removing on Linux

NOTE Context Menu

Licenses can be removed only if is already expired!

Step 1
Open a command line terminal.

Step 2
Change directory to location where the EB_Client_License_Administrator_Linux has installed. Usually /usr/
local/share/FNP/service64/[Version]/.
Command: # cd /usr/local/share/FNP/service64/11.19.1/

Step 3
Return the license using ebactutil.sh.
Command: # ./ebactutil.sh -delete "YOUR-CODE-FORA-EBPR"

Step 4
Verify the license is not stored in local trusted storage anymore using ebactutil.sh.

Page 50 of 87
 Product licensing User Guide
Chapter 5. Single user or evaluation licenses

Command: # ./ebactutil.sh -view

Page 51 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

6. Floating licenses
6.1. Activating floating licenses
Floating licenses are provided via FlexNet Operations On Cloud activation codes. Floating licenses are served
by a floating license server within the customers network infrastructure. You can find the activation codes either
in the order notification email or in Order History of the EB licensing portal.

STEP Activating floating licenses on a server machine

Prerequisite:

■ A lmadmin license server is set up and configured. For more information, see chap-
ter 11, License server configuration.

Step 1
Obtain your activation code from the EB licensing customer portal or from the order notifi-
cation email. For more information, see chapter 3, Using the EB licensing portal.

Step 2
Activate your license with the EB Server License Administrator Tool.
For online activation, see section 6.1.2, Activating a floating license online.
For offline activation, see section 6.1.3, Activating a floating license offline.

Page 52 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

6.1.1. Installing the EB Server License Administrator tool

STEP Installing the EB Server License Administrator tool

Prerequisite:

■ Download the EB_Server_License_Administrator_Setup.exe tool from EB

Command:
https://command.elektrobit.com

Step 1
Run EB_Server_License_Administrator_Setup.exe.

Step 2
Select the destination folder.

Step 3
Optionally create a Start menu entry.

Step 4
Optionally create a desktop shortcut.

Step 5
The installation of the EB Server License Administrator tool is complete.

Page 53 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

6.1.2. Activating a floating license online

STEP Activating a floating license online
Step 1
Run the EB Server License Administrator tool from the Start menu or click the desktop
shortcut.
Step 2
Enter an activation code in the Activation Code text box.

Figure 6.1. Online server license activation

Step 3
Enter the number of licenses you want to activate. You can activate all ordered licenses
on one machine or you can split your licenses to several license servers.

Step 4
Click Activate.

Step 5
Verify the license activation in the Status section.

Step 6
Restart your license server or re-read the licenses with the license server front end.

Step 7
Your licenses are ready to use on your license server.

Page 54 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

6.1.3. Activating a floating license offline

STEP Activating a floating license offline
Step 1
Run the EB Server License Administrator tool from the Start menu or click the desktop
shortcut.
Step 2
Enter an activation code in the Activation Code text box.

Figure 6.2. Offline server license activation

Step 3
Enter the number of licenses you want to activate. You can activate all ordered licenses
on one machine or you can split your licenses to several license servers.

Step 4
Click Create Activation Request ....

Step 5
Save the activation request file and move it to a machine with internet access.

Step 6
On the machine with internet access, log in to the EB licensing portal.

Step 7
Browse to Offline License Handling.

Page 55 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

Figure 6.3. Processing the activation request file

Step 8
Click Browse... to load your previously created activation request file.

Step 9
Click Process to process your offline license activation request and save the activation
response file.

Step 10
Move the activation response file to your server machine where you created the activa-
tion request.

Step 11
On your server machine, click Process Activation ... to load and process the activation
response file.

Step 12
Verify the license activation in the Status section.

Step 13
Restart your license server or re-read the licenses with the license server front end.

Step 14
Your licenses are ready to use on your license server.

Page 56 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

6.2. Returning a floating license

6.2.1. Returning a floating license online
STEP Returning a floating license online
Step 1
Run the EB Server License Administrator tool from the Start menu or click the desktop
shortcut.
Step 2
Select the line that shows the license you want to return.

Figure 6.4. Offline server license return

Step 3
Click Return.

Step 4
Your license is successfully returned and the related seats are available again for new li-
cense activation.

6.2.2. Returning a floating license offline

STEP Returning a floating license offline
Step 1
Run the EB Server License Administrator tool from the Start menu or click the desktop
shortcut.

Page 57 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

Step 2
Select the line that shows the license you want to return.

Figure 6.5. Offline server license return

Step 3
Click Create Return Request ....

Step 4
Save the return request file and move it to a machine with internet access.

Step 5
On the machine with internet access, log in to the EB licensing portal.

Step 6
Browse to Offline License Handling.

Figure 6.6. Processing the return request file

Step 7
Click Browse... to load your previously created return request file.

Page 58 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

Step 8
Click Process to process your offline license return request file.

Step 9
Save the generated license return response file.

NOTE The license return response file

The license return response file contains the license return confirma-
tion. It is not needed further on.

Step 10
Your license is successfully returned and the related seats are available again for new li-
cense activation.

6.3. Upgrading a floating license

If you have purchased a subscription renewal of your floating license or your evaluation period was extended
then you can upgrade your license so that the new maintenance end date is applied to your current license.

Page 59 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

6.3.1. Upgrading floating license online

STEP Upgrading a floating license online
Step 1
Run the EB Server License Administrator tool from the Start menu or click the desktop
shortcut.
Step 2
Select the line that shows the license you want to upgrade.

Figure 6.7. Online floating license upgrade

Step 3
Click Upgrade.

Step 4
Your license has been successfully upgraded.

6.3.2. Upgrading a floating license offline

STEP Upgrading a floating license offline is a two step operation
Step 1
Return your floating license offline.
For offline return, see section 6.2.2, Returning a floating license offline

Step 2
Activate your floating license offline.
For offline activation, see section 6.1.3, Activating a floating license offline

Page 60 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

6.4. Removing an expired floating licenses

To remove an expired floating license without returning the license to the FlexNet Operations Cloud, click the
right mouse button on the expired license line and select Delete Expired License.

Figure 6.8. Removing an expired floating license

NOTE Context Menu

The context menu to delete an expired license is only available if the license is already
expired!

6.5. Repairing a floating license

A license might get invalid or broken e.g. after hardware defects and repair. A broken license could be recovered
in many cases. If the license repair does not succeed, please contact EB customer support.

Page 61 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

STEP Repair a floating license online

Step 1
Run the EB Server License Administrator tool from the Start menu or click the desktop
shortcut.
Step 2
Select the line that shows the broken license you want to repair.

Figure 6.9. Online floating license repair

Step 3
Click Repair.

Step 4
Your license might be recoverd.

6.6. Using floating licenses on a client machine

6.6.1. Configuring a license server in client application
STEP Configuring a license server in client application
Step 1
Run the application that requires a license.
Step 2
Configure the server settings in the application using the server name and port number
that your license server administrator has provided.

Step 3
Check the license in the license configuration of the specific application (e.g. EB tresos
studio or EB corbos studio).

Page 62 of 87
 Product licensing User Guide
Chapter 6. Floating licenses

6.6.2. Manual setup

If you use floating or dongled licenses on your PC, installing the EB Client License Administrator tool is optional.
You can configure the environment variable EB_LICENSE_FILE manually with the following values:
License server for floating licenses: EB_LICENSE_FILE=<port>@<your_server_name>

NOTE Obtain server name and port number

Contact your license server administrator to obtain the server name and port number
used by the FlexNet license server of your company.

License file for dongled licenses: EB_LICENSE_FILE=<path_to_your_license_file.lic>

License folder as an alternative for dongled licenses: EB_LICENSE_FILE=<path_to_your_li-
cense_files>

NOTE Combined options

You can combine different options. The license search order depends on the order of the
entries provided in the EB_LICENSE_FILE environment variable. The entries must be sep-
arated by semicolon.

Example: EB_LICENSE_FILE=C:\EB\Licenses;[email protected]

WARNING Usage of the generic LM_LICENSE_FILE environment variable

Do not use the generic LM_LICENSE_FILE environment variable to configure the EB li-
cense search order without having a reasonable requirement since using the generic envi-
ronment variable may lead to conflicts with other software vendors.

Page 63 of 87
 Product licensing User Guide
Chapter 7. Dongled licenses

7. Dongled licenses
7.1. Prerequisites when using dongled licenses
NOTE Using remote desktop or terminal server sessions is not possible

The Dongled license is not allowed to be used on remote desktop or terminal server ses-
sions. This usage is technically prohibited. Choose the floating license for remote desktop
or terminal desktop sessions instead.

STEP Prerequisites when using dongled licenses

Prerequisite:

■ Install the dongle driver by downloading the WkRuntime.exe dongle driver from EB
Command. Alternatively download the latest version from Wibu-Systems: http://www.-
wibu.com
■ Download license files. For more information see section 3.4.2, Accessing your licens-
es.

Step 1
Start the application.

Step 2
Specify the license location in the application.

Step 3
Use the application.

7.2. Downloading license files from the Order

History page
You can download a single license file or all license files in a ZIP archive from the Order History page.

STEP Downloading license files from the Order History page

Step 1
Browse to the Order History page.
Step 2
Click on related order number on the left side.

Step 3
On the Order Detail page, point to the Actions button on the right side of the related or-
der line.

Page 64 of 87
 Product licensing User Guide
Chapter 7. Dongled licenses

Step 4
In the context menu, click License(s).

Step 5
On the License Information page, click Download on the bottom to download all don-
gled licenses. To download a single dongled license, click Download on the right.

Figure 7.1. Download button

Page 65 of 87
 Product licensing User Guide
Chapter 7. Dongled licenses

7.3. Retrieving dongle serial number and

customer ID
STEP Retrieving dongle serial number and customer ID

NOTE Dongle serial number and customer ID

Dongle licenses are locked to the dongle serial number or to the cus-
tomer ID. If you need to contact EB according license issues with
your dongle, you need to provide the dongle serial number and the
customer ID to EB Customer Care. After you have connected the
WibuKey to your computer and you have installed the dongle driver
(see section 7.1, Prerequisites when using dongled licenses), you can
retrieve the required information via the WibuKey control panel applet.

Step 1
Plug in USB dongle.

Step 2
Open the WibuKey control panel applet from the Windows Control Panel.

Step 3
Retrieve your dongle serial number - Example: 12-12114690

Step 4
Retrieve your customer ID - Example: 180054

Figure 7.2. WibuKey control panel applet

Page 66 of 87
 Product licensing User Guide
Chapter 8. Hardware licenses

8. Hardware licenses
Hardware licenses are provided in a license file which must be uploaded to an EB hardware product, e.g. EB
5200 or EB 6100. The license technology is not based on FlexNet. Multiple module licenses are integrated in
one license file and a digital signature is applied during downloading the license file.

8.1. Downloading license files from the Search

Licenses menu
License files for EB hardware products are created during the download from the FlexNet portal. A license file
for a specific product accumulates all module licenses.

NOTE Download All Licenses

You can download all available license files associated to your account in a ZIP archive by
clicking on the Download All Licenses button. The ZIP archive contains hardware license
files as well as previously generated FlexNet license files and legacy licenses files if avail-
able. For more information about Search Licenses, see section 3.4.1, Searching licenses.

WARNING Download hardware licenses via the Order History is not possible

The hardware license files are generated during the download from the EB licensing portal.
It is not possible to download individual signed license files via the Order History page. The
received files provide only fragments of the required license file without a digital signature.

STEP Downloading license files from the Search Licenses menu

Prerequisite:

■ The EB hardware product serial number is known, see section 8.2, Finding the EB
hardware serial number.

Step 1
Login to the EB licensing portal and navigate to Search Licenses.

Step 2
Choose Serial Number in the Search drop-down box.

Step 3
Enter the last part of the serial number in the For text box with surrounding asterisks.

Step 4
Click Search Licenses.

Page 67 of 87
 Product licensing User Guide
Chapter 8. Hardware licenses

Figure 8.1. Searching and downloading EB hardware licenses

Step 5
Navigate to the bottom of the page and click the Download button.

Step 6
Save the file on your machine and upload it to your EB hardware product.

Page 68 of 87
 Product licensing User Guide
Chapter 8. Hardware licenses

8.2. Finding the EB hardware serial number

The EB hardware serial number is required to find and download the appropriate license file on the EB licensing
portal. You need the number behind the hardware type in the serial number.

NOTE Example

If your serial number is EB 5200-0860 then you need the number 0860 when you search
for your license on the EB licensing portal.

STEP Finding the serial number on an EB hardware box

Step 1
Find the nameplate on your box.
Step 2
Locate the box serial number on the nameplate.

Figure 8.2. EB hardware box nameplate

STEP Finding the serial number on an EB hardware slot card

Step 1
Find the nameplate on your slot card.
Step 2
Locate the slot card serial number on the nameplate.

Figure 8.3. EB hardware slot card nameplate

Page 69 of 87
 Product licensing User Guide
Chapter 9. Partner licenses for EB tresos Studio

9. Partner licenses for EB tresos Studio

9.1. Overview
Partner licenses are delivered to partner companies of EB that redistribute EB tresos Studio together with their
own modules to their customers. Therefore a redistributable license is required. Partner licenses are provided
as a set of activation codes. An additional license feature for EB tresos Studio contains the provider-ID which
is required to digitally sign the modules developed by the partner.

9.2. Background information

9.2.1. Restrictions for partner licenses
The EB tresos Studio partner license is provided to the partner to develop and test partner-specific modules.
The cryptographic key that is required to sign the partner-specific modules is included in this license.
The EB tresos Studio customer partner license contains the cryptographic key to unlock the signed partner
modules on the partner's customer machine.
All allowed modules on the partner's customer machine must be cryptographically signed with the key
provided by the partner license.
The partner customer can also use a full-featured EB tresos Studio which can be ordered from EB if it is
required to use also unsigned modules.

9.2.2. Restrictions for partner customers

The EB tresos Studio activation code for a partner license must not be shipped to the customer.

EB ships a bundle of EB tresos Studio license activation codes for partner customers to the partner. The
partner ships one activation code out of this bundle to one customer.
Unsigned modules in the partner's customer installation are not accepted and are deactivated as long as
the partner's customer uses the restricted EB tresos Studio version.
EB ships a number of evaluation licenses to the partner which can be forwarded to a partner customer to
evaluate EB tresos Studio.

9.3. Using partner licenses

9.3.1. Using a partner license as a partner
STEP Using a partner license as a partner
Step 1
Activate the partner license on the partner machine.

Page 70 of 87
 Product licensing User Guide
Chapter 9. Partner licenses for EB tresos Studio

Step 2
Develop and test the partner-specific modules.

Step 3
Sign the partner modules with the provider-ID on the command line.

Step 4
Redistribute EB tresos Studio to the customer.

Step 5
Provide one activation code for a partner customer license of EB tresos Studio to your
customer.

Step 6
Redistribute the EB Client License Administrator tool to your customer.

9.3.2. Using a partner license as a partner customer

STEP Using a partner license as a partner customer
Step 1
Install EB tresos Studio which you have received from the partner.
Step 2
Install signed modules received from the partner.

Step 3
Activate the partner customer license for EB tresos Studio with the activation code re-
ceived from the partner.

Step 4
Start working with EB tresos Studio.

Page 71 of 87
 Product licensing User Guide
Chapter 9. Partner licenses for EB tresos Studio

Figure 9.1. Partner license workflow

9.4. Retrieving the provider-ID

The provider-ID is contained within a special license feature which is included in the partner license. The
provider-ID is encoded as suffix in the EB_TS_CRYPTO feature line. It is required to sign modules using the
signature tool. The provider-ID is typically the partner's company name or an abbreviation of the partner's
company name.

STEP Retrieving the provider-ID

Step 1
If you have a single user license, double-click the EB tresos Studio product for partners in
the EB Client License Administrator tool.
Step 2
If you have a floating license, double-click the EB tresos Studio product for partners in the
EB Server License Administrator tool.

Step 3
Locate the EB_TS_CRYPTO feature and extract your provider-ID from the feature name
suffix.
Example: The provider-ID in EB_TS_CRYPTOyourPartnerCode is yourPartnerCode.

Page 72 of 87
 Product licensing User Guide
Chapter 9. Partner licenses for EB tresos Studio

Figure 9.2. The provider-ID in the EB Client License Administrator tool

9.5. Use of the signature tool

EB tresos Studio includes a signature tool which is capable to sign module plug-ins. The signature tool is
accessible via the command line of EB tresos Studio. To operate the signature tool, a partner license of EB
tresos Studio for must be activated.

For more information on working with the signature tool, see section How to sign modules with the crypto
command in your EB tresos Studio developer's guide.

9.6. Software redistribution

To operate EB tresos Studio on a partner's customer machine, several components must be shipped to the
partner customer:
Product licensing User Guide
EB Client License Administrator tool
A copy of EB tresos Studio for the partner customer
Activation code for a partner customer license of EB tresos Studio
Signed partner modules

Page 73 of 87
 Product licensing User Guide
Chapter 10. Legacy licenses

10. Legacy licenses

10.1. Overview
Legacy licenses are dongled and floating licenses which are not covered by the default Flexera license gener-
ation process. The following products are affected:
EB tresos OSEK
EB tresos AutoCore Generic 4 and the corresponding EB tresos Studio release
EB tresos AutoCore Generic 6 and the corresponding EB tresos Studio release
EB tresos AutoCore Generic 7 and the corresponding EB tresos Studio release, up to 7.2

10.2. Background information

Legacy licenses are distributed through .lic license files.

The schema for legacy license files is tresos_Customer_<customername>_<licensetype>.lic

<customername> is your company name
<licensetype> is either FLOATING or DONGLE

Example for a floating license: tresos_Customer_Elektrobit_Automotive_GmbH_FLOATING.lic

Example for a dongled license: tresos_Customer_Elektrobit_Automotive_GmbH_DONGLE.lic

10.2.1. Legacy dongled licenses

A legacy dongled license consists of one license file for the client machine.

10.2.2. Legacy floating licenses

A legacy floating license consists of two license files, one for the client machine and one for the floating license
server.

10.3. Accessing your legacy licenses

10.3.1. Accessing legacy floating licenses
You receive legacy floating licenses in the EB licensing customer portal either as single .lic license file or
packed in a .zip file.

Page 74 of 87
 Product licensing User Guide
Chapter 10. Legacy licenses

Figure 10.1. Legacy floating license in a .lic file

Page 75 of 87
 Product licensing User Guide
Chapter 10. Legacy licenses

Figure 10.2. Legacy floating license in a .zip file

Page 76 of 87
 Product licensing User Guide
Chapter 10. Legacy licenses

10.3.2. Accessing legacy dongled licenses

Legacy dongled licenses are shown in the Order Detail view of the Order History. Each order with a preceded
X is a delivery note for a legacy dongled license.

Figure 10.3. Legacy floating license in a .zip file

For more information on the EB licensing customer portal, see chapter 3, Using the EB licensing portal.

Page 77 of 87
 Product licensing User Guide
Chapter 11. License server configuration

11. License server configuration

11.1. Overview
This chapter is aimed for network administrators and server administrators. It provides information on how to
use and configure a FlexNet lmadmin license server.

The following components are mandatory to configure a FlexNet license server:

The FlexNet lmadmin license server package is installed as service on the server machine and listens on
the lmadmin default port number 8090. For more information on the FlexNet lmadmin license server, see
the FlexNet Publisher License Administration Guide.
The EB Server License Administrator tool is installed in the default directory, see section 6.1.1, Installing
the EB Server License Administrator tool.
Floating licenses are activated on the server machine, see section 6.1.2, Activating a floating license online
and section 6.1.3, Activating a floating license offline.
The EB_SERVER_CONFIG.lic license file is available in C:\EB\EB_Server_License_Administra-
tor\Licenses.
After installing the EB Server License Administrator tool, the EB vendor daemon executable file is located
in <installfolder>\<platform>\EB.exe.
Example: C:\EB\EB_Server_License_Administrator\x64\EB.exe

NOTE 64 Bit EB vendor daemon

The EB vendor daemon is only available as 64 Bit version for Microsoft Windows operating
systems.

11.2. Transferring floating licenses from lmgrd to

lmadmin
If you have older licenes from lmgrd, follow the instructions to transfer the licenses to lmadmin.

STEP Transferring floating licenses from lmgrd to lmadmin

Step 1
Shutdown the lmgrd service.
Step 2
Copy all licenses from your previous license file to the EB_SERVER_CONFIG.lic.
Your older licenses are now managed by the lmadmin server.

Page 78 of 87
 Product licensing User Guide
Chapter 11. License server configuration

11.3. Login to the license server

STEP Login to the license server

Prerequisite:

■ The lmadmin license server package is installed.

■ The EB Server License Administrator tool is installed, see section 6.1.1, Installing the
EB Server License Administrator tool.
■ Floating licenses are activated on the server machine, see section 6.1.2, Activating a
floating license online and section 6.1.3, Activating a floating license offline.
■ EB_SERVER_CONFIG.lic license file is available in C:\EB\EB_Server_Li-
cense_Administrator\Licenses.

Step 1
In your favorite browser, browse to localhost:8090.

Step 2
Click the Administration button to browse to the administration page.

Figure 11.1. lmadmin login

Step 3
Log in to the server as user admin.

Page 79 of 87
 Product licensing User Guide
Chapter 11. License server configuration

Step 4
The default password for the admin user is admin.

NOTE Password change

Upon your first login to the administration page you are prompted to change the default
password.

11.4. Importing a license file

STEP Importing a license file
Step 1
Click Vendor Daemon Configuration to browse to the Vendor Daemons page.

Figure 11.2. The Vendor Daemons page

Step 2
Click Import License.

Step 3
Click Browse and select the EB_SERVER_CONFIG.lic license file. The default location
of this file is C:\EB\EB_Server_License_Administrator\licenses.

Page 80 of 87
 Product licensing User Guide
Chapter 11. License server configuration

Figure 11.3. Importing a license file

Step 4
Click Import License to import the selected license file.

NOTE Overwrite license file

If you import the license file for the first time, do not select the Overwrite License File on
License Server option. Otherwise, select the check box.

11.5. Verifying the license file import

STEP Verifying the license file import
Step 1
Check that the license file import was successful in the Import Information section.

Page 81 of 87
 Product licensing User Guide
Chapter 11. License server configuration

Figure 11.4. License file import information

Step 2
If the path to the EB vendor daemon is not yet configured, ignore the vendor daemon er-
ror messages in the Import Errors and Import Warnings. For information on configuring
the EB vendor daemon, see section 11.6, Configuring the EB vendor daemon.

Step 3
Click OK.

Step 4
On the Vendor Daemons page, point to the vendor daemon line with the Stopped status
and click the highlighted line to browse to the EB vendor daemon configuration page.

Figure 11.5. The Vendor Daemons page

11.6. Configuring the EB vendor daemon

STEP Configuring the EB vendor daemon
Step 1
In the text box Vendor Daemon Location, enter the path to the EB vendor daemon file
EB.exe.

Page 82 of 87
 Product licensing User Guide
Chapter 11. License server configuration

Figure 11.6. Vendor daemon configuration

Step 2
Select the Enable Date-based Versions check box. It is very important to check this
check box because the end date of the license subscription is coded into the license ver-
sion.

Step 3
Click Save to save your EB vendor daemon configuration.

Step 4
A message indicates that the EB vendor daemon configuration was successfully updated.
Click Start to start the EB vendor daemon.

Figure 11.7. Successful EB vendor daemon configuration

Page 83 of 87
 Product licensing User Guide
Chapter 11. License server configuration

11.7. Verifying the EB vendor daemon

STEP Verifying the EB vendor daemon
Step 1
The lmadmin initiates the EB vendor daemon startup with the message Starting vendor
daemon: EB.

Figure 11.8. The Vendor Daemons page

Step 2
The status Starting up is shown.

Step 3
Wait a few seconds and click Vendor Daemon Configuration to refresh the page.

Step 4
The status Up indicates that the EB vendor daemon is active.

Page 84 of 87
 Product licensing User Guide
Chapter 11. License server configuration

Figure 11.9. Active EB vendor daemon

11.8. Verifying your licenses

STEP Verifying your licenses
Step 1
Click Dashboard to browse to the FlexNet Publisher license server dashboard.

Figure 11.10. Verify licenses

Step 2
Click Concurrent.

Step 3
The EB_TEST_SERVER license feature is available.

Page 85 of 87
 Product licensing User Guide
Chapter 11. License server configuration

NOTE All activated licenses are shown

This page shows all your activated licenses available on your server
machine.

NOTE Activating floating licenses at the license server

For instructions on how to activate a floating license, see chapter 6,

Floating licenses.

11.9. Testing the license server with lmgrd

command line utility
To support debugging a license server configuration, two batch files are provided in the EB_Server_Li-
cense_Administrator\x64 folder of your Server License Administrator installation. Use these batch files
to run a local test of a floating server. The server test will use EB_SERVER_CONFIG_DEMO.lic which includes
a public EB_TEST_SERVER feature.
STEP Testing the license server with lmgrd command line utility
Step 1
Run test_lmgrd.bat to start the FlexNet Publisher license server on port 28000 of
your localhost.

Figure 11.11. Output of test_lmgrd.bat

Step 2
Run test_checkout.bat to checkout the license feature EB_TEST_SERVER.

Page 86 of 87
 Product licensing User Guide
Chapter 11. License server configuration

Figure 11.12. Output of test_checkout.bat

Page 87 of 87