Deploy a Vega Prime Application

Information on how to deploy a Vega Prime Application 1. For Deploying a Vega prime application in target machines first of all we need to generate cookie file (.mpi). 2. We can generate Cookie file by using MPIDevToolCRO utility for a specific Vega prime application.it contains the information related to the development system, the Vega prime application and the development licenses used for developing that Vega prime application. Cookie files areused to grant permission to the application when running on a deploymentsystem.

MPIDevToolCRO
MPIDevToolCRO is an executable used to generate the cookie file for a Vega Prime application on a development system.

Cookie files generation using MPIDevToolCRO

The MPIDevToolCRO is a command line only utility used to generate the Cookie file for a Vega Prime application on a development system where thedevelopment licenses are available. It is distributed with Vega Prime and isinstalled under $(PRESAGIS_VEGA_PRIME_5)\bin folder.The command line arguments for MPIDevToolCRO are:

MPIDevToolCRO [-n] [-f dev-license-list] [-l] [-h] application Where: -n: Does not print disclaimer -f dev-license-list: A comma separated list of development licenses of thefeatures used by the application. If -f is not specified on the command line, theMPIDevToolCRO will attempt to embed all development licenses that areallowed and are available to it. See -l below.

-l: Display a list of development licenses that are allowed to be embedded inthe cookie file. This information is stored in the$(PRESAGIS_VEGA_PRIME_5\bin\MPIDevToolCRO.pdm file. -h: Prints usage application: The full path and name for your Vega Prime application. Yourunique cookie file is generated for this specific build of this specificapplication. Note that there can be no spaces in the path unless the path issurrounded by quotes.For example, if you have a Vega Prime application called myApp.exe that usedthe LADBM feature, the following command line would create a valid cookiefile. $(PRESAGIS_VEGA_PRIME_5)\bin\MPIDevToolCRO -f vsg_dev, vp_base_dev,vp_ladbm_dev C:\myAppFolder\myApp.exe Where, vsg_dev and vp_base_dev are required for the Vega Prime basefeatures and p_ladbm_dev is required for the LADBM module.After executing the command, if the requested development licenses areavailable, a message will be displayed stating that the cookie file is valid, and itwill list all the embedded development licenses. In this example, a cookie filecalled myApp.mpi is created in C:\myAppFolder.

Deployment stage
This stage takes place on a deployment system where a Vega Primeapplication is set up to run with runtime licenses only. The application runssuccessfully with the appropriate permissions and keys. 1 Permissions The cookie file of the Vega Prime application is properlygenerated on a development system and is placed in the same folder as theassociated application on the deployment system. It is the user'sresponsibility to copy the cookie file to the deployment system along withthe application. 2 Keys The runtime licenses are properly installed on the deploymentsystem. The application is ready to go once these two things are set up correctly. Troubleshooting This section describes some common problems seen on the deploymentsystem when the application fails to check out a runtime license. Fatal -> vsgu::initialize - initialization failed! Unable to check out xxx_rtl license.

1 Make sure the runtime licenses are installed properly and are available tothe application. The View/Test feature of the LicenseToolCRO can beused to verify the installed licenses. 2 Make sure the associated cookie file is up-to-date and is placed in thesame folder as the application. 3 Try running Active Preview from LynX Prime. If it runs successfully, thenthe problem may be related to the cookie file. 4 Try running the Vega Prime application on the development system usedto build the application and the cookie file. If it runs successfully, then theproblem could be in the cookie file.

Note: Please refer the Vega prime Programmers guide page no: 21 for complete reference.