Once an application has been completed in a development environment, it must be migrated or deployed to a production environment for use by the end-users of the application. Change management strategies use many different approaches for application deployment and these strategies may involve moving objects to test environments before moving to production environment. The common element of these strategies is the need to move an identified group of objects from one place to another. The group of objects may be identified as described by the 6.1.3 Impact Analysis Concepts.
LANSA provides two techniques for moving objects:
The export and import facilities in LANSA are provided to enable the LANSA objects to be 'exported' from one LANSA partition and then 'imported' into another LANSA partition. You create export lists that may also contain objects that are not part of the LANSA system. (These lists can be based on Task IDs as described in 6.1.2 Task Tracking Concepts.) From an export list, a set of export files are generated. These files can be moved to the target machine and imported into the LANSA System.
Using the Visual LANSA Deployment Tool, you create a package or series of related packages containing the relevant objects for an application. In addition to the LANSA objects the package details options and settings that relate to the environment in which the package will be deployed. Once you have completed the selection process the package is built and prepared for deployment.
In Visual LANSA you can create a Remote Deployment System, and after appropriately configuring this system, you can deliver LANSA and Non-LANSA objects to this system using the Deliver To command. Single objects, a selection of objects or all objects associated with a task or editor list can be delivered to the remote deployment system.
This utility is intended to assist move objects between a development and test environment on different platforms. It should not be used to move objects directly into a production.