Migrating the Model from EAE

To migrate the EAE System to Agile Business Suite, perform the following:

  1. EXTRACT the MDL from EAE 3.3.

  2. IMPORT the MDL to Agile Business Suite.

  3. Prepare configuration properties for building and transferring the Base system.

Extracting the MDL from EAE 3.3

In the EAE Developer Model directory, select the Business Segment for the application you want to migrate.

On the File menu, click the Extract option. Select the Extract Type as Full Extract and System Options as ALL, so that all the configurations and the System details to get extracted.

Importing the MDL to AB Suite

Import the model into the AB Suite Development environment.

Refer to Importing Full EAE Extracts into Migration Database and Creating AB Suite Model Database for more information on Import.

Differences in Group Initialization

There are a few runtime behavioral differences between EAE MCP runtime and AB Suite runtime, which includes Windows and MCP, with respect to group initialization. If a member of the group is a number testing the group for glb.spaces after the group is initialized, it results in the following for EAE (MCP) and AB Suite:

Prepare Configuration Properties for Building the Base System

The final step in migrating the Base system is to prepare the configurations for the first build and transfer the Base system. For a model that has configurations used in MCP Runtime Transfer, perform the following:

  1. Fix the configuration names.

  2. Update the <<segment>> and Deployment folder properties for the Configure configuration.

  3. Update the Deployment folder properties for the Source configuration.

  4. Build the Base system.

Fixing the Configuration Names

When you import a model from EAE, Import prefixes the EAE generate set names with the EAE system name (for example, GTCIRDB_CONFIG, where CONFIG was the original generate set name). RTU does not accept a configuration name longer than 10 characters, so it is necessary to change the configuration name so that it does not exceed 10 characters (for example, GTCIRDB), or change it back to its original name.

To change configuration names, perform the following:

  1. Right-click the project and select Properties from the drop-down menu.

  2. Click Configuration Manager to open it.

  3. Open the drop-down list for the Active Solution Configuration, and select edit.

  4. In the Edit Solution Configurations dialog, select each configuration and change the name to 10 characters or less.

  5. Close the Edit Solution Configurations dialog.

  6. Open the drop-down list for the project configurations, and select edit.

  7. In the Edit Project Configurations dialog, select each configuration and change the name to 10 characters or less.

  8. Close the Edit Project Configurations dialog.

  9. Close the Configuration Manager and the Project configuration properties

  10. Close the Solution, reopen it, and continue working.

Updating Segment and Deployment Folder Properties for the Configure Configuration

The Configure configuration specifies the configurations of the Primary system. You can update the Configuration properties for the Configure configuration at this point to allow the RTU file to be created at the same time the Base system is built.

Configuration property checklist for <<segment>>

Notes:

  • The names you use for Alternate Name, Database Name, and COMS Window Name must be different from the names that you use for the Base system (Source Configuration).

  • The RDB Configuration field must be blank. The Secondary database is established using DB Centre.

Configuration property checklist for the Deployment folder

Updating Deployment Folder Properties for the Build Configuration

Modify the PORT #, HOST, Pack and Usercode details corresponding to the AB Suite Environment.

Configuration property checklist for the Deployment folder