hi

We are using WINNT 4.0 + option pack, to host various enterprise web
applications using IIS 4.0 and MTS2.0. There are several applications
and each one has a dedicated server. From time to time there are
issues with the webservers and overall application perfromance. We use
the MMC to peep at the components in mts. Amoung the details it lists
are the component names and details of what is in call. These counters
appear to refresh every second. It would be nice to record the number
of in call calls for each components to a database. Does anybody know
how we can get at these counters. Ideally we would like to access
these details remotly via an API call. We had a look on MSDN, but
didnt find much. There was some information on administration of MTS,
adding components to packages etc, but nothing on getting real-time
information on the number of in-call calls going through components.

Any ideas would be appreciated.

[ Post a follow-up to this message ]

Take a look here: http://www.xtremesoft.com/solutions...roduct_tour.htm

--
Chris


"barney" wrote:

> hi
>
> We are using WINNT 4.0 + option pack, to host various enterprise web
> applications using IIS 4.0 and MTS2.0. There are several applications
> and each one has a dedicated server. From time to time there are
> issues with the webservers and overall application perfromance. We use
> the MMC to peep at the components in mts. Amoung the details it lists
> are the component names and details of what is in call. These counters
> appear to refresh every second. It would be nice to record the number
> of in call calls for each components to a database. Does anybody know
> how we can get at these counters. Ideally we would like to access
> these details remotly via an API call. We had a look on MSDN, but
> didnt find much. There was some information on administration of MTS,
> adding components to packages etc, but nothing on getting real-time
> information on the number of in-call calls going through components.
>
> Any ideas would be appreciated.
>

[ Post a follow-up to this message ]