The easiest way to license an executable is through the Instant Protection PLUS 3 licensing injector/wrapper tool. It has an easy-to-use licensing wizard, and is available from SoftwarKey.com / Concept Software. This exercise will show how to license a LabVIEW-built executable using Instant Protection PLUS 3.
Prerequisites
Open LabVIEW Executable.lvproj
View the source code of LabVIEW Executable.vi and test its functionality.
Close LabVIEW Executable.vi
In the project explorer window, right click on “LabVIEW Executable” under “Build Specifications” and select build.
When the build is complete, click Explore to view the executable file.
Double click on LabVIEW Executable.exe to run it. See that the VI runs instantly.
The first time that the licensed application is run, it is important to change the necessary permissions of all license files and registry entries if you changed the License File Location setting on step 13 to something other than the default "Auto-create in the current user registry". This can be done by calling the EXE with the command line parameter /OPENLF. Since this needs to be done at install time, your installer can copy over the licensed EXE file to the target system and immediately call it with the /OPENLF command line parameter to set the permissions and exit.
This hands-on covers licensing a LabVIEW Executable using SoftwareKey Instant Protection PLUS 3. If you need more advanced licensing functionality, you can also utilize Third Party Licensing & Activation Toolkit Licensing API. For licensing a LabVIEW Library, you can use the Third Party Licensing & Activation Toolkit Add-on Licensing Tool.
I keep getting an error when I try to login into the test account :
a. Author ID: 3801470
b. Login: 3801470
c. Password: labviewtplat
Please help...
EDIT (3h later) : and now it work...
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
I'm glad that you got it to work. If you do need further help with InstantPLUS, you should contact ConceptSoftware for support since they are the developers of the product. We endorse it and wrote a tutorial for it, but they'll be able to fully understand what problems you are having.
ok, thx
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
Have you been able to protect labview exe using this product? Can ConceptSoftware really support use with LabVIEW? Last time I checked they could not.
At SAPHIR, we are currently using ConceptSoftware tools to protect and activate all of our toolkits --> https://decibel.ni.com/content/groups/saphir-toolkit and our application --> https://decibel.ni.com/content/groups/saphir-topaze.
As Thoric asks, I'd to hear more about your concern.
Nothing unsafe that I'm aware of; although we currently use hardware locks. Would you say this toolkit is secure enough to protect expensive applications?
I'm just looking for simple and customizable implementation in LabVIEW and some examples and LabVIEW specific support if need be.
Is this possible now? Before it didn't seem like it was.
Can you guys point me where to start? I have read the NI tutorials and downloaded the toolkit.
Does the last document listed by David_L make sens for you ? VIs allow you to retrieve the status of the license file and you can do what you want in your app depending on this status.
Perhaps the most "difficult" is to understand features of Instant Plus...
I had another question.
What's the actual process for activating software in use by the client? Do you need to manually generate licence files?
I'm just going through that example now. It seems quite easy. We actually implemented something similar ourselves.
How does this (licence files) tie with InstantPlus?
How do you implement trial versions and activate/de-activate features? Is it easy?
Sorry for the million questions I'm just very keen to implement this!!
"web activation URL" - what do I need to implement to allow user to automatically activate.
Do I issue them a unique Serial No.?
What's the process you use to activate your clients software?
Hi Battler. I think it makes more sense to answer these questions in the discussion forum rather than having the comments on this document grow too long. I will answer these questions on the thread you started here: