You must complete a number of preparatory tasks in EAE 3.3 before you import an existing application into Agile Business Suite. You must ensure that the EAE model to be migrated is error free. For best results, complete these tasks in the order in which they are described in the following content.
Matching Business Segment Label
You should ensure that the Business Segment name is same across all versions of the application. If you maintain a single repository with different versions having different names, you might need to create multiple EAE repositories, each using the same Business Segment name to migrate all versions of the model.
Remove All Unused Elements
For example, you should delete unused Insertables, Performables to migrate easily.
Deleting Previous Configurations
You should delete previous configurations because:
EAE stores snapshots of configurations as they change.
AB Suite does not migrate previous configurations.
The “.MDL” file becomes larger and migration takes longer if previous configurations are not deleted.
Note: When you delete previous configurations, you should be careful because this has an impact on ongoing EAE development.
To delete previous configurations in EAE, perform the following:
Point to the EAE System Directory.
Right-click Previous Configuration for the Segment.
Select Delete.
Synchronizing an EAE Model
You should synchronize an EAE Model because:
EAE System Directory might contain references to deleted elements.
Synchronization removes invalid references.
To synchronize a model in EAE, perform the following:
Point to EAE System Directory.
From the menu, select Analysis and click Synchronize Configuration.
Validating Logic in EAE 3.3
Agile Business Suite assumes that all logic in existing applications is validated without errors before you extract the LCIF file from EAE 3.3. If not, then the results of migrating the model might be unpredictable.
To avoid any possible complications, you should validate the logic in your entire model before extracting the LCIF file from EAE 3.3.
To validate logic in an entire model, perform the following:
In EAE Developer, double-click the Business Segment and select Logic Status List from the options available.
On the Edit menu, click Select All, or press CTRL-A to select the entire model.
On the Logic menu, click Validate & Save, or press F12 to calculate the logic status.
If the Developer message reveals any logic validation errors or logic that is not validated, you must resolve them prior to extracting the EAE application. Ensure that you re-validate after addressing any validation errors.
Validating Presentations
Agile Business Suite assumes that there are no overlapping fields in Ispecs with fixed presentations. If these are present when you migrate your model from the Enterprise Application Environment, you might see build warnings and possibly errors. You should modify any Ispec in painter of Enterprise Application Developer before migrating to resolve overlapping attributes for fixed presentations.
Exporting Version Control Banks
To migrate version control history to Agile Business Suite, you must export your EAE 3.3 version control data to an XML file initially. This XML file is then imported through the History Viewer. Refer to History Viewer for more information about History Viewer.
Version Control offers two methods to export data from a Version Bank:
The Export Wizard – This wizard steps you through the tasks to perform the export and permits you to specify a subset of records that you want to export and (optionally) archive from the Version Bank.
The Export Utility – If you are familiar with the command line utility from earlier releases, you can continue to perform an export task in this way.
To run an export operation by either method, you must log off from Developer Version Control.
Both export methods create:
An XML file containing data from the Version Bank. This file is readable by the current and all subsequent versions of Version Control import tools.
A subdirectory of LCIF files, which are referenced by the XML file.
Error and status messages for the export operation
As part of the export task, you must define a directory for the XML file. The LCIF files are exported to the same location. If you later want to move these files before performing an import task, you must move them together so that the relative path from the XML file to the LCIF files is maintained.
All passwords are lost during an export operation. If you import your data into a new Source Control bank, a user password defaults to the username.
Refer to the Migration Online Help for more information on using the Export Wizard.