Operator Guide

10.5
- 10.4.1
- 10.4.0

Back Next

Publication Schedules

The publication schedule defines the frequency of the publication for publications that are triggered by

Data Integration Hub

When you define a schedule for a publication, you can select to publish the data manually or by an external trigger, at defined intervals, or after a specific publication or subscription run completes. For publications with a flat file source or with a pass-through file source, you can also select to run the publication immediately after the published files are ready.

If you use file transfer, you can run the publication immediately after the published files are ready only if

Data Integration Hub

deletes the files after it reads them. This ensures that files are not read multiple times.

For file publications that are published manually, by an external trigger, or at defined intervals, and that publish multiple files, all the files must be present in the source location when the publication starts.

For publications with a defined schedule, the publication starts when one of the following conditions is true:

The scheduled start time arrives.

You run the publication manually.

A publication pre-process starts the publication process.

The developer starts the publication from a command-line API or from a REST API.

The developer starts the publication from PowerCenter with the DX_StartPublication transformation.

The running of the publication or subscription after which the current publication is configured to run is complete.

Retry Policy: To improve business continuity, you can configure a retry policy for publications that are triggered by Data Integration Hub. The policy defines the number of times
Data Integration Hub
retries to run the publication in case of failure and the retry interval. The policy does not apply to publications that you run manually. You can define a policy of up to nine retry attempts with a retry interval that is between five minutes and 23 hours.
Data Integration Hub
attempts to reprocess publication events in an Error status based on the policy you define.
Data Integration Hub
doesn't attempt to reprocess Error events in the following scenarios:
You manually change the status of an Error event to Complete.
You manually change the status of an event to Error.
You manually reprocess an Error event and the publication runs successfully.

You can define a retry policy for automatic file publications.

Data-driven publications and multi-latency publications are not triggered by
Data Integration Hub
. For publications of those types you define the time intervals according to which
Data Integration Hub
groups the published data.

Rename Saved Search

Table of Contents

Operator Guide

Operator Guide

Publication Schedules

Publication Schedules