1 Planning Your Site

Visual LANSA Admins

1. Planning Your Site

If you have not yet installed the Visual LANSA software, you should take time to properly plan and understand how the Visual LANSA software will be used at your site. The Visual LANSA development environment may be just one component of a complete LANSA System installation that involves many different LANSA Products.

For an easy to follow planning guide, go to Install Planner.

LANSA is a family of multi-platform application development tools. This section defines each of the software components that can be installed.

Because LANSA supports multiple platforms, the software can be configured to use development environments on IBM i and Windows.

Web development and Web deployment models may also be multi-tier using both IBM i and Windows.

Web development and Web deployment models may be installed in virtualized and Citrix IT infrastructure. Search in LANSA Support to view the latest:

  • Citrix install instructions
  • LANSA's Virtualization support policy
  • LANSA's Supported Versions.

It is important to be clear about the software components and where they are required. They are described in:

The various models for development and deployment are described in:

Basically, LANSA Systems can be classified as:

  • 1.5 Promotion & Deployment, which are remote systems, for example Linux, that receive objects from a Visual LANSA development system.

If you are using a master and slave system, it is important that you understand the task of 1.2.10 Synchronizing Master and Slave Systems.

A LANSA System is defined as a group of LANSA Software Components that share a common LANSA System Definition.  A single system may contain many different products. For example, a single LANSA System could be a development environment using LANSA for iSeries on an IBM i  server with LANSA for the Web on a Windows server and many Slave Visual LANSA Systems on developer PCs. A LANSA for iSeries System running a different LANSA version would be a separate LANSA System because it uses a different LANSA System Definition (e.g. System Definitions for that version).