IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Configure IBM Tivoli Monitoring components > Tivoli Monitoring protocol usage and protocol modifiers > KDE_TRANSPORT Transmission Control Protocol
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
How to change KDE_TRANSPORT settings
If you decide to change KDE_TRANSPORT you must change the settings on all IBM Tivoli Monitoring tasks, when appropriate.
For example, if you decide to turn off the IBM Tivoli Monitoring internal web server using the HTTP_SERVER:N modifier, you must make the same change for all IBM Tivoli Monitoring tasks.
Mass change to Windows and Linux/UNIX agents
For details on how to make a mass change to Windows and Linux/UNIX agents, see http://www-01.ibm.com/support/docview.wss?uid=swg21441836.
Linux/UNIX – Tivoli Enterprise Monitoring Server
This environment is similar to agents. The difference is the config file generation is only performed when you run the command:itmcmd config -S -t <temsname>Edit the ms.ini in the same way as the agent case above, and then reconfigure the Tivoli Enterprise Monitoring Server using the itmcmd config command.
i/5
The environment variable is manually changed in:
QAUTOTMP/KMSPARM(KBBENV)
z/OS
In z/OS these values are kept in the RKANPARU(KDSENV) member for Tivoli Enterprise Monitoring Server and in RKANPARU(KppENV) for agents. Configuration changes here are manual.
Interactions with other environment variables
KDEB_INTERFACELIST and KDEB_INTERFACELIST_IPV6
The dash “-“ option is used alone. These environment variables do not scan any of the related interfaces. In such a scenario a protocol might go unused even though it is specified in KDE_TRANSPORT. You can also eliminate all the interfaces by name to achieve the same result.
Parent topic:
KDE_TRANSPORT Transmission Control Protocol