Talend MDM Demo Content


This demo illustrates the basic features of Talend MDM CE. It may also be used as a reference for your projects.

Since 4.0.2, Talend MDM CE includes Talend Open Studio. So it integrates a comprehensive and powerful Data Integration platform to cover the complete lifecycle of a master data in the hub:

  • Initial loading from heterogeneous sources
  • Ongoing updates from data owners to keep the “single version of the truth”
  • Real-time enrichment with external sources and information providers
  • Real-time rule validation processes
  • Synchronization of subscribing applications with the latest changes

The demo comprises the MDM model, associated jobs, and instructions to get started.

INFO Updated for 4.1

INFO The material and steps described here are not sufficient for Enterprise Edition. If you use EE, you still need to follow all the steps here and then follow additional steps.

Demo Material


If you already have the product installed and setup, you can jump to “Install the demo material” below.

Install the product

  • Download the latest version of Talend MDM Community Edition from Talend's web site (http://www.talend.com/download.php#mdm)
  • Unzip the TMDMCE-All-r<revision#>-V4.1.X.zip archive
  • Install the MDM Server:
    • On Windows, double-click on TMDMCE-Server-All-r<revision#>-V4.1.X.jar to launch the installer
    • On Linux, run “java -jar TMDMCE-Server-All-r<revision#>-V4.1.X.jar”, or right-click and select “Open with JDK
  • Install MDM Studio:
    • Unzip TMDMCE-Studio-All-r<revision#>-V4.1.X.zip in a directory WARNING Windows built-in zip support may not unzip correctly; use 7zip

Run the product

  • Run the MDM Server:
    • Windows: start the service or run in console mode: execute <MDM server install dir>\jboss-4.2.2.GA\run.bat
    • Linux: execute <MDM server install dir>/jboss-4.2.2.GA/run.sh
  • Run MDM Studio:
    • Windows: run TMDMCE-win32-x86.exe (32 bits) or TMDMCE-win32-x86_64.exe (64 bits)
    • Linux: run TMDMCE-linux-gtk-x86.sh

Setup the Studio for the first time

WARNING The activation of “Deploy to MDM” is OBSOLETE IN 4.2

  • Activate the “Deploy to MDM” menu: see howtoactivate_the_export_to_mdm_menu_on_jobs. In a nutshell, this consists in those 2 steps:
    • Select Windows > Preferences, then expand Talend > Import/Export, select “Talend MDM Server”
    • Add your MDM Server, for instance host = “localhost”, port = “8080”

INFO This is still useful is you want to deploy a job to MDM from the TOS Repository view, but it is no longer necessary, as the job repository tree now shows up directly within the MDM Server view.

  • You can switch between the Design (Data Integration) or MDM perspectives, or simply activate the MDM Server view within the Design perspective:
    • Select Windows > Show View, select “MDM Server”
    • (Optional) Drag the MDM Server view and dock it alongside the Repository view
  • Connect to the MDM Server:
    • Click on the “Add MDM Server Location” button:
    • Change “localhost” and or the port number in the URL, if applicable
    • Enter Username = “admin”, Password = “talend”
    • Click on “Save password”
    • Hit OK.

Install the demo material

  • In the MDM Server view:
    • Right-click on the top node and select “Import”
    • Select “Select Archive File” and browse to ProductDemo_41_Model.zip
    • Hit Finish
  • In the TOS Repository view:
    • Right-click on the “Job Designs” node and select “Import Items”
    • Select “Select Archive File” and browse to ProductDemo_41_Jobs.zip
    • Hit the Finish button

At this point you need to deploy a few jobs to MDM. You have two options: 1) stay in the TOS Repository view and use a right-button click (you must have completed “setup the Studio for the first time” above) 2) switch back to the MDM Server view and use the new job repository node. INFO You may have to right-click on the job repository node and click “Refresh” for all the imported jobs to show up.

  • Right-click on each of the following jobs and select “Deploy to MDM”: INFO IMPORTANT Choose the ZIP format, not the WAR format
    • CheckAvailability
    • CompleteStoreURL
    • ValidatePriceChange
    • MakeAvailable
    • SynchronizeApps

(Job repository node within the MDM Server view)

NOTE We are using the ZIP format for the jobs in this demo. When a job is sent to MDM as a ZIP, the MDM Server dynamically loads it, so the Java code is co-located with MDM, which greatly reduces the latency of MDM triggers. The WAR format is still a valid choice for distributing the load, deploying the jobs onto different servers, or executing the job closer to the sources/targets.

  • Next, populate the data-container:
    • Run the job: MDM_LoadAll
  • Finally add the pictures on the server:
    • Unzip ProductDemo_41_Pictures.zip onto <MDM server install dir>/jboss-4.2.2.GA/server/default/deploy/zz.50.ext.imageserver.war/upload

Run the demo

WARNING At this point you can only run the demo on a Community Edition. Enterprise Edition requires role-based authentication, please proceed to the additional steps before you can run the the demo.

  • Connect to the MDM Web interface
    • Open an Internet Explorer or Firefox browser (sorry, Chrome not supported)
    • Connect as user “user”, password “user”
  • Use the “Browse Records” menu to browse the product catalog
  • Use “Grouping Hierarchy” to view the products by family:
    • Entity: select Product
    • Pivot: select Family→Name
    • Display: select Name
  • You can also group on something else, such as availability:
    • Entity: select Product
    • Pivot: select Availability
    • Display: select Name
  • Trigger a job to enrich a record:
    • Go to Browse Records
    • Select the Product view
    • Click on the “New Record” button
    • Enter an Id, a Name, Description and a Price
    • Click on the little magnifier with a '+' sign to link it to a product family
    • Click on “Save & Close”
    • The CheckAvailability job was kicked off automatically to update the Availability flag
    • Double click on the product you just created, then click on “Journal”
  • Trigger a job to validate a record:
    • Increase the price by more than 15%, then hit “Save”
    • The ValidatePriceRange will disallow the change
  • Look into the JBoss console:
    • Whenever a Product is updated, SynchronizeApps simulates a synchronization by logging the new record
  • Integrate new products from external sources:
    • The AddProduct job simulates a system that sends new products

Reset the demo

  • Use the MDM_Reset job
mdmce/demo.txt · Last modified: 2011/12/17 03:52 (external edit)
Recent changes RSS feed Driven by DokuWiki