, 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 the
B2B Data Exchange
server receives a file that contains documents to process, it generates an event associated with the file. This initial event is a file-level event. It is the root event for the file and is the parent event for all other events that the
B2B Data Exchange
server generates during the course of processing the documents in the file. The workflow that processes the document can generate child events of the file-level event during document processing.
When an application that runs a publication pre-process publishes data or files to the publication repository, the
B2B Data Exchange
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
B2B Data Exchange
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
B2B Data Exchange
server generates another Publication event for the publication process.
If a file publication publishes more than one file,
B2B Data Exchange
creates a File event for each file that it picks up.
B2B Data Exchange
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
B2B Data Exchange
server generates during processing. After the published data is ready for subscribers, the
B2B Data Exchange
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.
You can view parent events and child events for system events, user events, and monitor events. To track a set of events, you can create an event monitor and set up the rules for the events to be included in the monitor. You can create multiple event monitors to track events for different profiles or to track different types of events. You can configure the monitor to notify you of changes to the events that you track.
You can view all events that the
B2B Data Exchange
server generated since the last archive. To keep the volume of events displayed in the Operation Console at a manageable level, archive the events regularly. If you archive events with the
B2B Data Exchange
accelerator for Informatica Data Archive from the
B2B Data Exchange
repository to the history database, you can view the archived events in the Operation Console.