You must always deploy your repository items to the MDM Server for any changes you make to be taken into account at runtime.
You have a choice of how you deploy items to the MDM Server.
You can click the Update Server button in the repository icon bar to deploy some or all of the items that have changed in the MDM Repository since your last deployment.
In the specific case of Jobs, only those Jobs that have previously been deployed using the Deploy to... option are proposed for update.
You can manually select which items you want to deploy from the MDM Repository tree view, either by specifying the destination server explicitly or by choosing to deploy to the last server used.
You can edit the Preferences so that, when you save an item, it is automatically deployed to the last server used.
Entity names must be unique, both within a Data Model and across multiple Data Models deployed to the same MDM Server.
The steps involved in each of these different deployment methods are described in more detail in the following procedures. For further information on deploying Jobs, see How to deploy Jobs from the MDM perspective
To deploy items that have changed in the MDM Repository since your last deployment, do the following:
In the MDM Repository tree view, click the Update Server button in the repository icon bar.
In the window that opens, select the server where you want to deploy the item or items from the drop-down list, select the item or items to deploy, and then click OK to perform the deployment.
To manually select the items you want to deploy to the MDM Server, do the following:
In the MDM Repository tree view, right-click the item you want to deploy, and then click one of the following deployment options:
Deploy To... to select the MDM Server where you want to deploy the item from the list of available servers
Deploy To Last Server to reuse the server you used for the most recent deployment action
Update Server to open the server update dialog box, as described in the previous procedure.
The deployment options available may vary depending on the type of item you want to deploy, and if you are deploying the item for the first time or if it has already been deployed to a server.
If you want to deploy multiple items at the same time, press and hold down the Ctrl key while you click each of the items you want to deploy.
A dialog box appears, allowing you to add dependencies for the selected item or items.
Click the Add Dependencies button to add dependencies of the selected item(s).
You can click the Add Dependencies button for multiple times until all item dependencies are added or click the Add All Dependencies button to add all item dependencies in one go.
Then, click Continue.
For more information about item dependencies, see Managing item dependencies in the MDM Repository.
If appropriate, select the server where you want to deploy the items in the [Select server location definition] window.
In the [Deploy to Talend MDM] window, leave the Context scripts check box selected.
Click Finish to deploy your items.
To automatically deploy items to the MDM Server on saving, do the following:
Click Windows > Preferences.
The [Preferences] window opens.
Expand Talend, and then click MDM.
Select the Automatically deploy items onto last server when saving check box, and then click OK to enable this option.
If this option is enabled, whenever you save any changes you make to an item, the item is automatically deployed to the MDM Server.
You can also deploy all types of items except Jobs and
workflows to the MDM server using the command
the CommandLine. To deploy Jobs to the MDM server, use the command
mDeployJob. To deploy workflows to the MDM server, use
mDeployWorkflow. To deploy new items or the
existing items that have changed in the MDM Repository since your last
deployment, use the command
mUpdateServer. For more information
on how to use these commands, see the help provided in the
For more information about the CommandLine, see the appendix on CommandLine in the Talend Administration Center User Guide.
If the items you want to deploy are being handled and deployed by another user, one or more conflicts will occur. You can set up a strategy to reconcile the conflict(s). For more information, see Setting up a reconciliation strategy for deployment conflicts.
You can also undeploy one or more deployed items from the MDM server. For more information, see Undeploying one or more repository items from the MDM Server.
Sometimes, several users may handle items simultaneously. In this case, conflicts could easily occur when one of the users wants to deploy items to the MDM server. You can set up a reconciliation strategy for the deployment conflict(s).
This feature is only available to users who install MDM servers with relational databases.
The following reconciliation strategies for deployment conflicts are available:
Default (Skip same, overwrite difference, and deploy not exists): the same items are skipped, the items which are different from those on the studio side will be overwritten, and the items which do not exist will be created.
Overwrite All: all relevant items will be overwritten.
Skip Difference (Skip same and different object): both the same items and the items which are different from the those on the studio side will be skipped.
To set up the reconciliation strategy for deployment conflicts in the dialog box that warns about deployment conflict(s), proceed as follows:
In case of one or more deployment conflict(s), the following dialog box appears:
Select the desired reconciliation strategy according to your need.
Select the Remember my choice, don't show this dialog again check box to make the reconciliation strategy remain unchanged upon validation.
If you want to show this dialog box once again so that you can set up a new reconciliation strategy, select the Show the conflict dialog when more than one object has conflict check box in the [Preferences] dialog box. For more information, see Setting up a reconciliation strategy in Preferences.
If needed, click the Show Conflicts button to learn about the conflict details.
The Operation column allows you to select the reconciliation action to be taken for each conflict.
Besides, you can set up the operation in batch mode by clicking the buttons on the right side of the dialog box.
If you want to overwrite all relevant items, click Overwrite All. If you want to skip the same items, click Skip Same. If you want to skip the items which are different from those on the studio side, click Skip Difference.
If needed, select the Only Show Conflict and Modified Objects check box to view only the items which are modified and involved in the conflicts.
If needed, select the Show Local And Server Timestamp check box to view the timestamp differences.
Click OK to close the dialog box.
Click OK to validate your changes.
Alternatively, you can set up the reconciliation strategy for deployment conflicts in the [Preferences] dialog box.
To do that, proceed as follows:
From the menu bar, click Window > Preferences to open the [Preferences] dialog box.
Expand the Talend > MDM node and click Consistency.
By default, the Show the conflict dialog when more than one object has conflict check box is selected. It means that the dialog box that warns about deployment conflict(s) will appear even if only one deployment conflict occurs.
Select the appropriate reconciliation strategy option according to your needs.
Click OK to validate your changes.
can be configured with the integration of Talend Data Stewardship to perform the integrated matching tasks. In this case, when you deploy a newly created data model or an updated data model to an MDM server, as long as the data model has a match rule attached to it, the changes of the MDM data model will be propagated to Talend Data Stewardship automatically. To learn more information about Talend Data Stewardship concepts and working principles, see the Talend Data Stewardship Documentation.
When you create a new data model and deploy it to an MDM server, for each entity that has a match rule attached to it, the following changes are made in Talend Data Stewardship:
A new data stewardship data model is created with attributes that correspond to each simple type element in the MDM entity, and its name is in the format of <MDM_data_model_name> - <MDM_entity_name> - TMDM (for example, PRODUCT - STORE - TMDM).
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 the documentation about the mapping tables between Talend Help Center (https://help.talend.com).and Talend Data Stewardship on
A new merging campaign is created using the new data stewardship data model, and its name is in the format of <MDM_data_model_name> - <MDM_entity_name> - TMDM (for example, PRODUCT - STORE - TMDM).
Meanwhile, the Talend Data Stewardship campaign will declare a role for each role access right configured on the MDM entity, and also any role access right configured for an element in the MDM entity will be mapped into the role access right for the corresponding Talend Data Stewardship attribute.
Besides, the campaign will have only NEW and RESOLVED steps in its workflow, without a VALIDATION step.
If no role access rights are defined for the MDM entity, the corresponding Talend Data Stewardship campaign has one built-in role created named "Steward", all Talend Data Stewardship attributes are ready-only for this role and the "Steward" role is linked to the NEW step.
When you update a data model and re-deploy it to an MDM server, for each entity that has a matching key contained in this data model, the following changes are made in Talend Data Stewardship depending on your updates in the MDM data model:
If you add a new entity with one or more match rules attached to it, a new data stewardship data model and a new merging campaign will be created accordingly.
If you attach a match rule to an existing entity with no match rule attached to it before, a new data stewardship data model and a new merging campaign will be created accordingly.
If the data stewardship data model already exists, it will be updated accordingly.
If the merging campaign already exists, it will be updated accordingly.
However, if you remove an entity or remove the attaching of all match rules to an entity, the corresponding data stewardship data model and merging campaign which already exist will not be removed. If needed, you can remove them manually.