Browse Prior Art Database

Build Event Transaction Manager using Message Broker and Database

IP.com Disclosure Number: IPCOM000237345D
Publication Date: 2014-Jun-13
Document File: 6 page(s) / 134K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to build the Event Transaction Manager on any middle-ware component, based upon the Staged Event Drive Architecture (SEDA). It delivers a framework of components that are required to set up an Enterprise Application Integration message handling platform step-by-step.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 33% of the total text.

Page 01 of 6

Build Event Transaction Manager using Message Broker and Database

End-to-end event transactions may involve integration among various legacy systems using Staged Event Drive Architecture (SEDA) and Service Oriented Architecture (SOA)/Enterprise Service Bus (ESB) Architecture Patterns. This transaction may be a long run integration process in various stages, which may have exception errors. Traditional monitoring tools can monitor at the system level, but not the application itself with business transaction rules. The event transaction manager can monitor an end-to-end transaction with business transformation rules, such as an end-to-end transaction failed with an integration of a Customer Relationship Management (CRM) system, and the system can make a decision about what to do next. The event transaction manager can also use a timestamp to capture performance information through the end-to-end transactions.

The novel method builds the Event Transaction Manager on any middle-ware components and is based upon the SEDA. It delivers a framework of components that are required to set up an Enterprise Application Integration (EAI) message handling platform step-by-step. Components include a data model deployed in database and message flows for deployment to a Message Broker. The Event Message Transaction Process is a lightweight workflow manager, managing the status and storage of Enterprise Transactions with various application integrations such as CRM, Enterprise Resource Planning (ERP), Human Resources (HR), etc. The Event Transaction Manager can capture entire transformation performance data as well as exceptional handling.

Figure 1: Event Transaction Manager Components

Event Transaction Manager Process Macro Design

The Event Transaction Manager is a lightweight workflow manager managing the status and state of Enterprise Application Integration for Exchange to Exchange (E2E) transaction processes. This may appear to be a substantial effort; however, most state machines are actually rather simple.

Figure 2: Event Transaction Manager

1


Page 02 of 6

The Event Transaction Manager Process is composed of the following key elements:


 Transaction Manager Repository Service Node: The Transaction manager Node determines which transaction is associated with a particular event. It also determines state by evaluating the status of events arriving in the Transaction Input Queue.


 Exception Handling Service Processing Node: A particular state may have an error status. If this is the case, the error-processing node determines the appropriate action for the state and transaction type. This could be responding via email, text message to mobile phone, or performing some other task, such as compensating transactions.


 Client Acknowledgement Service Node: The notification node handles the disbursement of notifications based on transaction type and error/success status.


 Transaction Database:The transaction database support database schema...