A common implementation scenario for LANSA Composer involves using two or more LANSA Composer installations:
1. One for designing LANSA Composer Solutions ("design")
2. One for testing the solutions ("test/QA")
3. One for running LANSA Composer Solutions in a live environment ("production")
Separating the 'design', 'test' and 'production' systems has many obvious advantages and is recommended for most cases. When you maintain separate LANSA Composer installations, you will need to deploy LANSA Composer solutions between them.
Following are some considerations for deploying your solutions and the features LANSA Composer provides to support your deployments. For more information, review the following:
Export Definitions from LANSA Composer
Import Definitions to LANSA Composer
Unattended Export and Import Operations on the LANSA Composer Server