working with codemeter licensing technology - … activationhow to update the firmware of a cmdongle...

dSPACE Installation Manager

Working with CodeMeterLicensing Technology

Release 2018-A – May 2018

How to Contact dSPACEMail: dSPACE GmbH

Rathenaustraße 2633102 PaderbornGermany

Tel.: +49 5251 1638-0Fax: +49 5251 16198-0E-mail: [email protected]: http://www.dspace.com

How to Contact dSPACE SupportIf you encounter a problem when using dSPACE products, contact your local dSPACErepresentative:

§ Local dSPACE companies and distributors: http://www.dspace.com/go/locations

§ For countries not listed, contact dSPACE GmbH in Paderborn, Germany.Tel.: +49 5251 1638-941 or e-mail: [email protected]

You can also use the support request form:http://www.dspace.com/go/supportrequest. If you are logged on to mydSPACE, youare automatically identified and do not need to add your contact details manually.

If possible, always provide the relevant dSPACE License ID or the serial number of theCmContainer in your support request.

Software Updates and PatchesdSPACE strongly recommends that you download and install the most recent patchesfor your current dSPACE installation. Visit http://www.dspace.com/go/support forsoftware updates and patches.

Important NoticeThis document contains proprietary information that is protected by copyright. Allrights are reserved. The document may be printed for personal or internal use providedall the proprietary markings are retained on all printed copies. In all other cases, thedocument must not be copied, photocopied, reproduced, translated, or reduced to anyelectronic medium or machine-readable form, in whole or in part, without the priorwritten consent of dSPACE GmbH.

© 2017 - 2018 by:dSPACE GmbHRathenaustraße 2633102 PaderbornGermany

This publication and the contents hereof are subject to change without notice.

ConfigurationDesk, ControlDesk, MicroAutoBox, MicroLabBox, SCALEXIO, SYNECT,SystemDesk, TargetLink and VEOS are registered trademarks of dSPACE GmbH in theUnited States or other countries, or both. Other brand names or product names aretrademarks or registered trademarks of their respective companies or organizations.

mailto:[email protected]

http://www.dspace.com

http://www.dspace.com/go/locations

mailto:[email protected]

http://www.dspace.com/go/supportrequest

http://www.dspace.com/go/support

Contents

About This Document 7Conventions Used in dSPACE User Documentation................................ .............. 7

Accessing dSPACE Help and PDF Files................................................................... 8

Related Documents............................................................................................ 10

Basics on CodeMeter Licensing Technology 11Introduction to CmContainers............................................................................ 11

Basics on License Management ......................................................................... 13

Validity of CodeMeter Licenses........................................................................... 16

Methods for Accessing CmContainers................................................................ 17

Basics on Adding Ticket IDs................................................................................ 20

Requirements for Communication...................................................................... 21

Compatibility with Earlier Releases..................................................................... 22

Starting with dSPACE Release 2018-A 25Use Case 1: New Customer or Starting with New CmDongle............................. 26

Use Case 2: Starting with WibuKey Dongle ....................................................... 28

Use Case 3: Starting with Old CmDongles (Rev. 2‑xxxx)...................................... 30

Use Case 4: Starting with Old CmDongles (Rev. 3‑xxxx)...................................... 31

Use Case 5: Updating the Maintenance Period of Activated Licenses(SMS Contracts)................................................................................................. 34

FNL Use Case 1: New Customer or Starting with a New FloatingNetwork License Installation............................................................................... 35

FNL Use Case 2: Migrating Floating Network Licenses........................................ 37

FNL Use Case 3: Updating the Maintenance Period of ActivatedLicenses (SMS Contracts).................................................................................... 38

Showing Available Licenses, CmContainers, and Tickets 41How to Show Available CmContainers and Their Attributes............................... 41

How to Show Available Licenses and Their Attributes......................................... 44

How to Request and Show Ticket Information....................................... ............ 47

Dongle Migration 51Basics on Dongle Migration................................................................................ 51

Contents

May 2018 Working with CodeMeter Licensing Technology 3

How to Migrate from a WibuKey Dongle........................................................... 53

How to Migrate from an Old CmDongle............................................................ 57

How to Disable a WibuKey Dongle..................................................................... 60

How to Update the Firmware of a CmDongle........................................ ............ 61

License Activation 65Use Cases and Workflows for License Activation................................................ 65

How to Activate Licenses (Local Access to CmContainer).................................... 70

How to Activate Licenses (LAN Access to CmContainer)..................................... 74

How to Activate Licenses (File-Based Access to CmContainer)............................ 80

License Update 85Use Scenario and Workflows for License Updates............................................... 85

How to Update Licenses (Local Access to CmContainer)..................................... 89

How to Update Licenses (LAN Access to CmContainer)...................................... 92

How to Update Licenses (File-Based Access to CmContainer)................. ............ 94

License Deactivation 99Use Scenarios and Workflows for License Deactivation....................................... 99

How to Deactivate Licenses (Local Access to CmContainer).............................. 103

How to Deactivate Licenses (File-Based Access to CmContainer)....................... 105

Executing Steps in CodeMeter Control Center (for File-Based Access) 111

How to Create an Initial RAC File..................................................................... 111

How to Update a CmContainer with an RAU File............................................. 117

Using Floating Network Licenses 123Basics on Using Floating Network Licenses....................................................... 123

Basics on Setting Up a License Server and the License Clients........................... 126

How to Set up the dSPACE License Server........................................................ 129

How to Set up a Connection Between Client and Server.................................. 133

Manual License Confirmation 137Use Scenario and Workflows for License Confirmation..................................... 137

How to Confirm the License Status Manually (Local Access toCmContainer).................................................................................................. 140

Contents

4 Working with CodeMeter Licensing Technology May 2018

How to Confirm the License Status Manually (LAN Access toCmContainer).................................................................................................. 142

How to Confirm the License Status Manually (File-Based Access toCmContainer).................................................................................................. 145

Manual RAU File Request 149Use Scenario and Workflow for Requesting a RAU File..................................... 149

How to Request an RAU File Manually................................................... .......... 150

Manual CmContainer Creation 155Workflows for Creating CmActLicense Containers .......................................... 155

How to Create a License Information File (LIF).................................................. 157

How to Request an RAU File for the New CmActLicense Container.................. 159

License Handling for SMS Contracts 163Workflows for Updating to dSPACE Release 2018-A (with SMSContract)......................................................................................................... 163

Workflows for Updating an SMS Contract ............................................ .......... 167

Workflows for Purchasing a New SMS Contract............................................... 168

Special License Handling Scenarios 173Workflow for License Activation for dSPACE Release 2017-A and Earlier.......... 173

Workflow for Replacing a Missing CmContainer.............................................. 175

Troubleshooting 179CmDongle Firmware Update Aborts with Error Message.................................. 179

CmDongle Firmware Update Not Possible........................................................ 179

Appendix 181Appendix: Dongle Types................................................................................... 181

Index 185

Contents


Contents


About This Document

This document shows you how to manage licenses for dSPACE Release 2017-Band later. Licenses for these Releases are based on the CodeMeter licensingtechnology. The document introduces you to the technology and givesinstructions for license handling, for example, for license activation.

Contents

Knowledge in handling the host PC and the Microsoft operating system isassumed.

Required knowledge

Information in this section

Conventions Used in dSPACE User Documentation .................................. 7

Accessing dSPACE Help and PDF Files ...................................................... 8

Related Documents ............................................................................... 10

Where to go from here

Conventions Used in dSPACE User Documentation

dSPACE user documentation uses the following symbols:

Symbol Description

DANGERIndicates a hazardous situation that, if not avoided,will result in death or serious injury.

WARNINGIndicates a hazardous situation that, if not avoided,could result in death or serious injury.

CAUTIONIndicates a hazardous situation that, if not avoided,could result in minor or moderate injury.

Symbols

About This Document


Symbol Description

NOTICEIndicates a hazard that, if not avoided, could result inproperty damage.

NoteIndicates important information that you should takeinto account to avoid malfunctions.

TipIndicates tips that can make your work easier.

Indicates a link that refers to a definition in theglossary, which you can find at the end of thedocument unless stated otherwise.

Precedes the document title in a link that refers toanother document.

dSPACE user documentation uses the following naming conventions:

%name% Names enclosed in percent signs refer to environment variables forfile and path names.

< > Angle brackets contain wildcard characters or placeholders for variablefile and path names, etc.

Naming conventions

Some software products use the following special folders:

Common Program Data folder A standard folder for application-specificconfiguration data that is used by all users.

%PROGRAMDATA%\dSPACE\<InstallationGUID>\<ProductName>or

%PROGRAMDATA%\dSPACE\<ProductName>\<VersionNumber>

Documents folder A standard folder for user-specific documents.

%USERPROFILE%\My Documents\dSPACE\<ProductName>\<VersionNumber>

Local Program Data folder A standard folder for application-specificconfiguration data that is used by the current, non-roaming user.

%USERPROFILE%\AppData\Local\dSPACE\<InstallationGUID>\<ProductName>

Special folders

Accessing dSPACE Help and PDF Files

After you install and decrypt your dSPACE software, the documentation for theinstalled products is available as online help in dSPACE Help and as Adobe® PDFfiles.

Introduction

About This Document


There are various ways to open dSPACE Help.

Note

Not all the ways to open dSPACE Help are available for all dSPACE softwareproducts.

Opening from Windows You can open dSPACE Help on its home page:

§ Via Windows Start Menu

Opening from dSPACE software with menu bar You can open dSPACEHelp on a product's start page:

§ Via the menu bar in a dSPACE product

Opening from dSPACE software with ribbons If you use dSPACE softwarewith ribbons, you can open dSPACE Help:

§ Via the Start page in dSPACE software

§ Via the Backstage view in dSPACE software (leftmost ribbon tab)

§ Via the button

Opening context-sensitive help dSPACE Help provides context-sensitivehelp. You can open help on the currently active context in dSPACE software:

§ Via F1

§ Via the Help button

Online help

You can open the PDF files as follows:

Opening from a topic in dSPACE Help You can access the PDF file with the

current topic via the button at the topic's top right. The following illustrationshows an example:

The PDF document opens on its first page.

Opening from dSPACE software with ribbons If your dSPACE softwarehas a user interface with ribbons, you can open a folder that contains the user

documentation in PDF format via the button in the Backstage view (leftmostribbon tab).

PDF files

Accessing dSPACE Help and PDF Files


Related Documents

Below is a list of documents that you are recommended to read when workingwith dSPACE Installation Manager.

Objective

Information in other documents

Managing dSPACE Software InstallationsShows you how to manage all the dSPACE installations on your host PCwith dSPACE Installation Manager. Managing means, for example,activating or deactivating installations, decrypting the encrypted archivesof the installed software and connecting dSPACE software installations toMATLAB software.

Working with Legacy Licensing TechnologiesShows you how to manage licenses for dSPACE Release 2017-A andearlier. Licenses for these Releases are based on legacy licensingtechnologies: WibuKey from Wibu-Systems for dongle licenses andFlexNet from Flexera for floating network licenses.

Contacting dSPACE SupportProvides best practices for solving problems and explains how to contactdSPACE Support. It also describes how to collect diagnostic informationvia dSPACE Installation Manager and to provide this information todSPACE Support.

dSPACE Installation Manager API ReferenceDescribes the API of dSPACE Installation Manager.

About This Document


Basics on CodeMeter Licensing Technology

With dSPACE Release 2017-B, the licensing technology for protecting dSPACEsoftware changes. From this Release forward, the WibuKey (for dongle licenses)and FlexNet technologies (for floating network licenses) are replaced by theCodeMeter licensing technology.

CodeMeter is a future-proof licensing technology from Wibu-Systems.

New licensing


Introduction to CmContainers ............................................................... 11

Basics on License Management .............................................................. 13

Validity of CodeMeter Licenses .............................................................. 16

Methods for Accessing CmContainers ................................................... 17

Basics on Adding Ticket IDs ................................................................... 20

Requirements for Communication ......................................................... 21

Compatibility with Earlier Releases ......................................................... 22


Introduction to CmContainers

CmContainers are basic components of the CodeMeter licensing technology,and the license information is stored in them. Each CmContainer can containmultiple licenses. A CmContainer can store licenses of different license types, forexample, single-user licenses and floating network licenses.

Basics on CmContainers



A CmContainer can be a CmDongle (hardware-based) or a CmActLicense(software-based). Thus, license information for all dSPACE products and versionsis no longer distributed over many files on your PC, but stored in one licensecontainer.

CmDongle Hardware-based variant of the CodeMeter protection andlicensing technology. The complete license information is stored on a smart cardchip in the CmDongle. With CmDongles, you can move the license informationbetween PCs by plugging the dongle into the PC you want to use. License filesare no longer needed.

CmDongles are available in different variants. The one provided by dSPACE iscalled CmStick. This variant is not a mass storage device. CmSticks areconfigured as human interface devices (HID). It is not possible to read or writearbitrary information. Therefore the CmSticks can be considered safe. You caneven use them in restricted areas and with restricted PCs where standard USBstick mass storage devices are not permitted.

CmActLicense Software-based variant of the CodeMeter protection andlicensing technology. CmActLicense containers are bound to a specific PC. Theycannot be transferred to another PC.

License information in CmContainers A license entry in a CmContainercan be viewed as a data record with various entries, such as the license name,license type, license quantity, and maintenance period. dSPACE InstallationManager shows this information as follows:

dSPACE Release 2018-A supports single-user licenses and floating networklicenses. Both are based on the CodeMeter licensing technology.

Supported license types

Single-user licenses

dSPACE product

Floating network licenses

License handling

CmContainer

CmActLicense

CmDongle

CodeMeter technology



As shown above, dSPACE Release 2018-A provides single-user licenses only onCmDongles. Floating network licenses are typically stored in CmActLicensecontainers, but you can also store floating network licenses on CmDongles. Incase of a defect or a planned upgrade of the license server, the CmDongle onlyneeds to be plugged into the new license server. You can immediately work withthe licenses again.

Basics on License Management

The CodeMeter Runtime software provides the basic functionality of theCodeMeter licensing technology. dSPACE Installation Manager is based onCodeMeter Runtime and is the central dSPACE tool for license management. Itfeatures almost all tasks required for handling licenses, for example, to activatelicenses. CodeMeter tools from Wibu-Systems are required only for certain tasks,for example, setting up a license server and connecting license clients to theserver.

CodeMeter software and dSPACE Installation Manager are installed automaticallywith dSPACE software installations. Furthermore, the tools can be downloadedseparately from the dSPACE website.

License management tools

License activation, license updates and deactivation are carried out via dSPACEInstallation Manager in combination with a database (dSPACE License Central)on the basis of tickets.

License management viadatabase

License Central

PC

Internet

CmDongle or CmActLicense

dSPACE License Central is hosted by dSPACE GmbH and is secured againstunauthorized access by a web gateway.

Ticket and ticket ID License handling, for example, license activation, uses aticket-based system. Depending on your order, dSPACE specifies the attributesfor each license and provides this information to the database. dSPACE LicenseCentral then generates a ticket ID for each license.

The ticket ID is a unique alphanumeric string of characters. The ticket ID of alicense remains unchanged as long as the license exists, but the licenseinformation related to it can be updated, for example, in case the maintenanceperiod of a license is extended with an SMS order.

Ticket group and ticket group ID A ticket group combines multiple ticketsthat dSPACE expects to be activated in one CmContainer based on your



purchase order. The ticket group ID represents all the tickets in the group. Youcan also clear individual tickets to exclude them from activation, for example.

License ALicense BLicense C...

Ticket group

Ticket group ID

63LU2506A7345Y2422NO1662

...

ACT-5E3D0

License overview sheets After you ordered dSPACE products, dSPACE sendsa license overview sheet via e-mail. This overview lists the required ticket IDs forthe purchased products as follows:

If you still use a WibuKey dongle, dongle migration is required. To do this, youneed a specific ticket ID, which is listed separately in the overview. Refer to thefollowing illustration.

Tip

In certain use cases, a number is specified in the Locked to WibuKey IDcolumn. If this is the case, the related ticket can only be activated on theCmDongle with the specified WibuKey ID.

The software installation process is now license-independent. Thus, aftersoftware installation, you have to activate licenses to run license-protecteddSPACE software.

License activation



Downloador DVD

Software Installation

CmContainer must be accessible

from host PC

License Activation

Decryption Use

To start the activation process, you have to enter the ticket IDs that you receivedfrom dSPACE via e-mail. During activation, data is transferred between dSPACEInstallation Manager and dSPACE License Central.

CmDongle (via mail)

Ticket IDs(via e-mail)

Web Gateway

Data exchange via Internet

Customer

License Central

CmContainer

Installation Manager

License A:License B:License C: ...

Ticket IDs

63LU2506A7345Y2422NO1662 ...

Activate

You can activate licenses online, which requires an Internet connection betweenthe Installation Manager and dSPACE License Central, or offline by means of filetransfer via e-mail. dSPACE strongly recommends to use online activationwhenever possible.

The workflow differs depending on how dSPACE Installation Manager can accessthe CmContainer. Refer to License Activation on page 65.

License updates are used if the license information of an already activated licensewas updated by dSPACE. This applies, for example, if the maintenance period ofyour dSPACE product is extended, because you purchased a SoftwareMaintenance Service (SMS) contract.

dSPACE informs you when the SMS order has been processed for a certainCmContainer number. You only have to provide access to the CmContainer (forexample, connect the corresponding CmDongle), select it in dSPACE InstallationManager, and start the update. dSPACEe Installation Manager then automatically

License updates



performs the update. You do not have to send files by e-mail to dSPACE, forexample, with ticket IDs.

If you do not have Internet access, you can use an offline update method.However, dSPACE does not recommend this method, because it is inconvenientand time-consuming.

The workflow differs depending on how dSPACE Installation Manager can accessthe CmContainer. Refer to License Update on page 85.

Validity of CodeMeter Licenses

CodeMeter licenses are Release-independent and can be valid for variousdSPACE Releases. Therefore, license handling becomes easier, especially forcustomers with a Software Maintenance Service (SMS) contract.

Introduction

License validity is independent from a specific dSPACE Release. Release-dependent License.dsp files are not used anymore.

Therefore, you can install a new dSPACE Release as soon as it is available. Eachlicense-protected software product is stamped with its release date. You can useevery Release of the product whose release date lies within the maintenanceperiod of the license.

Release-independent licensevalidity

Release date01.11.2017





Release 2017-B Release 2018-A Release 2018-B Release 2019-A Release 2019-B

25.06.2017 (delivery date) 24.06.2019

Maintenance period

Maintenance period The maintenance period limits the usable versions of asoftware product. Software Releases whose release date lies within themaintenance period can be executed. The initial maintenance period ends sixmonths after the delivery date but can be extended by purchasing SMScontracts.

SMS period The SMS period defines the duration of the optional SMScontract. During this time, you automatically receive all updates andenhancements for the software products included in the SMS contract.



To evaluate or to test dSPACE software, dSPACE provides evaluation licenses.There are two forms of evaluation licenses related to the evaluation time:

§ Licenses with a fixed expiration date.

You can use the protected software up to a fixed date, for example, up toMarch 1, 2018.

§ Licenses with a fixed usage period.

The usage period, for example, 60 days, begins with the first use of theactivated license from the related dSPACE product and ends after the usageperiod has expired.

Validity of evaluation licenses

Depending on your order, dSPACE Installation Manager displays certain validityentries for each activated license. For example, you can view the end date of themaintenance period, the expiration date of the license, or information on theusage period (duration, start and end date). Refer to How to Show AvailableLicenses and Their Attributes on page 44.

Viewing license validity

There are certain use scenarios, where the license validity must be extended. Forexample, if you purchase an SMS contract for the first time, if you want toextend an existing SMS contract, or if you want to extend the evaluation time.

In these cases, dSPACE provides license updates to make the modificationsavailable in your CmContainer. Refer to License Update on page 85.

Extending license validity

Methods for Accessing CmContainers

dSPACE Installation Manager provides several methods to access CmContainersfrom a PC. It is possible to manage licenses regardless of whether the PC withthe CmContainer has an Internet connection.

Motivation

Note

Online activation with local access to the CmContainer is the recommendedway to activate, update, and deactivate licenses.

Recommended method



The following table provides an overview of the possible ways to accessCmContainers and the actions that are supported for each license type.

Overview

License Type Action Access of dSPACE Installation Manager to CmContainer

Local Access LAN Access File-BasedAccess

File-Based RemoteAccess

Single-user licenses Activate licenses ✓ ✓ ✓ ✓

Update licenses ✓ ✓ ✓ ✓

Deactivate licenses ✓ - ✓ ✓

Floating networklicenses

Activate licenses ✓ ✓ ✓ ✓

Update licenses ✓ ✓ ✓ ✓

Deactivate licenses ✓ - ✓ ✓

dSPACE Installation Manager must be installed on the PC with direct access tothe CmContainer. The Installation Manager lists the CmContainers it finds on thePC (CmActLicense containers) and that are connected to it (CmDongles). dSPACEInstallation Manager has an Internet connection to dSPACE License Central.

License Central



Local access

CmContainer

Local access to CmContainer

You can use the LAN access method if one of the following cases applies:

§ The PC with dSPACE software and a CmContainer does not have an Internetconnection but is connected to other PCs via LAN. For example, PCs used inHIL test benches.

§ A PC configured as a CodeMeter license server uses a non-Windows operatingsystem and can therefore not run dSPACE Installation Manager.

dSPACE Installation Manager must be installed on a PC that is connected to theLAN. This PC must also be connected to dSPACE License Central via the Internet.dSPACE Installation Manager can then access CmContainers via the LANconnection and automatically performs the required actions and the dataexchange with dSPACE License Central online.

LAN access to CmContainer



License Central



LAN

LAN access

LAN

LAN connection

CmContainer

You have to use this access method if dSPACE Installation Manager cannotaccess the CmContainer at all.

On the PC with the CmContainer, CodeMeter Control Center can be used tocreate the files required for license activation, update, and deactivation. Thesefiles must be transferred between the PC and the PC on which dSPACEInstallation Manager is installed. Do this with a USB stick or via a network folder,for example.

On another PC, dSPACE Installation Manager must be installed and connected todSPACE License Central via the Internet. dSPACE Installation Manager exchangesdata (reads and sends the activation files) with dSPACE License Central online.


Manual transfer of activation files

File-based accessCodeMeter

Control Center

CmContainer

RUC

RAC

License Central


Activation files The files to transfer contain a fingerprint of theCmContainer contents. There are two types of files:

§ Remote activation context (RAC) files. These files are created by CodeMeterControl Center and have to be sent to dSPACE License Central via dSPACEInstallation Manager.

§ Remote activation update (RAU) files. These files are created by dSPACELicense Central and are used to update CmContainers.

File-based access toCmContainer



This method also uses manual file transfer, but CodeMeter Control Center on thePC with the CmContainer is operated from a remote PC. You can use a remotedesktop tool to access the PC with the CmContainer. This tool can be installedon the PC with dSPACE Installation Manager or on any other PC in the LAN tocontrol CodeMeter software and to transfer files manually between the PCs.

Remote access is useful if you want to access multiple CmContainers and workwith CodeMeter software installed on the PCs from only one administrator PC.Another use case is to manage single-user licenses that are not accessible directlyin a LAN.

File-based remote access toCmContainer

License Central


Administrator PCRemote PC


Manual transfer of activation files

Remote desktop connection

LAN

LAN connection

CodeMeter Control Center

CmContainer

RUC

RAC

As shown above, CodeMeter Control Center can be started on a remote PC togenerate the files required for license activation. These files must be transferredbetween the remote PC and an administrator PC. On the administrator PC,dSPACE Installation Manager reads and sends activation files from the remotePC. dSPACE Installation Manager also exchanges data with dSPACE LicenseCentral via the Internet.

Basics on Adding Ticket IDs

In most license management scenarios, for example, license activation, you haveto enter or paste ticket IDs or a ticket group ID in a specific edit field to start theprocess. Each time you add ticket IDs in the edit field, dSPACE InstallationManager connects to dSPACE License Central, gets the current ticketinformation, and displays it.

Motivation

With the Save to File functionality, you can save the displayed ticket informationto an XML file. The saved information can be regarded as a snapshot. A timestamp is added to the file name.

Saving ticket information tofile



You can use the file for documentation purposes, or you later can import the filevia the Import from File functionality. This makes it much easier to handlemultiple ticket IDs.

The following illustration shows that tickets from two ticket group IDs can besaved in one file.

Add ticket group ID A

Add ticket group ID B

2017-10-27-07-40.xml

XML

</>Save to File Import from File

Note

Each time you import a file, the contained ticket information is updatedimmediately from dSPACE License Central.

You can delete single ticket entries from the overview by selecting the entry andpressing the Del key.

Deleting entries

Requirements for Communication

To communicate with dSPACE License Central (via a web gateway), withCodeMeter tools from Wibu-Systems or other PCs in a LAN, your PC must beable to establish a TCP/IP connection.

Purpose

To access dSPACE License Central from your PC, you need an Internetconnection. dSPACE Installation Manager connects tohttps://licensing.dspace.de/gateways, HTTPS, Port 443. dSPACE InstallationManager can work with proxy servers that you might use. It can also handleproxy servers with authentication (user name, password).

Communication with dSPACELicense Central

Requirements for Communication


Tip

dSPACE Installation Manager uses the same settings for communication asMicrosoft Internet Explorer. Therefore, you can change the setting in theInternet Explorer to solve any communication problems. In addition, you cancheck the Internet connection to dSPACE License Central by entering thefollowing address in your web browser: https://licensing.dspace.de

Local firewalls and IT appliances must be configured accordingly to grant dSPACEInstallation Manager access to the Internet.

For LAN communication between CodeMeter software on different PCs, forexample, for connections between floating network license servers and clients, astandard TCP/UDP protocol is required. The default port number is 22350, whichis an officially registered port number (IANA). If needed, you can change the portnumber.

For communication with CmContainers on remote PCs in a LAN, dSPACEInstallation Manager uses the CodeMeter functionality. Thus, the connected PCsrequire the same open TCP/IP network port: 22350 (TCP and UDP).

Internal LAN communication

Compatibility with Earlier Releases

§ Green WibuKey dongles must be replaced and their License ID migrated toCmDongles. The CmDongles are automatically delivered with dSPACE Release2017-B to owners of WibuKey dongles with licenses covered by a SoftwareMaintenance Service (SMS) contract.

§ CmDongles (Rev. 3-xxxx) delivered for dSPACE Release 2014-B up to andincluding dSPACE Release 2017-A are not prepared to use the CodeMeterlicensing technology. They must be migrated to use dSPACE Release 2017-Band later.

§ CmDongles shipped for dSPACE Release 2017-B and later support CodeMeterlicensing without modifications.

Note

All CmDongles (Rev. 3-xxxx), including those shipped with dSPACE Release2017-B and later, can still be used with dSPACE Releases 2017-A and earlier,because they can emulate WibuKey dongles.

Compatibility of dongles



The parallel use of old and new licensing technologies is possible:

§ You can use the WibuKey (or FlexNet) licensing technology required forproducts of earlier dSPACE Releases in parallel with the CodeMeter licensingtechnology on the same PC.

§ You can use the same CmDongle for all dSPACE Releases. You can even useWibuKey dongles and CmDongles on the same PC if the WibuKey dongles arenot replaced by CmDongles. This might be the case if the associated licensesare not covered by an SMS contract.

For floating network licenses, the CodeMeter licensing technology cannotprovide downward compatibility with Releases earlier than dSPACE Release2017-B. If you need to use product versions of dSPACE Releases earlier thandSPACE Release 2017-B, you have to keep your FlexNet License Server running inparallel. Both FlexNet and CodeMeter floating network servers can be hosted onthe same PC.

Note

The dSPACE EULA does not allow FlexNet and CodeMeter license servers toprovide the same floating network license in parallel. If you have anyquestions or encounter any problems, contact dSPACE Support.

Parallel use of licensingtechnologies

To manage licenses for software installations from dSPACE Release 2017-A andearlier, you have to use the dSPACE License Manager (Legacy). This is aseparate tool that is always installed together with dSPACE Installation Manager5.0 and later.

dSPACE License Manager (Legacy) provides the same license managementfunctionalities as dSPACE Installation Manager 4.3 (distributed with dSPACERelease 2017-A) and earlier. This applies to dongle licenses (based on theWibuKey technology) as well as to floating network licenses (based on theFlexNet technology).

Managing licenses for earlierdSPACE Releases

Compatibility with Earlier Releases


Starting with dSPACE Release 2018-A


Use Case 1: New Customer or Starting with New CmDongle ................. 26

Use Case 2: Starting with WibuKey Dongle ............................................ 28

Use Case 3: Starting with Old CmDongles (Rev. 2‑xxxx) .......................... 30

Use Case 4: Starting with Old CmDongles (Rev. 3‑xxxx) .......................... 31

Use Case 5: Updating the Maintenance Period of ActivatedLicenses (SMS Contracts) ....................................................................... 34

FNL Use Case 1: New Customer or Starting with a New FloatingNetwork License Installation .................................................................. 35

FNL Use Case 2: Migrating Floating Network Licenses ............................ 37

FNL Use Case 3: Updating the Maintenance Period of ActivatedLicenses (SMS Contracts) ....................................................................... 38




Use Case 1: New Customer or Starting with New CmDongle

Your use case

UseCase

CurrentDongle

Dongle Provided by dSPACE License Overview DongleMigration

Instructions

1 - CmDongle Type 4

3xxx

Serial number

XLSX

File name pattern:

<OrderNumber>.xlsx

<OrderNumber> matches yourpurchase order number.

- Required steps:§ Install dSPACE Release

2018-A§ Activate licenses§ Decrypt encrypted

software archivesFor details, see below.

dSPACE has created videos to introduce you to the new CodeMeter licensingtechnology. The following video addresses your use case:

§ Installing dSPACE Software

§ New Licensing for dSPACE Products: An Overview

§ Activating Licenses and Decrypting Software Archives

Introduction videos

dSPACE has sent you an e-mail with an Excel file, called License Overview. Youreceived one Excel file per purchase order. The former License.dsp andKeys.dsp files are not applicable and not needed for dSPACE Release 2017-Band future Releases. The Excel files provide the license information and replacethe old license files. They contain ticket IDs for the Release 2018-A licenses.There is one ticket ID for each software product.

The file name of the License Overview resembles the number of your purchaseorder as closely as Windows file name conventions permit. The licenses can beactivated on any CmDongle. With your shipment, you may receive one or moreCmDongles Type 4, but you may also activate the new licenses on existingCmDongles Type 4 from an earlier delivery.

The License Overview lists the required ticket IDs for the purchased products asfollows:

License Overview



http://www.dspace.com/go/NewInstallation

http://www.dspace.com/go/NewLicOverview

http://www.dspace.com/go/NewLicActivation

Tip

dSPACE recommends using the same PC for license activation as you use forinstalling and running dSPACE software.

If you want to set up a separate PC only for license activation, the PC must meetthe following requirements:

§ Windows 7 or Windows 10 (64-bit versions only)

§ At least dSPACE Installation Manager 5.1, installed either together withdSPACE Release 2018-A or downloaded from http://www.dspace.de/go/im.

§ An Internet connection for accessing dSPACE License Central must exist (mightrequire appropriate proxy settings).

§ One free USB port

Note

If you want to install dSPACE software (ControlDesk, TargetLink, etc.) on thesame PC, the PC must meet additional requirements. Refer to Appendix:System Requirements ( Installing dSPACE Software).

Workflow steps1. Optional: Install dSPACE Release 2018-A by using a downloaded image or the

distributed DVDs. Refer to How to Install dSPACE Software ( InstallingdSPACE Software).

Install the product sets containing the products you want to use and forwhich you have licenses.

2. Mandatory: Activate CodeMeter licenses on the CmDongle. Refer to How toActivate Licenses (Local Access to CmContainer) on page 70.

3. Optional: To use software of dSPACE Release 2018-A, decrypt the encryptedparts of the installed software products by using the CmDongle with theCodeMeter licenses you just activated. Refer to How to Decrypt EncryptedArchives of dSPACE Software Installations ( Managing dSPACE SoftwareInstallations).

4. Optional: Verify that Release 2018-A works with the CmDongle.

5. Optional: To use software of dSPACE Release 2017-A or earlier as well,request the corresponding legacy license files from dSPACE.

6. Optional: Install the earlier Release by using the legacy license files. Managelegacy licenses in dSPACE License Manager (Legacy), which is installedtogether with dSPACE Installation Manager 5.1 and later.

Getting started

Use Case 1: New Customer or Starting with New CmDongle


http://www.dspace.de/go/im

Use Case 2: Starting with WibuKey Dongle

Your use case

UseCase

Current Dongle Dongle Provided bydSPACE

LicenseOverview

Dongle Migration Instructions

2

# 8899

WibuKey dongle Type 1

License ID (dongle number)

CmDongle Type 6

3xxx

Serial number

XLSX

File name pattern:

WKID-xxxxx.xlsx

xxxxx matchesthe dSPACELicense ID(dongle number).

# 8899 Installation Manager

Migrate

License ID 3xxx

WibuKey dongles must be replacedand the license IDs stored on themmust be transferred to CmDongles.

Requiredsteps:§ Migrate

licenseinformation

§ InstalldSPACERelease2018-A

§ Activatelicenses

§ Decryptencryptedsoftwarearchives

For details,see below.

You have been using a WibuKey dongle (Type 1). This type of dongle cannot beused for CodeMeter licensing. Therefore dSPACE has sent you a CmDongle (Type6) via mail. You must migrate the license ID (dongle number) from the WibuKeydongle to the CmDongle, then activate the licenses for dSPACE Release 2018-Aon the CmDongle. The CmDongle can then be used for earlier dSPACE Releases(2017-A and earlier) as well as for Release 2017-B and later.

dSPACE has created videos to introduce you to the new CodeMeter licensingtechnology. The following videos address your use case:

§ Migrating from WibuKey Dongles




Introduction videos

dSPACE has sent you an e-mail with an Excel file, called License Overview. Theformer License.dsp and Keys.dsp files are not applicable and not needed fordSPACE Release 2017-B and future Releases. The Excel sheets provide the licenseinformation and replace the old license files. They contain ticket IDs for theRelease 2018-A licenses. There is one ticket ID for each software product.

For this particular dongle migration use case the License Overview sheet has aspecial format. Its file name is WKID-xxxxx.xlsx. The xxxxx number mustmatch the license ID of the WibuKey dongle you have been using.

License overview



http://www.dspace.com/go/MigrationWibu




For migration, you need a specific ticket ID, which is listed separately in theoverview. Refer to the following illustration.

This special file format is used only for the initial migration. It will not be usedagain for this dongle.

The licenses for dSPACE Release 2018-A can be activated only on the newCmDongle after completing the dongle migration.

Tip

dSPACE recommends using the same PC for dongle migration and licenseactivation as you use for installing and running dSPACE software.

If you want to set up a separate PC only for dongle migration and licenseactivation, the PC must meet the following requirements:




§ Two free USB ports

Note





2. Mandatory: Migrate the existing WibuKey dongle to the new CmDongle.Refer to How to Migrate from a WibuKey Dongle on page 53.

Getting started

Use Case 2: Starting with WibuKey Dongle



3. Mandatory: Activate CodeMeter licenses on the CmDongle. Refer to How toActivate Licenses (Local Access to CmContainer) on page 70.

4. Optional: To use software from dSPACE Release 2018-A, decrypt theencrypted archives of the installed software products by using the CmDonglewith the CodeMeter licenses you just activated. Refer to How to DecryptEncrypted Archives of dSPACE Software Installations ( Managing dSPACESoftware Installations).

5. Mandatory: Verify that dSPACE Release 2018-A works with the CmDongle. Ifrelevant, verify that the older dSPACE Releases work as expected with theCmDongle.

6. Mandatory: Disconnect the WibuKey dongle and discard it. It cannot be usedanymore.

Use Case 3: Starting with Old CmDongles (Rev. 2‑xxxx)

Your use case

UseCase

Current Dongle Dongle Providedby dSPACE

LicenseOverview

Dongle Migration Instructions

3 CmDongle Type 2

xxxx


CmDongle Type 5

CmDongle Type 5:§ Does not contain

any licenseinformation.

- Migrate

dSPACE Dongle Migration tool

After migration, the CmDongle Type 5is equivalent to a CmDongle Type 3.

Required steps:§ Migrate license

informationFor details, seebelow.

You are still using a first-generation CmDongle Type 2 (serial number startingwith 2-xxxx, white connector).

In Q1/2017, dSPACE sent you a new CmDongle Type 5 (serial number startingwith 3-xxxx, red connector, no tag attached). You were encouraged to migratefrom the old dongle immediately. If you have not done so yet, this step is nowmandatory. Download the instructions and the dongle migration tool from ourwebsite (www.dspace.com/go/donglemigration). If you need dSPACE to sendyou additional replacement dongles, contact your local dSPACE salesrepresentative.

To migrate the CmDongle, the host PC must meet the following requirements:



§ Two free USB ports

Getting started



http://www.dspace.com/go/donglemigration

Workflow steps1. Mandatory: Download the dSPACE Dongle Migration tool from

www.dspace.com/go/donglemigration and install it on the PC.

The dSPACE Dongle Migration tool is self-contained and does not require anyother dSPACE software to be installed on the host PC.

2. Mandatory: Connect the CmDongle Type 2 and the CmDongle Type 5 to thePC.

3. Mandatory: Migrate the license information.

4. Mandatory: Switch the dongle tag from the CmDongle Type 2 to theCmDongle Type 5.

5. Mandatory: Disconnect the CmDongle Type 2 and dispose it as electronicwaste. It cannot be used anymore.

6. Mandatory: The new CmDongle is now equivalent to a CmDongle Type 3.Continue with Use Case 4: Starting with Old CmDongles (Rev. 3‑xxxx)on page 31.


Your use case

UseCase

Current Dongle DongleProvidedby dSPACE

License Overview Dongle Migration Instructions

4 CmDongle Type 3

xxxx


-XLSX

File name pattern:

WKID-xxxxx.xlsx

<xxxxx> matches yourlicense ID (donglenumber).


Migrate

3xxx

Required steps:§ Migrate license

information§ Install dSPACE Release

2018-A§ Activate licenses§ Decrypt encrypted

software archivesFor details, see below.

You have been using a CmDongle Type 3. This type of dongle must be updatedso you can use it with the CodeMeter technology. After you migrate the licenseinformation, you can activate the licenses for dSPACE Release 2018-A on theCmDongle. The CmDongle can then also be used for earlier dSPACE Releases(2017-A and earlier) as well as for Release 2017-B and later.

dSPACE has created videos to introduce you to the new CodeMeter licensingtechnology. The following videos address your use case:

§ Migrating from Old CmDongles




Introduction videos




http://www.dspace.com/go/MigrationOldCM




dSPACE has sent you an e-mail with an Excel file, called License Overview. Theformer License.dsp and Keys.dsp files are not applicable and not needed fordSPACE Release 2017-B. The Excel files provide the license information andreplace the old license files. They contain ticket IDs for the Release 2018-Alicenses. There is one ticket ID for each software product.

For this particular dongle migration use case the License Overview file has aspecial format. Its name is WKID-xxxxx.xlsx. The xxxxx number must matchthe license ID of the CmDongle you are currently using and the tickets for the2018-A licenses can be activated only on that particular CmDongle after youmigrated the CmDongle. This special file format is used only for the initialmigration. It will not be used again for this dongle.


License Overview

Tip

dSPACE recommends using the same PC for dongle migration and licenseactivation as you use for installing and running dSPACE software.

If you want to set up a separate PC only for dongle migration and licenseactivation, the PC must meet the following requirements:





Note


Getting started







2. Mandatory: Migrate the CmDongle you are using. Refer to How to Migratefrom an Old CmDongle on page 57.

Note

CmDongles contain a microchip with firmware code. To use CmDonglesType 3 with CodeMeter technology, they require a minimum firmwareversion. During migration, you are prompted to perform a firmwareupdate. To do this, an Internet connection to the Wibu-Sytems updateserver is mandatory. The following message might be displayed if anerror occurs during the firmware update: "Connection to the updateserver failed (Error WB5000). Please check the selected server name andyour network connection." In this case, refer to FAQ 360(http://www.dspace.com/faq?360) for a solution.

3. Mandatory: Activate CodeMeter licenses on the migrated CmDongle. Refer toHow to Activate Licenses (Local Access to CmContainer) on page 70.

4. Optional: To use software from dSPACE Release 2017-B, decrypt theencrypted parts of the installed software products by using the CmDonglewith the CodeMeter licenses you just activated. Refer to How to DecryptEncrypted Archives of dSPACE Software Installations ( Managing dSPACESoftware Installations).

5. Optional: Verify that dSPACE Release 2018-A works with the CmDongle. Ifrelevant, verify that the older dSPACE Releases work as expected with theCmDongle.



http://www.dspace.com/faq?360

Use Case 5: Updating the Maintenance Period of Activated Licenses (SMSContracts)

Your use case

UseCase

Current Dongle DongleProvided bydSPACE

License Overview DongleMigration

Instructions

5 CmDongle Type 3

xxxx


- or -

CmDongle Type 4

3xxx

Serial number

-XLSX

File name pattern:

CM-3-xxxxx.xlsx

3-xxxxx matches the serial numberof the CmDongle.

- Required steps:§ Update licensesFor details, see below.

If you use a CmDongle Type 3 or Type 4 and the CodeMeter licenses werealready activated on a CmDongle, you can easily update licenses, for example, byentering a Software Maintenance Service (SMS) contract to extend themaintenance period of the licenses.


§ New Licensing: Updating Licenses

Introduction videos

dSPACE has sent you an e-mail with an Excel file, called License Overview. Youreceived one Excel file for each CmDongle for which you ordered the SMS. Thefiles are sent only to document the maintenance period update. The ticket IDsare the same as those used when initially activating the licenses. If you did notpurchase SMS for all licenses on a CmDongle, the License Overview shows onlythe tickets of the licenses that can be updated. The name of a License Overviewfile is CM 3-xxxxx.xlsx, with 3-xxxxx matching the serial number of theCmDongle with the licenses to be updated.

If your purchase order contains SMS for several CmDongles, one LicenseOverview is generated per CmDongle. The files might then be delivered in a ZIParchive (PIZ), one archive per purchase order. In this case, save and unzip thePIZ file.

License Overview



http://www.dspace.com/go/NewLicUpdate

Tip

dSPACE recommends using the same PC for license updates as you use forinstalling and running dSPACE software.

If you want to set up a separate PC only for license updates, the PC must meetthe following requirements:





Note


Workflow steps1. Mandatory: Update CodeMeter licenses on the CmDongle. Refer to How to

Update Licenses (Local Access to CmContainer) on page 89.

Getting started

FNL Use Case 1: New Customer or Starting with a New Floating NetworkLicense Installation

Your use case

Use Case License Overview Instructions

FNL 1XLSX

File name pattern:

<OrderNumber>.xlsx

<OrderNumber> matches the number of yourpurchase order.

Required steps on the license server:§ Configure one PC in the network as the dSPACE License Server§ Activate licenses on the serverRequired steps on each license client:§ Install dSPACE Release 2018-A on dSPACE License Clients§ Decrypt encrypted software archivesFor details, see below.




Introduction videos

FNL Use Case 1: New Customer or Starting with a New Floating Network License Installation





dSPACE has sent you an e-mail with an Excel file, called License Overview. Youreceived one Excel file per purchase order. The former License.dsp,License.dat and Keys.dsp files are not applicable and not needed for dSPACERelease 2017-B and future Releases. The Excel files provide the licenseinformation and replace the old license files. They contain ticket IDs for theRelease 2018-A licenses.

The file name of the License Overview resembles the number of your purchaseorder as closely as Windows file name conventions permit.


License Overview

An important attribute of floating network licenses is the license quantity, whichdefines the number of licenses that can be used on client PCs at the same time.Floating network licenses can have a quantity ≥ 1.

Note

Unfortunately, the License Overviews do not indicate whether a particularticket ID is for a single-user license or for a floating network license. If yourpurchase order contained only floating network licenses, all ticket IDs applyfor floating network licenses. If you are not sure what license type the ticketIDs are associated with, check dSPACE Installation Manager. If it lets youactivate a ticket ID in a dSPACE Activation Container, the ticket ID isassociated with a floating network license. See below.

Installing dSPACE License Clients The PC must meet system requirementsso you can use dSPACE software on it. Refer to Appendix: System Requirements( Installing dSPACE Software).

Getting started



Repeat the following steps on every dSPACE License Client:

1. Mandatory: Install dSPACE Release 2018-A by using a downloaded image orthe distributed DVDs. Refer to How to Install dSPACE Software ( InstallingdSPACE Software).


2. Mandatory: Add the license server to the server search list by entering thename or the IP address of the license server. Refer to How to Set up aConnection Between Client and Server on page 133.

By default, localhost is added to the server search list during softwareinstallation to avoid unwanted network broadcasts by the CodeMeterRuntime software.

3. Mandatory: To use software of dSPACE Release 2018-A, decrypt theencrypted parts of the installed software products by using the CmDonglewith the CodeMeter licenses you just activated. Refer to How to DecryptEncrypted Archives of dSPACE Software Installations ( Managing dSPACESoftware Installations).

Installing dSPACE License Server The PC that you want to configure as thedSPACE License Server, should meet the following requirements:



1. Mandatory: Install dSPACE Installation Manager 5.1, either together withdSPACE Release 2018-A or downloaded from http://www.dspace.de/go/im.

2. Mandatory: Configure CodeMeter Runtime as the floating network server.Refer to How to Set up the dSPACE License Server on page 129.

3. Mandatory: Activate CodeMeter floating network licenses on the licenseserver. Refer to How to Activate Licenses (Local Access to CmContainer)on page 70.

FNL Use Case 2: Migrating Floating Network Licenses

Your use case


FNL 2XLSX

File name pattern:

FlexID-xxxxx.xlsx

<xxxxx> matches your former FlexNet Publisherlicense ID.

Proceed as described in FNL Use Case 1: New Customer orStarting with a New Floating Network License Installationon page 35.

You have been using a FlexNet floating network license server. The FlexNetlicensing technology and CodeMeter licensing technology are not compatible.

FNL Use Case 2: Migrating Floating Network Licenses



However, FlexNet and CodeMeter floating network servers can be hosted on thesame PC at the same time.

dSPACE has sent you an e-mail with an Excel file, called License Overview. Theformer License.dsp, License.dat and Keys.dsp files are not applicable andnot needed for dSPACE Release 2018-A.

The Excel files provide the license information and replace the old license files.They contain ticket IDs for the Release 2018-A licenses.

For this particular floating network migration use case, the License Overview filehas a special format. Its name is FlexID-xxxxx.xlsx. The xxxxx numbermatches your former FlexNet Publisher license ID.

This special file format is used only for the initial migration. It will not be usedagain.

License Overview

Continue with FNL Use Case 1: New Customer or Starting with a New FloatingNetwork License Installation on page 35.

Getting started

FNL Use Case 3: Updating the Maintenance Period of Activated Licenses (SMSContracts)

Your use case


FNL 3XLSX

File name pattern:

CM-130-xxxxx.xlsx

<130-xxxxx> matches the serial number of theCmActLicense container (dSPACE ActivationContainer).

XLSX

File name pattern:

CM-3-xxxxx.xlsx

<3-xxxxx> matches the serial number ofthe CmDongle.

Required steps:§ Update licensesFor details, see below.

If the CodeMeter licenses were already activated in a CmActLicense container oron a CmDongle, you can easily update licenses, for example, by entering aSoftware Maintenance Service (SMS) contract to extend the maintenance periodof the licenses.

dSPACE has sent you an e-mail with an Excel file, called License Overview. Youreceived one Excel file for each CmContainer for which you ordered the SMS.

The files are sent only to document the maintenance period update. The ticketIDs are the same as those used when initially activating the licenses. If you did

License Overview



not purchase SMS for all licenses in a CmContainer, the License Overview showsonly the tickets of the licenses that can be updated.

The name of the License Overview file depends on the CmContainer type used:

§ CM-130-xxxxx.xlsx, with 130-xxxxx matching the serial number of theCmActLicense container (dSPACE Activation Container) with the licenses to beupdated.

§ CM-3-xxxxx.xlsx, with 3-xxxxx matching the serial number of theCmDongle with the licenses to be updated.

Use the same PC you set up to activate the floating network licenses.

Workflow steps1. Mandatory: Update CodeMeter floating network licenses. Refer to How to

Update Licenses (Local Access to CmContainer) on page 89.

Getting started

FNL Use Case 3: Updating the Maintenance Period of Activated Licenses (SMS Contracts)


Showing Available Licenses, CmContainers, andTickets

dSPACE Installation Manager provides several overviews to show detailedinformation on available licenses, CmContainers, tickets and their attributes.

Motivation


How to Show Available CmContainers and Their Attributes ................... 41

How to Show Available Licenses and Their Attributes ............................. 44

How to Request and Show Ticket Information ....................................... 47


How to Show Available CmContainers and Their Attributes

To view available CmContainers and their attributes, you can use dSPACEInstallation Manager.

Objective

With dSPACE Installation Manager, the following CmContainers are accessibleand displayed:

§ All CmDongles connected to your PC.

dSPACE Installation Manager can access and therefore display only CmDongleswhich contain a dSPACE firm code. CmDongles without a dSPACE firm codecannot be displayed. Therefore you cannot use them to activate dSPACElicenses, for example.

§ All CmActLicense containers on your PC.

Accessible CmContainers

Showing Available Licenses, CmContainers, and Tickets


§ All CmContainers in a LAN connected to a PC that is configured as a dSPACELicense Server. The server must be listed in the server search list on your PC.

To show available CmContainers and their attributes

1 From Start – All Programs – dSPACE Installation Manager, select dSPACEInstallation Manager.

dSPACE Installation Manager opens.

2 Click the Licensing – CmContainer tab.

Method

3 Check the setting of the Show only local items checkbox. Clear thischeckbox if you also want to view CmContainers that are accessible in a LAN.

All accessible CmContainers are displayed:

4 Right-click the CmContainer page and select Configure Columns from thecontext menu.

5 In the Configure Columns dialog, select the attributes you want to displayon the CmContainer page.



The following attributes are available:

Attribute Description

Name The name of the CmContainer.If the selected CmContainer is a CmDongle, you canmodify this entry via Rename.

Serial number The unique serial number of the CmContainer.Valid for CmDongles shipped with dSPACE Release 2017-B and later: The serial number is also printed on thedongle tag.

CmContainerType

The type of the CmContainer:§ CmDongle§ dSPACE Activation Container. The dSPACE Activation

Container is a CmActLicense container. With dSPACERelease 2017-B and dSPACE Release 2018-A,CmActLicense containers support only floating networklicenses.

WibuKey ID A special ID used to emulate the license ID (donglenumber) required for dSPACE Release 2017-A and earlier.

Location The location of a CmContainer:§ Local: The CmContainer is located on your PC.§ LAN: The CmContainer is located on a PC connected to

the LAN.

Version The CmContainer version number.

FirmwareUpdate

Indicates whether the firmware of the CmContainer isoutdated and needs to be updated. If Required isdisplayed, refer to How to Update the Firmware of aCmDongle on page 61.

Info Provides further status information on the CmContainer.Possible entries are:§ Hardware based CmContainer to activate licenses on it.§ Software based CmContainer to activate licenses on it.§ Migration required via 'dSPACE Dongle Migration'

utility.§ Migration required. Go to 'License Administration -

Dongle Migration'.§ CmContainer not prepared for license activation. Go to

'License Administration - Manual CmContainerCreation'.

§ Unsupported CmDongle. No WibuKeyID found.§ Unsupported CmDongle. No ID_DSPACE entry found.

Server Address The IPv4 address of the PC or license server that containsthe CmContainer.

Server Name The name of the dSPACE License Server that hosts theCmContainer with the floating network licenses.

How to Show Available CmContainers and Their Attributes


dSPACE Installation Manager displays accessible CmContainers with the selectedattributes.

Note

dSPACE Installation Manager stores the settings in the Configure Columnsdialog.

Result

How to Show Available Licenses and Their Attributes

To view available dSPACE licenses and their attributes, you can use dSPACEInstallation Manager.

Objective

With dSPACE Installation Manager, the following licenses are accessible anddisplayed:

§ All licenses in CmContainers (CmDongles or CmActLicense containers) on yourPC.

§ All licenses in CmContainers in a LAN network connected to a PC that isconfigured as a dSPACE License Server. The server must be listed in the serversearch list on your PC.

In a LAN, dSPACE Installation Manager can show only floating networklicenses.

Note

Single-user licenses are not accessible and therefore not displayed.

Accessible licenses

To show available licenses and their attributes



2 Click the Licensing – License Overview tab.

Method



3 Check the setting of the Show only local items checkbox. Clear thischeckbox if you also want to view licenses that are accessible in your LAN.

4 Right-click the License Overview page and select Configure Columns fromthe context menu.

5 In the Configure Columns dialog, select the attributes you want to displayon the CmContainer page.

How to Show Available Licenses and Their Attributes


The following attributes are available:


License Name The name of the license.

License Type The type of the license. Possible entries: Standard,Unknown.

Location The location where the license is accessible:§ Local: The license is located on your PC.§ LAN: The license is a floating network license and

located on a dSPACE License Server in the LAN.

Accessibility The type of the license:§ Single-user§ Floating network

License Quantity Number of licenses that can be used in parallel on clientPCs. The quantity depends on your order. Floatingnetwork licenses can have quantities ≥ 1.

Maintenance End End date of your maintenance period.

CmContainer The serial number of the CmContainer where therelated license is activated.Valid for CmDongles shipped with dSPACE Release2017-B and later: The serial number is also printed onthe dongle tag.

CmContainerName

The name of the CmContainer.

CmContainerType

The type of the CmContainer where the related licenseis activated:§ CmDongle§ dSPACE Activation Container. The dSPACE Activation

Container is a CmActLicense container. With dSPACERelease 2017-B, CmActLicense containers supportonly floating network licenses.

Product Code The product code identifies the license entry via aunique code.

Linger Time Some floating network licenses have linger times. Aftera license is released by the software product, it remainsreserved for the same license client PC for the durationof the linger time. After the linger time has elapsed, thelicense can be used by other license clients.

Server Address The IPv4 address of the host PC or server that containsthe CmContainer with the license.

Server Name The name of the dSPACE License Server that hosts theCmContainer with the floating network licenses.

Ticket ID The ticket ID for the license. Ticket IDs are used, forexample, for license activation.

Expiration Date The date when the license expires.




Usage period The time in days for which the license can be used.The period begins with the first use of the activatedlicense from the related dSPACE product and ends afterthe usage period has expired.

Usage PeriodStart

Date when a dSPACE product first uses a license with adefined usage period.

Usage Period End Expiration date of a license with a defined usage period.

dSPACE Installation Manager displays available dSPACE licenses with the selectedattributes.

Note

dSPACE Installation Manager stores the settings in the Configure Columnsdialog.

Result

How to Request and Show Ticket Information

dSPACE uses a ticket-based system to manage licenses, for example, to activatelicenses.

With dSPACE Installation Manager, you can request the current information ofyour tickets from dSPACE License Central and view it. For example, you can seelicenses and their activation states, and the current CmContainer on which theyare activated.

Objective

§ An Internet connection for accessing dSPACE License Central exists.

§ A valid ticket ID is available.

Preconditions

To request and show ticket information



2 Click the Licensing – License Administration tab.

Method



3 Select Show Ticket Information as shown in the following illustration:

4 Enter a ticket ID or ticket group ID in the edit field.



5 Click Add.

dSPACE Installation Manager connects to dSPACE License Central, gets ticketinformation from the database, and displays the information as follows:

The following information is available:


License Name The name of the license.

Supported Action The action you can perform with the license. Possibleactions are:§ None§ Activation§ Deactivation§ Update

License State The state of the license. Possible states are:§ Activated§ Not activated

Confirmation State Confirmation is the last step in activating, updatingand deactivating a license. Possible states are:§ None§ Confirmed§ Unconfirmed

CurrentCmContainer

The CmContainer where the related license isactivated.

RecentCmContainer

The CmContainer where the related license wasactivated before.

SupportedCmContainerTypes

The CmContainer type that is supported for therelated license. Possible types are:§ CmDongle§ dSPACE Activation Container. The dSPACE Activation

Container is a CmActLicense. With dSPACE Release2017-B and dSPACE Release 2018-A, CmActLicensecontainers support only floating network licenses.

Ticket ID The ticket ID of the related license.



dSPACE Installation Manager gets the current state of your tickets from dSPACELicense Central and displays this information.

Result



Dongle Migration

Dongles delivered for earlier Releases cannot be used for the new CodeMeterlicense technology. Therefore, dongle migration is required for these donglesbefore you can continue with the workflow, for example, to activate licenses.

CmDongles shipped for dSPACE Release 2017-B and later support CodeMeterlicensing without modifications.

Motivation


Basics on Dongle Migration ................................................................... 51

How to Migrate from a WibuKey Dongle ............................................... 53

How to Migrate from an Old CmDongle ................................................ 57

How to Disable a WibuKey Dongle ........................................................ 60

How to Update the Firmware of a CmDongle ........................................ 61


Basics on Dongle Migration

Depending on which dongle you already use (for installations of dSPACE Release2017-A and earlier), one of the following scenarios applies.

Migrate from WibuKey dongle WibuKey dongles must be replaced and thelicense ID stored on a WibuKey dongle must be migrated to a CmDongle.

CmDongles are automatically delivered with dSPACE Release 2017-B to ownersof WibuKey dongles with licenses covered by a Software Maintenance Service(SMS) contract. When shipped, the new CmDongles do not contain any licenseinformation.

Migration scenarios

Dongle Migration


License

Central


License code

MigratedCmDongle

# 8899

WibuKey dongle


License code

# 8899

During migration, the WibuKey dongle is disabled and can no longer be used.After migration, the CmDongle is prepared to use the CodeMeter licensetechnology. Additionally, the CmDongle contains the WibuKey ID of theWibuKey dongle. This ID is required to use the CmDongle with dSPACE Release2017-A and earlier.

Migrate from old CmDongle CmDongles delivered for dSPACE Release2014-B up to dSPACE Release 2017-A are not prepared to use the CodeMeterlicensing technology. They must be migrated to use dSPACE Release 2017-B andlater.

License

Central


License code

MigratedCmDongle


License code

CmDongle Rev. 3-xxx

During migration the license information is modified. After migration, theCmDongle is prepared to use the CodeMeter license technology. MigratedCmDongles still contain the embedded WibuKey ID. This ID is required to use theCmDongle with dSPACE Release 2017-A and earlier.

Disable WibuKey dongle In some use scenarios, dSPACE prompts you toreturn a WibuKey dongle. This is necessary to continue with the steps in yourworkflow. As an alternative to returning the WibuKey dongle, you can disable itwith dSPACE Installation Manager.

License

Central


License code

# 8899

WibuKey dongle


License code

# 8899

During the disabling process, the license ID is deleted from the dongle.Afterwards, you can no longer use the WibuKey dongle.

After migration, all CmDongles (Rev. 3-xxxx), including those shipped withRelease 2017-B and later, can still be used with dSPACE Releases 2017-A andearlier, because they can emulate WibuKeys. As of dSPACE Release 2017-B, theyalso support the CodeMeter licensing technology.

Compatibility of migrateddongles with earlier Releases

Dongle Migration


How to Migrate from a WibuKey Dongle

WibuKey dongles must be replaced and the license ID (stored on the WibuKeydongle) must be migrated to CmDongles.

Objective


§ Two USB ports are available for connecting the WibuKey dongle and the newCmDongle.

§ A ticket ID for dongle migration is available.

§ A new CmDongle that does not contain any license information, e.g., aWibuKey ID is available.

Note

It is not possible to store or migrate more than one WibuKey ID to the sameCmDongle.

Preconditions

If the migration process is interrupted (e.g., if the connection to dSPACE LicenseCentral is lost) no license information will be lost and no dongle will becorrupted. Find the reason for the interruption and resolve it. Then restart themigration. The old WibuKey dongle is no longer usable only if the migration wassuccessful.

Interruption of the migrationprocess

To migrate from a WibuKey dongle

1 Connect the WibuKey dongle and the CmDongle to the host PC.



Method




4 Select Dongle Migration and click Next.

5 Select Migrate from WibuKey.

6 Select the WibuKey dongle you want to migrate from.

If no dongle is listed, click the Rescan button to reload the dongleinformation.

7 Click Next.

8 Enter or paste the ticket ID for dongle migration you received from dSPACEvia e-mail in the text field and click Add.

Dongle Migration


The required ticket ID is displayed in the license overview sheet:

Note

The license ID of the WibuKey dongle to migrate and the WibuKeydongle number preceding the ticket ID in the license overview sheetmust match.

dSPACE Installation Manager connects to dSPACE License Central, gets ticketinformation from the database, and displays the information as follows:



9 Click Next and select the CmDongle you want to migrate to.

Note

The CmDongle you want to migrate to must have the followingcharacteristics:

§ No WibuKey ID entry. The WibuKey ID column must display n/a.

§ Up-to-date firmware. If dSPACE Installation Manager displaysRequired in the Firmware Update column, a firmware update isnecessary. Refer to How to Update the Firmware of a CmDongleon page 61.

10 Click Next.

A confirmation prompt is displayed.

11 Click Yes to start the migration.

dSPACE Installation Manager automatically performs the migration processand the data exchange with dSPACE License Central.

Note

Do not remove any connected dongle during the migration process.

Dongle Migration


When the migration is completed, dSPACE Installation Manager displays theresult as follows:

12 Click Close.

The WibuKey is disabled and can no longer be used. The CmDongle is preparedfor using the CodeMeter license technology and contains the WibuKey ID of theWibuKey dongle. This ID is required to use the CmDongle in combination withdSPACE Release 2017-A and earlier.

Result

How to Migrate from an Old CmDongle

CmDongles delivered before dSPACE Release 2017-B are not prepared to use theCodeMeter licensing technology. They must be migrated to use dSPACE Release2017-B and later.

Objective


§ The firmware of the CmDongle is up to date. Refer to How to Update theFirmware of a CmDongle on page 61.

Preconditions



To migrate from an old CmDongle

1 Connect the CmDongle to the PC.



Method



5 Select Migrate from old CmDongle.

Dongle Migration


6 Select the CmDongle you want to migrate.

If no dongle is listed, click Rescan to reload dongle information.

Note

The CmDongle you want to migrate must have up-to-date firmware. IfdSPACE Installation Manager displays Required in the FirmwareUpdate column, a firmware update is necessary. Refer to How toUpdate the Firmware of a CmDongle on page 61.

7 Click Next.


8 Click Yes to start the migration process.

dSPACE Installation Manager automatically performs the migration processand the data exchange with dSPACE License Central. When completed,dSPACE Installation Manager displays the result:

9 Click Close.

The CmDongle is prepared for using the CodeMeter license technology.Migrated CmDongles still contain the embedded WibuKey ID. This ID is requiredto use the CmDongle with dSPACE Release 2017-A and earlier.

Result



How to Disable a WibuKey Dongle

In some use scenarios, dSPACE prompts you to return your WibuKey dongle. Thisis necessary to continue with your workflow. As an alternative to returning theWibuKey dongle, you can disable it with dSPACE Installation Manager.

Objective


§ dSPACE approval for disabling the WibuKey dongle is available.

Precondition

To disable a WibuKey dongle

1 Connect the WibuKey dongle to the PC.




Method


Dongle Migration


5 Select Disable WibuKey Dongle.

6 Select the WibuKey dongle you want to disable.

If no dongle is listed, click Rescan to reload dongle information.

7 Click Next.


8 Click Yes to start disabling the dongle.

dSPACE Installation Manager automatically performs the disabling processand the data exchange with dSPACE License Central. When completed,dSPACE Installation Manager displays the result.

9 Click Close.

The license ID is deleted from the dongle. The WibuKey dongle can no longer beused.

Result

How to Update the Firmware of a CmDongle

dSPACE Installation Manager checks if the firmware of a connected donglematches at least the firmware version that was defined by dSPACE. If thefirmware version does not match, a firmware update is required before you cancontinue the license activation, deactivation, or update.

Firmware is updated via CodeMeter Control Center.

Objective



dSPACE Installation Manager shows the firmware update state on theCmContainer page. Refer to How to Show Available CmContainers and TheirAttributes on page 41.

In addition, the state is displayed on every workflow page that uses dongles. Onthese pages, the Update Firmware button is available if a firmware update isnecessary.

Showing firmware status

§ An Internet connection is available. Then, CodeMeter Control Centerautomatically connects to the Firmware Update Server of Wibu-Systems.

Preconditions

§ dSPACE Installation Manager displays a required firmware update as follows:

Dongle Migration


To update the firmware of a CmDongleMethod

1 Click Update Firmware as shown in the following illustration.


2 Click Yes.

CodeMeter Control Center opens.

3 Select the related CmDongle and click Update Firmware of selectedCmDongle as shown in the following illustration:



A confirmation prompt is displayed:

4 Click OK.

CodeMeter Control Center establishes an Internet connection to update thefirmware of the related CmDongle.

Note

Do not remove the CmDongle during the update process.

Removing the CmDongle from the host PC might cause data loss.

After the update process is finished, CodeMeter Control Center displays aninformation dialog about the update.

5 Click OK.

You updated the firmware of a CmDongle to the latest version. You can nowcontinue to activate, deactivate or update licenses on the CmDongle.

If you cannot update the firmware of your CmDongle, refer to:

§ CmDongle Firmware Update Aborts with Error Message on page 179

§ CmDongle Firmware Update Aborts with Error Message on page 179

Result

Dongle Migration


License Activation

Before you can use licenses for the first time, you have to activate them. Forlicense activation, dSPACE GmbH uses a ticket-based system and hosts adatabase. This database is called dSPACE License Central. To start the activationprocess, you have to enter the ticket IDs that you received from dSPACE via e-mail. During activation, data is transferred between dSPACE Installation Managerand dSPACE License Central.

You can activate multiple licenses on one CmContainer (for example, CmDongle)in one step.

Introduction


Use Cases and Workflows for License Activation .................................... 65

How to Activate Licenses (Local Access to CmContainer) ....................... 70

How to Activate Licenses (LAN Access to CmContainer) ......................... 74

How to Activate Licenses (File-Based Access to CmContainer) ................ 80


Use Cases and Workflows for License Activation

Online activation with local access of the dSPACE Installation Manager to theCmContainer is the recommended way to activate license. For a detaileddescription of the use cases, refer to Methods for Accessing CmContainerson page 17.

Use cases

License Activation


Local access

CmContainer


Activate

LAN access


Activate

LAN

CmContainer

File-based access


Transfer of activation files

CmContainer

RUC

RAC

Web Gateway

License Central


Ticket IDs

63LU2506A7345Y2422NO1662 ...

Ticket IDs(via e-mail)


The workflow differs depending on how dSPACE Installation Manager can accessthe CmContainer.

License Activation


The following illustration shows the workflow for single-user licenses as well asfor floating network licenses:

Customer via Installation Manager

dSPACE License Central

Enter ticket IDs

Provides ticket information

dSPACE


Select licenses to activate

Select “Local access to CmContainer”

If required: create new CmActLicense container

Select the target CmContainer

Activate licenses


Displays activation result

Sends license overview sheet (via e-mail) including

ticket IDs

For instructions, refer to How to Activate Licenses (Local Access to CmContainer)on page 70.

Workflow for local access






Sends license overview sheet (via e-mail) including ticket IDs

Enter ticket IDs


dSPACE



Select “LAN access to CmContainer”

If required: create new CmActLicense container

Select the target CmContainer

Activate licenses


Performs license activation

Displays activation result

Configure the PC with CmContainer as a license server

Set up a connection between license client and license server

Customer via CodeMeter Control Center

For instructions, refer to How to Activate Licenses (LAN Access to CmContainer)on page 74.

Workflow for LAN access

License Activation



Customer

Transfer RAC file to PC with Installation Manager

Customer


Customer

Transfer RAU file to PC on which RAC file was created

(with access to CmContainer)

Sends license overview sheet (via e-mail) including ticket IDs

dSPACE

Create RAC file on PC with access to CmContainer



Enter ticket IDs


Confirm license activation



Select “File-based access to CmContainer”

Transfer RAC file to dSPACE License Central

Select RAC file




Creates RAU file and transfers it to Installation Manager


Displays confirmation result

Activate licenses on CmContainer with the delivered RAU file

Create RAC file for confirmation


For instructions, refer to How to Activate Licenses (File-Based Access toCmContainer) on page 80.

Workflow for file-basedaccess



How to Activate Licenses (Local Access to CmContainer)

To activate single-user and floating network licenses on a CmContainer that isaccessible locally on your PC.

Tip

You can activate multiple licenses on one CmContainer in one step.

Objective


§ At least one ticket ID is available.

§ A CmDongle is available (mandatory for activating single-user licenses).

Note

Dongles delivered for dSPACE Releases 2017-A and earlier cannot be usedfor the new CodeMeter license technology without modifications.Therefore, dongle migration is required for these dongles before you canactivate licenses on them. Refer to Dongle Migration on page 51.

Preconditions

To activate licenses (local access to CmContainer)

1 Connect the CmDongle to your PC if you want to activate the license on aCmDongle.




Method

License Activation


4 Select License Activation and click Next.

5 Enter or paste the ticket ID for license activation you received from dSPACEvia e-mail in the edit field and click Add.

The license overview sheet displays the required ticked IDs and ticket groupIDs as follows:



The ticket information is provided by dSPACE License Central.

6 Select the licenses you want to activate.

Note

Each ticket for a single-user license can be activated only once.Deactivating a license that was activated on the wrong CmDongle ispossible only via dSPACE Support. Therefore, try to avoid such incorrectactivations.

7 For floating network licenses: Click Choose CmContainer Type and selectthe desired CmContainer type: (CmDongle or dSPACE ActivationContainer):

8 Click Next.

License Activation


9 Select Local access.

dSPACE Installation Manager displays all accessible CmContainers.

10 Only for floating network licenses: Click Create New CmContainer if noCmActLicense container is available or if you want to create a new one.

After creating the CmActLicense container, dSPACE Installation Managerdisplays a confirmation prompt with the serial number of the newCmContainer:

11 Select the target CmDongle or CmActLicense container.



12 Click Next.


13 Click Yes to start the activation process.

dSPACE Installation Manager automatically performs the data exchange withdSPACE License Central and displays the activation result as follows:

14 Click Close.

You activated single-user licenses or floating network licenses. The licenses arenow ready for use.

Result

How to Activate Licenses (LAN Access to CmContainer)

To activate floating network licenses on a CmContainer that is accessible fromdSPACE Installation Manager via LAN.

Note


Objective

License Activation


You cannot activate single-user licenses on CmContainers via LAN access. In thiscase, you have to use the file-based method. Refer to How to Update Licenses(File-Based Access to CmContainer) on page 94.

Restriction

§ The PC with the CmContainer is configured as a dSPACE License Server. Referto How to Set up the dSPACE License Server on page 129.

§ The PC with dSPACE Installation Manager is able to establish an TCP/IPconnection to the dSPACE License Server. Refer to How to Set up aConnection Between Client and Server on page 133.



§ A CmDongle is available if you want to activate the floating network licenseson a CmDongle.

Note


Preconditions

To activate licenses (LAN access to CmContainer)




Method






License Activation




Note


6 Click Choose CmContainer Type and select the desired CmContainer type:(CmDongle or dSPACE Activation Container).

7 Click Next.



8 Select LAN access.

dSPACE Installation Manager displays all accessible CmContainers.

9 Click Create New CmContainer if no CmActLicense container is available orif you want to create a new one.

Select the server on which you want to create the CmActLicense containerfrom the list and click OK.

After creating the CmActLicense container, dSPACE Installation Managerdisplays a confirmation prompt with the serial number of the newCmContainer:

License Activation


10 Select the target CmDongle or CmActLicense container.

11 Click Next.



dSPACE Installation Manager automatically performs the data exchange withdSPACE License Central and displays the activation result as follows:

13 Click Close.



You activated floating network licenses. The licenses are now ready for use.Result

How to Activate Licenses (File-Based Access to CmContainer)

To activate single-user and floating network licenses on a CmContainer that isaccessible only via manual file transfer from your PC.

Note


Objective

§ An administrator PC (with dSPACE Installation Manager installed) has anInternet connection for accessing dSPACE License Central.

§ CodeMeter Runtime software is installed on the PC with the CmContainer.


§ A CmContainer (CmDongle or CmActLicense) is available. If no CmActLicensecontainer is available or if you want to create a new one, refer to ManualCmContainer Creation on page 155.

Note


Preconditions

To activate licenses (file-based access to CmContainer)

1 Create an initial RAC file (*.WibuCmRaC) with CodeMeter Control Center.Refer to How to Create an Initial RAC File on page 111.

2 On the administrator PC: From Start – All Programs – dSPACE InstallationManager, select dSPACE Installation Manager.



Method

License Activation




Note


7 For floating network licenses: Click Choose CmContainer Type and selectthe desired CmContainer type: (CmDongle or dSPACE ActivationContainer):

8 Click Next.

License Activation


9 Select File-based access and enter the path of the RAC file.

10 Click Next.



12 Select a folder to store the RAU file in and click Save.

Note

You must not rename the file. The file name is the serial number of theCmContainer.



On the basis of the delivered RAC file, dSPACE License Central generates anRAU file (*.WibuCmRaU) that contains information about the activatedlicense.

When the process is completed, dSPACE Installation Manager displays theresult as follows:

13 Click Close.

14 Transfer the RAU file (*.WibuCmRaU) to the PC with the CmContainer. Do thiswith a USB stick or via a network folder, for example.

15 Update the CmContainer with the delivered RAU file (*.WibuCmRaU). UseCodeMeter Control Center to do this. Refer to How to Update aCmContainer with an RAU File on page 117.

16 Confirm the license activation. Use dSPACE Installation Manager to do this.Refer to How to Confirm the License Status Manually (File-Based Access toCmContainer) on page 145.

You activated dSPACE software licenses by using the file-based access method.The licenses are now ready for use.

Result

License Activation


License Update

License updates are required if the license information of an activated license hasbeen updated by dSPACE.

Motivation


Use Scenario and Workflows for License Updates .................................. 85

How to Update Licenses (Local Access to CmContainer) ........................ 89

How to Update Licenses (LAN Access to CmContainer) .......................... 92

How to Update Licenses (File-Based Access to CmContainer) ................. 94


Use Scenario and Workflows for License Updates

A license update becomes necessary if the license information of an activatedlicense is updated by dSPACE. For example, if you purchased a SoftwareMaintenance Service (SMS) contract for your dSPACE product and themaintenance period is extended, you have to update the license.

When the update becomes available in dSPACE License Central, the licenses tobe updated are displayed in dSPACE Installation Manager. To perform theupdate, you only have to provide access to the relevant CmContainer, forexample, by connecting the relevant CmDongle.

Use Scenario

License Update


Local access

CmContainer


Update

File-based access



CmContainer

RUC

RAC

Web Gateway

License Central


Update available

LAN access


Update

LAN

CmContainer


License Update


Customer

Provide access to CmContainer with license to

be updated

Informs customer (sends license overview sheet via e-mail) that

license update is available

dSPACE


Displays licenses that can be updated


Select licenses to update

Start update process


Select “Local access” to CmContainer


Provides license update


Performs license update

Displays update result

For instructions, refer to How to Update Licenses (Local Access to CmContainer)on page 89.

Workflow for local access toCmContainer

Use Scenario and Workflows for License Updates


Customer

Provide access to CmContainer with license to

be updated



dSPACE


Displays licenses that can be updated


Select licenses to update

Start update process


Select “LAN access” to CmContainer

Select CmContainer


Provides license updatedSPACE License Central


Displays update result

Configure the PC with the CmContainer as license server



For instructions, refer to How to Update Licenses (LAN Access to CmContainer)on page 92.

Workflow for LAN access toCmContainer

License Update


Confirm license update

Select “File-based access” to CmContainer


Import RAC file

Select licenses to be updated



dSPACE






Customer





Customer


Customer



Create RAC file on PC with CmContainer that contains

license to be updated


Update licenses on CmContainer with the delivered RAU file

Create RAC file for confirmation


For instructions, refer to How to Update Licenses (File-Based Access toCmContainer) on page 94.

Workflow for file-basedaccess to CmContainer

How to Update Licenses (Local Access to CmContainer)

To update licenses in a CmContainer that is accessible from dSPACE InstallationManager locally.

Tip

dSPACE Installation Manager supports the update of multiple licenses in oneor multiple CmContainers in one step.

Objective



Note

Valid for floating network licenses: Depending on the number of thelicenses you want to update, updating licenses on a dSPACE License Servermight be time-consuming. Therefore, it is recommended to perform licenseupdates on a license server only during maintenance.

When to update

§ dSPACE License Central provides an update for activated licenses.


§ The CmContainer (for example, a CmDongle) you want to update is accessiblewith dSPACE Installation Manager.

Preconditions

To update licenses (local access to CmContainer)

1 If you want to update the licenses on a CmDongle, connect the CmDongle toyour PC.



Method


4 Select License Update and then select Local access.

5 Click Next.

6 Of all licenses of the CmContainers accessible on the PC (CmActLicensecontainers and CmDongles), dSPACE Installation Manager displays only thosefor which dSPACE provides an update.

License Update


Note

Updatable licenses on a CmDongle are displayed only if the relatedCmDongle is connected to the PC. Do not remove the CmDongle fromthe PC during the update process. This causes the update to fail.

7 Select the licenses you want to update.

8 Click Next.


9 Click Yes to start the update process.

dSPACE Installation Manager automatically performs the data exchange withdSPACE License Central and displays the result as follows:

10 Click Close.



You updated dSPACE licenses.Result

How to Update Licenses (LAN Access to CmContainer)

To update licenses in a CmContainer that is accessible from dSPACE InstallationManager via LAN.

Tip

dSPACE Installation Manager supports the update of multiple licenses in oneor multiple CmContainers in one step.

Objective

Note

Valid for floating network licenses: Depending on the number of thelicenses you want to update, updating licenses on a dSPACE License Servermight be time-consuming. Therefore, it is recommended to perform licenseupdates on a license server only during maintenance.

When to update

§ The PC with the CmContainer is configured as a dSPACE License Server. Referto How to Set up the dSPACE License Server on page 129.

§ The PC with dSPACE Installation Manager is able to establish a TCP/IPconnection to the dSPACE License Server. Refer to How to Set up aConnection Between Client and Server on page 133.



§ The CmContainer (for example, a CmDongle) you want to update is accessiblewith dSPACE Installation Manager.

Preconditions

To update licenses (LAN access to CmContainer)

1 If you want to update the licenses on a CmDongle, connect the CmDongle tothe PC configured as dSPACE License Server.



Method

License Update



4 Select License Update and then select LAN access.

5 Click Next.

dSPACE Installation Manager displays all CmActLicense container and allCmDongles that can be accessed via LAN.

6 Select the CmContainer that contains licenses to be updated.

7 Click Next.

dSPACE Installation Manager displays only those licenses for which dSPACEprovides an update.

Note

Updatable licenses on a CmDongle are displayed only if the relatedCmDongle is connected to a PC accessible via LAN. Do not remove theCmDongle from the PC during the update process. This causes theupdate to fail.

How to Update Licenses (LAN Access to CmContainer)


8 Select the licenses you want to update.

9 Click Next.




11 Click Close.

You updated dSPACE licenses.Result

How to Update Licenses (File-Based Access to CmContainer)

To update single-user and floating network licenses on a CmContainer that isaccessible only via manual file transfer.

Objective

Note

Valid for floating network licenses: Depending on the number of licensesyou want to update, updating licenses on a dSPACE License Server might betime-consuming. Therefore, it is recommended to perform license updateson a license server only during maintenance.

When to update

License Update



§ An administrator PC (with dSPACE Installation Manager installed) has anInternet connection for accessing dSPACE License Central.


Preconditions

To update licenses (file-based access to CmContainer)




Method


4 Select License Update and then select File-based access.

5 Click Next.



6 Enter the path of the RAC file (*.WibuCmRaC).

7 Click Next.

Note

Licenses are displayed only if dSPACE provides an update for them.

8 Select the licenses you want to update and click Next.



On the basis of the delivered RAC file, dSPACE License Central generates anRAU file (*.WibuCmRaU) that contains information about the licenses whichare updated.

License Update



Note

Do not rename the file. The file name is the serial number of theCmContainer.


11 Click Close.





14 Confirm the license update. Use dSPACE Installation Manager to do this.Refer to How to Confirm the License Status Manually (File-Based Access toCmContainer) on page 145.

You updated licenses by using the file-based access method.Result

License Update


License Deactivation

Deactivated licenses can be activated again if you want to use them in a differentCmContainer.

Motivation


Use Scenarios and Workflows for License Deactivation .......................... 99

How to Deactivate Licenses (Local Access to CmContainer) .................. 103

How to Deactivate Licenses (File-Based Access to CmContainer) .......... 105


Use Scenarios and Workflows for License Deactivation

For license deactivation, you transfer activated licenses from a CmContainer backto dSPACE License Central. The deactivated licenses can be activated again if youwant to use them in a different CmContainer. dSPACE Installation Managerdisplays only the licenses that can be deactivated.

Note

If you want to deactivate single-user licenses, you have to request this fromdSPACE. You can deactivate single-user licenses only after dSPACE approvedthe deactivation of the related license. dSPACE Installation Manager thendisplays the license as deactivatable.

Floating network licenses can be deactivated anytime.

Use scenario




Local access

CmContainer


Deactivate

File-based access



CmContainer

RUC

RAC

Web Gateway

License Central


Deactivation is possible

Deactivating licenses via LAN access is not supported, to prevent unintendeddeactivation in a LAN.



Customer

Requests license deactivation from dSPACE (via e-mail)

Required info: CmContainer Serial number, licenses, or ticket IDs

Informs customer (sends license overview sheet via

e-mail) that license deactivations is possible

dSPACE


Performs deactivation of licenses

Displays deactivation result

Single-user licenses Floating network licenses





Select “License Deactivation”

Select licenses to deactivate

Start deactivation process



License activation on other CmContainer is possible with

existing ticket ID


Performs deactivation of licenses




Select “License Deactivation”

Select licenses to deactivate

Start deactivation process

License activation on other CmContainer is possible with

existing ticket ID

For instructions, refer to:

§ How to Update Licenses (Local Access to CmContainer) on page 89

§ How to Deactivate Licenses (Local Access to CmContainer) on page 103


Use Scenarios and Workflows for License Deactivation



Customer



Customer


Confirm license deactivation



Single-user licenses


Customer





Create RAC file on PC with CmContainer that contains license

to be deactivated


Deactivate licenses with the delivered RAU file

Create RAC file for confirma-tion

License activation on other

CmContainer is possible with

existing ticket ID


Customer

Requests license deactivation from dSPACE (via e-mail)

Required info: CmContainer Serial number, licenses, or ticket IDs

Informs customer (sends license overview sheet via

e-mail) that license deactivations is possible

dSPACE







Import RAC file

Select licenses to be deactivated


For instructions, refer to:

§ How to Update Licenses (File-Based Access to CmContainer) on page 94

§ How to Deactivate Licenses (File-Based Access to CmContainer) on page 105



How to Deactivate Licenses (Local Access to CmContainer)

To deactivate single-user and floating network licenses on a CmContainer that isaccessible locally on your PC.

Tip

dSPACE Installation Manager supports the deactivation of multiple licensesin one or multiple CmContainers in one step.

Objective

Note

Valid for floating network licenses: Depending on the number of thelicenses you want to deactivate, deactivating licenses on a dSPACE LicenseServer might be time-consuming. Therefore, it is recommended to performlicense deactivation on a license server only during maintenance.

When to deactivate

Note

For deactivating single-user licenses, you have to contact dSPACE. You candeactivate single-user licenses only if dSPACE approved the deactivation.However, you can deactivate floating network licenses at any time.

Restriction


§ For deactivating single-user licenses:

1. Approval from dSPACE to deactivate the license is available. In this case,dSPACE provides a license update.

2. You performed the license update. Refer to How to Update Licenses (LocalAccess to CmContainer) on page 89. You can deactivate the licenseafterwards.

Preconditions

To deactivate licenses (local access to CmContainer)

1 Connect the CmDongle to your host PC if you want to deactivate the licenseson a CmDongle.




Method

How to Deactivate Licenses (Local Access to CmContainer)


4 Select Show all on the left of the page.

5 Select License Deactivation and click Next.


dSPACE Installation Manager displays only licenses that can be deactivated.

7 Select the licenses you want to deactivate.



8 Click Next.


9 Click Yes to start the deactivation.

dSPACE Installation Manager automatically performs the data exchange withdSPACE License Central and displays the deactivation result as follows:

10 Click Close.

You deactivated the selected licenses.Result

How to Deactivate Licenses (File-Based Access to CmContainer)

To deactivate single-user and floating network licenses in a CmContainer that isaccessible only via manual file transfer from the host PC.

Tip

dSPACE Installation Manager supports the deactivation of multiple licensesin one or multiple CmContainers in one step.

Objective



Note

Valid for floating network licenses: Depending on the number of thelicenses you want to deactivate, deactivating licenses on a dSPACE LicenseServer might be time-consuming. Therefore, it is recommended to performlicense deactivation on a license server only during maintenance.

When to deactivate

Note

For deactivating single-user licenses, you have to contact dSPACE. You candeactivate single-user licenses only if dSPACE approved the deactivation.However, you can deactivate floating network licenses at any time.

Restriction

§ An administrator PC (with dSPACE Installation Manager installed on it) has anInternet connection for accessing dSPACE License Central.


§ A CmDongle is available (mandatory for deactivating single-user licenses).

§ For deactivating single-user licenses:

1. Approval from dSPACE to deactivate the license is available. In this case,dSPACE provides a license update.

2. You performed the license update. Refer to How to Update Licenses (File-Based Access to CmContainer) on page 94. You can deactivate the licenseafterwards.

Preconditions

To deactivate licenses (file-based access to CmContainer)





Method




5 Select License Deactivation and click Next.

6 Select File-based access and enter the path of the RAC file (*.WibuCmRaC).



7 Select the licenses you want to deactivate and click Next.


8 Click Yes to start the deactivation process.

On the basis of the delivered RAC file, dSPACE License Central generates anRAU file (*.WibuCmRaU) that contains information about the deactivatedlicense.


Note





10 Click Close.



13 Confirm the license deactivation. Use dSPACE Installation Manager to do this.Refer to How to Confirm the License Status Manually (File-Based Access toCmContainer) on page 145.

You deactivated the selected licenses by using the file-based access method.Result



Executing Steps in CodeMeter Control Center (forFile-Based Access)

If you use the file-based method for license activation, deactivation or licenseupdates, you have to execute some steps in CodeMeter Control Center.

Motivation


How to Create an Initial RAC File ......................................................... 111

How to Update a CmContainer with an RAU File ................................. 117


How to Create an Initial RAC File

If you use the file-based method for license activation, deactivation or licenseupdates, you first have to create an initial RAC file (*.WibuCmRaC) withCodeMeter Control Center.

Objective

You can use a remote desktop tool to access the PC with the CmContainer. Thistool can be installed on the PC with dSPACE Installation Manager or any otherPC in the LAN to control CodeMeter software and to transfer files manuallybetween the PCs.

Remote access is useful if you want to access multiple CmContainers and workwith CodeMeter software installed on the PCs from only one administrator PC.Another use case is to manage single-user licenses that are not accessible directlyin a LAN. For more information, refer to Methods for Accessing CmContainerson page 17.

Remote access toCmContainer

Executing Steps in CodeMeter Control Center (for File-Based Access)



§ The CmContainer (CmDongle or CmActLicense container) on which you wantto activate, update, or deactivate licenses is accessible with CodeMeter ControlCenter.

If no CmActLicense container exists on your PC or you want to create a newone, you first have to import a license information file (LIF) that you createdwith dSPACE Installation Manager beforehand. Refer to How to Create aLicense Information File (LIF) on page 157.

Precondition

To create an initial RAC file

1 On the PC with the CmContainer: From Start – All Programs – CodeMeter,select CodeMeter Control Center.

CodeMeter Control Center opens and list all accessible CmContainers on theLicense page.

2 § If the CmContainer you want to use is displayed, continue with step 5.

§ If you want to create a new CmActLicense container on the PC, continuewith the next step.

Method



3 Select File – Import License and import a LIF from a USB stick or a networkfolder, for example.

CodeMeter Control Center displays the following confirmation prompt:

4 Click OK.

CodeMeter Control Center creates an empty CmActLicense container anddisplays it as follows:



5 Select the CmContainer for which you want to create an RAC file and clickLicense Update.

6 Click Next and select Create license request to create an RAC file(*.WibuRaC).

7 Click Next to continue.

8 If you want to create an RAC file for a CmActLicense container, continue withstep 10.



9 Only if you use CmDongles: Select Extend existing license.

Click Next and select the vendor "dSPACE (6000107)".

Click Next to continue.



10 Select a folder to store the RAC file and click Commit.

Note


CodeMeter Control Center creates the RAC file and displays the result asfollows:

11 Click Finish.

You created an initial RAC file for the selected CmContainer.Result

§ Transfer the RAC file (*.WibuCmRaC) to the administrator PC. Do this with anUSB stick or via a network folder, for example.

Next steps



§ Use the RAC file to request an RAU file via dSPACE Installation Manager onthe administrator PC. Depending on your workflow, refer to:

§ How to Activate Licenses (File-Based Access to CmContainer) on page 80

§ How to Update Licenses (File-Based Access to CmContainer) on page 94

§ How to Deactivate Licenses (File-Based Access to CmContainer) on page 105

§ How to Request an RAU File for the New CmActLicense Containeron page 159

How to Update a CmContainer with an RAU File

After you request an RAU file via dSPACE Installation Manager, you have toupdate the CmContainer with this file.

Objective

You can use a remote desktop tool to access the PC with the CmContainer. Thistool can be installed on the PC with dSPACE Installation Manager or any otherPC in the LAN to control CodeMeter software and to transfer files manuallybetween the PCs.

Remote access is useful if you want to access multiple CmContainers and workwith CodeMeter software installed on the PCs from only one administrator PC.Another use case is to manage single-user licenses that are not accessible directlyin a LAN. For more information, refer to Methods for Accessing CmContainerson page 17.

Remote access toCmContainer


§ An RAU file (*.WibuCmRaU) requested via dSPACE Installation Manager isavailable.

§ The CmContainer (e.g., CmDongle) you want to update is accessible withCodeMeter Control Center.

Preconditions

To update a CmContainer with an RAU file

1 On the PC with the CmContainer: From Start – All Programs – CodeMeter,select CodeMeter Control Center.

Method



CodeMeter Control Center opens and lists all accessible CmContainers on theLicense page.

2 Select the CmContainer you want to update and click License Update.



3 Click Next and select Import license update to import the RAU file.

4 Click Next and enter the path of the RAU file.



5 Click Commit to start the import process.

CodeMeter Control Center performs the update and displays the updateresult as follows:

6 Click here in the dialog to create an RAC file (*.WibuCmRaC) for confirmingthe license update.

7 Select a folder to store the RAC file and click Commit.

Note




CodeMeter Control Center creates the RAC file and displays the result asfollows:

8 Click Finish.

You updated the CmContainer with an RAU file and created another RAC file toconfirm the process.

Result

You now have to confirm the activation, update or deactivation process. Refer toHow to Confirm the License Status Manually (File-Based Access to CmContainer)on page 145 .

Next steps



Using Floating Network Licenses

dSPACE software products support floating network licenses.Motivation


Basics on Using Floating Network Licenses ........................................... 123

Basics on Setting Up a License Server and the License Clients ............... 126

How to Set up the dSPACE License Server ............................................ 129

How to Set up a Connection Between Client and Server ...................... 133


Basics on Using Floating Network Licenses

Floating network licenses are useful when a limited number of licenses for asoftware product has to be shared among a larger number of users.

When a user wants to run a software product or a license-protected process, thesoftware requests a license from a central license server. If a license is available,the license server allows the software or the process to run. When the user closesthe software product or the license-protected process, the license is reclaimed bythe license server and made available to other users (client PCs) connected to thelicense server.

Using floating network licenses requires a permanent TCP/IP connection betweenserver and client.

Principle of floating networklicenses



Floating network licenses are typically stored in CmActLicense containers, but it isalso possible, to store floating network licenses on CmDongles.

dSPACE product


License handling

CmContainer

CmActLicense

CmDongle

In case of a defect or a planned upgrade of the license server, the CmDongleonly has to be plugged into the new license server. Users can immediately workwith the licenses again.

Supported CmContainer types

The type of a license is shown in dSPACE Installation Manager. On the LicenseOverview page, the Accessibility column displays Floating network. Refer tothe following screenshot:

An important attribute of floating network licenses is the license quantity, whichdefines the number of licenses that can be used in parallel on client PCs. Thelicense quantity is also displayed on the License Overview page.

The license quantity is also stated in the License Overview sheet (provided bydSPACE via e-mail) that also contains the ticket IDs.

Identifying floating networklicenses

dSPACE CmActLicense containers that are suitable for storing floating networklicenses are called dSPACE Activation Containers. The serial number of such acontainer always begins with 130. Example: 130-1186644671.

Identifying CmActLicenses



The following screenshot shows an example for a CmActLicense container. It isdisplayed on the CmContainer page in dSPACE Installation Manager.

Usually, floating network licenses are requested from dSPACE software installedon client PCs connected to a server via a TCP/IP connection. However, they alsocan be requested by dSPACE software installed locally on the PC that also hoststhe floating network licenses (i.e., the license server).

dSPACE software products first search for a local CmContainer with the requiredlicense. If they do not find a relevant local CmContainer, they search forCmContainers that are stored on license servers.

Searching for licenses

Licenses are checked and blocked, for example, when a product or a process isstarted.

The license is released immediately after the product or the process is closed. If alicense has a linger time, the license is released after the linger time has elapsed.Then, the license can be used by other license clients.

The linger time of a specific floating network license is shown in dSPACEInstallation Manager. On the License Overview page, the Linger time entrydisplays the specified time in the format hh:mm:ss. For all products the lingertime is defined by dSPACE.

Extending the linger time You cannot directly extend the linger time on thedSPACE License Server. However, there is a workaround using CodeMeterWebAdmin. In its advanced mode, you can specify access rules to reserve alicense (i.e., to block it) for a longer period without losing the license. For moreinformation, refer to the CodeMeter user documentation installed on your PC at

License behavior of floatingnetwork licenses

Basics on Using Floating Network Licenses


http://localhost:22350/$help/CmUserHelp/us/index.html?license_access_permissions.htm.

For floating network licenses, the CodeMeter licensing technology cannotprovide downward compatibility with Releases earlier than dSPACE Release2017-B. If you need to use product versions of dSPACE Releases earlier thandSPACE Release 2017-B, you have to keep your FlexNet License Server running inparallel. Both FlexNet and CodeMeter floating network servers can be hosted onthe same PC.

Note


Compatibility with FlexNettechnology (earlier Releases)

Basics on Setting Up a License Server and the License Clients

If you purchased floating network licenses, you have to configure one PC in thenetwork as the dSPACE License Server. The PCs on which you want to rundSPACE software (dSPACE License Clients) need to be connected to the dSPACELicense Server via TCP/IP connection.

The CodeMeter technology does not need special license server software. EveryPC with a CodeMeter Runtime software installation can be configured as alicense server.

The configuration of a license client to connect to a license server is done bymeans of a server search list.

Note

You cannot use dSPACE Installation Manager to set up a license server andconnect license clients to the server. This can be done only via CodeMeterWebAdmin from Wibu-Systems.

Single-user licenses that are stored in local CmContainers on the dSPACE LicenseServer do not become floating network licenses when the PC is configured as alicense server. The license itself contains an attribute whether it can be used as asingle-user or as a floating network license.

Setting up license server andclients

Preparing the dSPACE License Server requires knowledge about the networkconfiguration, e.g., TCP/IP addresses, available TCP/IP ports on the dSPACELicense Server, and configuration of firewalls and routers. Therefore, it is

Required knowledge



http://localhost:22350/$help/CmUserHelp/us/index.html?license_access_permissions.htm

http://localhost:22350/$help/CmUserHelp/us/index.html?license_access_permissions.htm

recommended that only experienced network administrators prepare the dSPACELicense Server.

The following steps show the recommended workflow for configuring a host PCas a dSPACE License Server:

Check the system requirements for the PC that is used as the dSPACE License Server.

Set up the dSPACE License Server.

Define the server search list on the license clients.

Set up a connection between the license server and license clients.

Recommended workflow

dSPACE software products first search for a local CmContainer with the requiredlicense. If they do not find a relevant local CmContainer, they search forCmContainers stored on license servers. Any PC in the network can be set up asa license server with a few clicks. Refer to How to Set up the dSPACE LicenseServer on page 129. The license servers are available via the client's server searchlist that has to be defined by the user. Refer to the following illustration.

Accessing floating networklicenses

CodeMeter WebAdmin

Network server:

Enable

dSPACE

License Server

CodeMeter WebAdmin

Server search list:

192.253.1.1

CodeMeter WebAdmin

Server search list:

192.253.1.1

CodeMeter WebAdmin

.

.

.

Server search list:

192.253.1.1

CodeMeter WebAdmin

Server search list:

192.253.1.1

LAN

192.253.1.1

dSPACE

License Client

dSPACE

License Client

dSPACE

License Client

dSPACE

License Client

Basics on Setting Up a License Server and the License Clients


Define the server search list as follows to prevent network broadcasts:

§ On the dSPACE license clients, add the license server to the server search list byentering the name or the IP address of the license server.

§ If you have more than one license server in the network, move the preferredserver to the top of the server search list. dSPACE software searches forCmContainers on the license server in the order listed in the server search listof the clients.

§ If dSPACE software products are installed and executed on the dSPACE LicenseServer, add localhost to the server search list of the license server. This wayinstalled dSPACE software does not search for license servers in the network.

Note

If you do not define the server search list (i.e., leave the list empty), thedSPACE software on the clients searches for available license server in theconnected LAN. The clients send network broadcasts to get access to licenseservers. To reduce network broadcasts and thus the traffic in your network,always define at least one server in the server search list. By default,"localhost" is added to the server search list during software installation.This way installed dSPACE software does not search for license servers in thenetwork.

To use license-protected dSPACE software, you have to create a CmContainer onthe dSPACE License Server and activate the floating network licenses in it. As analternative, you can activate floating network licenses in CmDongles. These tasksare done via dSPACE Installation Manager. For more information, refer to LicenseActivation on page 65.

If you cannot install dSPACE Installation Manager on your license server (forexample, because the required operating system does not match), you canactivate the floating network licenses via LAN connection from another PC. Thus,dSPACE Installation Manager needs not to be installed on the dSPACE LicenseServer.

Activating licenses on alicense server

You can use CodeMeter WebAdmin to configure further network options for thelicense server and its clients, for example, allowing remote access from other PCswith CodeMeter software in a network. For more information, refer to theCodeMeter user documentation.

Further settings for thelicense server and licenseclients

The following table lists hardware and software requirements:

Subject Host PC and Network Requirements

Requiredhardware

§ Intel Core 2 Duo processor at 2 GHz or equivalent§ 4 GB RAM main memory (or more)

System requirements for thedSPACE License Server



Subject Host PC and Network Requirements

Operatingsystem

§ Valid for servers without dSPACE software:dSPACE only tests license servers with Microsoft Windowsoperating systems in combination with protected dSPACEsoftware.

Note

Non-Windows operating systems, such as Ubuntu Linux,are not tested. You can use them at your own risk. dSPACEdoes not provide support in this case.

§ Valid for servers with dSPACE Installation Manager:dSPACE Installation Manager supports the same operatingsystems as the other dSPACE software products described above.

Requiredsoftware

§ On dSPACE License Client: CodeMeter Runtime Version 6.50c(automatically installed with dSPACE software installations).

§ On dSPACE License Server: CodeMeter Runtime. The versioninstalled on the server must be equal to or higher than theversion installed on the dSPACE License Clients.

§ If you want to use a PC as a dSPACE License Server, but do notwant to install dSPACE software on it, you can download andinstall the CodeMeter Runtime software fromhttp://www.dspace.com/go/wibudrv.Here you will always find the latest version that has been testedto be used in combination with dSPACE software.

Enablingfloatingnetworklicenses

All host PCs on which you want to run dSPACE software (licenseclients) must be able to establish a TCP/IP connection (standardTCP/UDP protocol is required) to the dSPACE License Server.The default port number is 22350 (TCP and UDP), which is anofficially registered port number (IANA). If needed, you can specifya different port number.

How to Set up the dSPACE License Server

You have to install and configure one of the network PCs as the dSPACE LicenseServer.

Objective

The PC used as a dSPACE License Server must meet the system requirements.Refer to Basics on Setting Up a License Server and the License Clientson page 126.

Preconditions



http://www.dspace.com/go/wibudrv

To set up the dSPACE License Server

1 From Start – All Programs – CodeMeter, select CodeMeter ControlCenter.


Method

2 Click WebAdmin.

CodeMeter WebAdmin opens in a new page in the web browser.

3 From the CodeMeter WebAdmin menu, select Configuration – Server –Server Access.



4 Select Enable in the Network Server group.

By default, the network port 22350 is set as the CodeMeter communicationport. The port number is registered at Internet Assigned Numbers Authority(IANA) and uniquely assigned to CodeMeter communication.

Note

You can change the default port setting. In this case, make sure that allCodeMeter license servers and license clients in your network use thesame port settings. If they do not, you cannot use CodeMeter softwarein a network without restrictions. For instructions on changing the portsetting, refer to the CodeMeter user documentation.

5 Click Apply.

6 Only if license-protected dSPACE software is installed and executed on thedSPACE License Server:

From Configuration – Basic – Server Search List select add new Server onthe Server Search List page.



Enter localhost or the server's host name into the edit field and click Add.

Click Apply and close CodeMeter WebAdmin by closing the tab in yourbrowser.

7 Change to CodeMeter Control Center.

8 From the Process menu, select Restart CodeMeter Service.

The changes take effect after CodeMeter Service restarted.

You configured a PC as a dSPACE License Server.Result

§ Set up a connection between dSPACE License Client and dSPACE LicenseServer. Refer to How to Set up a Connection Between Client and Serveron page 133.

Next steps



§ Create a CmContainer on the dSPACE License Server and activate the floatingnetwork licenses on it. You also can activate floating network licenses inCmDongles. Refer to License Activation on page 65.

How to Set up a Connection Between Client and Server

To set up a connection between client and server, you have to adjust the settingsof your dSPACE License Client to the address of the dSPACE License Server toinstruct the client to use the server.

Objective

To configure dSPACE License Clients, you have to use CodeMeter WebAdmin.You can set up a connection to as many servers as you need.

Refer to Basics on Setting Up a License Server and the License Clientson page 126.

Basics

To set up a connection between client and server

1 Establish a TCP/IP connection to the dSPACE License Server.

2 If necessary, configure firewall and/or other network components, such asrouters and switches, to open the specified TCP/IP port to allow networkcommunication between the client and server.

The default network port that is specified on the dSPACE License Server is22350.

Note

If you specified a different network port on the license server than thedefault network port (22350), you have to change it on the licenseclients as well. To change the communication port, use CodeMeterWebAdmin. For more information, refer to the CodeMeter userdocumentation.

3 From Start – All Programs – CodeMeter, select CodeMeter ControlCenter.

Method




4 Click WebAdmin.

CodeMeter WebAdmin opens a new page in the default web browser.

5 From the CodeMeter WebAdmin menu, select Configuration – Basic –Server Search List.

The server search list opens.



6 Click add new Server.

Tip

To display available license servers, click Current Server: <servername(IP-address)> at the bottom left in the CodeMeter WebAdmin window.

7 Enter the server's name or IP address in the edit field and click Add.

Tip

The license server connects to the first found Ethernet adapter bydefault. If your dSPACE License Server is located in another subnet, enterthe server's IP address instead of its host name. This prevents problemswith UDP broadcasts.



You can add as many servers as needed.

8 Click Apply to confirm your changes.

You added a new dSPACE License Server to the server search list.Result



Manual License Confirmation

In certain cases, you might have to perform license confirmation manually. Thisparticularly applies if dSPACE Installation Manager has file-based access to theCmContainer. However, in most cases, dSPACE Installation Manager performsthe license confirmation automatically.

Motivation


Use Scenario and Workflows for License Confirmation ........................ 137

How to Confirm the License Status Manually (Local Access toCmContainer) ...................................................................................... 140

How to Confirm the License Status Manually (LAN Access toCmContainer) ...................................................................................... 142

How to Confirm the License Status Manually (File-Based Access toCmContainer) ...................................................................................... 145


Use Scenario and Workflows for License Confirmation

To confirm the license status, you transfer a fingerprint of the CmContainer todSPACE License Central after you activated, updated, or deactivated the licenses.This is the last step in the related process.

Purpose



Local access

CmContainer


Confirm

File-based access



CmContainer

RUC

RAC

Web Gateway

License Central


LAN access


Confirm

LAN

CmContainer





Select CmContainer

Start license confirmation




License is activated, updated or deactivated but the

process is not confirmed

For instructions, refer to How to Confirm the License Status Manually (LocalAccess to CmContainer) on page 140.


Select “LAN access to CmContainer”

Select CmContainer

Start license confirmation




Configure the PC with CmContainer as a license server

License is activated, updated or deactivated but the process is not

confirmed



For instructions, refer to How to Confirm the License Status Manually (LANAccess to CmContainer) on page 142.

Workflow for LAN access

Use Scenario and Workflows for License Confirmation


Customer

Transfer confirmation RAC file to PC with Installation Manager



Import RAC file




License is activated, updated or deactivated but the

process is not confirmed

For instructions, refer to How to Confirm the License Status Manually (File-BasedAccess to CmContainer) on page 145.


How to Confirm the License Status Manually (Local Access to CmContainer)

To confirm an activation, update or deactivation process manually on aCmContainer that is accessible on your PC.

Objective


§ An activation, update or deactivation process is not yet confirmed to dSPACELicense Central.

Preconditions

To confirm the license status manually (local access to CmContainer)

1 If you want to confirm the license status on a CmDongle, connect theCmDongle to your PC.




Method




5 Select Manual License Confirmation and click Next.


dSPACE Installation Manager displays all CmContainers that it can accesslocally on your PC.

7 Select the CmDongle or CmActLicense container on which you want toconfirm the license status.

How to Confirm the License Status Manually (Local Access to CmContainer)


8 Click Next.


9 Click Yes to start the confirmation process.


10 Click Close.

You made the completion of an activation, update or deactivation process isknown to dSPACE License Central.

Result

How to Confirm the License Status Manually (LAN Access to CmContainer)

To confirm an activation, update or deactivation process manually on aCmContainer that is accessible from your PC via LAN.

Objective

§ The PC with access to the CmContainer is configured as a dSPACE LicenseServer. Refer to How to Set up the dSPACE License Server on page 129.

§ The PC on which dSPACE Installation Manager is installed to confirm thelicense status is able to establish a TCP/IP connection to the dSPACE LicenseServer. Refer to How to Set up a Connection Between Client and Serveron page 133.

Preconditions




§ An activation, update or deactivation process is not yet confirmed to dSPACELicense Central.

To confirm the license status manually (LAN access to CmContainer)

1 If you want to confirm the license status on a CmDongle, connect theCmDongle to the PC configured as the dSPACE License Server.




Method



How to Confirm the License Status Manually (LAN Access to CmContainer)


6 Select LAN access.

dSPACE Installation Manager displays all CmContainers that it can access viaLAN.

7 Select the CmDongle or CmActLicense container on which you want toconfirm the license status.

8 Click Next.




9 Click Yes to start the license confirmation.


10 Click Close.

You made the completion of an activation, update or deactivation processknown to dSPACE License Central.

Result

How to Confirm the License Status Manually (File-Based Access toCmContainer)

To confirm an activation, update or deactivation process manually on aCmContainer that is accessible from the host PC only via manual file transfer.

Objective


§ An RAC file (*.WibuCmRaC) that was created after updating the CmContainerwith an RAU file (*.WibuCmRaU) exists and is available on the PC with dSPACEInstallation Manager. Refer to How to Update a CmContainer with an RAU Fileon page 117.

Preconditions

To confirm the license status manually (file-based access to CmContainer)




Method

How to Confirm the License Status Manually (File-Based Access to CmContainer)




5 Select File-based access and enter the path of the RAC file (*.WibuCmRaC).

6 Click Next.




7 Click Yes to start the confirmation process.


8 Click Close.

You made the completion of an activation, update or deactivation processknown to dSPACE License Central.

Result

How to Confirm the License Status Manually (File-Based Access to CmContainer)


Manual RAU File Request

You have to request a RAU file manually if dSPACE Installation Manager only hasfile-based access to the CmContainer.

Motivation


Use Scenario and Workflow for Requesting a RAU File ......................... 149

How to Request an RAU File Manually ................................................. 150


Use Scenario and Workflow for Requesting a RAU File

You can request an RAU file (*.WibuCmRaU) from dSPACE License Central. This isuseful if an existing RAU file is missing on your PC, for example. After you receivethe RAU file, you can complete the file-based activation, update, or deactivationprocess.

If dSPACE Installation Manager has local or LAN access to the CmContainer, RAUfiles are transmitted automatically.

Use scenario




License Central


Ticket IDs

63LU2506A7345Y2422NO1662 ...

RAU

1. Enter ticket IDs

2. Request RAU file

3. Generate RAU fileData exchange

via Internet

Workflow

How to Request an RAU File Manually

To request an RAU file (*.WibuCmRaU) from dSPACE License Central manually.Objective


§ You want to activate, deactivate or update your licenses using the file-basedmethod.

§ The ticket ID or ticket group ID used to create the initial RAU file is available.

Preconditions

To request an RAU file manually




Method




4 Select Manual WibuCmRaU File Request and click Next.

5 Enter or paste the ticket ID or ticket group ID that was used to create theinitial RAU file into the edit field and click Add.

dSPACE Installation Manager lists all licenses associated with the ticket IDs asfollows:



6 Select a license of the desired CmContainer.

Note

An RAU file contains all licenses stored in a specific CmContainer. Thus,it is sufficient to select any license stored in the CmContainer, regardlessof the license and the confirmation state. However, dSPACE LicenseCentral creates the requested RAU file only if at least one license in theCmContainer has the state Unconfirmed and in addition one of thefollowing states: Activated, Updated or Deactivated.

7 Click Next.

8 Select a folder to store the RAU file (*.WibuCmRaU) in and click Save.

Note

Do not rename the file. The file name is the serial number of theCmContainer for which you need the RAU file.

A confirmation prompt opens.



9 Click Yes.

dSPACE Installation Manager automatically requests the RAU file fromdSPACE License Central and displays the result as follows:

10 Click Close.

You received the desired RAU file (*.WibuCmRaU).Result

You can now use the RAU file to update the CmContainer by using CodeMeterControl Center. Refer to How to Update a CmContainer with an RAU Fileon page 117.

Next step



Manual CmContainer Creation

If you do not use a CmDongle, you have to create the required CmActLicensecontainer (software-based CmContainer) by yourself. CmActLicenses are node-locked containers and therefore bound to a specific PC. They cannot betransferred to another PC.

Motivation


Workflows for Creating CmActLicense Containers ............................... 155

How to Create a License Information File (LIF) ...................................... 157

How to Request an RAU File for the New CmActLicense Container ....... 159


Workflows for Creating CmActLicense Containers

The workflow differs depending on how dSPACE Installation Manager can accessthe PC on which you want to create the new CmActLicense container.

Introduction

If you want to create the CmActLicense container locally on your PC or on a PCthat you can access via LAN, dSPACE Installation Manager creates theCmContainer online during license activation.

Refer to:

§ How to Activate Licenses (Local Access to CmContainer) on page 70

§ How to Activate Licenses (LAN Access to CmContainer) on page 74

Workflows for local and LANaccess



If dSPACE Installation Manager does not have access to the PC on which youwant to create the new CmActLicense container, you have to create it manuallyusing activation files.

Customer


Import LIF file

Create RAC file for new created CmActLicense container


Customer

Transfer RAU file to PC with CmActLicense container


Select “Manual CmContainer Creation”

Create license information file (LIF)


Select “Create RAU file”

Import RAC file




Import RAU file to activate CmActLicense container

License activation can be started


Customer

Transfer LIF to PC where CmActLicense container

should be created

The license information file (LIF) is the basis for creating CmActLicense containersmanually. You only have to create the LIF once. You then can use the file tocreate several CmActLicense containers. Each CmActLicense container createdfrom the same LIF is given a unique serial number. After you created a newCmActLicense container, you have to activate the CmContainer with an RAU filethat you request from dSPACE License Central.

You have to perform the following main steps to create a CmActLicensecontainer manually:

1. Create a license information file (*.WibuCmLif). Use dSPACE InstallationManager to do this. Refer to How to Create a License Information File (LIF)on page 157.

2. Create an RAC file (*.WibuCmRaC) on the basis of the LIF. Use CodeMeterControl Center to do this. Refer to How to Create an Initial RAC Fileon page 111.

3. Request an RAU file (*.WibuCmRaU). Use dSPACE Installation Manager to dothis. Refer to How to Request an RAU File for the New CmActLicenseContainer on page 159




4. Update the CmContainer with the delivered RAU file (*.WibuCmRaU). UseCodeMeter Control Center to do this. Refer to How to Update aCmContainer with an RAU File on page 117.

How to Create a License Information File (LIF)

To create a license information file (LIF) that is the basis for creating aCmActLicense container manually.

Objective

You only have to create the LIF once. You can then use the file to create severalCmActLicense containers. Each CmActLicense container created from the sameLIF is given a unique serial number.

Basics

To create a license information file (LIF)




Method


4 Select Manual CmContainer Creation and click Next.

How to Create a License Information File (LIF)


5 Click Create License Information File.

6 Select Save License Information File and specify the path to save the LIF file(*.WibuCmLif), i.e., C:\dSPACE\*.WibuCmLif.

7 Click Next.

dSPACE Installation Manager displays the result as follows:

8 Click Close.

You created and saved a license information file (*.WibuCmLif).Result



§ Transfer the LIF file (*.WibuCmLif) to the PC on which you want to create aCmActLicense container. Do this with a USB stick or via a network folder, forexample.

§ Create an RAC file (*.WibuCmRaC) on the basis of the LIF file. Use CodeMeterControl Center to do this. Refer to How to Create an Initial RAC Fileon page 111.

Next steps

How to Request an RAU File for the New CmActLicense Container

After you created a new CmActLicense container, you have to activate thecontainer with an RAU file (*.WibuCmRaU) that you have to request via dSPACEInstallation Manager.

Objective


§ An RAC file (*.WibuCmRaC) exists and is available on the PC with dSPACEInstallation Manager. Refer to How to Create an Initial RAC File on page 111.

Preconditions

To request an RAU file for the new CmActLicense container

1 From Start – All Programs – dSPACE Installation Manager, select dSPACEInstallation Manager



Method




4 Select Manual CmContainer Creation and click Next.

5 Select Create RAU file and enter the path to the RAC file.

6 Click Yes to start the creation process.

7 Select a folder to store the RAU file (*.WibuCmRaU) in and click Save.

Note


On the basis of the delivered RAC file, dSPACE Installation Manager createsan RAU file (*.WibuCmRaU) that contains information about the createdCmContainer.




8 Click Close.

You received the requested RAU file (*.WibuCmRaU).Result

§ Transfer the RAU file (*.WibuCmRaU) to the PC with the CmActLicensecontainer. Do this with an USB stick or via a network folder, for example.

§ Update the CmActLicense container with the delivered RAU file(*.WibuCmRaU). Use CodeMeter Control Center to do this. Refer to How toUpdate a CmContainer with an RAU File on page 117.

Next steps



License Handling for SMS Contracts

dSPACE provides an optional Software Maintenance Service (SMS) contract. Thiscontract extends the initial maintenance period of a software product, whichends six months after the delivery date.

The workflows describe the steps required for license handling, for example, forupdating an SMS contract or for purchasing a new SMS contract.

Motivation


Workflows for Updating to dSPACE Release 2018-A (with SMSContract) ............................................................................................. 163

Workflows for Updating an SMS Contract ........................................... 167

Workflows for Purchasing a New SMS Contract ................................... 168


Workflows for Updating to dSPACE Release 2018-A (with SMS Contract)

You have a Software Maintenance Service (SMS) contract and want to updateyour software from an earlier Release to dSPACE Release 2018-A.

Use case

Tip

The workflows show the steps for online activation using dSPACEInstallation Manager.

Focus of workflows



If you still use the (green) WibuKey dongle, the following workflow applies.

Perform dongle migration: “Migrate from WibuKey

dongle”

Sends CmDongle and license overview sheet (via e-mail), including:

dSPACE


Perform license activation


Ticket IDs for activating licenses according to SMS contractTicket ID for dongle migration

-

-

Further information

Task Basics Instructions

Donglemigration

Basics on Dongle Migrationon page 51

How to Migrate from a WibuKeyDongle on page 53

Licenseactivation

Basics on LicenseManagement on page 13

How to Activate Licenses (Local Accessto CmContainer) on page 70

How to Activate Licenses (LAN Access toCmContainer) on page 74

How to Activate Licenses (File-BasedAccess to CmContainer) on page 80

Workflow for customersusing WibuKey dongles



If you use CmDongles delivered before dSPACE Release 2017-B, the followingworkflow applies.

Perform dongle migration: “Migrate from old CmDongle”

Sends license overview sheet (via e-mail) with Ticket IDs

for activating licenses according to SMS contract

dSPACE




Further information


Donglemigration


How to Migrate from an Old CmDongleon page 57

Licenseactivation





Workflow for customersusing existing CmDongles

Workflows for Updating to dSPACE Release 2018-A (with SMS Contract)


If you use floating network licenses, the following workflow applies.

Create new CmActLicense container or connect a CmDongle

Sends license overview sheet (via e-mail) with Ticket IDs for activating licenses according

to SMS contract

dSPACE




Set up floating network license server

Set up connection between license client and license server


If you need to use product versions of dSPACE Releases earlier than dSPACERelease 2017-B, you have to keep your FlexNet License Server running in parallel.FlexNet and CodeMeter floating network servers can be hosted on the same PC.

Note


Further information


Setting up licenseserver and licenseclients

Basics on Using FloatingNetwork Licenseson page 123

How to Set up the dSPACE LicenseServer on page 129

How to Set up a Connection BetweenClient and Server on page 133

License activation Basics on LicenseManagement on page 13

How to Activate Licenses (LocalAccess to CmContainer) on page 70

How to Activate Licenses (LAN Accessto CmContainer) on page 74


Workflow for customersusing floating networklicenses



Workflows for Updating an SMS Contract

You use dSPACE Release 2017-B or later and want to update your existingSoftware Maintenance Service (SMS) contract, for example, you want to extendthe maintenance period.

Use case

Tip

The workflow shows the steps for online activation using dSPACEInstallation Manager.

Focus of workflow

The following workflow applies for single-user licenses as well as for floatingnetwork licenses.

Customer

Purchase update of SMS contract (e.g., extension of

maintainance period)

Customer

Provide access to CmContainer


Perform license update

Sends license overview sheet (via e-mail), including

Ticket IDs for licenses that can be updated (only for information)Serial number of affected CmContainer

-

-

dSPACE

Further information


Licenseupdate


How to Update Licenses (Local Access toCmContainer) on page 89

How to Update Licenses (File-BasedAccess to CmContainer) on page 94

Workflow

Workflows for Updating an SMS Contract


Workflows for Purchasing a New SMS Contract

§ You use dSPACE Release 2018-A and want to purchase a new SoftwareMaintenance Service (SMS) contract for all licenses in a CmContainer.

§ You want to purchase a new Software Maintenance Service (SMS) contract incombination with dSPACE Release 2018-A, but you still use dSPACE Release2017-A or earlier.

Use cases

Tip


Focus of workflows



If you use single-user licenses, the following workflow applies.Workflow for single-userlicenses

Customer

Purchase SMS contract

CodeMeter licensing technology

is already used?

Yes

No

Which dongle do you use?

WibuKey dongle

Old CmDongle

Customer

Provide access to the CmContainer




Ticket IDs for licenses that can be updated (only for information)Serial number of CmContainer

-

-

dSPACE



-

-

dSPACE

Sends CmDongle and license overview sheet (via e-mail), including

Ticket IDs for activating licenses according to SMS contractTicket ID for dongle migration

-

-

dSPACE

Perform dongle migration: “Migrate from WibuKey

dongle”



Customer via Installation Manager Perform dongle migration: “Migrate from old

CmDongle”




Tip

After migration, the CmDongles also contain the WibuKey ID. Therefore,you can use the migrated CmDongle with dSPACE Release 2017-A andearlier.



Further information

ToDo Basics Instructions

Donglemigration


How to Migrate from a WibuKey Dongleon page 53

How to Migrate from an Old CmDongleon page 57

Licenseactivation


How to Activate Licenses (Local Access toCmContainer) on page 70



License update License Update on page 85 How to Update Licenses (Local Access toCmContainer) on page 89




If you use floating network licenses, the following workflow applies.

Customer

Purchase SMS contract

CodeMeter licensing technology

already used?

Yes

No

Customer

Provide access to CmContainer





-

-

dSPACE

Create a new CmActLicense container or connect a CmDongle

Sends license overview sheet (via e-mail) with Ticket IDs for activating licenses according

to SMS contract

dSPACE




Set up floating network license server

Set up connection between license clients and license server


If you need to use product versions of dSPACE Releases earlier than dSPACERelease 2017-B, you have to keep your FlexNet License Server running in parallel.FlexNet and CodeMeter floating network servers can be hosted on the same PC.

Note


Workflow for floatingnetwork licenses



Further information


Setting uplicense serverand licenseclients

Basics on Using FloatingNetwork Licenseson page 123

How to Set up the dSPACE LicenseServer on page 129

How to Set up a Connection BetweenClient and Server on page 133

Licenseactivation



How to Activate Licenses (LAN Accessto CmContainer) on page 74


License update Basics on LicenseManagement on page 13

How to Update Licenses (Local Accessto CmContainer) on page 89




Special License Handling Scenarios

Handling licenses is also required in some non-standard licensing scenarios.Motivation


Workflow for License Activation for dSPACE Release 2017-A andEarlier .................................................................................................. 173

Workflow for Replacing a Missing CmContainer .................................. 175


Workflow for License Activation for dSPACE Release 2017-A and Earlier

§ You purchased a new dSPACE system with dSPACE Release 2018-A. However,you want to use dSPACE Release 2017-A or earlier with this dSPACE system.

§ You purchased a new dSPACE product that you want to add to your existingdSPACE Release 2017-A installation.

Use cases

Tip

The workflow shows the steps for online activation using dSPACEInstallation Manager.

Focus of workflow

There are separate workflows for single-user licenses and for floating networklicenses.

Workflow




Sends dSPACE Release 2018-A, ticket IDs, and CmDongle (optional)

Single-User License

Perform license activation for dSPACE Release 2018-A

dSPACE

Sends keys.dsp and license.dsp license files

dSPACE software is ready to use

dSPACE

Floating Network License

Customer

Purchase new dSPACE system

Customer

Request license files for legacy licensing technology (keys.dsp

and license.dsp).Required information: WibuKey ID, products to be used on the

dongle, Release version

Customer

Install dSPACE Release 2017-A or earlier with delivered keys.dsp

and license.dsp license files

On host PC with installed dSPACE Release (2017-A and earlier): Install

the latest Installation Manager version

On host PC with installed dSPACE Release (2017-A and earlier):

Connect CmDongle with activated licenses

Sends dSPACE Release 2018-A and ticket IDs

dSPACE

dSPACE software is ready to use

Customer

Purchase new dSPACE system

Customer

Request license files for legacy licensing technology (keys.dsp,

license.dsp, license.dat).Required information: MAC

address of Flexera server, products to be used, Release version

Sends license files (keys.dsp, license.dsp and license.dat)

dSPACE

Customer

Set up floating network license server based on Flexera

licensing technology

Install dSPACE Release (2017-A or earlier) with delivered license files (keys.dsp, license.dsp, license.dat)

Note

Valid for floating network licenses: The dSPACE EULA does not allowFlexNet and CodeMeter license servers to provide the same floating networklicense in parallel. If you have any questions or encounter any problems,contact dSPACE Support.



Further information


Licenseactivation


How to Activate Licenses (Local Access toCmContainer) on page 70



License update License Update on page 85 How to Update Licenses (Local Access toCmContainer) on page 89


Workflow for Replacing a Missing CmContainer

§ The CmDongle is lost or damaged.

§ The CmActLicense container is no longer available, for example, because thehard disk of your PC is defective.

Use cases

Tip


Focus of workflows



There are separate workflows for the different types of CmContainer.


Send new CmDongle and new ticket IDs (via e-mail)

Send serial number of the lost or damaged CmDongle

to dSPACE (via e-mail)

CmDongle

Perform license activation on new CmDongle

dSPACE

CmActLicense

Customer

Inform dSPACE about lost or damaged CmDongle

(license on affected CmContainer was activated)


Sends new ticket IDs (via e-mail)

Create new CmActLicense container

Perform license activation on new CmActLicense container

dSPACE

Requests “Notice of Loss Commitment” from the customer

dSPACE

Customer

Customer

Inform dSPACE about missing CmActLicense container

(license on affected CmContainer was activated)

Send serial number of CmActLicense container to

dSPACE (via e-mail)

Customer

Customer

Sends signed “Notice of Loss Commitment” to dSPACE

Requests “Notice of Loss Commitment” from the customer

dSPACE

Customer

Sends signed “Notice of Loss Commitment” to dSPACE

NOTICE

Make sure that you can always determine the serial number of allCmContainers you use. dSPACE strongly recommends to document theserial numbers in a place different from the PC on which they are used.

dSPACE does not provide new CmDongles or new ticket IDs, if you are notable to determine the unique serial number and forward it to dSPACE.dSPACE agrees to the Notice of Loss / Commitment if it is possible tounambiguously identify the lost CmContainer.

If you have any questions or encounter any problems, contact dSPACESupport.

Workflow



Further information


Licenseactivation







Troubleshooting


CmDongle Firmware Update Aborts with Error Message ...................... 179

CmDongle Firmware Update Not Possible ............................................ 179


CmDongle Firmware Update Aborts with Error Message

If you perform a firmware update for CmDongles, the following error message isdisplayed: Connection to the update server failed (Error WB5000).Please check the selected server name and your networkconnection.

Problem

A possible cause for the error message is that your company uses a proxy server.If the proxy server is not configured in CodeMeter WebAdmin, it preventscommunication with the Firmware Update Server of Wibu-Systems.

To solve the problem, configure the proxy server settings as described in FAQ360. Refer to http://www.dspace.com/faq?360.

Remedy

CmDongle Firmware Update Not Possible

You cannot update the firmware of the CmDongle by means of the CodeMeterControl Center, for example, because online update via the Firmware UpdateServer of Wibu-Systems is not possible.

Problem

Troubleshooting



1. Configure the proxy server settings as described in FAQ 360. Refer tohttp://www.dspace.com/faq?360.

2. Only if remedy 1 does not solve the problem: Perform an offline update.

Download a ZIP archive containing the CmDongle firmware and detailedinstructions from http://www.dspace.com/go/cmofu. The containeddocumentation is the original user documentation from Wibu-Systems. Westrongly recommend to connect only one dSPACE CmDongle to the PC whenupdating the firmware with the cmu32 CodeMeter Universal Support Tool. Ifyou do not specify a serial number, all connected CmDongles that can beupdated will be updated.

This remedy also is described in FAQ 364. Refer tohttp://www.dspace.com/faq?364. availalbe

Remedy

Troubleshooting



http://www.dspace.com/go/cmofu


Appendix

Appendix: Dongle Types

Below you find descriptions of all dongle types mentioned in this document aswell as their relevant features.

Introduction

WibuKey donglesType 1

Design Description

# 8899

WibuKey dongle Type 1


§ Have the original green design.§ Have 16-bit dongle numbers smaller than 65536.§ Have a sticker with the dongle number.§ Work with the legacy licensing method using License.dsp and Keys.dsp files.§ Suitable for legacy licensing for all Releases up to and including dSPACE Release 2017-A.§ Must be migrated to CmDongle 3-xxx to be used with dSPACE Release 2017-B and later.§ Must be migrated using latest Installation Manager version as of dSPACE Release 2017-B.

CodeMeter dongles 2-xxx, delivered 12/2014 - 9/2015Type 2

Design Description

CmDongle Type 2

xxxx


§ Have the white design.§ Have 16-bit dongle numbers smaller than 65536.§ Have a small aluminum tag with the engraved dongle number.§ Work with the legacy licensing method using License.dsp and Keys.dsp files.§ Suitable with legacy licensing for dSPACE Release 3.5 on Windows XP SP3 up to and including

dSPACE Release 2017-A.§ Cannot be used for dSPACE Release 2017-B and later.§ Must be migrated to CmDongle 3-xxx if to be used with dSPACE Release 2017-B or later.§ Were recommended to be migrated to CmDongle 3-xxx, replacement supplied in Q1/2017.§ Must be migrated using the Dongle Migration tool. Refer to www.dspace.com/go/donglemigration.

Appendix



CodeMeter dongles 3-xxx, delivered 9/2015 – 12/2017Type 3

Design Description

CmDongle Type 3

xxxx


§ Have the white design with LEDs and a red plastic inlay.§ Have 16-bit dongle numbers smaller than 65536.§ Have a small aluminum tag with the engraved dongle number.§ Work with the legacy licensing method using License.dsp and Keys.dsp files.§ Suitable for legacy licensing for dSPACE Release 3.5 on Windows XP SP3 up to and including dSPACE

Release 2017-A.§ Must be migrated using the latest dSPACE Installation Manager as of dSPACE Release 2017-B.§ Can then also be used with CodeMeter licensing.§ Suitable for CodeMeter licensing as of dSPACE Release 2017-B.

CodeMeter dongles 3-xxx, delivered 1/2018 - presentType 4

Design Description

CmDongle Type 4

3xxx

Serial number

§ Have the white design with LEDs and a red plastic inlay.§ Have dongle numbers greater than 70000.§ Have large aluminum tag with a sticker stating the CmDongle serial number.§ Work for legacy licensing method using License.dsp and Keys.dsp files.§ Suitable with legacy licensing for dSPACE Releases 2013-B ... 2017-A1)

§ Can also be used with CodeMeter licensing.§ Suitable for CodeMeter licensing as of dSPACE Release 2017-B.

1) The lower limit of dSPACE Release 2013-B is due to the License Manager version used in all products in earlier dSPACE Releases.The License Manager version was limited to handling 16-bit dongle numbers.

CodeMeter dongles 3-xxx, delivered as the 2-xxx replacementType 5

Design Description

CmDongle Type 5 § Were delivered in Q1/2017 to replace existing type 2 CmDongles.§ Came without an embedded WibuKey ID (dongle number).§ Receive the embedded WibuKey ID from the type 2 dongle during dongle migration.§ Do not have an aluminum tag.§ Have to receive their aluminum tag with engraved dongle number from the migrated type 2 dongle.§ Are identical to type 3 dongles after dongle migration.

CodeMeter dongles 3-xxx, delivered with SMS updates to dSPACE Release2017-B

Type 6

Design Description

CmDongle Type 6

3xxx

Serial number

§ Were delivered in Q1/2018 to replace existing WibuKey dongles.§ Do not have an embedded WibuKey ID (dongle number).§ Receive the embedded WibuKey ID from the WibuKey dongle during dongle migration.§ Have a large aluminum tag with a sticker with the CmDongle serial number.§ Are identical to type 3 CmDongles after dongle migration. The only difference is the number on the

aluminum tag, which is the serial number instead of the dongle number.

Appendix


The same procedure has to be applied if WibuKey dongles (Type 1) are notsubject to the SMS update in Q1/2018, but are later updated to dSPACE Release2017-B or later.

Dongle types and supporteddSPACE Releases

Dongle Type Supported dSPACE Releases

Type 1 All Releases up to and including dSPACE Release 2017-A.

Type 2 dSPACE Release 3.5 ... dSPACE Release 2017-A. Will be migrated to type 3.

Type 3 dSPACE Release 3.5 ... dSPACE Release 2017-A and later.

Type 4 dSPACE Release 2013-B ... dSPACE Release 2017-A and later.§ All CmDongles delivered by the end of 2017, including their migrated replacements, support all Releases as of

dSPACE Release 3.5.§ All CmDongles delivered as of 1/2018 support dSPACE Release 2013-B and later.

Appendix: Dongle Types


Appendix


A

activatinglicenses 65

attributesCmContainer 42ticket 47

B

basicsfloating network licenses 123

C

CmActLicense 12CmActLicense containers

identifying 124CmContainer

attributes 42basics 11CmActLicense 12CmDongle 12serial number 42

CmDongle 12compatibility 22firmware update 61migration 57WibuKey ID 42

CodeMeter Control Centercreate RAC file 111update CmContainer with RAU file 117

CodeMeter Runtime 13internal communication 22

Common Program Data folder 8CommonProgramDataFolder 8compatibility

CmDongle 22WibuKey dongle 22

D

Documents folder 8DocumentsFolder 8dongle migration

migrating dongles 51dSPACE License Central 13

Internet connection 21dSPACE License Manager (Legacy) 23dSPACE License Server

system requirements 128

E

evaluation license 17

F

file-based access to CmContainer 145firmware update CmDongle 61floating network licenses

basics 123identifying 124

license behavior 125

L

LAN access to CmContainer 142license activation

file-based access to CmContainer 80LAN access to CmContainer 74local access to CmContainer 70

license confirmation manually 142, 145local access to CmContainer 140

license deactivationdeactivating licenses 99file-based access to CmContainer 105local access to CmContainer 103

license typessupported 12

license updatefile-based access to CmContainer 94LAN access to CmContainer 92local access to CmContainer 89updating licenses 85

licensesactivating 65attributes 44floating network licenses 124

Local Program Data folder 8LocalProgramDataFolder 8

M

maintenance period 16migrating

WibuKey dongle 53migration

CmDongle 57

R

RAU filemanual request 150

request ticket information 47requesting RAU file 150

S

setting up license client 126setting up license server 126SMS period 16supported license types 12system requirements

dSPACE License Server 128

T

ticket 13ticket group 13ticket group ID 13ticket ID 13ticket states 47

W

WibuKey dongle

compatibility 22disabling 60migration 53

Index


Index
