IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Configure IBM Tivoli Monitoring components
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tivoli Monitoring protocol usage and protocol modifiers
IBM Tivoli Monitoring basic services communications are defined by the KDE_TRANSPORT environmental variable.
In earlier releases KDC_FAMILIES was used but KDE_TRANSPORT is the successor. The two variables are processed identically, however many agent installers are only aware of the earlier variable. You should examine the agent installation and adopt whatever is used.
IBM Tivoli Monitoring uses other communication protocols such as the following:
- Tivoli Enterprise Portal Client to Tivoli Enterprise Portal Server uses CORBA IIOP after startup.
- Tivoli Enterprise Portal Server, Warehouse Proxy Agent, and Summarization and Pruning Agent can use ODBC or JDBC to communicate with the warehouse database.
- Most IBM Tivoli Monitoring to IBM Tivoli Monitoring communications use the TCP/IP protocol.
Modifiers to the protocols are of the form attribute:value. If the modifier occurs first, then it is global in effect. If the modifier occurs after a protocol and before the next protocol, then the effect is only on the protocol that precedes it. The protocol names and modifiers are not case sensitive although they are presented in uppercase in the following paragraphs.
- KDE_TRANSPORT Structure
KDE_TRANSPORT Structure is a string that lists protocols and modifiers. All protocols are assumed as present. A protocol is activated only if an interface is available for use.
- KDE_TRANSPORT Transmission Control Protocol
Transmission Control Protocol (TCP) is a connection oriented protocol. Connection is made through a port number such as 0-65535.
Parent topic:
Configure IBM Tivoli Monitoring components