[ |../../index.htm#lansa/l4wadm03_0105.htm]
You are here:

5.3.2 Linux Deployment System Development Cycle Example

Following is a simple example of a typical development cycle using a Visual LANSA System and a Deployment System on Linux:

• Developers code and test their application on a Visual LANSA installation on Windows.
• LANSA is installed on Linux as described in the Install or Upgrade LANSA on Linux Guide.
• The Remote Deployment System is defined in Visual LANSA on Windows with a corresponding entry in the LANSA Communications Administrator (refer to 5.12 Define a Deployment System).
• The Partition Initialization menu option, available in the Remote System right click menu, is used to initialize the Partition on the Deployment System, that is the Visual LANSA on Linux installation. For example, if the application was developed in the training partition TRN, the matching TRN partition is created on the Deployment System and populated with the partition definition from the Visual LANSA on Windows installation.
• Deliver To is used to deliver application objects, message files and so on to the Deployment System. Only non-Visual objects are required. Visual components, for example Forms, cannot be delivered to the Deployment System, as execution is not supported (or required) on the LINUX environment.

It is important to note that the following from this example:

• The Deployment System does not have to be a complete copy of the Visual LANSA Repository. Only the application related objects are required to be Delivered To the Deployment System.

[ |../../index.htm#lansa/l4wadm03_0105.htm]