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

5.3.3 IBM i 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 IBM i:

• Developers code and test their application on a Visual LANSA installation on Windows.
• LANSA is installed on IBM i as described in the Installing LANSA on IBM i Guide.
• Partition is defined on IBM i matching the partition definition on the Visual LANSA installation.
• The Remote Deployment System is defined in Visual LANSA with a corresponding entry in the LANSA Communications Administrator (refer to 5.12 Define a Deployment System).
• The Refresh menu option, available in the Remote System right click menu, is used get workstation names from the Deployment System, that is LANSA for i on the IBM i.
• On the IBM i, create or choose an active Task ID that will be used for the Deliver To process. This must be typed in or selected from the dropdown during connection to the remote server.
• Deliver To is used to deliver application objects to the Deployment System. "Create an IBM i export list" can be selected on the Deliver To dialog to automatically create an export list on the deployment system including the delivered objects.
• The task selected during the remote system connection is assigned to the object on the IBM i. It overwrites the current assignment on IBM i. It does not use the Task that the object is assigned to on the PC. If the Task is a special task that has Unlock on Check In set to Yes, the Task Id will be cleared on IBM i.

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