ReplayDIRECTOR for JavaEE functions like a DVR for enterprise Java applications – recording all inputs and events affecting your application server while it is running then providing the ability to replay exactly what happened - so any problem can be reproduced immediately without the need to replicate the environment they occurred in.

ReplayDIRECTOR for JavaEE ensures that the teams responsible for enterprise applications based on Java application servers can:

• Save money and increase efficiency by eliminating complex processes needed to reproduce defects
• Improve collaboration by easily sharing recordings between teams around the world
• Improve application quality by fixing hard to find or intermittent defects

ReplayDIRECTOR for JavaEE does not just replay screen captures of what the user saw, but actually executes source code in a virtual execution environment that completely eliminates the effort of recreating the specific environment and conditions a problem occurred in. With ReplayDIRECTOR there is no need to set up the database, reproduce the load, find the exact operating system, or any other time consuming and tedious setup tasks!

Every line of code that an application executes is determined by interactions with its environment. ReplayDIRECTOR captures all these interactions – file i/o, network input, interrupts, call-backs, multi-threaded timings, etc. – and then uses this data to run the application and reproduce the exact same sequence of program instructions. This means that every line of code that was executed when the application was recorded will be executed in the same way during replay. Elements such as the database, other servers and clients connected to the application will all be simulated by the virtual execution. The application will run in precisely the same way it did during the recording, and will have no ability to detect that it is being replayed, and not, in fact, running live.

ReplayDIRECTOR for JavaEE does not require your organization to change existing problem resolution processes or tools. Because your application is actually executing during replay, your existing debuggers, IDEs and other tools can be used to quickly isolate and resolve the defect, without impacting the normal workflow. A recording can be easily shared with other teams using existing defect tracking, test management or help desk tools using the same processes your teams are already using. And most importantly – there are no changes required to any source code.

ReplayDIRECTOR for JavaEE has been architected from the ground-up with high-performance in mind to ensure minimal application impact – even in production environments. With a very efficient method of data capture and small performance footprint, ReplayDIRECTOR can be “always on” so you don’t have to know a problem is about to occur in order to capture it. ReplayDIRECTOR does not work one way in development and another way in production. All users have access to the same powerful record/replay functionality.