This content has been marked as final. Show 2 replies
In TSAM Online Documents, it refer to TSAM only monitor three call-in: JSH/WSH, Client, Application Server ,also currently only monitor tpcall/tpacall.
So, TSAM can not monitor requests' call path from WTC and remote tuxedo domain. But we can monitor initiator's call path in domain of subscribing the request.
DomainA and DomainB
ServiceA in DomainA , ServerB in DomainB
A WS/Local client call a serviceA which advertises in DomainA;
the serviceA need invoke serviceB which advertises in DomainB.
In TSAM, when I set initiator's domain is DomainA, I will get the call path, also including path in DomainB ;because it is from A "CLIENT"
But, when I set intiator's domain is DomainB, no "call path" will be show. because it is from SYSTEM SERVER "GWTDOMAIN"
TSAM 1.1/10gR3 does not support GWTDOMAIN as a call path initiator yet. In TSAM 11gR1, we will support this.