The OpcAnalyzerRedirector simplifies the use of the OPC Foundation’s OpcAnalyzer tool.
The server access can be analyzed without any changes in the client. This is especially important when the client to be analyzed has the OPC server ProgID hard coded and the source code is not available.
It is also convenient when the OpcAnalyzer is used in combination with the OPC Compliance Test Tool to get more detailed information in case of errors. In CTT the ProgID cannot be changed without having to specify the complete test configuration. With the OpcAnalyzerRedirector the server ProgID doesn’t need to be changed.

The OpcAnalyzerRedirector modifies the server registration. After redirection the test server access goes into the OpcAnalyzer.
The registration of  OpcTestLab.OpcAnalyzer.1  is changed to the ProgID of the server to be tested. The ProgID of the server to be tested is modified with the prefix  _ARD_
E.g.: after redirection the server Advosol.SimDAServer.1 is directly accessible as _ARD_Advosol.SimDAServer.1while Advosol.SimDAServer.1 connects to the OpcAnalyzer.
The OpcAnalyzer needs to be configured to use the modified name (e.g. _ARD_Advosol.SimDAServer.1) as the test server.

.NET applications can access OPC AE server through a set of conveniant classes and methods. The EventView control handles a wide range of OPC Alarms&Events viewing requirements. OPC Alarms&Events .NET clients can be created without writing code and without knowledge of the OCP AE specification.