Exercise 1.1 - Target map, Introduction

Modified on Mon, 18 Mar 2024 at 05:43 PM

In this section of the exercises, you will be working with the Target map. Here's a video to get you started on the right track:

Target Map

The purpose of the Target map is to specify how the data to be delivered to the Target System is to be created. So the first step in the following exercises is to import the metadata describing the Target System, so we know the task ahead of us.

Once that is done, you will be creating the hierarchy of Business Objects to specify the target mapping for the Card Business Object, and for each Business Object in this hierarchy, you will define the Interface Fields you need, in order to create the data for the Target System.

Next up is to link these Business Objects to structures in the Target System by creating Target Objects and deciding how to create the value for each Target Field on each Target Object.

That's the gist of it, but of course, there will be a myriad of details as you get on. But do not despair - the Studio is here to help you!

Even though this section of the exercises is only concerned with creating the Target Map in Studio, it is worth keeping an eye on what is going to happen further down the line, when the Runtime actually executes the migration.

The essence of the Target Map in Studio is to import the metadata describing the data structures to deliver to the Target System and then map these metadata to the Target Interface the Target Map expects in order to do this job.

The next thing that happens is that - based on the Target Map - the Engine Generator will generate the Target Engine. It is the Target Engine that - at run time - will do exactly what was specified in the Target Map. Receiving data that conforms to the Target Interface, the Target Engine will execute and produce the Target data to be delivered to the Target System.

It's actually quite simple once you get down to it.

Important points on the Target Map

The Target Map is hugely important. It is the Target Map that defines the Business Object hierarchies upon which everything else is built. In these training exercises, we have basically made this hierarchy for you. 

But once you proceed to a real-life migration project, you should put considerable effort into designing the hierarchy of Business Objects.

There are some fundamental rules when building the Target Map:

  • The Target Map reflects the structure and requirements of the Target System(s) only
  • The Target Map exposes an interface and validates that data received through this interface
  • The Target Map knows nothing of the source data and may not make any assumptions based on source data

Heartfelt advice - commit your changes!

As you proceed in the exercises you will be creating new items along the way and making a lot of modifications. It is a very good idea to regularly commit your changes to the Repository.

At the very least, commit once you are through an exercise and happy with your work. 

Good commit discipline allows the Studio Repository to provide you and your team with valuable assistance. You can see the complete history of all your changes, compare versions, roll back to previous versions and more. You can read more about all this here: The Studio Repository

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article