As the Integration Engineer on this project, you will be responsible for developing all of the inbound and outbound data migration routes to support the customer's pricing application. You will be creating the automated routes using the IM templates using the "no-code" approach and all routes will be running remotely. 

🎯 Learning Outcomes

The completion of this project will accomplish the following objectives:

• Migration of all product-related data

• Migration of all customer-related data

• Migration of all transactional history

• Migration into selected datasources

• Migration of pricing parameter data

• Exporting of Customer master data

• Creation of a datamart per requirements

• Performing data quality validation

Completion Requirements

• IM Instance

• SFTP Connections

• Product migration inbound route

• Customer migration inbound route

• Multiple Product Extension inbound routes

• Multiple Customer Extensions inbound routes

• Transaction Data Source inbound route

• Customer master outbound route

Note on CSV Files

When working with CSV files, one must pay attention to the conversion from xlsx to csv.

The default Camel Route expects the text to be in a UTF-8 encoding block... some conversion tools ( i.e. Microsoft Excel ) convert from xlsx to ANSI ...this is fine for most cases, but this is not the DEFAULT for the Camel Routes which we will be using.

Please see Camel Data formats for additional info.

This behavior can observed by opening an Excel CSV converted xlsx file in the Notepad++ editor  ...observe the flagged encoding block that Notepad++ detects ( ANSI ) :

To remedy this, simply select Encoding / Convert to UTF-8 on the Notepad++ menu : 

Then save the new UTF-8 blocked file.

Note that it is possible to overtly specify the encoding block you desire by adjusting the Route ( See Camel documentation ), however, for this exercise, simply ensure the .CSV encoding block is UTF-* using either the technique outlined above or one similar.