ReplayDIRECTOR™ for Java EE is built specifically to handle Java enterprise applications. With complex and distributed IT environments, replicating and resolving application issues has become extremely challenging, and resulted in great amounts of wasted time. In addition, the world today is highly outsourced, with globally dispersed teams, leading to communication and application environment disparity issues between the different teams, be they development, QA or customer support.

Replay can eliminate up to 80% of the time required to fix bugs in your product. As all developers and QA teams know, consistently reproducing a problem is often their most challenging task. The time spent reproducing issues is unpredictable and can have great negative impact on quality, and to your schedule. Replay gives your schedule predictability, and gives you peace of mind.

The ReplayDIRECTOR™ recording will reproduce the exact state of an application and its environment. This allows developers and application support teams to identify the root cause of an issue quickly, and easily. To leverage this value, QA teams as well as customer support organizations can also attach recordings of application issues to their bug reports. Using a standard debugger, the replay of the application allows the user to view actual code that they can step through and identify the root cause of the issue. This is much more powerful than a screen capture, or parsing through a log file.

ReplayDIRECTOR™ replicates the application and environment allowing any team member to reproduce an issue, outside the original IT environment. As a result, an outsourced and global organization can leverage the recordings to communicate issues across teams  between QA and development or customers, operations and support teams. As today's companies take advantage of IT manpower around the world, the value of instantly communicating issues across regions and time-zones has a direct savings impact to their bottom line.

Developers: Increase productivity by removing wasteful, iterative steps Replay source code from any point in the business process Always be able to recreate bugs from any environment Leverage existing debugging and analysis tools that you are already familiar with

QA teams: Minimize documentation, and improve communication with development teams Find a bug once, and all of the data required for exact reproduction of the issue will be recorded. Attach the recording to your bug report, and avoid incomplete documentation issues

Customer / Application Support teams: Compress Mean Time To Resolution (MTTR) Production issues can be recorded and easily replicated by globally distributed teams outside complex and expensive production environments

ReplayDIRECTOR™ is a recording technology that captures each interaction with an application; the replay of a recording actually executes the interaction, causing application code to execute on the server and behave in exactly the same way as it did originally. This means that root cause analysis can be completed quickly and precisely using any standard tools such as a debugger, profiler, or any other analysis tool.

Here's a short list of what Replay reproduces:

1. JSP and Servlet code execution
2. Database transactions, with no database required during Replay
3. Hibernate, JPA, NIO, JMS, and most others APIs
4. Multi-thread context switches
5. Asynchronous file IO, network IO, and callbacks
6. Application Exceptions