Deploying an application ingestion and replication task

After you define an application ingestion and replication task, deploy the task to create an executable job instance on the on-premises system that contains the Secure Agent and the Database Ingestion agent service. You can run an application ingestion and replication job only after you deploy the associated task. When you deploy the task, Application Ingestion and Replication also validates the task definition.

If you undeploy a job and then want to run the job again, you must deploy the task again to create a new job instance. The new job instance name ends with an incremented number in the format taskname-job_instance_number. The job instance number is incremented each time you deploy the ingestion task by adding 1 to the maximum instance number across all ingestion jobs.

Before you deploy a task that is configured for a Snowflake target, you must drop the existing target tables that do not match the structure of source objects. The existing target tables might not match the structure of source objects because of newly added source fields, dropped source or target fields, or modified field null constraints or data types. When you deploy the task after dropping the existing target tables, a new set of target tables are generated based on the source object selection rules and target table renaming rules.

To deploy an application ingestion and replication task, in the task wizard, save the completed task definition and then click Deploy.

Deployment considerations:

•If you included spaces in the application ingestion and replication task name, the spaces are omitted from the corresponding job name for the generated job instance.

•If the deployment process fails, the job status switches to Failed. You can then Undeploy the job. To diagnose the error, you can download the error log from one of the monitoring interfaces: 1) the My Jobs page accessed from the unified Home page, 2) the All Jobs page in Monitor, or 3) the All Jobs tab on the Data Ingestion and Replication page in Operational Insights. To download the error log, on the Actions menu for the job, click Error Log. After you resolve the issue, deploy the task again from the application ingestion and replication task wizard or from the Actions menu for the job.

•If the Secure Agent is restarted while the task is deploying, the job status switches to Failed. Avoid restarting the Secure Agent while tasks are being deployed.

•If a task appears to be hung in the Deploying state, restart the Secure Agent. The associated job instance acquires the status of Failed. You can undeploy it and then deploy it again.