Cloud Integration Hub

Back Next

Creating a subscription that triggers a file ingestion task

Use the Navigator to create subscriptions that trigger a file ingestion task to retrieve the files from a specific topic in the

file store publication repository.

The following conditions must exist before you create a subscription:

An application or applications that consume files must exist. You can either use existing applications, or create and save new applications.

A file store topic from which to consume files must exist. You can either use an existing topic, or create and save a new topic.

A subscription file ingestion task must exist.

On the Navigator, click

New

Subscription

The

New Subscription

page appears.

Enter the subscription name. Optionally, enter a description for the subscription.

Select the subscription mode. Choose one of the following options:

Enable

. The subscription runs according to the schedule that you define in the

Schedule

page. You can also run the subscription manually from Cloud Integration Hub.

Pause

. The subscription does not run according to a schedule or by an external API. You can only run the subscription manually from Cloud Integration Hub to consume the delayed events.

Disable

. The subscription does not run according to a schedule or by an external API. You cannot run a disabled subscription manually from Cloud Integration Hub. If the related publication runs successfully, the disabled subscription doesn't create a delayed event. You cannot consume the published data when the subscription is in disabled mode.

Select

Consume files with a file ingestion task

Select the application that subscribes to the files.

Select the topic that stores files in a file store from which the application consumes the files and then click

Add Topic

Select the file ingestion task that defines the subscription mapping.

Select the method and the frequency of file consumption.

When published data is ready: Runs the subscription immediately after the published files are ready
Manually or by an external trigger: No schedule. You can use the following methods to run the subscription:
Run manually from the
Cloud Integration Hub
explorer.
Run by an API. Call a REST API that starts the subscription.

If a file subscription uses this scheduling option and publishes multiple files, all the files must be present in the source location when the subscription starts.
By schedule: Runs the subscription according to the defined schedule. Select one of the following options:
Every n minutes. Runs the subscription in intervals of up to 60 minutes. You select the number of minutes from the list.
Hourly. Runs the subscription in intervals of up to 24 hours. You select the number of hours from the list.
Daily. Runs the subscription at the same hour every day.
Weekly. Runs the subscription every week on one or more days at the same hour. Select the check boxes of the days of the week that the subscription runs on. For example, select Saturday and Sunday to schedule the subscription to run on weekends.
Monthly. Runs the subscription every month on a specific date or a specific day at the same hour.

For minutes and hourly intervals, you can define a period of the day when the subscription runs. For example, schedule the subscription to run during nighttime hours.

Select a time zone for the schedule. The schedule runs the subscription in the selected time zone. You can change the default time zone in the user profile.

Define the delivery intervals in the
Repeat running
area.
Data to Consume: If a subscription runs manually or by an external trigger, or runs by a schedule, multiple files from the same publication might be available for consumption at the scheduled time, or at the time the subscription is triggered. Select one of the following options:
All available publications
. Consumes data or files from all available publications.
Latest publication only
. Consumes data or files from only the latest publication.