Method, system, and program product for transaction management in a distributed content management application
View Patent ↗Managing a content management system. The content management system is one that is configured and controlled to establish a connection between a client and a library server, generate a transaction identifier and insert, a record for the transaction in a tracking table associated with the library server, pass transaction data from the client to a resource manager, process the transaction at the resource manager and record transaction data in a tracking table associated with the resource manager. The resource manager returns transaction success/failure data to the client, compares activity recorded in the tracking tables, and takes corrective action based upon the activity comparison.
1. A method of managing a content management system, said content management system being configured and controlled to begin a transaction and create an item at a client, establish a connection between the client and a library server, generate a transaction identifier and insert a record for the transaction in a tracking table associated with the library server, pass transaction data from the client to a resource manager, process the transaction at the resource manager and record transaction data in a tracking table associated with the resource manager, return transaction success/failure data to the client, compare activity recorded in the tracking tables, and take corrective action based upon the activity comparison.
2. The method of claim 1 wherein an object and its corresponding resource manager tracking table record have no corresponding library server item, said method further comprising rolling back the resource manager store, deleting both the object and the resource manager tracking table record.
3. A method of managing a content management system, said content management system being configured and controlled to establish a connection between the client and a library server, generate a transaction identifier and check out an item, insert a record for the transaction in a tracking table associated with the library server, pass transaction data from the client to a resource manager, process the transaction at the resource manager, transfer the requested item to the client, processing the requested item at the client and returning the item to the resource manager, record transaction data in a tracking table associated with the resource manager, and return transaction success/failure data to the client, compare activity recorded in the tracking tables, and take corrective action based upon the activity comparison.
4. The method of claim 3 wherein the processing of the requested item is not committed to the resource server, comprising rolling-back resource manager entries.
5. The method of claim 3 wherein processing of the requested item is committed to the resource server but before resource manager records are updated wherein library server records have been updated and committed, the requested item has been replaced at the resource server, but the resource manager tracking table shows the replace is in progress, further leaving updated LS meta data as is, and deleting the resource tracking table records.
6. A content management system, said content management system being configured and controlled to begin a transaction and create an item at a client, establish a connection between the client and a library server, generate a transaction identifier and insert a record for the transaction in a tracking table associated with the library server, pass transaction data from the client to a resource manager, process the transaction at the resource manager and record transaction data in a tracking table associated with the resource manager, and return transaction success/failure data to the client, compare activity recorded in the tracking tables, and take corrective action based upon the activity comparison.
7. The content management system of claim 6 wherein an object and its corresponding resource manager tracking table record have no corresponding library server item, said method further comprising rolling back the resource manager store, deleting both the object and the resource manager tracking table record.
8. A content management system, said content management system being configured and controlled to establish a connection between the client and a library server, generate a transaction identifier and check out an item, insert a record for the transaction in a tracking table associated with the library server, pass transaction data from the client to a resource manager, process the transaction at the resource manager, transfer the requested item to the client, processing the requested item at the client and returning the item to the resource manager, record transaction data in a tracking table associated with the resource manager, and return transaction success/failure data to the client, compare activity recorded in the tracking tables, and take corrective action based upon the activity comparison.
9. The content management system of claim 8 wherein the processing of the requested item is not committed to the resource server, comprising rolling-back resource manager entries.
10. The content management system of claim 8 wherein processing of the requested item is committed to the resource server but before resource manager records are updated wherein library server records have been updated and committed, the requested item has been replaced at the resource server, but the resource manager tracking table shows the replace is in progress, further leaving updated LS meta data as is, and deleting the resource tracking table records.
11. A program product comprising a media having computer readable code for of managing a content management system, said content management system being configured and controlled to begin a transaction and create an item at a client, establish a connection between the client and a library server, generate a transaction identifier and insert a record for the transaction in a tracking table associated with the library server, pass transaction data from the client to a resource manager, process the transaction at the resource manager and record transaction data in a tracking table associated with the resource manager, and return transaction success/failure data to the client, compare activity recorded in the tracking tables, and take corrective action based upon the activity comparison.
12. The program product of claim 11 wherein an object and its corresponding resource manager tracking table record have no corresponding library server item, said method further comprising rolling back the resource manager store, deleting both the object and the resource manager tracking table record.
13. A program product comprising a media having computer readable code for of managing a content management system, said content management system being configured and controlled to establish a connection between the client and a library server, generate a transaction identifier and check out an item, insert a record for the transaction in a tracking table associated with the library server, pass transaction data from the client to a resource manager, process the transaction at the resource manager, transfer the requested item to the client, processing the requested item at the client and returning the item to the resource manager, record transaction data in a tracking table associated with the resource manager, and return transaction success/failure data to the client, compare activity recorded in the tracking tables, and take corrective action based upon the activity comparison.
14. The program product of claim 13 wherein the processing of the requested item is not committed to the resource server, comprising rolling-back resource manager entries.
15. The program product of claim 13 wherein processing of the requested item is committed to the resource server but before resource manager records are updated wherein library server records have been updated and committed, the requested item has been replaced at the resource server, but the resource manager tracking table shows the replace is in progress, further leaving updated LS meta data as is, and deleting the resource tracking table records.