The trouble-shooter for your processes

An understanding of weaknesses and potential for improvement is what separates high performers from less successful companies. Classic error analysis tools often have significant problems dealing with errors in the interfaces between different applications. Beyond this, the incremental tracing of errors with the help of a debugger during production is not desirable as an interruption in the program flow is unwanted. If you don’t want to be left on your own when searching for errors at this stage then you need a strong partner – the E2E Analyzer.

The E2E Analyzer has been specially designed to make quality assurance across multiple systems as transparent as possible. The tool supports you in the better understanding of your processes and shows you all the relevant information in an uncomplicated and model-based way.

Debugger – vs. Analyzer

In the introduction the problems and limitations of traditional debuggers in production were explained. But what is the difference between the Analyzer and a debugger and how can individual processes and program steps be analysed and traced during production? As opposed to a debugger, E2E BRIDGE writes so-called trace-files which can be switched on and off dynamically and contain the process steps and the object data. The writing of these files is asynchronous and occurs in a single thread so that the actual performance of the service is not affected. A developer can thus also analyse processes and services with all their runtime information, even if their execution occurred in the past.

Core functions of the Analyzer:

Model based cause analysis – the definitive guide to faultless operations

The complete model based, static and dynamic analysis of errors is unique. The behaviour of all system components involved is depicted simply and transparently. The Analyzer does not limit itself to the display of the complete data flow but shows all the relevant status information and contents of the data objects and depicts these clearly in a model context. Detailed profiling information shows you, at all times, where system performance bottlenecks are occurring.

Automated test case creation – test before problems can occur

In order to check whether every process and interface is functioning correctly the Analyzer creates test case templates automatically. The data for these test cases can be collected automatically from the production operation logs. This is particularly advantageous with upgrades or migrations. Additionally, the data can be easily condensed into scenarios for regression testing.

Combined analysis and control – find errors immediately

When a problem occurs, single transactions can be checked by the Analyzer. Errors can be localized and rectified within the shortest of timeframes. Static information about individual components can also be gained through localization. This way you have an overview, available at any time, of which points require modernization.