Note that in most production configurations the Windows web server and the Windows application server are two separate machines.
Step | Activity | How to Do It | OK |
|---|
Make sure your target system is ready | Ensure your target application server has a database engine and an empty database. |
Ensure you have a Web license | Ensure the target application server has a Web license. | If you need more information, see Licensing at the LANSA Support website. |
Install the deployment material | Install the package by running the package .MSI file as Administrator. | If you don't know how to run the file, see this tutorial step in the Deployment Tool guide. If you encounter problems during the installation, check the MSI*.log file in the end user's defined %TEMP% folder, for example: MSI2ce4c.log. As well as installing the Application, a standard Windows program menu folder will be created for each Application using the Company and Application descriptions as folder names. This means that every Application built with the same Company details and installed on the same PC will be grouped together. |
Execute the Framework application | Execute the VLF-ONE application. | Typically starting URLs are formatted like this: http://<host>/<lansa system>/<partition>/<entry point web page>?Lang=<language code>&FrameworkID=<framework id> http://localhost/MyLansaSystem/PRD/MY_OEXEC.html?Lang=ENG&FrameworkID=MY_VLFONE_SYSTEM |
Instruct your users to create a shortcut for the application. | Usually the best way to launch a VLF-ONE application is from a shortcut. | See Shortcuts for Launching VLF-ONE Applications in the Framework guide. |