Microsoft COM+ monitor Installation
1. To use the monitor, you need the license for the COM+ monitor
2. The server being monitored requires Windows 2000 and higher.
3. The client machine running the Controller requires LoadRunner version 7.6 or higher.
1. COM+ graphs: Data collected in the scenario’s last few seconds (~ twice the sampling rate) may be missing from the Analysis graphs.
2. The Microsoft COM+ monitor does not display nested methods.
Microsoft COM+ Server Setup
To monitor the Microsoft COM+ server performance, you must first install the Microsoft COM+ Server Monitor Probe on the server machine.
1. On the Microsoft COM+ server machine, run Mercury’s COM+ server add-in:
· For LoadRunner8.0, locate the Add-ins installation CD, and run Com_Plus_Probe.exe on the Additonal compoenetsCom_Plus_Probe directory.
· For LoadRunner 7.8, run the UpdateService (Start -> Programs -> LR -> UpdateService), and select ‘COM+ monitor server side installation’ on a machine with LoadRunner 7.8 or 7.8 Feature Pack 1 installed.
· For LoadRunner 7.6, download <COM_Plus_Server_Add-in.exe> from Patch LR76P4
LoadRunner Controller Setup
Verify that you have the appropriate component:
1. For LoadRunner 8.0, you do not need to apply any patches
2. For LoadRunner7.8, apply LoadRunner Feature Pack 1 on all the LoadRunner machines
3. For LoadRunner7.6, you will download and apply <Com_Plus_Client_Add-in.exe> from Patch LR76P4
To configure the COM+ monitor:
1. Click the Microsoft COM+ graph in the graph tree, and drag it into the right pane of the Run view.
2. Right-click the graph and choose Add Measurements, or choose Monitors -> Add Measurements.
3. In the Monitored Server Machines section of the Microsoft COM+ dialog box, click Add to open the Add Machine dialog.
a. For regular monitoring without a firewall, enter the server name or IP address of the machine you want to monitor, select the platform on which the machine runs, and click OK.
b. To connect to the monitor over a firewall, enter the server name or IP address of the machine you want to monitor, according to the following format, and click OK:
<MI Listener machine>:<server machine key>
where server machine key is the unique key that you chose when configuring the firewall Agent on the server machine. For example: 220.127.116.11:serverid
4. In the Resource Measurements section of the Microsoft COM+ dialog box, click Add to select the measurements that you want to monitor.
5. Browse the Measured Components tree, and check the required performance counters.
6. Click ‘OK’ in the Microsoft COM+ Performance Monitors dialog box, and in the Microsoft COM+ dialog box, to activate the Microsoft COM+ monitor.
Note: The data sampling rate for the COM+ monitor is fixed and cannot be modified using the Controller Tools à Options à Monitors dialog.
|Authenticate||Frequency of successful method call level authentication. When you set an authentication level for an application, you determine what degree of authentication is performed when clients call into the application.|
|Authenticate Failed||Frequency of failed method call level authentication.|
|Activation||Frequency of application activation or startup.|
|Shutdown||Frequency of application shutdown or termination.|
|Thread Start||Rate at which single-threaded apartment (STA) thread for application have been started.|
|Thread Terminate||Rate at which single-threaded apartment (STA) thread for application have been terminated.|
|Work Enque||Event sent if a work is queued in single thread apartment object (STA). Note: These events are not signaled/sent in Windows Server 2003 and later.|
|Work Reject||Event sent if a work is rejected from single thread apartment object (STA). Note: These events are not signaled/sent in Windows Server 2003 and later.|
|Transaction Duration||Duration of COM+ transactions for selected application.|
|Transaction Start||Rate at which transactions have started.|
|Transaction Prepared||Rate at which transactions have completed the prepare phase of the two-phase protocol.|
|Transaction Aborted||Rate at which transactions have been aborted.|
|Transaction Commit||Rate at which transactions have completed the commit protocol.|
|Object Life Time||Duration of object existence (from instantiation to destruction).|
|Object Create||Rate at which new instances of this object are created.|
|Object Destroy||Rate at which instances of the object are destroyed.|
|Object Activate||Rate of retrieving instances of a new JIT-activated object.|
|Object Deactivation||Rate of freeing JIT-activated object via SetComplete or SetAbort.|
|Disable Commit||Rate of client calls to DisableCommit on a context. DisableCommit declares that the object’s transactional updates are inconsistent and can’t be committed in their present state.|
|Enable Commit||Rate of client calls to EnableCommit on a context. EnableCommit declares that the current object’s work is not necessarily finished, but that its transactional updates are consistent and could be committed in their present form.|
|Set Complete||Rate of client calls to SetComplete on a context. SetComplete declares that the transaction in which the object is executing can be committed, and that the object should be deactivated on returning from the currently executing method call.|
|Set Abort||Rate of client calls to SetAbort on a context. SetAbort declares that the transaction in which the object is executing must be aborted, and that the object should be deactivated on returning from the currently executing method call.|
|Method Duration||Average duration of method.|
|Method Frequency||Frequency of method invocation.|
|Method Failed||Frequency of failed methods (i.e. methods that return error HRESULT codes).|
|Method Exceptions||Frequency of exceptions thrown by selected method.|