Administrator Guide

10.2.2
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2

Back Next

Events Overview

An event is a representation of a publication or a subscription instance, at a particular stage of the publication or subscription process. The

B2B Data Exchange

server generates events as it runs and processes publications and subscriptions, and it changes the status of the events as the publication or subscription process progresses. 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

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 the publication process. 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.

An event changes status as it is processed. The

B2B Data Exchange

server changes the status of an event based on a set of event statuses that you define in the Operation Console.

As each subscriber consumes the published data, the child event finishes processing. After all subscribers consume the published data, the

B2B Data Exchange

server updates the consumption status of the parent event for the publication

You can manage storage space in the

B2B Data Exchange

run-time repository by purging events that

B2B Data Exchange

generates when they are no longer needed.

Events