IBM Support

.NET Data Collector LA Fix available from support.



A LA fix for the .NET data collector for Transaction Tracking has been made available through support. To obtain this fix please contact support and request fix . It addresses a number of issues including APAR IV12327 "THE ADO.NET NODE FOR A DB IS NOT DISPLAYED."


The LA fix contains the following content and can be obtained from support upon raising a service request.

a)Node for ASPX page
A node on transaction topology will be displayed for each ASPX page call with the following:
-Transaction Name = URI
-Application Name = AppPool Name
-Component Name = IIS
-Server Name = Machine Name

b)Interception of HTTP Client API support
HTTP Client APIs like GetResponse, BeginGetResponse, EndGetResponse along with Server.Transfer and Server.Execute are also intercepted.

To disable the Server.Transfer and Server.Execute methods, complete the following steps:
1.Browse to the config directory, and then open the file in notepad.
2.Modify the following properties:
-Property 'System.Web.HttpServerUtility.Execute.3.Enabled=true' to 'System.Web.HttpServerUtility.Execute.3.Enabled=false'.
-Property 'System.Web.HttpServerUtility.Execute.4.Enabled=true' to 'System.Web.HttpServerUtility.Execute.4.Enabled=false'.
This will disable the interception of HttpServerUtility.Execute by Profiler.
3.Save the Inactive file.
4.Open the command prompt.
Note: Ensure that you have administrative rights on the computer.
5.Specify the path of the bin folder and run the following commands at the command prompt:
-configDC activateConfig
The Server.Transfer and Server.Execute methods will be disabled.

c)Link to IHS-WAS
If any page that is hosted in IHS or WAS (using IHS with WAS plugin) is called from a .NET client and IHS is also monitored, then the nodes from IHS-WAS will also be linked with .NET node.

d)Optimization of number of nodes
From now on, one node per .NET handler in transaction topology will be displayed. This is an optimization from the last release to simplify the overall topologies. A single node per web service call will be displayed instead of two nodes. Following the same convention, the ASPX page will also be displayed as a single node.

e)Improvement in node naming convention
The following node naming convention will be used:
For transaction inside IIS:
-Application Name = AppPool Name
-Component Name = IIS
For transaction outside IIS:
-Application Name = Process Name
-Component Name = Microsoft .NET
For ADO .NET transaction:
-Component Name = ADO.NET
-Application Name = DBTYPE:DataSource or DBTYPE:Driver
where DBTYPE can be "SQL", "ORACLE", "DB2", "OLEDB", "ODBC" or "DB"
For web service:
-Transaction Name for Client = WSClient:ServiceName:Operation
-Transaction Name for Server = WS:ServiceName:Operation
-WCF web service with ASP impersonation enabled is considered as running inside IIS. Therefore, such a WCF web service follows the node naming convention for transaction inside IIS.
-WCF web service without ASP impersonation enabled is considered as running outside IIS. Therefore, such a WCF web service follows the node naming convention for transaction outside IIS.

f)IIS 7.x integrated mode support IIS 7.x integrated mode is also supported.

g)No manual steps required for IIS 7.x classic mode and .NET Framework 4.0 support. With this patch, no manual steps are required to enable support for IIS 7.x classic mode and .NET Framework version 4.0.

h)From this version onwards, no nodes will be shown for static contents. This feature will generate more appropriate topologies by eliminating the nodes for static content that are not part of the monitored transaction.

Document information

More support for: Tivoli Composite Application Manager for Transactions
ITCAM TRANSACT Trac 5724S79TT v710

Software version: 7.3

Operating system(s): Windows

Reference #: 1580210

Modified date: 06 February 2012