Deploy and redeploy pipelines into selected instances and configure the runtime behavior using policies.


In this section you will learn:

  • Assign a pipeline, or multiple to an instance.
  • Assign a policy.
  • Deploy
  • Redeploy changes


Please make sure you know what you’re doing. You can break production stuff.

Once a pipeline has been tested and you are ready to move things to a development or production environment, it is important to set up an appropriate deployment plan. Deployment plans will help you configure a number of critical steps such as remote or manual installation, the policies that dictate how the DDC operates in the host environment, and the properties of the installation, once complete such as the version, status, and functionality. You will need a previously created Pipeline that has been tested and published.

Add a pipeline

Once a pipeline has been selected and assigned the pipeline and policy will be selected and you will have the opportunity to confirm that the components are correct, and if not, you will be able to edit the installation method, the pipeline and the policy settings.

This will then allow you to select the correct pipeline, policies and assign this to the deployment instance. 

Adding multiple pipelines to the same Instance

Adding an additional processing pipeline is as simple as following these same steps to add a single pipeline, for your additional pipeline. Simply add a new pipeline, select the instance to assign it, the policy that you need to apply. In the screenshot below, is an example of two pipelines both assigned to the same machine and instance.

Add Policies

 You will always need to add select the policy to apply.  Adding a policy is done through the add a policy drop down. Either select the default policy or you can stop and use DDC deployment policy to create a new policy plan to use on the deployment. Then assign the Pipeline policy you want to use, then add the pipeline that corresponds to the the policy you wish to run and  use. See the DDC policies section for more details on using the DDC policies to set the runtime behavior of the Pipeline. Once named and save it can be used in a deployment plan under the policies tab. Polices are a powerful way of controlling how the data is being processed in regards to periodicity and function. 

The default policy thread and batch values will be inefficient for some sources, please set them accordingly.


Once a machine, instance, pipeline and policies are configured and assigned, it is then possible to deploy.

Steps to deploy generally, and especially for the first time, follow these steps.

  • Create the machine(s) and instance(s) necessary
  • Create the DDC pipeline, or pipelines
  • Assign the DDC pipeline policies either default or assign a DDC pipeline policy
  • Assign a pipeline to an instance
  • Deploy

Add a machine;

Add an Instance;

Add a Pipeline from a published version;

Choose a Pipeline policy;

Assign it to an Instance;

Apply changes to Deploy;

Should everything work correctly you will now have a green indicator in both the Overview and Infrastructure panels.


It is also possible to stop a DDC, or delete a DDC on an instance by using the marked buttons. One possible reason to delete an DDC is if you would like to assign a new policy, as you would like to change the policy, or pipeline policy associated with the instance on the machine.

Stop a DDC, press stop.

Delete a DDC use the 3 vertical dot but and select from the drop down.

Then Apply changes.