Integrating MDM Server with Enterprise Information Systems using SAP as an example, Part 2: Enriching customer records with SAP specific information

This article is a sequel to the "Integrating MDM Server with Enterprise Information Systems using SAP as an example, Part 1" tutorial. In Part 1, the focus was on propagating customer master data from an MDM Server to an SAP® system. Part 2 focuses on how additional information added to the records in the SAP system can be sent to a MDM Server. In the demonstrated scenario, the customer record previously propagated to the SAP system is enriched with an SAP-generated tax identifier. The SAP Intermediate Document (IDoc) mechanism is used to send the modified customer record from the SAP system to the Enterprise Service Bus (ESB). On the ESB side, the WebSphere Adapter for SAP Applications is used to pick up the IDoc and feed its data into a mediation flow. Based upon the provided data, the mediation flow creates the MDM Server web service requests updating the customer record with the tax ID.

Share:

Hans Schoen (Hans.Schoen@de.ibm.com), Software Engineer, Information Platform and Solutions Development, IBM

Hans SchoenHans Schoen is a senior software engineer working in the Information Platform and Solutions team in IBM's Development Lab in Boeblingen, Germany. Hans joined IBM in October 2000. He started as developer for IBM Document Composing applications. In 2004 he moved to the WebSphere Process Server development team (Human Tasks). Since 2007 he's has been working in Information Platform and Solutions development. He is developing applications and tools for the integration of SAP into IBM Information Server products.



Sebastian Nelke (snelke@de.ibm.com), Software Engineer, Information Platform and Solutions Development, IBM

Sebastian NelkeSebastian Nelke is a senior software engineer working in the Information Platform and Solutions team in IBM's Development Lab in Boeblingen, Germany. Sebastian joined IBM in March 2005 after he participated in IBM's "Extreme Blue" program during summer 2004. He started working in the area of enterprise search and text analytics and moved on to Information Platform and Solutions development after 3 years. His current focus area is bringing together the Information Server product portfolio with SAP software.



Mike Grasselt (grasselt@de.ibm.com), Software Engineer, Information Platform and Solutions Development, IBM

Mike GrasseltMike Grasselt is a senior software engineer in the IBM Information Management Development organization in Germany. Mike is currently the architect and team lead for various Information Governance Compliance capabilities in the IBM Big Data platform. Prior to this role, he was responsible for assets that support data integration tasks for large SAP migrations and consolidation projects, and for integrating IBM Master Data Management products into SAP system landscapes. He lead the integration of InfoSphere Information Server with WebSphere Portal, IBM Business Process Manager, and InfoSphere MDM Server in the context of a broader Service Oriented Architecture effort. Mike has also developed an SQL extension for the Business Processes Execution Language (BPEL) and published several papers on data-aware business processes and web services. He has integrated text analysis technology with content management systems. Mike has been collaborating with several universities in Germany to define integration architectures and given lectures on IBM mainframe concepts. Mike was an author of IBM Redbooks publications. In addition to his technical responsibilities, he is a mentor in the IBM technical community.



25 July 2013

Before you start

What you will learn

Before you start, let's have a quick overview on what will be covered in this tutorial. You may remember the following figure from Part 1 of this tutorial's series.

Figure 1. Solution overview
Solution Overview

The "Configuring the SAP system" section describes the necessary steps to configure your SAP system so that it automatically sends IDoc documents of type DEBMAS to the ESB whenever data of a customer record is modified. To accomplish this, we will configure the SAP change pointer mechanism and set up a scheduled job. It is important to understand that this procedure will not only trigger updates on the tax identifier of a customer master data record, it will also trigger updates in case the name, address, or any other attribute of a customer record is modified. As this would blow our idea of the MDM Server holding the single version of the truth, requests containing updates on other attributes than the tax identifier will be ignored. Customer master data attributes are only maintained with MDM Server.

The Creating the ESB mediation flow section describes how you implement the mediation between the IDoc message sent by the SAP system and the web service call needed to update customer master data on the MDM system. The mediation flow is implemented using WebSphere Integration Developer (WID).

System requirements

Configuring the SAP system

As in Part 1 of this tutorial series, some settings on your SAP system have to be configured to enable the automatic communication between SAP and the ESB. First of all, the basic IDoc communication has to be set up. This is needed to ensure that the SAP system is generally able to send IDoc messages to the ESB. The next step is to enable change pointers on your SAP system. In our example, we'll configure the SAP system to use change pointers to track changes on customer records. Finally we will set-up a scheduled job which will periodically pick up all modified customer records, create one or multiple DEBMAS IDocs for them, and send them to the ESB. Additionally we will briefly describe how the scheduled job created in the previous job can be monitored.

Basic IDoc communication setup

  1. Make sure your SAP system is configured as described in the Configuring the SAP system section of Part 1 of this tutorial series, and the basic IDoc communication works.
  2. Additionally, you can always use SAP transaction SM59 for a quick connection test and to check whether the target ESB and the WebSphere Adapter for SAP software is up and running.

Activating change pointers

  1. Call transaction BD50 on your SAP system.
  2. Enable change pointers for the message type DEBMAS by selecting the check box.
  3. Click the Save icon, as shown in Figure 2.
    Figure 2. Enabling the SAP change pointer mechanism
    This figure shows the SAP transaction BD50 - Enabling the SAP change pointer mechanism

    SAP will now track changes on customer master data. This will allow us to send an IDoc with the updated customer information to our MDM system. Note: SAP will track changes on all customer attributes. However we only want the tax identifier being generated by SAP and propagated to MDM. All other attributes will be ignored on the ESB side as our MDM system is holding the single version of truth of our data.

Creating a variant of the RBDMIDOC report

The SAP report RBDMIDOC can used to send IDocs with data that was collected by the change pointer mechanism. To automatically notify our MDM system when the tax identifier on a customer record is created, we will set up a scheduled job which periodically calls a variant of the RBDMIDOC report.

  1. Open SAP transaction SE38 and type RBDMIDOC in the Program field.
  2. Click the Variants button, as shown in Figure 3.
    Figure 3. Creating a report variant for report RBDMIDOC
    This figure shows the SAP transaction SE38 - Creating a report variant
  3. Type DEBMAS_MDM in the Variant field and click Create button.
  4. Specify DEBMAS as the message type. Go back one step and save your settings, as shown in Figure 4.
    Figure 4. Setting the message type
    SAP transaction SE38 - Set the message type to DEBMAS and save the newly created process variant

Setting up a scheduled job

We will now set up scheduled job that periodically calls the report variant we created in the previous step.

  1. Open SAP transaction SM36.
  2. Click on the Job wizard button to start the job wizard, as shown in Figure 5.
    Figure 5. Running the job wizard
    SAP transaction SM36 - running the job wizard
  3. On the first page of the wizard, click on the Continue button.
  4. On the next page, specify MDM_SAP_scheduled for the name of the scheduled job. Make sure the priority is set to C - Low priority. The Target Server field must be left empty. Click Continue, as shown in Figure 6.
    Figure 6. Setting up a scheduled job
    SAP transaction SM36 - setting up a scheduled job
  5. On the next page, make sure the option ABAP Program name is selected, then again click Continue, as shown in Figure 7.
    Figure 7. Select option ABAP program name
    SAP transaction SM36 - select option ABAP program name
  6. Now, specify RBDMIDOC for the field ABAP Program name and select our previously created RBDMIDOC_MDM in the Variant drop down list, as shown in Figure 8.
    Figure 8. Scheduling process variant RBDMIDOC_MDM
    SAP transaction SM36 - pick previously created process variant RBDMIDOC_MDM from the list
  7. No Additional options are needed on the next page. Click on the Continue button, as shown in Figure 9.
    Figure 9. Additional Job options
    SAP transaction SM36 - no additional options needed
  8. Make sure the option to start the job Immediately is selected on the next page, and click Continue, as shown in Figure 10.
    Figure 10. Configuring the starting conditions
    SAP transaction SM36 - select option to run the job immediately
    In case a special starting condition for the job is needed, this would be the right place to configure it.
  9. On the next page, select the Period check box in the periodic jobs section and click Continue, as shown in Figure 11.
    Figure 11. Configuring the job to run periodically
    SAP transaction SM36 - configuring the job to run periodically
  10. Now specify the interval in which the job should be triggered. For demos you might want to set the interval to 1 minute. This is done by selecting the None of the above option, then clicking the Other periods button and specifying the period's value as 1 minute in the pop-up menu. When you're done, click the Create button to close the pop-up menu. Again click Continue, as shown in Figure 12.
    Figure 12. Configuring the job interval
    SAP transaction SM36 - set the job interval to 1 minute
  11. Check the status message and click the Complete button to activate your scheduled job, as shown in Figure 13.
    Figure 13. Activating the scheduled job
    SAP transaction SM36 - Activate the scheduled job

The SAP system will now trigger the scheduled job we created and start it every minute. The scheduled job will use our variant of report RBDMIDOC which will send IDocs of type DEBMAS to our MDM system for all customer records that were changed.

Monitoring the scheduled job's status

This is not a mandatory configuration step, however it will support you in monitoring what is happening on your SAP system.

  1. Back in SAP transaction SM36, click the Job Selection button, and search for your job or specify the exact job name (MDM_SAP_scheduled), as shown in Figure 14.
    Figure 14. Monitoring the scheduled job
    SAP transaction SM36 - monitoring the scheduled job
  2. Here, you can check whether your scheduled job is running successfully.

    Note: On some SAP systems it seems to take some time until the settings become effective on the job running periodically.

Creating the ESB mediation flow

Importing the MDM WebService WSDL files into WebSphere Integration Developer

In order to invoke an MDM Web Service in the ESB, the MDM Server WSDL files need to be imported into an ESB module.

  1. Open the MDM Workbench and select File > Export.
  2. In the Export window, expand the General folder and select File System.
  3. Expand the PartyWS_HTTPRouter > WebContent > WEB-INF folder and select wsdl.
  4. Specify a directory to export to and click Finish, as shown in Figure 15.
    Figure 15. Exporting the MDM Server WSDL files
    Export the MDM Server WSDL files
  5. Open the WebSphere Integration Developer and make sure you use the Business Integration perspective.
  6. Select File > New > Other.
  7. Expand the Business Integration folder and select Library.
  8. Specify the library name MDMWebService, then click Finish.
  9. Select File > Import.
  10. In the Import Window, expand the Business Integration folder and select WSDL and XSD, then click Next.
  11. Select Local WSDL or XSD file, then click Next.
  12. Use the Browse button to navigate to the wsdl directory in the directory you created in step 4 (the wsdl directory contains the exported WSDL files).
  13. Select the check box next to the wsdl directory.
  14. In the Target module or library field, select the library you created in step 8, (such as MDMWebService).
  15. Make sure the option Import dependent resources are checked, as shown in Figure 16.
    Figure 16. Importing the MDM Server WSDL files into your ESB module
    Import the MDM Server WSDL files
  16. Click Finish.
  17. In the Business Integration view, expand MDMWebService > Web Service Ports and double-click Party Port.
  18. In the WSDL editor on the right, update the host name and port number of the Party Port according to your MDM Server settings.

Create the SAP Export component listening for incoming SAP Server messages

An SAP export component is required to receive updated records from the SAP system.

  1. In WebSphere Integration Developer, select File > New > Other, expand the Business Integration folder, select Module and click Next.
  2. Specify a module name, for example, SAP2MDM, then click Next.
  3. Select the check box next to the MDMWebService library, then click Finish.
  4. In the Business Integration view, double-click Assembly Diagram.
  5. In the Assembly Diagram editor window, expand the Inbound Adapters section and drag an SAP component to the canvas.
  6. In the New External Service window, expand the SAP adapter tree and select the tree node representing your SAP system host. Click Next.
  7. On the next page verify the SAP system connection information. The SAP interface name to be used is ALE, as shown in Figure 17.
    Figure 17. Specifying the SAP connection properties
    Specify the SAP connection properties
  8. Click Next.
  9. Expand the ALE node and select Discover IDoc From System.
  10. Click the filter button and type *debmas* in the pattern field. Make sure you include both wildcard (*) characters, as shown in Figure 18.
    Figure 18. Filter for the SAP IDoc types
    Discover the DEBMAS06 IDoc type
  11. Click OK.
  12. Expand the Discover IDoc from System (filtered) node.
  13. From the list of discovered objects, select DEBMAS06 and add it to the Selected objects list on the right. A configuration dialog appears.
  14. In the Configuration Properties for 'DEBMAS06', select the first four check boxes and specify the Idoc release version 700, as shown in Figure 19.
    Figure 19. Select SAP IDoc type DEBMAS06
    Select SAP IDoc type DEBMAS06
  15. Click OK.
  16. Click Next.
  17. Select the Service operation Update, add the Idoc Identified using the Add button, and specify a folder for the generated business objects. Type debmas in the Folder field, as shown in Figure 20.
    Figure 20. Configuring the update service operation
    Configuring the update service operation
  18. Click Next.
  19. In Deployment Properties, select Using security properties from the activation specification, specify the UserName and Password, provide the RFC program ID MDM_SAP_TUTORIAL_PROGRAM_ID, enter a Event recovery table name MDMSAPRECOVERY and the Event recovery data source JNDI name jdbc/MDMSAP.
  20. Click Next.
  21. Click Finish.
  22. Save the MDM2SAP - Assembly Diagram Ctrl + S, as shown in Figure 21.
    Figure 21. Saving the newly created Assembly diagram
    Saving the newly created Assembly diagram

Creating the MDM Web Service Import component

In order to be able to send messages to the MDM Server, the MDM Service Web Service import component has to be configured.

  1. In the Assembly Diagram editor window, expand the Outbound Imports section and drag a Web Service component to the canvas.
  2. In the New Web Service Import Service wizard, select the PartyService interface, the existing PartyPort web service port and the SOAP 1.1/HTTP transport protocol. Click Finish.
  3. On the Assembly Diagram, right-click the new WSImport1 component, select Rename, and enter PartyServiceImport.
  4. Press Ctrl + S to save your settings, as shown in Figure 22.
    Figure 22. Configuring the MDM Web Service import
    Configuring the MDM Web Service import

Creating the mediation module

Now you have to create the mediation component between the incoming SAP message and the MDM Web Service.

  1. In the SAP2MDM - Assembly Diagram editor, expand the Components section and drag a Mediation Flow component to the canvas.
  2. Right-click the new Mediation Flow component, select Rename and specify a name, SAP2MDMMediation.
  3. In the Palette, click the Wire icon, as shown in Figure 23.
    Figure 23. Configuring the Mediation Flow
    This figure shows Configuring the Mediation Flow
  4. Click the SAPExport component and then the SAP2MDMMediation component.
  5. In the Add Wire dialog, click OK.
  6. Click the SAP2MDMMediation component and then the PartyServiceImport component.
  7. In the Add Wire dialog, click OK.
  8. Right-click the canvas and select Automatic Layout.
  9. In the Palette, click the Selection Tool, as shown in Figure 24.
    Figure 24. Wiring the components
    This figure shows Wiring the components
  10. Press Ctrl + S to save your changes.

Implementing the mediation component

  1. In the SAP2MDM - Assembly diagram, double-click the SAP2MDMMediation component and select Yes in the Open dialog.
  2. In the Generate Implementation window, click OK.
  3. In the MDM2SAPMediation editor window, select emitUpdateAfterImageSapDebmas06 of the SAPExport interface.
  4. Select Blank Mediation Flow, as shown in Figure 25.
    Figure 25. Generating the implementation
    Generating the implementation
  5. In the SAPMDMMediation editor on the right side, click the plus sign next to Transient Context.
  6. In the Filter field enter SapDebmas06, select SapDebmas06 from the Matching data types list and click OK, as shown in Figure 26.
    Figure 26. Adding the SAP message the to transient context
    This figure shows adding the SAP message the to transient context
  7. In the SAPMDMMediation editor on the left side, expand the Service Invocation section and drag a Callout to the canvas.
  8. Select the PartyServicePartner reference, click OK.
  9. From the Transformation section, drag a XSL Transformation to the canvas. Right-click the XSL Transformation, select Rename, and specify the name populate SearchPerson message.
  10. From the Transformation section, drag the following to the canvas:
    • a XSLT Transformation (name: populate GetPartyIdentification message)
    • a XSLT Transformation (name: populate UpdatePartyIdentification message)
  11. From the Routing section, drag the following to the canvas: Message Filter (name: update necessary?).
  12. From the Service Invocation section, drag the following to the canvas:
    • a Service Invoke (Reference: PartyServicePartner, Operation: SearchPerson, name: SearchPerson)
    • a Service Invoke (Reference: PartyServicePartner, Operation: GetPartyIdentification, name: GetPartyIdentification)
    • a Callout (Reference: PartyServicePartner, Operation: UpdatePartyIdentification, name: UpdatePartyIdentification)
  13. As shown in Figure 27, do the following:
    • Connect emitUpdateAfterImageSapDebmas06 with populate SearchPerson message.
    • Connect the out output of populate SearchPerson message with SearchPerson
    • Connect the out output of SearchPerson with populate GetPartyidentification message
    • Connect the out output of populate GetPartyIdentification message with GetPartyIdentification
    • Connect the out output of GetPartyIdentification with update necessary?
    • Connect the match1 output of update necessary? with populate UpdatePartyIdentification message.
    • Connect the out output of populate UpdatePartyIdentification message with UpdatePartyIdentification.
    • Right-click the canvas and select Automatic Layout.
    Figure 27. Connecting the components
    This figure shows Connecting the components
  14. Double-click populate SearchPerson message.
  15. In the New XML Map window, click Next.
  16. In the Message Root drop down box, select '/'.
  17. Verify the Input Message Body is set to emitUpdateAfterImageSapDebmas06RequestMsg and the Output Message Body is set to SearchPersonRequest, as shown in Figure 28.
    Figure 28. Configuring the SearchPerson message
    This figure shows Configuring the SearchPerson message
  18. Click Finish. The mapping editor is opened.
  19. In the mapping editor, create the following connections between the elements of the structure on the left and the elements of the structure on the right:
    Left ElementRight ElementTransform Function
    body/emitUpdateAfterImageSapDebmas06/emitUpdateAfterImageSapDebmas06Inputcontext/transientMove
    body/emitUpdateAfterImageSapDebmas06/emitUpdateAfterImageSapDebmas06Input/SapDebmas06IdocBO/SapDebmas06DataRecord/SapDebmas06E2kna1m005/KUNNRbody/SearchPerson/personSearch/adminClientNumbernumber
  20. Some fields of the SearchPerson message need to be set with default values. Default values can be assigned with the Assign function. To create an Assign, right-click the appropriate field and select Create Assign. In the Properties of the Assign, the value can be specified on the General tab. Create the assigns listed in the table below. In a production system, some of the sample values below may need to be set dynamically depending on the request message.
    Assign for fields (all fields below are relative to: body/SearchPerson) Value to be assigned
    control/requestId54321
    control/requesterNameuser
    control/requesterLanguage100
    adminSystemType/code1
  21. Press Ctrl + S to save your changes, as shown in Figure 29.
    Figure 29. Configuring mapping and default values for the SearchPerson message
    Configuring mapping and default values for the SearchPerson message
  22. Double-click populate GetPartyIdentification message.
  23. In the New XML Map window, click Next.
  24. In the Message Root drop down box, select '/'.
  25. Verify the Input Message Body is set to SearchPersonResponse and the Output Message Body is set to GetPartyIdentificationRequest, as shown in Figure 30.
    Figure 30. Configuring input and output messages
    This figure shows configuring input and output messages
  26. Click Finish. The mapping editor is opened.
  27. In the mapping editor, create the following connections between the elements of the structure on the left and the elements of the structure on the right:
    Left ElementRight ElementTransform Function
    context/transientcontext/transientMove
    body/SearchPersonResponse/result/controlbody/GetPartyIdentification/controlMove
    body/SearchPersonResponse/result/searchResult/matchedFields/partyIdbody/GetPartyIdentification/partyIdMove
  28. Create the assign listed in the table below:
    Assign for fieldsValue to be assigned
    body/GetPartyIdentification/identificationType6
  29. Press Ctrl + S to save your changes, as shown in Figure 31.
    Figure 31. Configuring the mappings
    This figure shows Configuring the mappings
  30. Click the update necessary? Message filter.
  31. In the Properties view, select the Details tab, click the Add button on the right.
  32. In the Add/Edit window, enter the following pattern.
    /context/transient/SapDebmas06IDocBO/SapDebmas06DataRecord/SapDebmas06E2kna1m005/STCD1 != /body/GetPartyIdentificationResponse/result/identification/number In this sample, it is verified the value stored in MDM Server differs from the value received in the SAP update message.
  33. Select match1 as the Terminal name.
  34. Press Ctrl + S to save your change, as shown in Figure 32.
    Figure 32. Configuring the field mappings
    This figure shows Configuring the field mappings
  35. Double-click populate UpdatePartyIdentification message.
  36. In the New XML Map window, press Next.
  37. In the Message Root drop down box, select '/'.
  38. Verify the Input Message Body is set to GetPartyIdentificationResponse and the Output Message Body is set to UpdatePartyIdentificationRequest, as shown in Figure 33.
    Figure 33. Setting the output message body
    This figure shows Setting the output message body
  39. Click Finish. The mapping editor is opened.
  40. In the mapping editor, create the following connections between the elements of the structure on the left and the elements of the structure on the right:
    Left ElementRight ElementTransform Function
    context/transient/SapDebmas06IDocBO/SapDebmas06DataRecord/SapDebmas06E2kna1m005/STCD1body/UpdatePartyIdentification/partyIdentification/numberMove
    body/GetPartyIdentificationResponse/result/controlbody/UpdatePartyIdentification/controlMove
    body/GetPartyIdentificationResponse/result/identification/idPKbody/UpdatePartyIdentification/partyIdentification/idPKMove
    body/GetPartyIdentificationResponse/result/identification/lastUpdatebody/UpdatePartyIdentification/partyIdentification/lastUpdateMove
    body/GetPartyIdentificationResponse/result/identification/partyIdbody/UpdatePartyIdentification/partyIdentification/partyIdMove
  41. Press Ctrl + S to save your changes, as shown in Figure 34.
    Figure 34. Creating the mappings
    This figure shows Creating the mappings
  42. In the SAPMDMMediation editor, some the components still have terminals that are not yet connected. Connect each fail terminal to a Fail component from the Error Handling section of the Palette. Connect all remaining unused terminals to a Stop component from the Error Handling section of the Palette.
  43. Right-click the Canvas and select Automatic Layout (the layout below is modified to fit the screen), as shown in Figure 35.
    Figure 35. The final mediation flow
    This figure shows The final mediation flow
  44. In the SAPMDMMediation editor, click the Response tab.
  45. Connect the out terminal of the Callout Response component with a Trace component from the Tracing section of the Palette.
  46. Connect the out terminal of this Trace component to a Stop component from the Error Handling section of the Palette.
  47. Connect all remaining unused terminals with a Fail component from the Error Handling section of the Palette.
  48. Right-click the canvas and select Automatic Layout.
  49. Press Ctrl + S to save your change, as shown in Figure 36.
    Figure 36. Adding tracing and error handling
    This figure shows Adding tracing and error handling

Deploy the application to the server

  1. In the Servers view, right-click WebSphere Process Server v7.0 at localhost and select Add and Remove projects.
  2. Select the SAP2MDMApp from the Available Projects list and click Add, as shown in Figure 37.
    Figure 37. Deploying the project
    This figure shows Deploying the project
  3. Click Finish.
  4. Wait for the Status to change to 'Synchronized'.

Running the scenario

In order to run the scenario, a Person record on the MDM site must be created, which is then populated to SAP (this is exactly the scenario described in the first part of this tutorial). Log on to the Data Stewardship Console and create a new Person record as described in the Running the scenario section in the first part of this tutorial. Memorize or copy the SAP customer ID created by the MDM system.

  1. Log-on to your SAP system and call SAP transaction XD03.
  2. Search for the customer record with said SAP customer ID, as shown in Figure 38.
    Figure 38. Searching the customer record
    This figure shows Searching the customer record
  3. Navigate to the Control Data tab and switch to the edit mode.
  4. Enter an arbitrary value for the Tax Number 1 field.
  5. Save your settings, as shown in Figure 39.
    Figure 39. Adding the tax number
    This figure shows Adding the tax number
  6. The scheduled job we set up on the SAP system will now detect that the tax ID field was modified. A change pointer will be created and according to the period value we specified, an IDoc of type DEBMAS06 is generated and sent back to the ESB which will the update the tax identifier on the MDM system. Note: If for some reason the IDoc isn't send automatically, you can always manually trigger SAP to send an IDoc by calling transaction BD12.
  7. As soon as the IDoc was received by the WebSphere Adapter for SAP software, the mediation flow we created will process the data and update the MDM person record's tax ID.
  8. Switch back to the MDM Data Stewardship Console and search for the previously created record. Click on the Identifiers tab. The tax ID you entered in your SAP system should appear here. Note: If it's nor appearing yet, don't press F5 to refresh your browser, instead just re-click the Identifiers tab, as shown in Figure 40.
    Figure 40. Reviewing the tax number in the Data Stewardship Console
    This figure shows Reviewing the tax number in the Data Stewardship Console

Conclusion

Now that you have finished this second part of our tutorial series, you have a good understanding of how to integrate MDM Server with an Enterprise Information System. We focused on an integration with SAP, but the basic steps you learned will be identical or at least similar for other system integrations. Generally the MDM Server should be the central repository for the master data. However, there are scenarios where some attributes are generated or maintained by an external system (in our example, a tax identifier is generated in an SAP system). In that case it is essential to update this attribute on the MDM system as soon as possible. In this tutorial, we do this by using SAP's change pointer mechanism to send out an IDoc to the ESB every time a record was modified. The ESB then checks whether the IDoc contains a modified tax identifier and updates the MDM record.

Resources

Learn

Get products and technologies

  • Build your next development project with IBM trial software, available for download directly from developerWorks.
  • Evaluate IBM products in the way that suits you best: Download a product trial, try a product online, use a product in a cloud environment, or spend a few hours in the SOA Sandbox learning how to implement Service Oriented Architecture efficiently.

Discuss

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into Information management on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management
ArticleID=938234
ArticleTitle=Integrating MDM Server with Enterprise Information Systems using SAP as an example, Part 2: Enriching customer records with SAP specific information
publish-date=07252013