Product Activation VI

Owning Palette: Third Party Licensing & Activation VIs

Requires: Third Party Licensing & Activation Toolkit

Configures and displays a dialog box in which users can activate an add-on license, and then activates the license. Use this VI to allow users to activate an executable add-on when the executable runs.

You can use the custom hardware ID input to bind the license to a specific hardware target.

Details  Example

	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 info contains the information you want to appear to the user in the activation dialog box. 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. 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. 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. supports automatic activation specifies whether the option to activate the add-on through an automated online process is available in the activation dialog box this VI displays when it runs. supports web activation specifies whether to enable the option to acquire activation codes through a Web page you specify in the web activation URL input. supports phone activation specifies whether to enable the option to acquire activation code(s) through a phone number that you list in the phone activation number input. web activation URL specifies the URL to the Web page that users must visit to obtain the activation code(s) they need to manually activate an add-on. phone activation number specifies the phone number that users must call to obtain the activation code(s) they need to manually activate an add-on. purchase page URL specifies the URL of the Web page through which users can purchase the add-on. This URL also is the page that the Purchase button in the activation dialog box displays in a Web browser.
	custom hardware ID specifies the serial number of the hardware target to which you want to bind the license. 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. By default, this VI does not bind the license to a specific serial number.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	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.

Product Activation Details

 Third Party Licensing & Activation Toolkit Home

Example

Refer to the Launch Activation Dialog VI in the labview\examples\addonlicensing\02 Launch Activation Dialog directory for an example of using the Product Activation VI.