Migration means migrating both your Enterprise Application specifications/models and application data.
If you use the optional version control systems provided with EAE 3.3 and are planning to continue using version control with Agile Business Suite, you should extract your existing version control banks from EAE 3.3 before you can migrate and use existing version control data in the new system.
If the migration is between two computers on a network, all migration tasks must be run on the destination machine (the machine on which Agile Business Suite is installed).
Since EAE and Agile Business Suite products have several differences, some specific items must be loaded initially before loading an actual Business Segment.
The specific items that must be loaded in AB Suite initially are:
Global Dictionary Items
Host/Pack information
Notes:
The Global Dictionary and Host/Pack information are areas that require planning when migrating. If you do not load these items initially, it is virtually impossible to create information after a Business Segment is loaded. Ideally, you can get this information into AB Suite by either entering it manually (which might be required against every Ispec/Report) or redoing the import of a Business Segment in a different order.
In EAE, any Model within the same repository can use the Global Dictionary Items and Host/pack information. In AB Suite, it is not necessary to load the different Business Segments into the same model database. However, you must load the Global Dictionary and Host/Pack information into each model database, so that it is available for use.
Automated Extract Processing is the way to ensure that these specific items are loaded into AB Suite in the correct order so that the model validates and thereby generates.
The automated extract includes an additional batch file (.bch suffix). The batch file details the files extracted in a format ready to load into another EAE repository or into an AB Suite Model. Refer to Migrating EAE Model for more information.