Page History

A LANSA system partition is a means of "dividing up" or "partitioning" one LANSA system. Each partition is completely separate from other partitions, but partitions may share some common system objects such as System Variables. Each partition has its own development characteristics and each partition has its own logical repository. Partitions are maintained at the LANSA System level.

Generally, partitions should be used to:

• Separate large and independent classes of users from one another (for example, production users, acceptance testing users and developers).
• Separate completely independent application systems or software packages.

Generally, partitions should NOT be used to:

• Divide up applications or software packages unless they are (and will remain) completely independent from one another.
• Satisfy a developer's urge to start new applications with a "blank page". The resulting impacts of satisfying such an urge may be poor reuse of existing objects and unnecessary and avoidable maintenance and deployment issues.

When you create a partition, please note that:

• There is no supported inter-partition communication. Fields, files, forms, processes and functions defined in one partition are not normally accessible from another partition.
• Each partition has a separate repository. Having multiple development partitions violates the fundamental concept of a single shared development repository, and creates unnecessary and avoidable maintenance and deployment issues.
• Each partition has a separate security system. If you have too many partitions this can become a maintenance overhead.

...

 Also Also See

 
If you are using Visual LANSA Slave System connected to a LANSA for i Master System, refer to:

• System Partition Definitions in the LANSA for i User Guide.
• Visual LANSA Slave Systems Administration.