Revenera Documentation site will be unavailable on July 2nd due to scheduled maintenance. For more information see the status dashboard.

Showing results for 
Show  only  | Search instead for 
Did you mean: 

FlexNet Operations UAT Issue (05 May 2022): FlexNet Operations LLM Customers Using FlexNet Embedded Licensing

FlexNet Operations UAT Issue (05 May 2022): FlexNet Operations LLM Customers Using FlexNet Embedded Licensing

As you have been notified in Revenera’s various status updates, device-related data no longer exists in FlexNet Operations UAT due to an issue that UAT experienced on 05 May 2022. The express purpose of this document is to provide guidance on how required and related data for devices can be restored in UAT.

For additional guidance, you might want to see FlexNet Operations UAT Issue (05 May 2022): FAQs.

Impacted Functionality

The functionality impacted by the UAT outage includes FlexNet Embedded licensing and Usage. The scope of entity data that is now inaccessible includes:

  • Publishers
  • Identities
  • Device series
  • Device models
  • License servers
  • Standalone devices
  • Served clients

These entities must be recreated in the UAT environment.

Verification of Other Entities

Producers are strongly advised to login to the UAT Producer Portal and End-User Portal in FlexNet Operations to confirm that the following entities are accessible and still populated with data:

  • Accounts
  • Members
  • User-defined fields
  • Entitlements
  • Product setup

For information about accessing these entities, refer to the following documentation under Resources and Documentation in the Producer Portal:

Recreating Device Data

Because device data is no longer accessible, producers must recreate device data from scratch in the Producer Portal. This process includes setting up publisher and identity information.

Use the following steps to guide you through this process.

Step 1: Obtain Publisher and Identity Data

To recreate publisher identities, producers first need to obtain the publisher and identity data from their Production environment. Follow these steps:

  1. Login to the Production environment using System Administrator credentials. Use the following URL:

  1. Navigate to Manage Hosts > List Publishers (under Device Licensing).
  2. Copy/record the five sets of publisher keys for each publisher you want to recreate in UAT.
  3. Navigate to Manage Hosts > List Identities (under the Device Licensing list).
  4. Click the desired identity, and select Binary File to download the Back Office Identity file (IdentityBackoffice.bin).
  5. Record the publisher and identity name, and save the file with a unique name.
  6. Repeat this procedure for each identity you want to export to UAT.

For more information about publisher identities, see Getting Started Guide for FlexNet Embedded Licensing.

Step 2: Create an Identity in the UAT

Once the identify information has been downloaded from the Production environment, producers need to create their publisher identities in the UAT. Follow these steps:

  1. Login to the UAT environment.
  2. Navigate to Manage Hosts > Add Publisher (under Device Licensing).
  3. Add the publisher name, description (Notes), and the five sets of keys; and click Save.
  4. Repeat the previous steps for each publisher.
  5. To add identities, navigate to Manage Hosts > Add Identity (under Device Licensing).
  6. Select the publisher name from the drop-down menu, and then enter the identity name.
  7. Select Choose File next to Custom IdentityBackOffice.bin to browse to the location of the saved back-office identity files.
  8. Select the desired identity file, and click Save.
  9. Repeat step 5 through 8 for each identity.

For more information about publisher identities, see Getting Started Guide for FlexNet Embedded Licensing.

Step 3: Create Custom Device Series, Device Model, or Server Host Types

When a publisher identity is added, a default device series (FLX_CLIENT_SERIES), default device model (FLX_CLIENT), and default server host type (FLX_SERVER) are automatically created. Based on UAT requirements, producers might need to create custom versions of these entities.

NOTE: When creating a custom device model, ensure that the identity, the default Host ID type, and the allowed Host ID types for the model reflect the values you want.

For more information about these device-related entities and how to add new ones, refer to Getting Started Guide for FlexNet Embedded Licensing.

Step 4: Re-enable Producer User Settings

If a producer user is experiencing authorization issues on CLS instances, the producer must manually re-enable the producer user's CLS authorization. Use this procedure:

  1. Navigate to Manage Hosts > Producer User for CLS (under Device Licensing).
  2. Unselect Enable Producer User for CLS, and click Save.
  3. To re-enable the producer user's CLS authorization, reselect Enable Producer User for CLS, and click Save.

The producer user's CLS authorization is now re-established.

Step 5: Register New Devices and Create/Provision License Servers

After the publisher identities have been set up (and any required custom device series, device models, or server host types), UAT Producer Portal users can create and register new devices and/or create and provision license servers.

For information about setting up devices and license servers, see Getting Started Guide for FlexNet Embedded Licensing.

Consider the following:

  • Until new devices and license servers are created in UAT, no device data exists in UAT.
  • Existing entitlements can be used to provision license servers or to map add-ons to standalone devices.
  • Available quantity will now be the full entitlement line quantity.
  • Any application using a UAT identity prior to 05 May 2022 might no longer be able to activate with UAT (in which case the application must be rebuilt using the newer identity).
  • Served devices polling for features can continue to poll against the newly created license server. However, polls to previous CLS instances will fail. (Clients should be changed to request features from the newly provisioned license servers.)

Step 6: Handle Usage Data

(For metered usage only) Usage data is available for download, but the data is current only up to 05 May 2022. The recommendation is that new entitlements be provisioned for accounts intended for Usage.

Step 7: Verify Functionality in End-User Portal

Once you have set up identity information and recreated devices and license servers in the UAT Producer Portal, login to the UAT End-User Portal and verify that you can perform the basic and device-related operations.

For information about performing these operations, refer to the Getting Started Guide for FlexNet Embedded Licensing.

Basic Checks

Verify that you can perform the following:

Device-Related Checks

Verify that you can perform these basic device-related operations:

  • Register/activate a new device.
  • Perform offline device management. Some clients might require an updated identity.

Step 8: (Customers Using Cloud Monetization API) Re-establish JSON Security

For those customers using Cloud Monetization API (available with CLS instances only), the JSON security needs to be re-established. The public key for the CLS must be re-uploaded for the newly created CLS instances. Use the producer user token to re-upload the certificate so that access requests against the CLS instances are successful. Follow these steps to re-upload the public key:

  1. For the upload, use the /rest_licensing_keys endpoint from the CLS REST APIs for the CLS instance.
  2. Attach the previously generated public key in DER format.
  3. For Authorization, enter the Bearer token for the CLS producer user.
  4. Upload the public key.

Additional Help

Should you need additional help in dealing with this UAT issue, enter a case via the Get Support menu in the Revenera Community. Be sure to specify your UAT environment and tenant ID and provide details about your issue.

Related Articles

The following additional articles related to the 05 March 2022 UAT issue are available:

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎May 18, 2022 03:55 PM
Updated by: