The publication process starts on the schedule that you define in the publication
, when an external process triggers the publication,
or when you manually run the publication.
When data transfer is complete, the topic data set is ready for subscribers. The subscription process starts when one of the following conditions exist, based on the configuration of data consumption in the subscriptions:
When data is published to the topic.
When all publishers that publish to the topic finish publishing.
If the topic to which the data is published has subscribers,
Cloud Integration Hub
triggers a
Cloud Integration Hub
subscription workflow for each subscriber, to consume the data.
Cloud Integration Hub
generates events to track the progress of the publication and subscription process. When an application publishes data,
Cloud Integration Hub
creates a parent publication event. When the publication process ends and the published data is ready to consume,
Cloud Integration Hub
generates a child event for each subscription.
The events change status as the publication and subscription process progresses, and reach a completed status after the process ends successfully. You also use events to monitor and troubleshoot issues that might occur during the process.
During the publication or the subscription process,
Cloud Integration Hub
communicates with
Informatica Intelligent Cloud Services
, going through the following stages:
When a cloud application publishes a data set, the
Cloud Integration Hub
server triggers the Data Integration task that is defined for the publication through an
Informatica Intelligent Cloud Services
REST API.
For cloud publications, the target is defined using a
Cloud Integration Hub
cloud connector. The publication process uses the connector to write the data to
Cloud Integration Hub
.
If the topic to which the data is published has subscribers,
Cloud Integration Hub
triggers the subscription workflows to consume the data.
For cloud subscriptions, the source is defined using a
Cloud Integration Hub
cloud connector. The subscription process uses the connector to read data from