COM Proxy › Preparing for Execution › Trace Log and Configuration File Locations

Trace Log and Configuration File Locations

By design, CA Gen COM Proxies operate in several configurations. They can be consumed by:

• a standalone COM aware application through a call to CoInitialize
• an IIS web application with the applicable COM Proxy DLL having been registered with the system registry through a call to "regsvr32"
• as a Component Services application where the COM Proxy DLL is registered during the Component Services management process

The name of the consuming application and the user ID that is executing the consuming application will vary depending upon how a given COM Proxy is configured and under which component the COM Proxy is executed.

As COM Proxy DLLs are COM objects, the typical configuration approach is to register the DLLs into the system registry. This can be done either by calling regsvr32 directly or by configuring the COM Proxy using Windows Component Services. Windows Component Services offer a myriad of configuration options not available to regsvr32. The trace log file name and its location are determined by the way a Proxy is configured and executed.