Export Job Automation

Connector jobs can be automated in multiple ways. This article explores the most common methods in detail.

Automation via Contentserv Active Job

The SAWSConnector suite contains several Contentserv Active Jobs, one such is the “SAWS – Start connector job” job.

This job allows you to start a connector job. Note that this Active Job only acts as a “kick-off”, it only starts the connector job and does not monitor or wait for it to finish.

Using the automation tab of the Contentserv Active Jobs, the automation can be timed. If an incremental/delta connector is used, most user let it run hourly, bigger exports daily or weekly.

Automation via Contentserv Workflow Action

Connector jobs can be started when a workflow action like for example Set Productive is executed. To configure this head into the action and select the action component Run SAWSConnector job.

You are then able to select the job that shall be started.

Automation via REST API

Connector jobs can be started via HTTP requests to the REST API. Read more here.

Chaining Connector Jobs

In many instances connector jobs shall be chained. For example the media shall be uploaded, then the categories shall be sent, followed by the products. These jobs shall not run in parallel since the categories and products need the existing media, and the products need the existing categories to link to them. Hence these jobs need to be chained.

To chain jobs the job-related task Run follow-up SAWSConnector job must be selected.

Since the connector version 1.19.0, you are now able to see the chained job from the outer view of the job center.

Do not use the Active Job for chaining!

These jobs would start these 3 jobs simultaneously instead of after one another. If you want to automate your chain, only select the first job of it in the Active Job.