Cloud Integration Hub > Subscriptions > Subscription processes
  

Subscription processes

The subscription process depends on the subscription type.

Subscription process for subscriptions that trigger Data Integration tasks

When a subscription triggers an Data Integration task, the subscription process includes retrieving the required data from the Cloud Integration Hub relational publication repository, running the subscription task, and writing the data to one or more subscriber targets. Cloud Integration Hub keeps the data in the publication repository until the retention period of the topic expires.
The subscription process includes the following stages:
  1. 1When the publication is ready for subscribers, the Cloud Integration Hub server triggers the Data Integration task that is defined for the subscription through an Informatica Intelligent Cloud Services REST API.
  2. 2The subscription process uses the Cloud Integration Hub cloud connector to read data from Cloud Integration Hub.
  3. 3The Data Integration task reads the data from Cloud Integration Hub and then writes the data to the subscribing application.
  4. 4The Cloud Integration Hub server changes the status of the subscription event to complete.

Subscription process for subscriptions that trigger file ingestion tasks

When a subscription triggers a file ingestion task, the subscription process includes running the subscription task and writing the files to a subscriber target. Cloud Integration Hub keeps the files in the file store publication repository until the retention period of the topic expires.
The subscription process includes the following stages:
  1. 1When the publication is ready for subscribers, the Cloud Integration Hub server triggers the file ingestion task that is defined for the subscription.
  2. 2The file ingestion task reads the files from the file store publication repository and then writes the files as-is to the target.
  3. 3The Cloud Integration Hub server changes the status of the subscription event to complete.

Subscription process for subscriptions that consume data with an API

When a subscription consumes data with an API, you run the Consume Data API in order to consume the data. The API retrieves the data from the topic in the relational publication repository and writes the data to the subscribing application.
When you create or edit a subscription that consumes data with an API, you can define a notification URL. Cloud Integration Hub sends notifications to this URL when data is ready to consume. Cloud Integration Hub must be able to access the notification URL.
The subscription process includes the following stages:
  1. 1The user triggers the Consume Data API.
  2. 2The Consume Data API runs the subscription, retrieves the data from the topic that is defined in the subscription, and writes the data to the subscribing application.
If the subscription process fails, you can attempt to consume the published data by reprocessing the subscription Error event with the Consume Data REST API.
You can reconsume data that had previously been processed by triggering the subscription Completed event with the Consume Data REST API.