OPC UA
      Back to home
      1. Help Center
      2. Applications
      3. OPC UA

      Generating License Files for OPC UA

      License allocations need to be created with new instances of OPC UA installations.

      1      Introduction

      These instructions are to be used by Owl Production to create a license file for customers who have purchased OPC UA Application Connector Version 1.0.0.0 on an OPDS. The customer uses OPC UA to generate a key file (which has a .key extension). The customer sends the key file to Owl, and Owl Production creates a license file (OPCUA-License.lcn) for the number of tags purchased. These instructions explain how to create the license file using the OPC UA License Creator found in the OPC Licensing Support Tool application (OPCLicensingSupportTool).

      2      Requirements

      Before you begin the procedures, make sure that you have the following:

      • The customer’s key file.
      • The number of tags this customer purchased. This information should be in the Work Order.
      • The customer’s email address.
      • The customer’s mailing address.
      • If using a Linux environment, you need CentOS 7 or higher and Internet access.
      • The OPCLicensingSupportTool which contains the zip file.

      3      Procedures

      3.1        Starting the OPC UA License Creator Tool

      Note: Save the key file in a directory of your choice and make note of the directory path. You will need this information in section 3.2.

      You can use the OPC Licensing Support Tool application in either a Windows or Linux environment.

      Important: Before starting OPCLicensingSupportTool on either Windows or Linux, you must install the dotnet-runtime-2.2 dependency. The OPCLicensingSupportTool requires the dotnet-runtime-2.2 dependency to run.

      3.1.1       Windows

      To run the OPCLicensingSupportTool on Windows:

      1. Navigate to the directory where the zip file is located, and double-click the zip file.
      2. Double-click dotnet-runtime-2.2.8-win-x64.exe to install it.
      3. Double-click the License Creator folder to open it.
      4. Double-click exe to run the application.

      The OPCLicensingSupportTool runs. A Command Prompt window appears showing possible options.

      3.1.2       Linux

      Note: To perform this procedure, CentOS 7 or higher is required. In addition, you need to have Internet access.

      To run the OPCLicensingSupportTool on Linux:

      1. Obtain root access.
      2. Type the following command, then press Enter to install this file. yum install rh-dotnet22-runtime
      3. At the command line, enter the directory path where OPCLicensingSupportTool is located on your machine.

      Important: The OPCLicensingSupportTool is included in the LicenseCreator.zip file.

      1. Type the following command and press Enter to run this file.

      scl enable rh-dotnet22 'dotnet OPCLicensingSupportTool.dll'

      The OPC Licensing Support Tool application runs. A command line appears showing possible options.

      3.2        Creating the License File

      Use the following procedure to create a license file. In this procedure you enter the number of tags the customer has purchased, encrypt, and name the folder where the license file will be stored.

      To create a license file:

      1. In the OPC Licensing Support Tool, select option 1.
        • prompt appears for the number of tags purchased.
      2. Type the number of tags purchased (for example: 1000), and press Enter.
        • prompt appears for the rsa-digital.xml file directory path.

      Note: The rsa-digital.xml file encrypts the customer’s license file. The rsa-digital.xml file is normally located in the tool’s default directory:

      <drive>/OPCLicensingSupportTool/LicenseCreator.zip/LicenseCreator/rsa/

      1. Do one of the following:
      • If the rsa-digital.xml file is located in the default directory, leave this entry blank, and press Enter.
      • If the file is located in a different directory, type the directory path, and press Enter.

      A prompt appears for the rsa-features.xml file directory path.

      Note: The rsa-features.xml file also encrypts the customer’s license file and is normally located in the tool’s default directory:

      <drive>/OPCLicensingSupportTool/LicenseCreator.zip/LicenseCreator/rsa/

      1. Do one of the following:
        • If the rsa-features.xml file is located in the default directory, leave this entry blank and press Enter.
        • If the file is located in a different directory, type the directory path, and press Enter.
        • prompt appears for a unique identification for the folder where the license file will be stored.  
      2. Type a unique identification for the folder where the license file (OPCUA-License.lcn) will be stored, and press Enter. For example, you can use the customer’s purchase order number or customer’s name and the date.

      Note: When a new license file is generated, it is always named (OPCUA-License.lcn). By giving the folder where this file is stored a unique identification, you associate the purchased tag amount to the specific customer. This supports Owl archival purposes.

      • prompt appears for the absolute path, which includes the filename and extension, of the key file received from the customer. (This directory path is where you stored the key file on your computer in section 3.1 above.)
      1. Type the directory path of the key file, including the key file name and the file extension, and press Enter.

      The application creates the license file (OPCUA-License.lcn) based on the information you entered and then encrypts the file.

      3.3        Sending the License File to the Customer

      The license file should be sent to the customer by email and regular mail.

      Note: You may want to check with Support in case they want to contact the customer.  

      To send the license file:

      1. Email the license file to the customer.
      2. As a backup, copy the license file onto a CD, address it and send it to the customer.