With RFgen Transaction Management capabilities you can monitor the stream of transactions as they are processed, see the data being submitted, alter the data, if required, right from the Mobile Administrator Console without disrupting the user, manage successes and failures of transactions as they are processed and view statistical data on the execution times of the transactions against the back-end systems. This data can then be used to optimize the entire update process which typically results in sub-second response times.

The transaction management database used to store queued, successful and failed transactions can be any ODBC compliant database of the user’s choice. This allows RFgen to plug in to the user’s existing infrastructure without the need to add additional components to what the IT department already manages.

The option of having any number of queues allows administrators to separate different types of transactions into categories. This provides the option of having a multi-threaded approach to processing different types of data. For example, transactions that rely on data integrity such as the ability to move an item only after it has been received can flow through one queue while requests to print barcodes or transferring data to other sub-systems can flow through another. This approach gives new meaning to real-time processing.

RFgen Transaction Management has some integrated Extended Options that allow administrators to create trace logs for some or all of the ways RFgen writes or changes data in your environment. To comply with some regulations regarding traceability, RFgen offers both basic and extensive logging options and usage statistics for complete control over the whole data collection solution.

Do you pay per license fees for connections to your enterprise system? RFgen Transaction Management can push all the transactions from all the queues through one or more connections to the enterprise server, perhaps saving you from significant additional and unnecessary costs. The alternative would be to allow each queue to parallel process against the database using its own connection, in essence disabling the pooling capability. In this case you can achieve a greater throughput without having one transaction waiting for the completion of another - thus providing real-time enterprise update capabilities even though the transaction has been handed off to a background process.

If you have the need to make your system perform tasks without any user intervention at all, then the Processing Events option is what you are looking for. Under this configuration you can setup RFgen on a schedule to perform any task automatically. Examples might be to poll the Failed queue and send e-mails based on your criteria or check for files in a monitored folder and print bar codes as they are needed. With access to all the data, all the time, there is no limit to what RFgen can be made to do.