Page History

[ Image Removed |../../index.htm#lansa/l4wadm03_0090.htm]
You are here:

...

Following is a simple example of a typical development cycle using a LANSA for i Master System with a Visual LANSA Slave System:

...

• A Visual LANSA System may only have one partition but the LANSA for i Master could have multiple partitions. Visual LANSA must be initialized for any partition where you want to do development with Visual LANSA.
• If system or partition definitions are modified on the LANSA for i Master, system and/or partition initialization may need to be performed again.
• The Visual LANSA Repository does not have to be a complete copy of the LANSA for i Repository. You can export any number of objects from the Master System.
• If you are using Repository Synchronization for a Visual LANSA System, then the complete object lists for the partition will match and system information will constantly be maintained.
• If you are not using Repository Synchronization, naming standards must be strictly adhered to, to avoid duplicate objects being created on Slave Visual LANSA Systems.

...