Versions Compared

Old Version 2

changes.mady.by.user Nadine Hinojosa

Saved on

compared with

New Version Current

changes.mady.by.user user-eb51a

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:•     

  • Minimum hardware requirements
•     
  • Minimum software requirements
•     
  • Supported screen resolutions
•     
  • Minimum networking capabilities
•     
  • Maximum data volumes.

 A formal MSC will:•     

  • Inform decisions about the overall solution cost.
•     
  • Establish the environment required to test the deployment of the solution or any patch/hotfix made to it.
•     
  • Raise management's awareness of the risk in implementing a "sub-MSC" solution.

 
For more information refer to to Application Performance in  in the Framework Guide. 


Licensing requirements for the target system

WEB license.

The license needs to be on the Windows application server.

If your application uses other LANSA software, you may need other LANSA licenses.

If you need more information,

see

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

application’s launch page includes VLFONE_Engine.js as a Resource

Refer

to

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

see Getting ready for deployment in VLF-ONE

in

 in the Framework Guide.

...