??SSA Conversion Adapter Engine 2.1
Introduction
SSA Conversion Adapter Baan Source Engine (SCA Baan Source Engine)
You only use this component if you migrate data from an earlier version of SSA Baan ERP to a new version of SSA Baan ERP, for example, SSA ERP LN. The SCA Baan Source Engine consists of a set of SSA Baan sessions developed in Baan 3/4GL, and grouped into preconversion processes and actual data extraction processes and is installed in the Source SSA Baan environment. The input to this component is the compiled conversion objects generated by SCA studio.
SSA Conversion Adapter Baan Target Engine (SCA Baan Target Engine)
You can use this component only if you migrate data from an earlier version of SSA Baan ERP, or any other legacy systems to a later version of SSA Baan ERP, for example, SSA ERP LN. The component consists of a set of SSA Baan sessions developed in Baan 3/4GL, and grouped into actual data
loading processes and post-conversion processes. The input to this component is the data files generated by the SCA Baan Source Engine.
SSA Conversion Adapter Logic Packs (SCA Logic Pack)
These Logic Packs are the actual conversion rules developed by the SCA studio. The respective SCA Engines consume these rules, which are stored as plain ASCII files and imported to SCA Studio, on demand.
The following architecture diagram illustrates the SCA Data Migration
SCA Technical Architecture Overview – General Data Migration
Figure 1-1: SCA Technical architecture overview
Lookup Database
The Lookup Database is an optional component in the SCA data conversion solution. For any complex data migration, apart from the source database, you must require an additional data store to do the following:
· Store manual data, which you cannot get from your source application.
· Generate additional data from your source application as a part of
· preconversion preparation.
· Recode some of your master data.
For each of these requirements, you can define your own table definitions in
any of the ODBC/OLE DB supported data store. To access the data store
easily, you can use the SCA provided functions, or store these data models
as part of your source application data models.
SCA Engine works in of the following ways:
· Extract the data and transform and load the data to the target database through the OLE-DB/ODBC interface. This method is called direct loading to target database. Average loading rate: 325 rows/second.
· Extract the data, transform and create data files in the format of target tables, this is done by the SCA Engine. Later the user needs to FTP these files to the Target Application Server and load to database with underlying database’s bulk loading utilities. This method is called creation of DAT files. Average loading rate: 3900 rows/second.
SCA Technical Architecture Overview. SSA Baan to SSA ERP LN Data Migration
Figure 1-2: SCA Technical Architecture Overview
You can perform the complete conversion process in either of the following ways:
Dump data in the SSA Baan Source Environment and start to load to the SSA Baan Target Environment in parallel. You can only use this method if either of the environments are in the same application server (singlemachine scenario) or if the target SSA Baan application server contains a FAT client installation of the SSA Baan Source (Two machines with Client/Server). You can also invoke multiple processes for dumping, as well as for loading, to improve the overall performance.
Alternatively:
· First dump data in the SSA Baan Source Environment, then transfer the data files to SSA Baan target environment and load the files into the target database (two machines without Client/Server). The user can also invoke multiple processes for dumping, as well as for loading, to improve the overall performance.
To work with SCA Engine
SCA Engine enables you to schedule and carry out data conversion from legacy systems to SSA products. To perform the data conversion, SCA Engine uses the XML files generated from SCA Studio. You must model the conversion process in SCA Studio in the form of conversion rules for each target table present in the target application before you carry out the actual data conversion. These conversion rules are exported in the form of XML files, and SCA Engine creates conversion scripts for each of these XML files
and runs the conversion.
To access the SCA Engine applications, on the Start menu, click All Programs ??SSA® Conversion Adapter ??SCA Engine 2.1.3.
The SCA Engine appears:
Figure 2-1: SCA Engine
This screen is the initial screen for SCA Engine. From this screen, the user can do the following:
· Create a new batch.
· Edit an existing batch.
· Select a predefined batch for execution.
· Schedule a predefined batch for execution.
The following sections describe the details of each of the menu items.
To work with batch menu
New
This feature enables you to create a new batch to work with.
1 To create a new batch, click Batch ->New. The Maintain Batch screen appears:
Figure 2-2: Maintain Batch screen