Implementation of a User-Controlled Transactional Resource

• US 20100218185A1
• Filed: 02/25/2009
• Published: 08/26/2010
• Est. Priority Date: 02/25/2009
• Status: Abandoned Application

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Ralev, Vladimir Angelov
• Application Number:
  US12/392,829
• Publication Number:
  US 20100218185A1
• Time in Patent Office: Days
• US Class Current: 718/100
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06Q 20/389 Keeping log of transactions for guaranteeing non-repudiation of a transaction
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/425 using two different networks, one for transaction and one for security confirmation

Abstract

In one embodiment, a mechanism for implementation of a user as a transactional resource in a telecommunications platform is disclosed. In one embodiment, a method includes initiating a transaction as part of a transactional application in a transaction processing architecture, performing one or more transaction operations as part of the transaction on one or more transactional resources of the transaction processing architecture, contacting a user of the transactional application as one of the transaction operations performed on a user-controlled transactional resource, and storing a result of contacting the user in at least one of the user-controlled transactional resource or a transaction manager overseeing the transaction.

Claims

1. A computer-implemented method, comprising:

initiating a transaction as part of a transactional application in a transaction processing architecture;

performing one or more transaction operations as part of the transaction on one or more transactional resources of the transaction processing architecture;

contacting a user of the transactional application as one of the transaction operations performed on a user-controlled transactional resource; and

storing a result of contacting the user in at least one of the user-controlled transactional resource or a transaction manager overseeing the transaction.

2. The method of claim 1, wherein a result of contacting the user includes at least one of a confirmation of the transaction, an approval of the transaction, a disapproval of the transaction, and no answer by the user.

3. The method of claim 2, wherein if the user-controlled transaction resource does indicate at least one of a user confirmation or approval, indicating by the user-controlled transactional resource a readiness to commit the transaction when the transaction ends.

4. The method of claim 3, wherein if the user-controlled transaction resource does not indicate at least one of a user confirmation or approval, rolling back the transaction when the transaction ends.

5. The method of claim 1, further comprising notifying the user of the overall result of the transaction including results of one or more other transactional resource operations.

6. The method of claim 1, wherein contacting the user may include utilizing at least one of a telephone, an email, a text message, an SMS message, and a USSD message.

7. The method of claim 1, wherein the transaction processing architecture is implemented as a JAVA transaction service (JTS) supporting a JAVA Transaction API (JTA).

8. The method of claim 7, wherein the user-controlled transactional resource and a resource manager associated with the user-controller transaction resource implement a XAResource interface to communicate.

9. A system, comprising:

a memory;

a processor communicably coupled to the memory; and

a transaction processing architecture that utilizes resources of the processor and the memory, the transaction processing architecture operable to;

initiate a transaction as part of a transactional application;

perform one or more transaction operations on one or more transactional resources as part of the transaction;

contact a user of the transactional application as one of the transaction operations performed on a user-controlled transactional; and

store a result of contacting the user in at least one of the user-controlled transactional resource or a transaction manager overseeing the transaction.

10. The system of claim 9, wherein a result of contacting the user includes at least one of a confirmation of the transaction, an approval of the transaction, a disapproval of the transaction, and no answer by the user.

11. The system of claim 10, wherein:

if the user-controlled transaction resource does indicate at least one of a user confirmation or approval, indicating by the user-controlled transactional resource a readiness to commit the transaction when the transaction ends; and

otherwise if the user-controlled transaction resource does not indicate at least one of a user confirmation or approval, rolling back the transaction when the transaction ends.

12. The system of claim 9, wherein the transaction processing architecture further operable to notify the user of the overall result of the transaction including results of one or more other transactional resource operations.

13. The system of claim 9, wherein contacting the user may include utilizing at least one of a telephone, an email, a text message, an SMS message, and a USSD message.

14. The system of claim 9, wherein the transaction processing architecture is implemented as a JAVA transaction service (JTS) supporting a JAVA Transaction API (JTA).

15. The system of claim 9, wherein the user-controlled transactional resource and a resource manager associated with the user-controller transaction resource implement a XAResource interface to communicate.

16. An article of manufacture comprising a machine-readable storage medium including data that, when accessed by a machine, cause the machine to perform operations comprising:

initiating a transaction as part of a transactional application in a transaction processing architecture;

performing one or more transaction operations as part of the transaction on one or more transactional resources of the transaction processing architecture;

contacting a user of the transactional application as one of the transaction operations performed on a user-controlled transactional resource; and

storing a result of contacting the user in at least one of the user-controlled transactional resource or a transaction manager overseeing the transaction.

17. The article of manufacture of claim 16, wherein a result of contacting the user includes at least one of a confirmation of the transaction, an approval of the transaction, a disapproval of the transaction, and no answer by the user.

18. The article of manufacture of claim 17, wherein the data, when accessed by the machine, causes the machine to perform further operations comprising:

determining whether the user-controlled transactional resource indicates at least one of a user confirmation or approval; and

if the user-controlled transaction resource does indicate at least one of a user confirmation or approval, indicating by the user-controlled transactional resource a readiness to commit the transaction when the transaction ends; and

if the user-controlled transaction resource does not indicate at least one of a user confirmation or approval, rolling back the transaction when the transaction ends.

19. The article of manufacture of claim 16, wherein contacting the user may include utilizing at least one of a telephone, an email, a text message, an SMS message, and a USSD message.

20. The article of manufacture of claim 16, wherein the transaction processing architecture is implemented as a JAVA transaction service (JTS) supporting a JAVA Transaction API (JTA), and the user-controlled transactional resource and a resource manager associated with the user-controller transaction resource implement a XAResource interface to communicate.