IBM Tivoli Monitoring, Version 6.3

KDE_TRANSPORT Hypertext Transfer Protocol

Each IBM® Tivoli® Monitoring process has an internal web server. The KDE_TRANSPORT Hypertext Transfer Protocols define what protocols are used to access the internal web server. The web server provides access to the IBM Tivoli Monitoring Service Console, the Tivoli Enterprise Portal client, the SOAP server tryout page, and the Agent Service Index pages (with Tivoli Monitoring V6.2.2 or higher).

The protocol names are as follows:

ip.tcp.http - http communications
ip.ssl.https - secure http communications
ip6.tcp.http - ipv6 http communications
ip6.ssl.https - ipv6 secure http communications

The protocol modifiers are as follows:

HTTP_SERVER: Defaults to Y. If set to N then the internal web server is not started.
HTTP_CONSOLE: Defaults to Y. If set to N then the IBM Tivoli Monitoring service console is not started.
HTTP: Defaults to 1920. If set to 0, access to non-secure internal web server is disabled.
HTTPS: Defaults to 3661. If set to 0, access to secure internal web server is disabled.
Note: To meet the FIPS 140-2 requirement for secure communication, you should consider setting HTTP:0 and only allowing internal web server access with HTTPS.
POOL: The HTTP protocol also uses temporary ports and the usage is controlled by separate pool control settings. These are not protocols, but are required for the POOL setting:
```
ip.tcp - pool control for the ip.tcp.http protocol
ip.ssl - pool control for the ip.ssl.https protocol
ip6.tcp - pool control for the ip6.tcp.http protocol
ip6.ssl - pool control for the ip6.ssl.https protocol
```
Here is an example of usage: IP.TCP.HTTP USE:Y IP.TCP POOL:20000-20031. You do not need to specify a protocol that is assumed enabled already, so you could simply add: IP.TCP POOL:20000-20031. To completely control pool usage, you must set the POOL value for all enabled protocols.

Feedback