Web Service logging

Background
Our govt. department's main application can perform an external search on
the records of another govt. department. This is effected via a SOAP adapter
in BizTalk 2006 at our end, communicating with a web service at the other
end. All fairly standard. However, we are being charged for each call we make
to their web service and there is some discrepancy in our estimates vs their
bill :(
Is there any logging available in IIS that can record the number of
successful calls to an external web service?
Searches in these forums indicate that SOAP logging is not generally
available inside BizTalk itself and this functionality needs to be written
into the orchestration when it is developed.
Please advise, thanks in advance,

Dave

Re: Web Service logging

On Apr 14, 3:28=A0pm, Dave wrote:
> Background
> Our govt. department's main application can perform an external search on
> the records of another govt. department. This is effected via a SOAP adapt=
er
> in BizTalk 2006 at our end, communicating with a web service at the other
> end. All fairly standard. However, we are being charged for each call we m=
ake
> to their web service and there is some discrepancy in our estimates vs the=
ir
> bill :(
> Is there any logging available in IIS that can record the number of
> successful calls to an external web service?
> Searches in these forums indicate that SOAP logging is not generally
> available inside BizTalk itself and this functionality needs to be written=

> into the orchestration when it is developed.
> Please advise, thanks in advance,
>
> Dave


IIS is a web server, so it can only log requests that are made TO it.
IIS is unaware and unable to log external search requests made FROM it
to another WebService. You will have to log that activity everytime
your application makes an external search.

In short, the IIS logs of the WebService at the other end contains the
definitive callers and quantity for billing.

Unless you log every instance of your outbound requests, you cannot
dispute anything.

The only thing you may dispute is HOW they assign a given request
against your bill. For example, if the requests are authenticated,
they should not count every 401.x request as a "call". Likewise, they
should not charge you for a "500" status because it indicates some
application failure on their end. etc

Basically, unless you track the outbound calls, you have no way to
dispute. And tracking outbound calls is never the responsibility of
IIS.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//