| DataSource |
Name |
Description |
Example |
| Options for TIBCO Rendezvous connections |
-rvdaemon: |
TIBCO Rendezvous Session
Daemon. Default is TIBCO Rendezvous daemon default (local daemon on TCP
socket 7500). |
-rvdaemon:7475 |
| -rvnetwork: |
TIBCO Rendezvous Session
Network. Default is TIBCO Rendezvous network default (primary network interface
for the host computer). |
"-rvnetwork:;" |
| -rvservice: |
TIBCO Rendezvous Session
Service. Default is TIBCO Rendezvous service default. |
-rvservice:7475 |
| Options for JMS connections |
-jmsclient: |
The client identifier for
the message server connection. |
-jmsclient:client1 |
| -jmsfactory: |
The fully qualified name
of the topic connection factory class to use when creating this connection.
The path to this class must be included in the RTV_USERPATH environment
variable. Refer to your JMS provider documentation if you do not know the
name of this class. The default is com.tibco.tibjms.TibjmsTopicConnectionFactory. |
-jmsfactory:com.tibco.tibjms.TibjmsTopicConnectionFactory |
| -jmshostname: |
For IBM WebSphere MQ
only. The name of the host to use for this connection. |
-jmshostname:myServer |
| -jmspassword: |
The password for the message
server connection. |
-jmspassword:pass1 |
| -jmsport: |
For IBM WebSphere MQ
only. The name of the port to use for this connection. |
-jmsport:1234 |
| -jmsqueuemanager: |
For IBM WebSphere MQ
only. The name of the queue manager to use for this connection. |
-jmsqueuemanager:myQueueManager |
| -jmsserver: |
The URL for your message
server. |
-jmsserver:tcp:\\myserver:7222 |
| -jmstimestamp |
Use the timestamp returned
by the Message interface method getJMSTimestamp(). instead of the time
the Transaction Monitor receieved the message. |
-jmstimestamp |
| -jmsuser: |
The user name for the message
server connection. |
-jmsuser:user1 |
| -tempdest: |
If temporary
destinations are used in your transaction definition, specify a destination
filter to use. Temporary destinations are supported in the Transaction Monitor
by listening for the following TIBCO system monitor messages:
$sys.monitor.Q.r.$TMP$.>
$sys.monitor.T.r.$TMP$.>
Since there is overhead associated
with listening for these messages, this option allows you to specify a more
specific system monitor topic. For example, if you specify $TMP$.myServer.*,
the following system monitor messages would be used:
$sys.monitor.Q.r.$TMP$.myServer.*
$sys.monitor.T.r.$TMP$.myServer.*
NOTE: Temporary destinations are
only supported for TIBCO JMS connections. |
-tempdest:myServer.* |
| -tempdestexpire: |
If
temporary destinations are used in your transaction definition, specify the
amount of time in milliseconds that temporary destination messages should be
kept in memory if no transaction have used them. Default is 5 minutes.
NOTE: Temporary destinations are
only supported for TIBCO JMS connections. |
-tempdestexpire:
10000 |
| -tempdestmode: |
If
temporary destinations are used in your transaction definition, specify
whether to listen for temporary topics or temporary queues. Valid options are
TOPIC_ONLY or QUEUE_ONLY. Default is to listen for both.
Temporary destinations are supported
in the Transaction Monitor by listening for the following TIBCO system monitor
messages:
$sys.monitor.Q.r.$TMP$.>
$sys.monitor.T.r.$TMP$.>
Since there is overhead associated
with listening for these messages, this option allows you to specify that the
Transaction Monitor should only listen for one or the other if your
application only uses temporary topics or temporary queues.
NOTE: Temporary destinations are
only supported for TIBCO JMS connections. |
-tempdestmode:QUEUE_ONLY |
| General options |
-activetranslimit: |
Number of active transactions,
per defined transaction, stored by the Transaction Monitor. If the number
of active transactions exceeds the limit, the Transaction Monitor will
expire enough transactions to reduce the transaction count to the limit.
The oldest transactions will expire first. Once a transaction has expired,
it will be output in the next update with the status EXPIRED and will no
longer be tracked. Default is no limit; no transactions will expire.
NOTE: This value will be
applied to all transactions. To set a limit
for a specific transaction you must define this value in the TRANSACTIONS.ini
file. |
-activetranslimit:10 |
| -activetranstimelimit: |
Time limit for active transactions,
per defined transaction, stored by the Transaction Monitor. If the time
limit is exceeded by a PROCESSING transaction, the transaction will be
output in the next update with the status EXPIRED and will no longer be
tracked. Default is no limit; no transactions will expire.
NOTE: This value will be
applied to all transactions. To set a limit
for a specific transaction you must define this value in the TRANSACTIONS.ini
file. |
-activetranstimelimit:5000 |
| -calcinterval:
(milliseconds) |
Rate,
latency and size averages are calculated as moving averages over this time
interval. Default is 60000 milliseconds (one minute), so these averages
are calculating using data from transactions and interfaces that have completed
over the previous minute. |
-calcinterval:10000 |
| -defaultds:(ds) |
Specifies the default data source.
JMS is the default. If a data source other than JMS or TIBCO Rendezvous is
found, the Transaction Monitor gives an error message and sets JMS as the
default data source. |
-defaultds:jms
-defaultds:rv |
| -jmxport:(port
number) |
The port number
to use to expose JMX methods to monitor
and manage the Transaction Monitor. There is no default port. If not specified,
these JMX methods will not be accessible. |
-jmxport:9994 |
| -maintainstate |
By default, summary values are
cleared between Transaction Monitor runs. Specify this option to set initial
summary information from the previous run.
Rate,
latency and size averages are calculated as moving averages over the specified
calcinterval. In order to determine how to weight the previous summary
information in the current moving averages, the Transaction Monitor takes the
summary rate value from the previous run and divides it by the calinterval.
For example, if your calcinterval is one hour and the summary rate value from
the previous run is 5, the new Transaction Monitor summary values are
calculated as though 5 transactions completed over the previous hour with the
rate, latency and size values from the previous summary information. Over the
next hour, one of these simulated transactions is dropped from the moving
average calculation every 12 minutes, so that after an hour, the summary
values from the previous run are not longer part of the moving average
calculations. |
-maintainstate |
| -nodetailactive |
Disables output of tm_detailactive.xml |
-nodetailactive |
| -nodetaildone |
Disables output of tm_detaildone.xml |
-nodetaildone |
| -nointdetailactive |
Disables output of IntDetailActive
table in tm_detailactive.xml |
-nointdetailactive |
| -nointdetaildone |
Disables output of IntDetailDone
table in tm_detaildone.xml |
-nointdetaildone |
| -nointsummary |
Disables output of IntSummary
table in tm_summary.xml |
-nointsummary |
| -0:(milliseconds) |
Set output rate of Transaction
Monitor. Default is 2000 milliseconds. |
-0:5000 |
| -port:(port
number) |
Specify port when
Transaction Monitor
is set to output data via socket. Default is 4068.
|
-port:1234 |
| -rateunit:
(milliseconds) |
Set
unit of time for displaying the rate of completed transactions. Default
is 60000 milliseconds (one minute), so the rate will display the
average number of transactions completed per minute. |
-rateunit:60000 |
|
-socket |
Set the Transaction Monitor to output data via socket. |
-socket |
