This exercise is another example of going through a full cycle of the migFx iteration.


In a previous exercise you determined that the Event I0023 was derived from another Event. The Event E0010 in the Account Export step rejected a number of Accounts - so these Account are missing when the Cards are migrated. This is the root cause of the Event I0023. To solve Event I0023 you actually need to solve Event E0010 on Account.



Solve Event E0010 - Source ProductType ({0}) not found in Product Translation Valueset

Locate the Event E0010 in the Event List for Account



Already from the Event Message it's pretty clear what the problem is. Some ProductTypes are missing from the product Translation Valueset. A drill down to the Intermediate List shows just 2 missing ProductTypes, PI and IP:


 

The correct action now is to delegate this Event to the Partition Users and ask them to determine the Target Product Types for the 2 missing Source Product Types and update the Translation Valueset accordingly. 


Add rows to Translation Valueset

However, for the sake of this exercise, let's just assume the role of Partition User in each bank and decide that the both missing types must be migrated to the Target ProductType salary01. Acting on behalf of the Partition USers, you can update the Translation Valueset in Tracker

  1. Select The tab Translations, the BankId 30 in the Partition Box and finally the Translation Valueset TranslateProductTypes:


  2. Add a row for Source Product Type PI
    1. Click the  to add a new row to the Valueset
      • Provide the values for the row

        • SourceProductType: PI
        • TargetProductType: salary01
        • Description: Default
      • Click the Save button to save the new row

  3. Add a row for Source Product Type IP
    1. Click the  to add a new row to the Valueset
      • Provide the values for the row

        • SourceProductType: IP
        • TargetProductType: salary01
        • Description: Default
      • Click the Save button to save the new row

  4. Select BankId 40 in the Partition Box and repeat the above steps to add the 2 missing ProducTypes


Load the Valueset into Director from Tracker

Acting as the Partition Users, the rows have now been added manually to the Tracker. Now the Valueset in the Director must be loaded from the Tracker.


In the Director, select the panel Source / Valuesets  and check the Valueset TranslateProductTypes in the Translation box. Note that hte number of rows in the Valueset presently is 34:



Click the Update Selected button to submit a job to update the Valueset and verify in the Job List that the job completes successfully. You can return to the Valueset list and click the Refresh button to verify that the row count for the Valueset is now 38.



Migrate the effected Accounts

With the addition of the missing rows to the Valueset, we now expect the problem to be solved and it is time to iterate the migration for the affected Accounts. As in the previous exercise it is necessary to create an Itemset containing the Accounts that fired Event E0010.


Go to the Director panel Source / Events to create the Itemset;



Select the row for the Event E0010 on Account and click the Item Set button to submit a job to build the Itemset. Verify in the Job List that the job completes successfully.


Go to the panel Execution / Item Sets and click the Refresh button to se the new Itemset:



To iterate the Accounts of the Itemset:

  1. Export the Accounts by clicking the Export... button to submit a job to export the Accounts

  2. Verify in the Job List that the job completes successfully and the Accounts are no longer rejected by the export
    .

  3. From the Itemset, ensure that Include descendants is checked, and click the Import button to submit a job to import the Accounts

  4. Verify in the Job List that the job completes successfully and that the Accounts and the dependent Cards have been imported


Similar to the previous exercise, you only selected the Accounts that fired the Event E0010 to be imported - the automatic resolution of dependencies included the dependent Cards for you. 



Publish Result

To publish the new result to the Tracker, go to the Director panel Administration / Manage and check the Tracker Publish radio button:



In the dialog move Account and Card from the Available to the Selected box and click the Ok button to submit a job to publish the result. 



Verify in the Job List that the job completes successfully.



Test & Feedback 

When the publish job has completed, you can return to the Tracker an reload the Event List for Account and set the state filter to (all) to see that the Event E0010 indeed has a count of zero:



Do likewise for the Event List for Card to verify that the Event I0023 now too has a count of zero




What happened here?

This was your third iteration of the migFx cycle. In this case, there were no modifications done in Studio, so the Studio step and the Generate and Deploy steps were not necessary. Assuming the role of Partition User you simply added some rows to a Translation Valueset to resolve the problem.


Again the automatic resolution of dependencies helped out by identifying the dependent Business Object instances that needed to be imported. In fact, on the panel Target / Objects in the Director, you will find the Full monty button. Clicking this one submits a job to simply import everything, automatically resolving the dependencies to ensure Business Object instances are imported in the correct order.



Grande finale!

Of course there Events remain in the Workshop migration project to be resolved - the project is not over. But with this exercise we feel that you have seen enough of migFx to enable you to start working on your own in the migration projects of your organization.

  

Application Data Migration is complex - there is just no way around that fact. The aim of these training exercises has been to teach you the workings of migFx and - we hope - convince you that the capabilities of migFx will assist you in handling and stay on top of all this vast complexity. 


Experience is king and after these exercises it is only by working with migFx in your migration project that you will truly become a migFx expert. 


On your future journey you can of course always contact us on http://support.hopp.tech with suggestions and questions. We will always be happy to help you out and will welcome all suggestions to help us improve migFx in future releases.