Licensing your STK Engine Application
- Jul 31, 2017
- Tech Tip
- STK Engine
Congratulations! You’ve successfully harnessed the power of STK’s application engine development capabilities to create a kick-butt custom-built engine-based application that is guaranteed to turn heads and fill a much needed gap in streamlined productivity tools, while simultaneously earning you kudos from those with direct input on your performance reviews. Woot! Fist bump! Next step – license this puppy and roll it out to internal, and hey why not even external, customers who may, or may not, have access to the various full-out STK desktop licenses needed to completely power up this bad boy.
Enter the STK Engine Runtime license, more affectionately known as STK-ERT. The standard STK-ERT license comes already embedded with STK Pro, Analysis Workbench, Integration and TIM capability. If your application needs nothing more to invoke all its bells and whistles, then the standard STK-ERT license is right for you. If your developed application calls up additional STK add-on module capabilities, maybe STK Communications and Radar for example, then you would purchase individual STK-ERT Extensions for each of those additional features. The beauty of the STK-ERT license is in allowing users to run your custom-built application without needing them to have access to full-out STK Desktop licenses.
Also embedded within your STK-ERT license will be a unique Vendor ID assigned specifically for you by AGI (yup, probably me) at the time of initial licensing. This Vendor ID will remain the same over the lifetime of your application. Before your application will recognize your STK-ERT license(s), this same Vendor ID also must be coded into your developed application before bundling it up for deployment, as it is the Vendor ID that ties the application and license together. Note that STK-ERT licenses will only run a Vendor ID-encoded application. Forgetting to code the Vendor ID into your application, and then running it on an STK-ERT license, will result in a “No License Found” error. Reference the Vendor ID property on the STK X / AgSTKXApplication Object page for specific help in coding your assigned Vendor ID into your developed application.
Finally, like so many distinctive ingredients, each one equally crucial to the ultimate consistency and flavor of the creation, and all neatly tucked inside the steaming outer crust of Grandma’s perfectly baked homemade pies (what . . . I’m hungry), if you were to look at the contents of your STK-ERT license, you would not outwardly see all the related product licenses as you would in a standard STK desktop license. Have no fear, though. All the relevant licenses are indeed there, each neatly encrypted inside the outer shell of the single “FEATURE STKEngRuntime” license that you will see inside the file.
For detailed instructions on building and licensing STK Engine applications, visit the online Programming Interface help, and expand “Develop Custom Applications.”