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.Note: 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.
The steps involved in each of these different deployment methods are described in more detail in the following procedures.
You can also
deploy all types of items except Jobs and workflows to the MDM server using
mDeployItem from the CommandLine. To deploy
Jobs to the MDM server, use the command
deploy workflows to the MDM server, use the command
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 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).
You can also undeploy one or more deployed items from the MDM server.