Administrator Guide

10.4.0
- 10.5
- 10.4.1

Back Next

Publication and Subscription Event Types and Statuses

Data Integration Hub

assigns a default set of event types and event statuses to publication and subscription events when the following conditions exist:

A publication with a publication pre-process runs.

A publication or a subscription with an automatic mapping runs.

A publication or subscription with a custom mapping that is associated with a Data Integration task runs.

A subscription post-process runs.

A data-driven publication runs.

It is recommended that publications and subscriptions with a custom mapping that is associated with a PowerCenter workflow use the same event statuses and types as those that

Data Integration Hub

assigns to the automatic mappings. The developer assigns event statuses and types for custom mapping in the PowerCenter workflow.

Default Event Types

Data Integration Hub

assigns

the following event types:

Publication. Assigned to a publication process

that is not initiated by a data-driven publication

. Acts as the parent event for all Subscription events and for File events of publications that publish multiple files.

For File events of publications that publish a single file, the event log includes a link to the file on the

Data Integration Hub

document store.

Data-driven Publication. Assigned to a publication process of a data-driven publication.

File Event. Assigned to the publication of a file in publications that publish multiple files.

The event log includes a link to the file on the

Data Integration Hub

document store.

Subscription. Assigned to a subscription process. Acts as a child event for a publication event.

For events of subscriptions that consume pass-through files and do not use file transfer, the event log includes a link to the file on the

Data Integration Hub

document store. For events of subscriptions that use file transfer to consume files, the event log includes a link to the file transfer list.

Aggregated Subscription. Assigned to a subscription process that consumes multiple data sets from the same topic with a single subscription mapping. The event contains references to all Subscription events that were created when the associated topic finished publishing each data set. The Subscription events inherit their status from the Aggregated Subscription event.

Compound Subscription. Assigned to a subscription process that consumes data sets from multiple topics with a single subscription mapping. The event contains references to all Subscription events that

Data Integration Hub

creates when each topic publication finished publishing the data set.

Default Event Statuses

For publications,

Data Integration Hub

assigns the following event statuses:

Pre-processing. Indicates that the publication pre-processing instance is running.

Processing. Indicates that the publication instance is running.

Delayed.

Relevant for File events, for publications that publish multiple files. Indicates that the file that is related to the event is ready but that not all the files that the publication publishes are ready. When all the files that the publication publishes are ready,

Data Integration Hub

creates a Publication event, and the related File events inherit the status of the Publication event. You cannot run delayed File events.

Completed. Indicates that the publication instance finished running and that the data is ready for subscribers.

Error. Indicates that the publication instance encountered errors and did not finish running.

Each Publication event also shows the consumption status of the child Subscription events. The status reflects the overall consumption and changes after all Subscription events changed status. For example, the consumption status changes to complete after all subscribers finished consuming the published data.

For subscriptions,

Data Integration Hub

assigns the following event statuses:

Delayed.

Indicates that the published data is ready but that the subscribing application did not start consuming the data. Relevant for subscriptions with a defined schedule and for subscriptions that are run manually or by an external trigger. You can run delayed subscription events from the

Subscriptions

tab of the

Application Details

page.

Processing. Indicates that the subscription instance is running.

Completed. Indicates that the subscription instance finished running and that the subscribing application consumed all published data.

Post-processing. Indicates that the subscription post-processing instance is running.

Error. Indicates that the subscription instance encountered errors and did not finish running.

Rename Saved Search

Table of Contents

Administrator Guide

Administrator Guide

Publication and Subscription Event Types and Statuses

Publication and Subscription Event Types and Statuses

Default Event Types

Default Event Statuses