10. Install into a Development System

Versions and Patches created with the deployment tool are typically installed as separate applications. It is also possible to construct Version and Patches that apply the change to a Development System. That is, MSI and MSP may be installed into a LANSA Development Environment.

The typical reason for doing this is to provide a complete set of tables, table data, JavaScript and executables along with the source code so the application may be executed and also allow for the application to be customized.

When creating the Application in the Deployment Tool, ensure you select No Template.

1.   Set the Package Options as follows:

• If you have selected No Template, the options circled in red should already be set to the values indicated. If not, delete the Application and start again.

• The options in blue need to be set as shown, plus set Partition Identifier (PART) and Setup Database (SUDB) to Prompt during Installation. This allows for an end user to choose to not update the database and to change the partition being imported to.

2.   While building the package, uncheck all the Settings options except Export for Development System. This is very important. You do not want to overwrite any of the executables already installed by the Development Environment nor import system definitions, etc.