MDM 7 WebServices vs Import Maps which one is best?

[Former Member]

Hello Experts,

The scenario is about importing data from different Remote Systems into MDM (triggered on create or change in remote system).

Our middleware can generate files in inbound port, also it can call WebServices.

Hence we have two option, iether write import map for each table or call WebService for each MDM table.

Which one is best for smooth integration between MDM and it's Remote Systems?

Regards,

Shaailesh.

[Former Member]

Hi Shailesh,

You should prefer WebServices interfaces due to tight coupling as it will directly create/update data into MDM, the moment data is provided to webservice.

BR,

Alok Sharma

[Former Member]

I would prefer writing files to Import server (use MDM Receiver adapter for this ).

In case of webservice, you are adding an extra layer of interface which is not required. If you want to have a synchronous scenario, then use webservice otherwise writing files to import server should be ok.

Thanks

Aamir

[Former Member]

Hello Aamir,

Thanks for your view...

We are facing issue in remote key creation/updation for multiple remote systems using single import map.

I wonder, whether WebServices allows to define remote keys for multiple remote systems in one (create or update) call.

Import map dosen't support creation of remote keys for multiple remote systems in single import map.

In this case we need to create saparate import maps for each remote system...

1. One for create (having display fields in matching criteria)

2. One for update (having remote key in matching criteria)

Well, Web Services also require two calls, but not for each remote system (I hope).

Also, if we create saparate import maps for create & update each,

then there is a need of controlled import sequece (i.e create should happen before update) ...

we dont found any provision/workaround on controlling import sequence in MDM.

Regards,

Shaailesh.

[Former Member]

Hi Shailesh

The standard Web services will also update/ceate remote keys for records for 1 remote system only.

In this case we need to create saparate import maps for each remote system...

1. One for create (having display fields in matching criteria)

2. One for update (having remote key in matching criteria)

Why is this required? For the repository what is the unique fields defined. Is this not same as display fields defined. If possible this can be changed in the repository schema so that the same map can be used for Create as well as Update with only the import action changing based on the match level.

Also, if we create saparate import maps for create & update each,

then there is a need of controlled import sequece (i.e create should happen before update) ...

we dont found any provision/workaround on controlling import sequence in MDM.

Again if you are using the same map/different map for update and if the records are not created itself nothing will be updated. No harm here. How are you getting the source file from remote systems? Do you have a cross reference number in the remote system to link with corresponding MDM record? This information can be used for separating newly created records with updated records based on a backfeed from MDM to remote system.

You can also try to explore sequence option while defining the Inbound ports in console for controlling the import sequence. I am not very sure if this works.

thanks

Ravi

[Former Member]

Hi Shailesh,

Import map dosen't support creation of remote keys for multiple remote systems in single import map.

1stly, in this case if you have same source structure for all remote systems, you can make use of same map for each remote system. Say e.g. for Remote System A, you create a Import Map and after that you need to export the map from File to your desktop a file with extension .map will get created on your location(e.g. Desktop) where you saved it. Now if Remote system B has also same structure then after selecting your Remote system and source file using Import Manager, you can import the map with extension .map which will result in all your Source structure mapped with Target Structure, just check for missing fields and values if any then map them and then save as new map. So in this way you don't need to recreate whole map again and again if your source structure is samp among Remote systems.

In this case we need to create saparate import maps for each remote system...

1. One for create (having display fields in matching criteria)

2. One for update (having remote key in matching criteria)

If your source structure and source file is same. For both cases Create/update then there is no need for two maps since Matching field during import itself will take care of Import Action Create/Update All Mapped fields. You can also try it your end. 1st using MDIS services, place the file with create records in Ready folder,after getting successfully imported this records, you will see these newly created records in MDM Data Manager, now for some field just change the value and put it there again in Ready folder, you will see again file should be disappeared from Ready folder and using Data Manager your existing records values for some fields will get updated using same map

then there is a need of controlled import sequece (i.e create should happen before update) ...

we dont found any provision/workaround on controlling import sequence in MDM.

This thing you can take care using PI (Middleware) by maintaining order in Interface Determination.

Please refer 2nd last reply from end by Aamir for more details:

Regards,

Mandeep Saini

[Former Member]

Hello Ravi,

Thanks for your input...

The reason of two different map for create and update is having 'Code' and 'Description' as two display fields.

If we use same map as per your explanation, then import of 'Description' change will create new record rather than modifying description of existing code (because Code and Description are two display fields).

Another thing is, there is no option for import sequence while defining inbound ports in Console!

Regards,

Shaailesh.