Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

Activate License for Custom Hardware VI

LabVIEW 2012 Third Party Licensing & Activation Toolkit Help

Edition Date: June 2012

Part Number: 373159C-01

»View Product Info
Download Help (Windows Only)

Owning Palette: Third Party Licensing & Activation VIs

Requires: Third Party Licensing & Activation Toolkit

Activates a license file and binds it to a specific hardware target. You can choose to allow automated online activation, manual activation, or both, but you must manually select the polymorphic instance you want to use.

When you bind a license to a specific custom hardware ID, this VI adds the ID to the license, and if a user tries to use the license on a different target, the status of the license is invalid. If you do not need to bind a license to a specific hardware target, use the Activate License VI.

Details  Examples

Use the pull-down menu to select an instance of this VI.

Activate Automatically

activation server URL specifies the path to the getcode.asp script file that creates the activation code(s) needed to activate the license. LabVIEW concatenates the activation server URL and the activation server name into a single string to locate the correct script file. Typically, the URL is /<path_to_activation_server>/unlock/getcode.asp.
Note  Activation code 1 is the RegKey1 code that you generate in LFEdit, and activation code 2 is the RegKey2 code that you generate in LFEdit.
activation server name specifies the name of the server on which you want LabVIEW to look for the getcode.asp script file that creates the activation code(s) needed to activate the license. If you use an Instant SOLO Server account, specify the value swk to identify the correct server.
license file info contains information that identifies the run-time license that protects the add-on when users run the add-on.
handle is a reference to the license file and is used internally only. You do not need to change this input.
full path specifies the full, or absolute, path to the license file on the user machine.
password specifies the password for the license file.
license ID is the license ID that the user receives when he or she purchases the add-on. The user enters the license ID only when performing the automated activation process through an Internet connection.
license password is the password that the user receives when he or she purchases the add-on. The user enters the license password only when performing the automated activation process through an Internet connection.
custom hardware ID specifies the serial number of the hardware target to which you want to bind the license.
error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
trigger code seed is the trigger code stored in the product definition you create in LFEdit. Refer to the EZ Trigger documentation on the SoftwareKey website to learn more about trigger codes.
encryption seed is the Reg Key 2 seed stored in the product definition you create in LFEdit.
license file info out returns information about the run-time license from the license file info input.
handle returns the reference that is used internally only.
full path returns the full, or absolute, path to the license file that the user wants to activate.
password returns the password to the license file that the user wants to activate.
activation successful? indicates whether the add-on was successfully activated. All inputs must be valid for successful activation.
error out contains error information. This output provides standard error out functionality.

Activate Manually

custom hardware ID specifies the serial number of the hardware target to which you want to bind the license.
user code 1 (activation session number) is a code that you can generate randomly from the PP_COMPNO function in keylib32.dll or keylib64.dll. Use this code to create the activation code(s) that the user enters in activation code 1 or activation code 2.
license file info contains information that identifies the run-time license that protects the add-on when users run the add-on.
handle is a reference to the license file and is used internally only. You do not need to change this input.
full path specifies the full, or absolute, path to the license file on the user machine.
password specifies the password for the license file.
activation code 1 is the first activation code that you create based on user code 1 and user code 2. The user enters this code after he or she receives the activation code(s) via the Web or telephone.
Note  Activation code 1 is the RegKey1 code that you generate in LFEdit, and activation code 2 is the RegKey2 code that you generate in LFEdit.
activation code 2 (Optional) is the second activation code that you create based on user code 1 and user code 2. The user enters this code if he or she receives two activation codes via the Web or telephone.
error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
trigger code seed is the trigger code stored in the product definition you create in LFEdit. Refer to the EZ Trigger documentation on the SoftwareKey website to learn more about trigger codes.
encryption seed is the Reg Key 2 seed stored in the product definition you create in LFEdit.
license file info out returns information about the run-time license from the license file info input.
handle returns the reference that is used internally only.
full path returns the full, or absolute, path to the license file that the user wants to activate.
password returns the password to the license file that the user wants to activate.
activation successful? indicates whether the add-on was successfully activated. All inputs must be valid for successful activation.
error out contains error information. This output provides standard error out functionality.

Activate License for Custom Hardware Details




 Third Party Licensing & Activation Toolkit Home

Examples

Refer to the following VIs for examples of using the Activate License for Custom Hardware VI:

  • Activate License - Activate Automatically with Custom Hardware VI: labview\examples\addonlicensing\03 Activate License
  • Activate License - Activate Manually with Custom Hardware VI: labview\examples\addonlicensing\03 Activate License

 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit