Abstract: A method is described for diagnosing errors within a production environment software platform that is arranged to process transaction messages and to store transaction history data related to processed transactions in a production database. The stored transaction history data comprises transaction objects that have been generated as the production environment software platform processes transaction messages. The method comprises detecting an error in a series of transaction messages processed by the production environment software platform, receiving the transaction history from the production database, the transaction history comprising a plurality of transaction objects, and configuring a development environment software platform to match the configuration of the production environment software platform at the start of the transaction history.

Abstract: A headlock lift including a base having a left column and a right column, with each column having a lower side and an upper side. A forward cross-spinning beam and a back cross-spinning beam both connect to the upper side of each column. A moveable gate having a topside, a bottom side, and a plurality of vertical poles fixably attachable to the top side and the bottom side, the moveable gate is slidably received over left and right pipes positioned parallel to the left and right columns. Two pulleys are fixed to the forward cross-spinning beam and two winches are fixed to the back cross-spinning beam. Two cables are continually disposed between the two winches and the two pulleys, with the cables each having a free operating-end attachable to the topside of the moveable gate and a captive-end attachable to a respective one of the winches.

Abstract: A method is described for diagnosing errors within a production environment software platform that is arranged to process transaction messages and to store transaction history data related to processed transactions in a production database. The stored transaction history data comprises transaction objects that have been generated as the production environment software platform processes transaction messages. The method comprises detecting an error in a series of transaction messages processed by the production environment software platform, receiving the transaction history from the production database, the transaction history comprising a plurality of transaction objects, and configuring a development environment software platform to match the configuration of the production environment software platform at the start of the transaction history.

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 configuration 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 object 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: A system and method for logging changes to a database table are disclosed. The system comprises an administration tool, table metadata, a history table, and a service engine. The administration tool provides an interface through which a DBA, database programmer, or other user can manage the table metadata and the history table, including the selection of columns within the table for which the system will track changes. In the preferred embodiment, the service engine is a middleware application that tracks changes for the selected columns. The service engine processes all user-requested database operations and adds operations to manage the history table before relaying the request operations to a DBMS. Alternatively or additionally, the service engine may be a wrapper to existing services that the database application provides.