Overview of components
This diagram shows an overview of the components involved in event publishing:
The client and the LN server
communicate through a middleware infrastructure consisting of the network and additional
technology such as a brokering solution. This infrastructure is enabled through the
Infor Technology Architecture. This allows the client to send the
PublishList
and PublishChanges
requests and to receive the resulting data or change
events.
The PublishList
is implemented in
LN through a process that is started in the
Business Object Layer.
For the PublishChanges
in LN, the implementation is delegated to the Synchronization
Server, which starts a process to detect events in the application data. The change
events are detected through auditing. When transactions are executed by user sessions or
other application processes, relevant changes are written to an audit trail. This is the
only overhead on the end user. An offline process picks up the transaction data that is
needed for the business object and in accordance with the specified selection and
filter. An event message is created representing the event and its data and that message
is published.
The PublishList
automatically stops if
the requested data set is processed. Regarding PublishChanges
, the publishing of events is a continuous process, because
new change events may always occur. It is stopped when the client sends an UnpublishChanges
request.