VLF-ONE-WINDOWS, Step 1. Pre-Requisite Actions and Other Considerations
Step |
Activity |
How to Do It |
OK |
Establish the minimum supported configuration (MSC) |
You need to formally define the minimum configuration your solution will viably support, including: |
A formal MSC will: |
|
Licensing requirements for the target system |
WEB license. |
If you need more information, see Licensing at the LANSA Support website. |
|
A Framework application ready for deployment |
You need to have an executable version of your Framework application ready for deployment. |
|
|
Make sure your application's launch page includes VLFONE_Engine.js as a Resource |
Refer to Framework Custom Logon Page. |
|
|
Copies of UF* and DF* objects |
If you are deploying your application for end-users, the package should not reference any Framework objects with names starting with UF* or DF* because there is a risk these objects may change the next time you install a new version of the VLF. |
For more information see Getting ready for deployment in VLF-ONE in the Framework Guide. |
|