Skip to main content Skip to complementary content

Deploying the data model to the MDM server

You must always deploy your data model to the MDM server for any changes you made to be taken into account at runtime.


  1. In the MDM Repository tree view, right-click the data model you want to deploy, and select Deploy To....
  2. In the dialog box that opens, click Add Dependencies and click Continue after adding the dependencies.
  3. In the Select a server location definition dialog box, select the server where you want to deploy the data model, and then click OK.
    A dialog box pops up, indicating that the deployment is successful.
  4. Click OK to complete deploying the data model.
    In this example, since Talend MDM is configured with Talend Data Stewardship, when you deploy the data model Customer to an MDM server, the following changes are propagated to Talend Data Stewardship automatically:
    • A new data stewardship data model named customer - customer - tmdm is created with attributes that correspond to each simple type element in the Customer entity;
    • A new merging campaign named customer - customer - tmdm is created using the new data stewardship data model.

    Meanwhile, MDM data types are mapped into Talend Data Stewardship data types, and MDM element constraints (if any) are translated into Talend Data Stewardship attribute constraints. For more information, see Mapping tables between Talend MDM and Talend Data Stewardship.

    For more information about how the changes of an MDM data model are propagated to Talend Data Stewardship upon its deployment to an MDM server, see Talend Studio User Guide.

    You can also create the relevant campaigns and data stewardship data models for an MDM data model through the REST API. For more information, see Set up the Data Stewardship metadata for a data model.


You have finished preparing your simple MDM project in Talend Studio.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!