IntroductionLast month, we started to dive into the underdocumented and largely misunderstood area of TIM Trace options.
See https://communities.ca.com/message/241847328#241847328 for Part 1. We went over some guidelines for TIM Trace options.
This month we continue the overview.
Behind the scenes
So from the TIM System Setup page via your browser, you can view and set the TIM trace settings. But what is happening behind the scenes at a high-level?
In your <tim_home>/config directory is a dynamically created file called tim.options. The contents look something like this:
# This file is generated automatically -- do not edit.# The script that starts tim reads options from this file.-tracetransets-tracetranunits-tracematchedtrancomps-traceallcomponents-traceparameters-traceconnections-tracessldebug
So, depending on your operation on the web page, you are either reading or writing values to this file. Fortunately, this can be done without a TIM service restart. In addition to writing these new values, the TIM also has to be informed of the TIM trace options and immediately start using them.
TIM Trace Options
Below is what the TIM Trace Options page looks like.
What does each setting show?
- No options -- Shows startup log output, OOO Packets Web Server status
- Trace Statistics -- provides various system statistics
- Trace Defects -- Gives useful information on whether a defect or not was produced and for which transaction(s).
- Trace Session and logins -- Gives session and login values for each monitored transaction being processed. Useful in knowing if a login/session id was found or not.
- Trace Business Transactions, Transactions, and Transaction Components. -- These three options provide information about the various levels of monitored transactions including parameter/value pairs, client/server IPs, transaction name, etc.
- Trace HTTP Components/Parameters/Flex Components -- These three options act like a sniffer displaying HTTP/HTTPS/XML/Flex Request & Response information.
- Trace connections -- Trace the connection Open, Reset, and Close operations for the traffic that the TIM is seeing.
- Trace SSL errors -- Shows messages about unsuccessful TIM SSL processing including cipher suites, SSL/TLS version, ability to decode SSL packet, and more.
In addition to this, there are TIM Trace Filters on the right hand side to show only traffic:
- from a specific IP address (Note this can be set to a client or server IP)- browser language setting- HTTP Parameters - Parameter Type (Cookie,Post, URL) - Parameter Name (Such as JSESSION except for URL Parameter Type that must be Host,Port,Path.)
1) This is an include not exclude filter and only one HTTP parameter filter can be reset.
2) Selecting Erase the TIM log only clears what displays on the screen for a log. The log physically still exists. Again, changes made on this page do not require a restart
Next month we wrap up by telling when to use each option. Until then I see you on the Community and webexes :-)