Logging for the OPC DA Server is enabled through the Citect.ini parameter [Debug]CategoryFilter, which allows you to specify the messages that are sent to the tracelog.dat file.

In the case of an OPC DA server, the tracelog file will use a name based on the following:

tracelog.OpcServer.<OPC server name>.dat

[Debug]CategoryFilter will support the following category definitions:

• OpcDaServerComApi - enables traces on a COM API level. Only return status of each OPC DA COM API if logged
• OpcDaBrowse205 - enables tracing related to OPC DA v2.05 item browsing
• OpcDaBrowse300 - enables tracing related to OPC DA v3.00 item browsing
• OpcDaServer - enables extensive tracing of OPC DA server object APIs
• OpcDaGroups - enables extensive tracing of OPC DA group object APIs

A Kernel page is available that displays low-level diagnostic information about the runtime status of the OPC DA server. It can be accessed from the main kernel window by typing "Page Table OPCServerConnections".

The information available from this table includes the following:

• OPC Handle - the handle which the OPC server uses to reference a particular OPC connection. This handle can be cross referenced with log file entries.
• Index - the server object index, which is incremented each time a new client connects.
• #Groups - the number of groups created within the OPC server instance (including both active and inactive groups).
• #Items - the number of items created within OPC server instances (including all active/inactive items in all groups).
• #Reads - the number of reads that have been requested for items.
• #Writes - the number of writes that have been request for items.
• #Updates - the number of updates that have been received for subscribed items.

For more information on using the Kernel's Table window, see the topic Page Table in the Using The Kernel section of the main Citect SCADA help.