Creating a License Technology

FlexNet Operations 2014

Administer Operations | Create a License Technology

Administer Operations | Manage License Technologies | Add a License Technology

To create a license technology

1. Navigate to Administer Operations > Create a License Technology.
2. Enter the following information in the Create a License Technology page:

Note: Default email templates are located in the <ops_install_dir/site/webapps/flexnet/templates directory. Customized email templates are located in the <ops_install_dir/custom/webapps/flexnet/templates directory, whose path mimics the default templates path. Relative email template paths are partial paths that start with the templates directory.

Creating License Technology

Field

Description

Name

Name to uniquely identify this license technology. This is a required field and must be unique.

Description

Describe the characteristics of this license technology that make it unique. The description can be changed at any time.

State

A new license technology is always created in draft state. Any attribute except the name of the license technology can be edited in this state.

Once a license technology is deployed, no attributes can be edited. Its state can be changed back to draft only if there are no products, suites, and licenses models (entities in draft state excluded) linked to the technology. A license technology can only be deleted in draft state.

Type

Select a license generator type:

• Manual: licenses are generated by a customer support representative manually using a third-party system.Since this license generator is not integrated into FLEXNet Operations, when a user generates a license, the generated fulfillment is placed on hold and an email address is sent to the administrator at the address configured in System Configuration. The administrator logs in to the third-party system and generates the license, and then returns to FlexNet Operations to set the license on the on-hold fulfillment record. The user can then download the license.
• Hands-Free: licenses are generated programmatically using a third-party system. After generation, a fulfillment record is placed on hold. Web services are used to update the license text on the fulfillment record. Please refer to the FlexNet Operations Web Services Guide for more information.
• Custom Generator: licenses are generated by FlexNet Operations, by implementing a CustomGenerator interface.

Refer to the Getting Started Guide for non-FlexNet License Technologies for more information on these types.

Generator Validator

Enter the name of the Java class that validates products and license models for this License Technology. This class must implement the com.flexnet.operations.publicapi.LicenseGeneratorValidator interface. For instructions on building and correctly placing the class file in your FlexNet Operations installation, refer to the FlexNet Operations Implementation Guide.

Entitlement Certificate Template

The relative path of the XSL template used to generate an entitlement certificate for this license technology. When no path is specified, the system-level entitlement certificate template specified in the System Configuration settings is used instead. Maximum length: 255 characters.

See the FlexNet Operations Implementation Guide additional details about email templates.

Entitlement Certificate Email Template

The relative path of the XSL template used to create the body of the email for sending an entitlement certificate email attachment for this license technology. When no path is specified, the system-level entitlement certificate email template specified in the System Configuration settings is used instead. Maximum length: 255 characters.

See the FlexNet Operations Implementation Guide additional details about email templates.

Multiple Consolidated Licenses Email Template

The relative path of the XSL template used to send a multiple consolidated license email attachment for this license technology. When no path is specified, the system-level version of this template specified in the System Configuration settings is used instead. Maximum length: 255 characters.

See the FlexNet Operations Implementation Guide additional details about email templates.

Consolidated License Email Template

The relative path of the XSL template used to send a consolidated license email attachment for this license technology. When no path is specified, the system-level version of this template specified in the System Configuration settings is used instead. Maximum length: 255 characters.

See the FlexNet Operations Implementation Guide additional details about email templates.

Multiple License Files Email Template

The relative path of the XSL template used to send a multiple license email attachment for this license technology. When no path is specified, the system-level version of this template specified in the System Configuration settings is used instead. Maximum length: 255 characters.

See the FlexNet Operations Implementation Guide additional details about email templates.

License File Email Template

The relative path of the XSL template used to send a license email attachment for this license technology. When no path is specified, the system-level version of this template specified in the System Configuration settings is used instead. Maximum length: 255 characters.

See the FlexNet Operations Implementation Guide additional details about email templates.

License Consolidator

Enter the name of the Java class that consolidates licenses for this License Technology. This class must implement the com.flexnet.operations.publicapi.LicenseConsolidator interface. For instructions on building and correctly placing the class file in your FlexNet Operations installation, refer to the FlexNet Operations Implementation Guide.

Filename Generator

Enter the name of the Java class that generates license file names for this License Technology. This class must implement the com.flexnet.operations.publicapi.MultipleLicenseFilenameGenerator interface. For instructions on building and correctly placing the class file in your FlexNet Operations installation, refer to the FlexNet Operations Implementation Guide.

Is Counted?

Indicate whether or not the user will be prompted to provide a fulfillment count when activating the license. If a license technology is counted,license models belonging to it can also be defined as counted.

For an uncounted license model, a license is generated for only 1 copy at a time.

Does this license technology generate replacement keys (i.e., regenerative licensing)

Select whether or not the license technology generates replacement keys. Such a license technology is called regenerative.

• With a regenerative (or replacement) license technology, the last license issued overwrites the previous one. Indicate whether or not the license technology is replacement or incremental. A master copy of the license is stored on the host. For all license lifecycle activities, such as returns or repairs, the master license is updated by FlexNet Operations. When a user downloads a license for a fulfillment record belonging to a replacement technology, the license on the corresponding host is given to the user. For more information on specific implementation, refer to the file /samples/CustomReplacementGenerator in your FlexNet Operations installation directory.
• For an incremental license technology, each fulfillment record contains its own license.

Is Return Operation Allowed?

Indicate whether the technology alllows license returns.

Is Repair Operation Allowed?

Indicate whether the technology allows license repairs.

Is Rehost Operation Allowed?

Indicate whether the technology allows license rehosts.

Is Stop Gap Operation Allowed?

Indicate whether the technology allows stop gap licenses.

Is Emergency Operation Allowed?

Indicate whether the technology allows emergency licensing.

Is Publisher Error Correction Operation Allowed?

Indicate whether the technology allows publisher correction operations.

Is Upgrade/Upsell/Renew Operation Allowed?

Indicate whether the technology allows upgrade, upsell or renewal operations.

File Definitions

If the license technology uses multiple license files, you can define mutiple file types for each fulfillment record. The end user will be able to download multiple files from each fulfillment record, or receive multiple files of different types as email attachments.

1. Click Add File Definition to add a license file type.
2. In the Create File Definition window, enter a name for the file definition.
3. Select whether the license file type is text or binary.
4. Optionally, enter a description of the file type.
5. If any custom host type attributes are defined for this type, enter values for these attributes. (See Managing Custom Host Attributes.)
6. Click OK.

Host Type (non-FlexNet)

Host type represents a class of device on which the license-enabled code is intended to run. When a license is generated for a product, FlexNet Operations prompts for the attributes that belong to the product’s host type. The settings in the Create Host Type window differ for FlexNet and non-FlexNet licensing technologies.

Host types can be included in a license technology either by adding a new host type or selecting an existing host type.

To add a host type

1. Click Add Host Type.
2. In the Create Host Type window, enter a name for the host type.
3. Optionally, enter a description of the host type.
4. Enter the name of the custom class (Hostid Generator Class) used to generate host IDs for the host type. This custom class should implement the interface:

com.flexnet.operations.publicapi.HostIdentifierGeneratorByHostType

5. Click OK.

To select an existing host type

1. Click Select Host Type.
2. In the Select Host Type window, click the checkbox for a host type, and then click OK.

For instructions on adding a host type to FlexNet licensing technology, see Host Type (FlexNet).

Host Type (FlexNet)

Host types can be added to FlexNet licensing technology. The settings in the Create Host Type window differ for FlexNet and non-FlexNet licensing technologies. For FlexNet licensing technology, these host types apply only to FlexNet Embedded licensing. A host type is typically a device model, and each host type can specify a set of custom attributes to track for that model.

Host types can be included in a license technology either by adding a new host type or selecting an existing host type.

To add a host type

1. Click Add Host Type.
2. In the Create Host Type window, enter a name for the host type.
3. Optionally, enter a description of the host type.
4. Set the Publisher Identity property. The Publisher Identity selection specifies the default publisher identity for this host type. This Publisher Identity is selected by the system, by default, when a device of this host type is created.
5. Set the Visible on Self-Service Portal property. Click Visible on Self-Service Portal if you want portal users to be able to select this host type from a list of available host types when they register a device.
6. Configure Device ID Types. Check all device ID types that you want to allow. For the ID type you want to be the default device ID type for the current host type, click the radio button under Default.
7. Click OK.

To select an existing host type

1. Click Select Host Type.
2. In the Select Host Type window, click the checkbox for a host type, and then click OK.

For instructions on adding a host type to a non-FlexNet licensing technology, see Host Type (non-FlexNet).
3. Click Save to save your changes, Reset to clear all fields, and Add New to specify a different license technology.
4. Click Next to specify attributes for a license generator configuration.

See Also

Configuring Email Template Settings

FlexNet Operations 2014 Help Library

June 2015

 Copyright Information | Contact Us

Open topic with navigation