Database Reference
In-Depth Information
• Sender ID (Sender's BA TP code).
• Object reference and Object Context.
The Rules Engine mechanism is explained using the following examples:
Business Case
Message, Basics Events, and Business Application statuses
BE: Port call ETA has been changed for voyage <voyage id>
BA Sender: BA1
Case 1
BA Operation: UPDATE , a basic event pattern
Message Code: Schedule , a generic message
BE: Port call purpose has been changed for port call <port call id>
BA Sender: BA1
Case 2
BA Operation: UPDATE , a complex event pattern
Message Code: Schedule , a generic message
BE: Port call has been changed for cargo unit <cargo id>
BA Sender: BA1
Case 3
BA Operation: UPDATE , a basic event pattern
Message Code: Cargo , a generic message
Case 1 - basic event type
We can combine solutions for these use cases in two main groups, based on the event's
type:
• The execution of a simple event expression will be sufficient in this case
• Using this information, Rule Engine will select all TPs that are bounded to this
rule unconditionally and with no historical retrospective, such as DWH and cor-
porate portal
• The rule is simple; select the TPs bounded to this message and BE
Cases 2 and 3 - complex event type
• This is the same BE, but TP here is interested only in port calls for one or many
ports in the voyage.
• TP maintains its own application database messages received from BA-sender
(complete decoupling). In this case, an operation on the Rule Engine side should
Search WWH ::




Custom Search