You are now through the exercises concerned with the Target Map. You have created the root Business Object Card with its hierarchy of child Business Objects, and by adding the Interface Fields you have created a very precise interface specification of the data your Target Map expect to receive. Based on this interface you have instructed the Target Map how to use the data received to produce the necessary data to deliver to the Target System.
In order to safeguard your work and make it available to the other members in your team, now is a good time to ensure that everything is committed to the Repository.
To ensure that your mapping is consistent and free of mistakes, you must validate the Target map (and of course correct any validation errors)
And finally publish the interface you have defined in your Target map so you can import it into the Source map in the next string of exercises.
Commit your work
By checking your work in to the Repository is like putting it into a Safe. No matter what you do afterwards, your work up to now is safe in the Repository. Additionally, by committing in you are also making your work available to the other members of your team. If they do a Get Latest Version from the Repository, they will get all your work merged into their local Target map.
You can commit in 2 different ways.
- Open the Pending Changes Tool Window in on the right edge of Studio, provide a commit message, select the items to commit and click the Commit button
- Right click the very top-most node in the Project Explorer tree view and select Commit... in in the context menu.
Validate the Target map
The Studio can perform a validation of the Target map (and of course the Source map later on). This validation is very deep and ensures that your Target map is consistent. In fact, if your validation is free of validation errors (warnings are ok) migFx guarantees that
- The Engine will be able to generate the engine code based on your mapping
- The generated engine will compile and execute
- When executing the generated engine will do exactly what you instructed it to do in your mapping
You can start the validation from the Studio Menu: Project -> Validation - or by using the keyboard shortcut alt-v.
When the validation is finished the Validation Tool Window at the bottom of Studio will open automatically. If you got through the exercises correctly, there will be no validation errors. If there are any errors, you must correct then in order to be able to publish your Target map. Double click on any error in the Validation list to open the item in question and correct the error.
A few validation warnings are ok. Your validation tool windows should look something like this
A couple of notes on the validation list
- The button Export to filelets you export the validation list to an Excel spreadsheet
- You can use the drop down Show Results for to filter the list to show the results for the entire Target Map or only show the results for the item currently active on the Document canvas
- You can use the filter buttonsto further filter the validation list
Publish Target Interface
Once free of validation errors you can proceed to publish the interface defined by your Business Objects and their Interface Fields. You can only publish after a succesful validation.
Publish is disabled
- if the validation produced any validation errors
- the moment you make any modification since the last validation
Publish can be activated from the Studio Menu: Project Publish Interface or by the keyboard shortcut alt-g. You will certainly notice the other publish option: Publish to Generator. This is in order to publish your Target map as input to the Engine to generate the code. You will be doing that later on.
Once you have activated the Publish Interface command, you are presented with this dialog, giving you 2 different ways to publish the interface defined by your Target Map:
|To Repository||The interface is published to the Repository. You and your team mates can then import the interface from the Repository in to a Source Map.|
This option is especially relevant, if your Target Map is used in several Source maps, maybe with a different team working on each Source map. In this way all the teams will have easy access to the Target Map interface you publish to import into different Source maps.
|To Folder||The interface is published as a set of files (one file for each root Business Object) to the local folder on your machine you specify.|
This option is relevant in a simpler setup, where you and your team is working on only one Source map using your Target map. In tis case you can simply publish your Target interface to the local folder and immediately open the Source map in Studio, import te Target interface and check your modification in. Your team mates can then simply do a Get Latest Version to get their local Source map updated
In this exercise we propose to publish the interface to the Repository. Leave the To Repository radio button selected and provide a description in order to enable the Publish button
Click the Publish button and you have now completed the Target Map exercises in Studio. Congratulations! Onwards to the Source Map!