Deploying activates the latest committed configuration on all runtime servers in the project. The deployment process enables you to deploy changes when it is convenient. For example, you may save and commit multiple configuration changes over the course of a few days then decide to deploy those changes during off hours, such as over the weekend.
- Navigate to IntegrationContinuous Replication.
- Click the ellipses next to the project you wish to validate, then select Apply Configuration Changes from the dropdown menu. This will open validate configuration window.
- Select one or all of the following options:
- Stage configuration changes: Commit the configuration changes for all replication pipelines.
- Make Configuration Changes Active: Deploy the configuration changes for all replication pipelines.
- Display alerts to monitor progress: Displays the Alerts dialog once the Deploy action is clicked.
- Force making configuration changes active: Forces the configuration changes to be active.
- If the option Force making configuration changes active is selected, the following are required fields:
- Backlog is empty: The backlog must empty within this time or the deployment will not start. The default value is 4 minutes.
- Dataset capture is disabled: Time allowed for the table capture status to be disabled for the deployment to start. The default value is 8 minutes.
- Replication is stopped: Replication processes must be stopped within this time or the deployment will not start. The default value is 4 minutes.
- Click Apply to apply the configuration.Note: Apply is enabled only if Stage Configuration Changes and/or Make Configuration Changes Active are selected.