Browse Prior Art Database

On-line, Real-time, Transaction Processor in Lotus Notes

IP.com Disclosure Number: IPCOM000020793D
Original Publication Date: 2003-Dec-15
Included in the Prior Art Database: 2003-Dec-15
Document File: 2 page(s) / 11K

Publishing Venue

IBM

Abstract

Disclosed is a functional improvement to the existing messaging/collaborating tool such as Lotus Notes*. It is desired that a sort of an OLTP (on-line, real-time, transaction processing) engine be included in Lotus Notes. If the application system is primarily characterized as an OLTP system then Lotus Notes according to this invention immediately transmits the transaction record to the next node, instead of waiting for the scheduled replication to occur. Otherwise, Lotus Notes behaves in its (default) usual processing mode, which is via replication.

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

Page 1 of 2

On-line, Real-time, Transaction Processor in Lotus Notes

Disclosed is a functional improvement to the existing messaging/collaborating tool such as Lotus Notes*.

It is desired that a sort of an OLTP (on-line, real-time, transaction processing) engine be included in Lotus Notes. If the application system is primarily characterized as an OLTP system then Lotus Notes according to this invention immediately transmits the transaction record to the next node, instead of waiting for the scheduled replication to occur. Otherwise, Lotus Notes behaves in its (default) usual processing mode, which is via replication.

More specifically, depending on the nature of the application, Lotus Notes forwards "transactions" from one node to another either in a default way (replication) or as an on-line, real-time transaction. This can be parameterized (e.g. parameter APPTYPE), where a certain value indicates that Lotus Notes should behave as an OLTP processor.

In operation, when node A of a Lotus Notes system receives a transaction from a certain Requestor, node A processes the "transactions" as appropriate, and then forwards this transaction to node B for further processing (simple workflow). The following steps are performed by node A:

(a) Receives the Transaction Request (TREQ) from Requestor.
(b) Processes the transaction
(c) Finishes processing and prepares to send the transaction to node B - looks at value of APPTYPE:

(1) if APPTYPE indicates real-time, node A immediately forwards the transaction to node B through the communication channel
(2) else, node A queues the "transaction" to the Lotus Notes replicator;
(3) if communication channel is down, Lotus Notes returns some abnormal condition return code to the calling application.

Every finantial (e.g. banking) transaction involves some sort of workflow, no matter how simple it is...