ITCAM for Transactions Tracking: tips,best practices,pitfalls Part2
ericmtn 1000009W88 Comment (1) Visits (7232)
A) TT MQ data collector does not connect to the Transaction Collector (TU) agent
To continue my series of blogs regarding Transaction Tracking environment, a mistake often done is to set up the connection string incorrectly, so for example the MQ data collector can connect to the Transaction Collector (TU) agent.
As documented here :
in the "Configuring MQ tracking" chapter, it says :
MQ Data Collector TT Settings
Transaction Collector Location : Specifies the protocol, IP address, and port that MQ Tracking uses to send tracking events to the Transaction Collector. For IPv4, use the format protocol:IPv4 address:port, for example tcp:127.0.0.1:5455. For IPv6, use the format protocol:[IPv6 address]:port, for example, tcp:[::1]:5455 is equivalent to the previous IPv4 example. The only protocol currently supported is TCP.
Sometimes, the above information is misread or misinterpreted, and in ttdcproxy.cfg file, there is wrong TTServerString setting, like :
TTServerString=<Tx collector IP@>
which is incorrect;
it should be set to :
Of course, verify if the Tx collector agent is listening to its default port (5455), or if it was reconfigured with another port. if it's left as default, you should see in latest updated Tx collector ras1 log file, <hos
B) Transaction Tracking Discovery Library Adaptor (DLA) : How to get the DLA input file, before transformation?
B1) On Tx reporter agent system edit tosu
for example on Windows: edit C:\I
and set as below:
which contains the input and output.
for part 1 of this blog, see :
Subscribe and follow us for all the latest information directly on your social feeds: