, and it changes the status of the events as they go through the transformation process.
When an application triggers a publication, if the triggered publication has a pre-process, the publication event also tracks the pre-process. When a subscription triggers a post-process, the subscription event also tracks the post-process.
When an application that runs a publication pre-process publishes data or files to the publication repository, the
Data Integration Hub
server assigns an event to the publication as follows:
If the pre-process passes the Publication event ID to the publication process, the publication uses the same event, and the
Data Integration Hub
server does not generate an additional Publication event for the publication process.
If the pre-process does not pass the event ID to the publication process, the
Data Integration Hub
server generates another Publication event for the publication process.
If a file publication publishes more than one file,
Data Integration Hub
creates a File event for each file that it picks up.
Data Integration Hub
creates a Publication event after all the files are picked up.
The Publication event is the root event and the parent event for all of the subscription events that the
Data Integration Hub
server generates during processing. After the published data is ready for subscribers, the
Data Integration Hub
server generates a Subscription child event for each subscriber that needs to consume the published data. The Publication event contains aggregated status information for all Subscription child events.
You monitor and perform actions on events in the Operation Console. You can view all events on the Event List page. You can perform a basic or advanced search for events, and drill down to a specific event to view event details.
By default, the Event List page displays root events: Publication, File, Aggregated Subscription, and Compound Subscription. After a publication is ready for subscribers, you can drill down to the associated Subscription child events of the publication.
You can
create rules that monitor publication and subscription events, and perform actions on events that are in a defined status.
For example, you can create rules to perform the following tasks:
Disable publications that have events with an Error status.
Invoke a PowerCenter workflow when a publication event is in an Error status.
Send an email to the
Data Integration Hub
administrator when a subscription event is in a Critical status.
Discard events that are in the non-final status or statuses to which the rule applies.