.NET Data Collector: Installation and Configuration Guide · 2016. 8. 8. · Internet Information...

IBM Tivoli Composite Application Manager for MicrosoftApplications: .NET Data Collector7.3.2 Fix Pack 4

Installation and Configuration Guide

SC27-5667-01

IBM

IBM Tivoli Composite Application Manager for MicrosoftApplications: .NET Data Collector7.3.2 Fix Pack 4

Installation and Configuration Guide

SC27-5667-01

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 21.

This edition applies to version 7.3.2.4 of IBM Tivoli Composite Application Manager for Microsoft Applications:.NET Data Collector (product number 5724-U17) and to all subsequent releases and modifications until otherwiseindicated in new editions.

© Copyright IBM Corporation 2012, 2016.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . v

Chapter 1. Overview of the .NET DataCollector . . . . . . . . . . . . . . 1New in this release . . . . . . . . . . . . 1Components of the .NET Data Collector . . . . . 1

Chapter 2. .NET Data Collectorinstallation . . . . . . . . . . . . . 3Requirements . . . . . . . . . . . . . . 3Prerequisites checking . . . . . . . . . . . 3Installing .NET Data Collector . . . . . . . . 3Permissions required for the .NET Data Collectorinstallation directory . . . . . . . . . . . . 4

Chapter 3. .NET Data Collectorconfiguration . . . . . . . . . . . . 7Configuring registration . . . . . . . . . . 7Configuring connection to the Transaction Collector . 8Enabling and disabling ADO.NET interfacesmonitoring . . . . . . . . . . . . . . . 8Activating the configuration . . . . . . . . . 9Modifying configuration settings of the .NET DataCollector. . . . . . . . . . . . . . . . 9

Modifying configuration settings in the GUI . . . 9Modifying configuration settings at the commandprompt . . . . . . . . . . . . . . . 10

Configuring logging for the .NET Data Collector . . 12Working with IBM Tivoli Composite ApplicationManager for SOA . . . . . . . . . . . . 12

Configuring the .NET Data Collector with IBMTivoli Composite Application Manager for SOA . 12

Verifying installation of the .NET Data Collector . . 13ADO Event Aggregation . . . . . . . . . . 16

Disabling ADO event aggregation . . . . . . 16

Chapter 4. Uninstalling the .NET DataCollector . . . . . . . . . . . . . . 17

Appendix. ITCAM for MicrosoftApplications documentation library . . 19Prerequisite publications . . . . . . . . . . 19Related publications . . . . . . . . . . . 20Tivoli Monitoring Community on ServiceManagement Connect . . . . . . . . . . . 20Other sources of documentation . . . . . . . 20

Notices . . . . . . . . . . . . . . 21Trademarks . . . . . . . . . . . . . . 23Terms and conditions for product documentation. . 23IBM Online Privacy Statement . . . . . . . . 24

Index . . . . . . . . . . . . . . . 25

© Copyright IBM Corp. 2012, 2016 iii

iv .NET Data Collector: Installation and Configuration Guide

Tables

1. .NET Data Collector - components required formonitoring scenarios . . . . . . . . . . 1

2. Permissions required for the .NET DataCollector installation directory . . . . . . 4

3. Names and descriptions of configurationparameters in the .NET Data Collector:Property Configuration window . . . . . 10

4. .NET Data Collector configuration commands 115. Verification steps for registration of .NET Data

Collector components . . . . . . . . . 14

© Copyright IBM Corp. 2012, 2016 v

vi .NET Data Collector: Installation and Configuration Guide

Chapter 1. Overview of the .NET Data Collector

IBM® Tivoli® Composite Application Manager for Microsoft Applications includes the .NET DataCollector that enables you to track the transactions that occur in the .NET Framework application and theInternet Information Services (IIS) web applications.

New in this releaseFor version 7.3.2.4 of the .NET Data Collector, the following enhancements have been made since version7.3.2, including the fix packs:v Changes related to system requirements. See the information about System requirements in the

Software product compatibility reports.v Enabled the end-point URL filtering feature.

Components of the .NET Data CollectorThe .NET Data Collector contains several components that are registered during the installation of the.NET Data Collector.

ProfilerThis component uses the .NET Common Language Runtime (CLR) profiler to provide thetransactions of ADO.NET database and directory service.

SOAP This component provides SOAP and WCF extensions to monitor ASP.NET web services and WCFrequests and responses.

ISAPI This component provides authentication timings in Internet Information Services (IIS) 6, IIS 7.x inclassic mode, and IIS 8 in classic mode.

HttpModuleThis component provides ASP.NET monitoring support and ASP.NET web forms linking support,and support to the ASP.NET MVC applications. It also provides authentication timings of IIS 7.xin integration mode, and IIS 8 in integration mode.

.NET Data Collector components required to monitor scenarios

The .NET Data Collector components that are required to monitor various scenarios are determined bythe systems that you want to monitor in your environment.

Table 1 contains the components of the .NET Data Collector that are required to monitor scenarios.

Table 1. .NET Data Collector - components required for monitoring scenarios

Domain tracking scenario .NET Data Collector component required

Tracking authentication timings of web applications inIIS 6, IIS 7.x in classic mode, and IIS 8 in classic mode

ISAPI and HttpModule

Tracking authentication timings of web applications inIIS 7.x in integration mode and in IIS 8 in integrationmode, and tracking basic, digest, and Windowsauthentication

HttpModule

Tracking transactions of ASP.NET web services by usingASPX

HttpModule, SOAP, and Profiler

Tracking SOAP transactions of APS.NET web services(synchronous or asynchronous)

SOAP, Profiler, and HttpModule

© Copyright IBM Corp. 2012, 2016 1

http://www-969.ibm.com/software/reports/compatibility/clarity/index.html

Table 1. .NET Data Collector - components required for monitoring scenarios (continued)

Domain tracking scenario .NET Data Collector component required

Tracking SOAP transactions of WCF web services SOAP, Profiler, and HttpModule

Tracking ADO.NET (synchronous or asynchronousdatabase calls) interfaces

Profiler and HttpModule (only profiler if ADO EventAggregation is disabled)

For more information about ADO Event Aggregation, see“ADO Event Aggregation” on page 16

Tracking Active Directory services (synchronous only)through LDAP & ADSI

Profile and HttpModule (only profiler if ADO EventAggregation is disabled)

Tracking HTTP request for ASP.NET web forms ISAPI, HttpModule, and Profiler

Tracking HTTP request for ASP.NET web forms by usingResponse.Redirect

HttpModule

Tracking .NET > IHS > WAS linking Http, SOAP, and Profiler

Tracking .NET > WAS linking HttpModule, SOAP, and Profiler

Tracking .NET > Websphere Message Broker (WMB) HttpModule, SOAP, Profiler, and ISAPI

Tracking SOAP failed transactions of WCF/ASP.NET webservices

HttpModule, SOAP, and Profiler

Tracking HTTP failed transactions of ASP.NET web pages HttpModule, ISAPI, and Profiler

Tracking MVC transaction HttpModule and Profiler

2 .NET Data Collector: Installation and Configuration Guide

Chapter 2. .NET Data Collector installation

Installation and configuration of the .NET Data Collector requires the use of the IBM Tivoli MonitoringInstallation and Setup Guide and the installation and configuration information specific to the .NET DataCollector.

RequirementsBefore installing and configuring the .NET Data Collector, make sure your environment meets therequirements for the IBM Tivoli Composite Application Manager for Microsoft Applications: .NET DataCollector.

For the most up-to-date information about system requirements, see the Software product compatibilityreports (http://www-969.ibm.com/software/reports/compatibility/clarity/index.html). Search for theITCAM for Microsoft Applications product.

Prerequisites checkingThe prerequisite checker utility verifies whether all the prerequisites that are required for the installationare met. The prerequisite checker creates a log file that contains a report of all the prerequisites checkswhen the prerequisite checker is run.

For the .NET Data Collector, the prerequisite checker verifies the following requirements:v Memoryv Diskv Operating systemsv .NET Framework versions

Additionally, the prerequisite checker verifies whether the user, who installs the agent, is a member of theAdministrators group.

For detailed information about installation prerequisites, see the Software product compatibility reports(http://www-969.ibm.com/software/reports/compatibility/clarity/index.html).

You can run the prerequisite checker in stand-alone mode or remotely. For more information about theprerequisite checker, see "Prerequisite Checking for IBM Tivoli Monitoring Agents" in the IBM TivoliMonitoring Installation and Setup Guide.

Installing .NET Data CollectorInstall the .NET Data Collector on the computer where you installed the applications that you want tomonitor. The .NET Data Collector does not support remote and silent installations.

Before you beginv Ensure that your system meets the requirements for IBM Tivoli Composite Application Manager for

Microsoft Applications: .NET Data Collector.For the most up-to-date information about system requirements, see the Software product compatibilityreports (http://www-969.ibm.com/software/reports/compatibility/clarity/index.html). Search for theITCAM for Microsoft Applications product.

v Use the ServiceModel Registration tool to ensure that all the WCF components are installed.







Procedure1. If you are installing the .NET Data Collector on an x86-32 processor or on an x86-64 processor,

launch the installation wizard by double-clicking the setup.exe file in the WINDOWS subdirectory onthe installation media.Use the IBM Tivoli Monitoring Base Agent DVD or a distributed agent product CD for Windowsoperating systems. Do not use the Data Files for z/OS® CD.

2. Click Next on the Welcome window.

Note: If you have another IBM Tivoli Monitoring component already installed on this computer,select Modify on the Welcome window. A message displays the items that you selected. Click OKand go to Step 5.

3. Read and accept the software license agreement.4. Browse to the CANDLE_HOME/TMAITM6 directory.5. On the Select Features window, expand the Tivoli Enterprise Monitoring Agents list.6. Select .NET Data Collector and click Next.7. Review the installation summary details. The summary provides information about what you want

to install and the location of installation. Click Next to start the installation.After the installation is complete, the Setup Type window opens that contains the following checkboxes:v Configure agents default connection to Tivoli Enterprise Monitoring Serverv Launch Manage Tivoli Monitoring Services for additional configuration options and to start Tivoli

Monitoring services

These check boxes are selected by default. You can clear the check boxes if you are installing only.NET Data Collector.

8. To configure the .NET Data Collector, click Next.9. To complete the installation, click Finish.

10. If you are updating an existing installation, on the Maintenance Complete window, click Finish.The .NET Data Collector is not displayed in the Manage Tivoli Enterprise Monitoring Serviceswindow.

What to do next

You must provide permissions for the .NET Data Collector installation directory. To know more about thepermissions, see “Permissions required for the .NET Data Collector installation directory”

Permissions required for the .NET Data Collector installation directoryBefore you use the .NET Data Collector to monitor the applications, you must provide appropriatepermissions for the .NET Data Collector installation directory.

Table 2. Permissions required for the .NET Data Collector installation directory

Applications Built-in account Required users Required access

IIS Applications ApplicationPoolIdentity User group andLocalMachine\IIS_IUSRS

v Read access to theCANDLE_HOME directory

v Read, Execute, and Writepermissions for the K4directory and itssubdirectories


Table 2. Permissions required for the .NET Data Collector installation directory (continued)

Applications Built-in account Required users Required access

LocalSystem v For IIS 7.x and IIS 8:

LocalMachine\IIS_IUSRS

v For IIS 6:

LocalMachine\IIS_WPG



Network Service v LocalMachine\NetworkService

v For IIS 7.x and IIS 8:


v For IIS 6:




Local Service v LocalMachine\LocalService

v For IIS 7.x and IIS 8:


v For IIS 6:




Built-in or Active Directoryor custom-created user

LocalMachine\username

or

DomainName\username



Desktop applications (all.NET-based applicationsinstalled and running afterthe .NET Data Collector isinstalled)

System LocalMachine\Users v Read access to theCANDLE_HOME directory


Network Service v LocalMachine\NetworkService

v LocalMachine\USRS



Local Service v LocalMachine\LocalService

v LocalMachine\USRS



Built-in or Active Directoryor custom-created user

LocalMachine\username

or

DomainName\username



Chapter 2. .NET Data Collector installation 5


Chapter 3. .NET Data Collector configuration

After you install the .NET Data Collector, you must configure the .NET Data Collector to monitor theapplications.

To configure the .NET Data Collector, you must complete the following steps:1. “Configuring registration”2. “Configuring connection to the Transaction Collector” on page 83. “Enabling and disabling ADO.NET interfaces monitoring” on page 84. “Activating the configuration” on page 9

For information about configuring the .NET Data Collector with IBM Tivoli Composite ApplicationManager for SOA, see “Working with IBM Tivoli Composite Application Manager for SOA” on page 12.

Configuring registrationAfter you complete the installation of the .NET Data Collector, you must configure the .NET DataCollector to monitor .NET transactions.

Before you begin

Ensure that you perform the following tasks:v Stop the IIS Server by running the following command:

iisreset /stop

v Stop all .NET applications.

About this task

When you configure the .NET Data Collector, all components of the .NET Data Collector that are requiredfor monitoring .NET transactions are registered automatically.

Procedure1. Perform one of the following steps:

a. To register the .NET Data Collector, go to the CANDLE_HOME/TMAITM6/K4/bin directory, and run thefollowing command:configdc registerdc [-f]

where -f overrides any existing .NET profiler without further prompts. If a profiler exists, and the-f option is not specified, the .NET Data Collector profiler is not configured.

b. To stop the .NET Data Collector from monitoring .NET transactions, go to theCANDLE_HOME/TMAITM6/K4/bin directory, and run the following command:configdc unregisterdc

2. To start the IIS Server, run the following command:iisreset /start

3. Restart all .NET applications.


What to do next

After you configure registration, you must configure connection to the Transaction Collector. For furtherinformation, see “Configuring connection to the Transaction Collector”

Configuring connection to the Transaction CollectorThe .NET Data Collector events are sent to the Transaction Collector. Therefore, you must configureconnection to the Transaction Collector after you install the .NET Data Collector.

About this task

The location of the Transaction Collector is automatically set in the configuration file during installation.If you are not prompted for the location of the Transaction Collector during installation of the .NET DataCollector, you might need to manually update the location.

Procedure

From the CANDLE_HOME\TMAITM6\K4\bin directory, run the following command:configdc ttserver -name [host name/ip address] -port [port number]

What to do nextv If configuration is complete, activate your configuration changes. See “Activating the configuration” on

page 9 for more information.v If you want to monitor ADO.NET interfaces to be monitored, see “Enabling and disabling ADO.NET

interfaces monitoring.”

Enabling and disabling ADO.NET interfaces monitoringChoose the ADO.NET client interfaces that you want the .NET Data Collector to monitor.

Before you begin

You might want to view the ADO.NET interfaces that are supported by the .NET Data Collector. Forinformation about supported ADO.NET interfaces, see the Functions of namespaces supported by the.NET Data Collector topic in the .NET Data Collector Reference.

About this task

By default, all supported ADO.NET interfaces are enabled for monitoring during installation of the .NETData Collector. To select the interfaces that must be monitored by the .NET Data Collector, enable ordisable monitoring for specific interfaces. If you disable monitoring of an interface, any associatedapplication domain filter is retained when the interface is enabled again.

Procedure1. To enable monitoring, from the CANDLE_HOME\TMAITM6\K4\bin directory, run the configdc

enableMonitor command:configdc enableMonitor all | adsi | db2 | ldap | odbc | oledb | oracle | sql| http | web[-appdomain appdomain filter list]

2. To disable monitoring, from the CANDLE_HOME\TMAITM6\K4\bin directory, run the configdcdisableMonitor command:configdc disableMonitor all | adsi | db2 | ldap | odbc | oledb | oracle | sql| http | web


For more information about using the configdc command, see “Modifying configuration settings ofthe .NET Data Collector.”For information about default configuration values for configuring the .NET Data Collector, see theConfiguration values of .NET Data Collector topic in the .NET Data Collector Reference.

What to do next

After you enable or disable the ADO.NET interfaces for monitoring, activate the configuration changes.See “Activating the configuration” for more information.

Activating the configurationActivate the updated configurations for the changes to take effect.

Procedure

To activate an inactive configuration:1. From the CANDLE_HOME\TMAITM6\K4\bin directory, run the configdc activateconfig command.2. Restart all .NET applications.

What to do next

If IIS transactions are monitored and the Transaction Collector connection configuration is updated,restart IIS to finish activating the configuration.

If ASP.NET web forms or WCF web services are monitored and the Transaction Collector connectionconfiguration is updated, complete one of the following steps:v Restart the process that hosts the web service.v Register the .NET Data Collector again by running the unregisterdc command, and then run the

configdc registerdc command.

Modifying configuration settings of the .NET Data CollectorYou can perform basic configuration tasks of the .NET Data Collector, such as registering the .NET DataCollector, validating and storing the connectivity information, enabling and disabling trace logging, andso on.

You can perform the configuration tasks in the following ways:v Modifying the settings in the graphical user interfacev Modifying the settings at the command prompt

Modifying configuration settings in the GUIYou can use the .NET Data Collector: Property Configuration window to modify the configurationsettings of the .NET Data Collector.

Procedure1. To open the .NET Data Collector: Property Configuration window, go to the CANDLE_HOME\TMAITM6\k4\

bin\PropertiesEditor directory, and double-click the KK4ConfigProperties.exe file.2. On the General tab, specify the settings that are related to the Transaction Server, ADO event

aggregation, integration with SOA agent, and logging and tracing.3. On the Advanced tab, specify the settings that are related to the Profiler configuration, ADO .NET

pseudonodes, log file garbage collection, and enabling or disabling monitoring for methods, classes,and namespaces.

Chapter 3. .NET Data Collector configuration 9

4. Click OK. The configuration settings that you specified are validated. Error messages are displayedfor the invalid values. The configuration is activated if all the configuration settings are valid. Thesettings are saved to the dotNetDcConfig.properties file.

Configuration parameters in the .NET Data Collector: Property ConfigurationwindowThe .NET Data Collector Property Configuration window contains the parameters to configure the .NETData Collector properties, such as Transaction server details, logging and tracing, enabling and disablingmonitoring for namespaces and methods.

Table 3 contains the descriptions of the configuration parameters in the .NET Data Collector PropertyConfiguration window.

Table 3. Names and descriptions of configuration parameters in the .NET Data Collector: Property Configurationwindow

Tab Configuration parameters for ... Description

General Transaction Server settings Configure values of port number, Transaction Collector hostname, and protocol.

ADO.NET Event Aggregation Enable or disable the ADO.NET event aggregation.

Integration with SOA agent Enable or disable the configuration of the .NET DataCollector with SOA agent.

General logging and tracing Enable or disable general logging and tracing.

SOAP logging and tracing Enables or disable SOAP logging and tracing.

Advanced Profiler configuration Configure the .NET Data Collector to send the data to theTransaction Collector.

ADO.NET Pseudonodes Enable or disable generation of ADO.NET Pseudonodes.

SOA feature of the .NET Data Collector Enable or disable SOA features of the .NET Data Collector.

General logging and tracing Configure general logging and tracing.

SOAP logging and tracing Configure SOAP logging and tracing.

Log File Garbage Collector Settings Enable or disable garbage collection, set the interval forgarbage collection, and so on.

Monitored APIs - Namespaces Enable or disable monitoring for namespaces.

Monitored APIs - Classes Enable or disable monitoring for classes.

Monitored APIs - ADSI Methods Enable or disable monitoring for ADSI methods.

Monitored APIs - LDAP Methods Enable or disable monitoring for LDAP methods.

Monitored APIs - DbDataAdapterMethods

Enable or disable monitoring for DbDataAdapter methods.

Monitored APIs - DbCommand Methods Enable or disable monitoring for DbCommand methods.

Monitored APIs - OdbcCommandMethods

Enable or disable monitoring for OdbcCommand methods.

Monitored APIs - MVC Methods Enable or disable monitoring for MVC methods.

Modifying configuration settings at the command promptYou can use the command prompt to modify the configuration settings of the .NET Data Collector.

Procedure1. At a new instance of the command prompt, change the path to the CANDLE_HOME\TMAITM6\KD4\bin

directory.


2. Run the .NET Data Collector configuration commands to change the configuration settings forregistering the components, logging and tracing, enabling or disabling monitoring, and so on.

3. To save the configuration changes, run the configdc activateconfig command. The configurationsettings are saved to the dotNetDcConfig.properties file.

.NET Data Collector configuration commandsRun all the configuration commands of the .NET Data Collector at the command prompt to modify theconfiguration settings.

Ensure that you run all commands that are mentioned in Table 4 from the CANDLE_HOME\TMAITM6\K4\bindirectory.

Table 4. .NET Data Collector configuration commands

Command syntax Description

configdc registerdc [-f] Registers the .NET Data Collector.

-f overrides any .NET profiler that is already registeredwithout any notifications. If a profiler exists and the -foption is not specified, the .NET Tracking profiler is notconfigured.

Run this command as an administrator.

configdc unregisterdc Stops the .NET Data Collector from intercepting .NETtransactions. Run this command as an administrator.

configdc ttserver -name name -port port Validates and stores the connectivity information of theTransaction Collector to which the data collector sends thetracking data.

configdc logging [level ERROR | DEBUG | WARNING| INFO] [-size #] [-files #] [-tracing on|off]

Enables or disables trace logging. Sets tracing attributes, forexample, the level of trace detail, the maximum trace log filesize, and the maximum number of trace log files.

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 interfaces are enabled for monitoring bydefault.

Use all to enable all the supported ADO.NET interfaces fortransaction tracking. Use http to enable interception ofsupporting APIs for http monitoring. (See configdcinterface and http supported APIs in Functions ofnamespaces intercepted by the .NET Data Collector topic inthe .NET Data Collector Reference.)

The -appdomain command restricts the ADO.NET interfacemonitoring 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 (*) toenable all application domains. All application domains areenabled by default during the installation.

When an application domain list is assigned to an ADO.NETinterface, the list remains unchanged in the configurationunless it is set to another value. If an interface is enabled formonitoring without specifying an application domain, the lastapplication domain value that you specified or that wasspecified by default for the interface is used.


Table 4. .NET Data Collector configuration commands (continued)

Command syntax Description

configdc disablemonitor [all | adsi | db2 |ldap | odbc | oledb | oracle | sql | http |web]

Disables transaction monitoring of an ADO.NET interface.Use all to disable all supported ADO.NET interfaces fortransaction tracking.

Use http to intercept GetResponse (System.Net) and use webto disable the monitoring of http requests.

configdc getconfig [-active] Displays the properties file where you can add or remove.NET API calls to be intercepted by the .NET Data Collector.When the changes are complete, activate the edited file byusing the configdc activateconfig command.

configdc activateconfig Activates the updated configuration.

Configuring logging for the .NET Data CollectorIn the IBM Tivoli Composite Application Manager for Microsoft Applications V6.3.1, logging for the .NETData Collector is separately configured for each component of the .NET Data Collector.

Performance of the .NET Data Collector might be affected when tracing is enabled. Disable tracing afterthe required trace logs are gathered.

For the .NET profiler, configure logging by using the configdc command. For further information aboutusing the command, see “.NET Data Collector configuration commands” on page 11.

If both .NET Data Collector and IBM Tivoli Composite Application Manager for SOA agent are installedon a computer, the ASP.NET web forms/WCF trace and operation logging is controlled by the IBM TivoliComposite Application Manager for SOA agent. Use the Take Action commands of IBM Tivoli CompositeApplication Manager for SOA agent to modify the logging settings.

If only the .NET Data Collector is installed on a computer, the settings for ASP.NET web forms/WCFtrace and operation logging are taken from the dotNetDcConfig.properties file.

For information about default configuration values for configuring the .NET Data Collector, see theConfiguration values of the .NET Data Collector topic in the .NET Data Collector Reference.

Working with IBM Tivoli Composite Application Manager for SOAYou can configure the .NET Data Collector with IBM Tivoli Composite Application Manager for SOA.

For installation and prerequisites information of IBM Tivoli Composite Application Manager for SOA, seethe user's guide for IBM Tivoli Composite Application Manager for SOA V7.1.1, Fix Pack 2, or later.

Configuring the .NET Data Collector with IBM Tivoli CompositeApplication Manager for SOAIn an environment where the ITCAM for SOA agent (V7.1.1 Fix Pack 2, V7.1.1 Fix Pack 3, or V7.2) isinstalled, you can use the KD4configureTT.bat configuration utility to configure .NET Data Collector withIBM Tivoli Composite Application Manager for SOA.

Procedure1. Open a new instance of the command prompt, and change the path to the bin directory:CANDLE_HOME\

TMAITM6\KD4\bin where CANDLE_HOME is the location where IBM Tivoli Monitoring is installed. Forexample, on Windows systems, C:\IBM\ITM is the default value for CANDLE_HOME.


2. Run the following command: KD4configureTT -enable -server tcp:[ip address of collector:port]The default port is 5455.

3. To enable the .NET Data Collector to work with IBM Tivoli Composite Application Manager for SOA,modify the dotNetDcConfig.properties.inactive file that is located in the CANDLE_HOME\TMAITM6\K4\config directory as follows: default.kd4.enabled=true

4. Open the command prompt, and change the path to the bin directory: cd CANDLE_HOME\TMAITM6\K4\bin

5. Run the configdc activateconfig command.6. Run the configdc registerdc and iisreset command. To see the transaction topology, view the

SOAP component.For more information about configuring the .NET Data Collector with ITCAM for SOA, see theITCAM for SOA Information Center.

Verifying installation of the .NET Data CollectorIf the components of the .NET Data Collector that you selected while installing the .NET Data Collectorare successfully registered, the .NET Data Collector is successfully installed and is monitoring theapplications.

The Table 5 on page 14 provides information about the procedures to verify whether each component ofthe .NET Data Collector that you selected during the installation is successfully registered.


http://www.ibm.com/support/knowledgecenter/SS3JRN_7.2.0/com.ibm.itcamsoa.doc/welcome.htm

Table 5. Verification steps for registration of .NET Data Collector components

ComponentName Location for verification Procedures to verify

HttpModule Global Assembly Cache 1. To open the Global Assembly Cache (GAC), go to Start > Run > enterassembly command.

2. Verify whether NetdcHttpModule is displayed in the GAC.

machine.config file If .NET Framework 3.5 is installed, complete the following steps:

1. Go to the system_root\Microsoft.NET\Framework\v2.0.50727\CONFIGdirectory.

2. Open the machine.config file.

3. Verify whether the <add name="NetdcHttpModule"type=="KTJdotnetdc.NetdcHttpModule, NetdcHttpModule,Version=7.3.2.0, Culture=neutral,PublicKeyToken=df3a8c65f5d404b8"/> tag is displayed in the file.

4. If the 64-bit version of .NET Framework 3.5 is installed, go to thesystem_root\Microsoft.NET\Framework64\v2.0.50727\CONFIGdirectory and repeat steps 2 and 3.

If .NET Framework 4.0 is installed, complete the following steps:



3. Verify whether the <add name="NetdcHttpModule"type="KTJdotnetdc.NetdcHttpModule, NetdcHttpModule,Version=7.3.2.0, Culture=neutral,PublicKeyToken=df3a8c65f5d404b8"/> tag is displayed in the file.


applicationHost.configfile (only for IIS 7.x andIIS 8)

1. To open the applicationHost.config file, go to thesystem_root\System32\inetsrv\config directory.

2. Open the applicationHost.config file.

3. Verify whether the <add name="NetdcHttpModule"type="KTJdotnetdc.NetdcHttpModule, NetdcHttpModule,Version=7.3.2.0, Culture=neutral,PublicKeyToken=df3a8c65f5d404b8"/> tag is displayed in the file.


Table 5. Verification steps for registration of .NET Data Collector components (continued)


SOAP Global Assembly Cache 1. To open the GAC, go to Start > Run > enter assembly command.

2. Verify whether the following .dll files with version 7.3.2.0 aredisplayed in the GAC:

v KD4SoapHandler

v KD4WCFExtension

v KD4dcAgent

machine.config file If .NET Framework 3.5 is installed, complete the following steps:



3. Verify whether the following tags are displayed in the file:

v <add type="com.ibm.management.soa.msnet.KD4SoapHandler,KD4soapagent,Version=7.3.2.0,Culture=neutral,PublicKeyToken=10a210f9548106b4" group="1" priority="50" />

v <add name="KD4WCFExtension"type="com.ibm.management.soa.msnet.KD4WCFExtension,KD4wcfagent, Version=7.3.2.0, Culture=neutral,PublicKeyToken=10a210f9548106b4" />(If only .NET Framework3.5 is installed, this value will not be displayed in the file.)


If .NET Framework version 4.0 is installed, complete the following steps:




v <add type="com.ibm.management.soa.msnet.KD4SoapHandler,KD4soapagent,Version=7.3.2.0,Culture=neutral,PublicKeyToken=10a210f9548106b4" group="1" priority="50"/>

v <add name="KD4WCFExtension"type="com.ibm.management.soa.msnet.KD4WCFExtension,KD4wcfagent, Version=7.3.2.0, Culture=neutral,PublicKeyToken=10a210f9548106b4"/>



Table 5. Verification steps for registration of .NET Data Collector components (continued)


ISAPI Metabase.xml file (onlyfor IIS 6)

1. To open the Metabase.xml file, go to the system_root\System32\inetsrv\ directory.

2. Open the Metabase.xml file.

3. Verify whether a tag that includes Location ="/LM/W3SVC/1/Filters/IISDC" string is displayed.

applicationHost.configfile (only for IIS 7.x andIIS 8)

1. To open the applicationHost.config file, go to thesystem_root\System32\inetsrv\config directory.

2. Open the applicationHost.config file.


v <filter name="IISDC" path="$(Candle_Home)\TMAITM6\K4\bin\iisdc_32.dll" enabled="true"/>

v <filter name="IISDC64" path="$(Candle_Home)\TMAITM6\K4\bin64\iisdc_64.dll" enabled="true"enableCache="true" preCondition="classic,bitness64/>

Profiler Environment Variable 1. On Windows desktop, right-click My Computer and the clickProperties.

2. Complete one of the following steps:

v On Windows 2003 system, click Advanced tab and then clickEnvironment Variables.

v On Windows 2008 system, click Advanced System Settings andthen click Environment Variables.

3. Verify whether the COR_ENABLE_PROFILING variable is displayedand the value of the variable is 1.

4. Verify whether the COR_PROFILER variable is displayed and thevalue of the variable is {5569032F-9CDC-40E8-B31C-F35DB9BD1F5D}.

ADO Event AggregationADO Event Aggregation enables the .NET Data Collector to generate only one node for all the calls thatare made to a database from an ASP.NET page. Event aggregation simplifies instance topology andreduces traffic to the Transaction Collector.

ADO Event Aggregation is enabled by default when you configure the .NET Data Collector.

Disabling ADO event aggregationWhen ADO event aggregation is enabled, and only the Profiler component is registered, nodes for thedatabase calls are not seen in the topology. Therefore, if only the Profiler component is enabled, youmust disable the ADO event aggregation.

Procedure1. Go to the CANDLE_HOME\TMAITM6\K4\config\ directory.2. Open the dotNetDcConfig.properties.inactive file.3. Change the value of the ktj_ADOAggregation.Enabled property to false.

Tip: You can change the value of the ktj_ADOAggregation.Enabled property by using the .NET DataCollector: Property Configuration window. For more information about the .NET Data Collector:Property Configuration window, see “Configuration parameters in the .NET Data Collector: PropertyConfiguration window” on page 10


Chapter 4. Uninstalling the .NET Data Collector

When you uninstall the .NET Data Collector, all components of the .NET Data Collector are automaticallyuninstalled.

Before you begin

You must disable application pools filtering. For more information, see the Disabling the applicationpools filtering topic in the .NET Data Collector Reference.

Procedure1. On the computer where you installed the .NET Data Collector, go to Start > Settings > Control Panel.v If you are uninstalling the .NET Data Collector on a Windows 2003 system, click Add/Remove

Programs.v If you are uninstalling the .NET Data Collector on a Windows 2008 system, click Programs and

Features.2. Click IBM Tivoli Monitoring, and perform one of the following steps:

a. If you have installed only the .NET Data Collector, click Remove, and then click Next. Go to step4.

b. If you have other IBM Tivoli Monitoring components already installed along with the .NET DataCollector on this computer, click Modify.

3. Click .NET Data Collector, and then click Modify/Remove.4. Click Next and complete the following steps:

a. Expand Tivoli Enterprise Monitoring Agents list and clear the .NET Data Collector check box.a. Click Next.b. On the message window, click Next. A message window is displayed for each IBM Tivoli

Monitoring component that is registered with the .NET Data Collector.c. Click Next on each message window.

5. Click Finish to complete the uninstallation. All components of the .NET Data Collector areuninstalled.



Appendix. ITCAM for Microsoft Applications documentationlibrary

Various publications are relevant to the use of ITCAM for Microsoft Applications.

For information about how to access and use the publications, see Using the publications(http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.1/com.ibm.itm.doc_6.3/common/using_publications.htm).

To find publications from the previous version of a product, click Previous versions under the name ofthe product in the Contents pane.

Documentation for this product is in the ITCAM for Microsoft Applications Knowledge Center(http://www.ibm.com/support/knowledgecenter/SSDKXQ_6.3.1/com.ibm.itcamms.doc_6.3.1/welcome_msapps631.html)v Quick Start Guidesv Offering Guidev Download instructionsv Links to Prerequisitesv Installation and Configuration Guide for each agentv Link to Reference information for each agentv Link to Troubleshooting Guide for each agent

Prerequisite publicationsTo use the information about the agents effectively, you must have some prerequisite knowledge.

See the following information at the IBM Tivoli Monitoring Knowledge Center (http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/welcome.htm) to gain prerequisiteknowledge:v IBM Tivoli Monitoring Administrator's Guide

v IBM Tivoli Monitoring Installation and Setup Guide

v IBM Tivoli Monitoring High Availability Guide for Distributed Systems

v IBM Tivoli Monitoring: Installation and Configuration Guides for the following agents: OperatingSystem agents and Warehouse agents

v IBM Tivoli Monitoring: User's Guides for the following agents: Agentless OS monitors, Log file agent,System p agents, Systems Director base agent

v IBM Tivoli Monitoring Agent Builder User's Guide

v IBM Tivoli Monitoring Command Reference

v IBM Tivoli Monitoring: Messages

v IBM Tivoli Monitoring Troubleshooting Guide

v IBM Tivoli Monitoring: References for the following agents: Operating System agents and Warehouseagents

v IBM Tivoli Monitoring: Troubleshooting Guides for the following agents: Operating System agents andWarehouse agents

v Tivoli Enterprise Portal User's Guide


http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.1/com.ibm.itm.doc_6.3/common/using_publications.htm

http://www.ibm.com/support/knowledgecenter/SSDKXQ_6.3.1/com.ibm.itcamms.doc_6.3.1/welcome_msapps631.html

http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/welcome.htm

Related publicationsThe publications in related information centers provide useful information.

See the following information centers, which you can find by accessing Tivoli Documentation Central(https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Documentation%20Central):v Tivoli Monitoringv Tivoli Application Dependency Discovery Managerv Tivoli Business Service Managerv Tivoli Common Reportingv Tivoli Enterprise Console®

v Tivoli Netcool/OMNIbus

Tivoli Monitoring Community on Service Management ConnectService Management Connect (SMC) is a repository of technical information that is organized bycommunities.

Access Service Management Connect at https://www.ibm.com/developerworks/servicemanagement.

For information about Tivoli products, see the Application Performance Management community(http://www.ibm.com/developerworks/servicemanagement/apm/index.html).

Connect, learn, and share with Service Management professionals. Get access to developers and productsupport technical experts who provide their perspectives and expertise. You can use SMC for thesepurposes:v Become involved with transparent development, an ongoing, open engagement between other users

and IBM developers of Tivoli products. You can access early designs, sprint demonstrations, productroadmaps, and prerelease code.

v Connect one-on-one with the experts to collaborate and network about Tivoli and the (enter yourcommunity name here) community.

v Read blogs to benefit from the expertise and experience of others.v Use wikis and forums to collaborate with the broader user community.

Other sources of documentationYou can obtain additional technical documentation about monitoring products from other sources.

See the following sources of technical documentation about monitoring products:v IBM Integrated Service Management Library (http://www.ibm.com/software/brandcatalog/

ismlibrary/) is an online catalog that contains integration documentation as well as otherdownloadable product extensions.

v IBM Redbook publications (http://www.redbooks.ibm.com/) include Redbooks® publications,Redpapers, and Redbooks technotes that provide information about products from platform andsolution perspectives.

v Technotes (http://www.ibm.com/support/entry/portal/software), which are found through the IBMSoftware Support website, provide the latest information about known product limitations andworkarounds.


https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Documentation%20Central

https://www.ibm.com/developerworks/servicemanagement

http://www.ibm.com/developerworks/servicemanagement/apm/index.html

http://www.ibm.com/software/brandcatalog/ismlibrary/

http://www.redbooks.ibm.com/

http://www.ibm.com/support/entry/portal/software

Notices

This information was developed for products and services offered in the US. This material might beavailable from IBM in other languages. However, you may be required to own a copy of the product orproduct version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program,or service that does not infringe any IBM intellectual property right may be used instead. However, it isthe user's responsibility to evaluate and verify the operation of any non-IBM product, program, orservice.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate withoutincurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions.Actual results may vary.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related tonon-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to actual people or business enterprises isentirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative workmust include a copyrightnotice as follows:© (your company name) (year).Portions of this code are derived from IBM Corp. Sample Programs.© Copyright IBM Corp. 2012, 2016.


TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web at"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the following terms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBM website.

Personal use

You may reproduce these publications for your personal, noncommercial use provided that allproprietary notices are preserved. You may not distribute, display or make derivative work of thesepublications, or any portion thereof, without the express consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within your enterprise provided thatall proprietary notices are preserved. You may not make derivative works of these publications, orreproduce, distribute or display these publications or any portion thereof outside your enterprise, withoutthe express consent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, eitherexpress or implied, to the publications or any information, data, software or other intellectual propertycontained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use ofthe publications is detrimental to its interest or, as determined by IBM, the above instructions are notbeing properly followed.

You may not download, export or re-export this information except in full compliance with all applicablelaws and regulations, including all United States export laws and regulations.

Notices 23

http://www.ibm.com/legal/us/en/copytrade.shtml

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THEPUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OFMERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy StatementIBM Software products, including software as a service solutions, (“Software Offerings”) may use cookiesor other technologies to collect product usage information, to help improve the end user experience, totailor interactions with the end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offerings can help enable you tocollect personally identifiable information. If this Software Offering uses cookies to collect personallyidentifiable information, specific information about this offering's use of cookies is set forth in thefollowing paragraphs.

Depending upon the configurations deployed, this Software Offering may use session cookies that collecteach user's user name for purposes of session management, authentication, and single sign-onconfiguration. These cookies can be disabled, but disabling them will also likely eliminate thefunctionality they enable.

If the configurations deployed for this Software Offering provide you as customer the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes, SeeIBM's Privacy Policy at http://www.ibm.com/privacy and IBM's Online Privacy Statement athttp://www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and OtherTechnologies” and the “IBM Software Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

Index

AADO Event Aggregation

disabling event aggregation 16Application Performance Management community on

SMC 20

Cconfiguring

NET Data Collector 9configuring .NET Data Collector

activating configuration 9command prompt 10configuration commands 11connection to Transaction Collector 8

Ddocumentation

See publications

Iinstalling .NET Data Collector 3Integrated Service Management Library documentation 20

NNET Data Collector

.NET Data collector: Property Configuration window 10ADO Event Aggregation 16configuration commands 11configuration parameters 10configuration with IBM Tivoli Composite Application

Manager for SOA 12configuring ADO.NET connection 8configuring logging 12new in this release 1overview 1Property Configuration window 9working with IBM Tivoli Composite Application Manager

for SOA 12

Ooperating systems 3

Pprerequisite checker 3prerequisite publications 19prerequisites 3publications 19, 20

IBM Tivoli Monitoring 19Integrated Service Management Library 20prerequisite 19Redbooks 20related 20

publications (continued)Service Management Connect 20SMC

See Service Management ConnectTechnotes 20wikis 20

RRedbooks 20requirements 3

SService Management Connect 20SMC

See Service Management Connect

TTechnotes 20

Uuninstalling NET Data Collector 17

Wwikis 20



IBM®

Printed in USA

SC27-5667-01

Date post:	31-Dec-2020
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times

.NET Data Collector: Installation and Configuration Guide · 2016. 8. 8. · Internet Information...

Documents