Abstract:
A system, a method, and a medium for processing a spreadsheet to store the spreadsheet to a database are provided to process/store the spreadsheet to the database by automatically processing records of the spreadsheet and applying a conventional validation/business process logic. A request for processing the spreadsheet including a plurality of records to store the spreadsheet to the database is received(502). A configuration file related to the spreadsheet is generated by receiving more than one name of a business object related to the record of the spreadsheet, metadata for more than one column of the spreadsheet, and the name of a back-end business component related to the spreadsheet. The generated configuration file is accessed(508). A new business object is generated for each record of the spreadsheet, and is populated based on the records and the configuration file(514). Each new business object is transferred to a back-end business application(516).
Abstract:
PROBLEM TO BE SOLVED: To provide a device and a method for maintaining the integrity of data in a software environment. SOLUTION: According to the present device and method, individual software resources associated with a transaction are identified, and the processing of these resources is started. When the processing of these resources is finished, their associated APIs return messages indicating either that the software resource committed or could not commit and a reason why the software resource could not commit. Based on this reason, appropriate error resolution and recovery operations are performed, and the transaction is resubmitted only to those software resources which could not commit. The software resources which already committed have their states maintained. By this method, the roll back of committed software resources is avoided. COPYRIGHT: (C)2005,JPO&NCIPI
Abstract:
Generally speaking, systems, methods and media for processing a spreadsheet for storage in a database are disclosed. Embodiments may include a method for processing records of a spreadsheet by receiving a request to process a spreadsheet having a plurality of records for storage in a database. Embodiments may also include accessing a configuratio n file associated with the spreadsheet and, for each record of the spreadsheet, creating a new business object and populating the new business object based on the record and the configuration file associated with the spreadsheet. Embodiments may also include passing each new business obje ct to a back-end business component for processing. The configuration file may include a name of a business object associated with a record of the spreadsheet, metadata for one or more columns of the spreadsheet, and/or a name of a back-end business component associated with the spreadsheet.
Abstract:
An apparatus and method for maintaining integrity of data in a software environment are provided. The individual software resources associated with a transaction are identified and the processing of these resources is started. As the processing of these resources terminates, their associated APIs return messages indicating either that the software resource committed or was unable to commit and the reason why the software resource was unable to commit. Based on this reason, appropriate error resolution and recovery operations are performed and the transaction is resubmitted only to those software resources that were unable to commit. The software resources that already committed have their states maintained. In this way, roll back of committed software resources is avoided.
Abstract:
An apparatus and method for maintaining integrity of data in a software environment are provided. With the apparatus and method, the individual software resources associated with a transaction are identified and the processing of these resources is started. As the processing of these resources terminates, their associated APIs return messages indicating either that the software resource committed or was unable to commit and the reason why the software resource was unable to commit. Based on this reason, appropriate error resolution and recovery operations are performed and the transaction is resubmitted only to those software resources that were unable to commit. The software resources that already committed have their states maintained. In this way, roll back of committed software resources is avoided.