To create an initial install package for a standalone Windows application. The package will be defined using the XALONE template.
To achieve this objective, you will complete the following:
Deploying Your Own Applications
When initially deploying your own applications, you will want to deploy to a test partition.
For training purposes, you will be deploying the application using a new SQL database, into the partition which you are using for training. If your training partition is TRN, you will deploy to TRN.
Since this is a stand alone deployment to a new database, as well as the application, you will include the files used by the application and the file data. If you were deploying another application to this database using the same files, the files would not need to be included. If you later needed to deploy changes to any files, you would do this by creating a new version for the application which originally deployed the files.
In this application, the primary file is xEmployee – Employees. When you deploy LANSA defined files, it is important to remember that validation rules and predetermined join fields will refer to other files. For example, the Department Code field in the file xEmployee has a lookup rule which says it must exist in the Department table xDepartments. Your deployment must therefore include file xEmployee and also all other files it depends on or refers to.
When you are managing your own application deployment, if you develop in partition DEV and deploy to partition TST, your setup should include:
a. Developer PC with Visual LANSA using partition DEV
b. A Deployment PC with Visual LANSA using partition TST. Your application definition is checked out to Visual LANSA on the Deployment PC, via an IBM i Master or a Master VCS system
c. Deployed applications located on a Windows server, a Terminal Server or directly installed on an end user desktop.
Before You Begin
You must have completed the following: