IBM Performance Management

About the configdc command

You can use the command-line configuration tool of the .NET Data Collector to perform the configuration tasks, such as registering the data collector, validating and storing the connectivity information, enabling and disabling trace logging, and so on.

Run all commands that are mentioned in Table 1 from the install_dir\qe\bin directory, where install_dir is the installation directory of the Microsoft .NET agent.

Table 1. Data collector configuration commands
Command syntax	Description
`configdc registerdc [-f][all \|isapi \| isapi32 \| profiler \| httpmodule \| soap]`	Registers the .NET Data Collector. Run this command as an administrator. For more information, see Unregistering the data collector.
`configdc unregisterdc [all \| isapi \| profiler \| httpmodule \| soap]`	Unregisters the .NET Data Collector. Run this command as an administrator. For more information, see Unregistering the data collector.
`configdc ttserver -name name -port port`	Validates and sets the connectivity information of the Transaction Framework Extension, to which the agents send the tracking data.
`configdc logging [-level ERROR \| DEBUG \| WARNING \| INFO] [-size #] [-files #] [-tracing on\|off]`	Enables or disables trace logging for the .NET profiler. Sets the tracing attributes, for example, the level of trace detail, the maximum trace log file size, and the maximum number of trace log files. For valid values, see the dotNetDcConfig.properties file in the `install_dir`\qe\config directory. The settings for ASMX/WCF trace and operation logging are specified in the dotNetDcConfig.properties file.
`configdc enablemonitor [all \| adsi \| db2 \| ldap \| odbc \| oledb \| oracle \| sql \| http \| web] [-appdomain app domain list]`	Enables transaction monitoring of an ADO.NET interface. After installation, all the interfaces are enabled for monitoring. Use `all` to enable all the supported ADO.NET interfaces for transaction tracking. Use `http` to enable the interception of supporting APIs for HTTP monitoring. The -appdomain command restricts the ADO.NET interface monitoring to one or more .NET application domain names. If you specify more than one application domain name, separate each name with a semicolon (;). Use an asterisk (*) to enable all application domains. All the application domains are enabled during the installation. When an application domain list is assigned to an ADO.NET interface, the list remains unchanged in the configuration unless the application domain is set to another value. If an interface is enabled for monitoring without specifying an application domain, the last application domain value that you specified, or that was specified by default for the interface is used.
`configdc disablemonitor [all \| adsi \| db2 \| ldap \| odbc \| oledb \| oracle \| sql \| http \| web]`	Disables the transaction monitoring of an ADO.NET interface. Use `all` to disable all the supported ADO.NET interfaces for transaction tracking. Use `http` to intercept GetResponse (System.Net) and use `web` to disable the monitoring of HTTP requests.
`configdc getConfig [-active]`	Displays the properties file where you can add or remove the .NET API calls that the data collector intercepts. When the changes are complete, activate the updated file by using the `configdc activateconfig` command.
`configdc deepdivedc -tracelevel trace_level`	Configures the level of the diagnostics data to be collected by the data collector. For more information, see Configuring the collection of diagnostics data.
`configdc activateconfig`	Activates the updated configuration. For information about what to do after you activate the configuration, see Activating the configuration in the dotNetDcConfig.properties.inactive file.