IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Prepare for installation > Security options
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Communication between components
To secure communication between agents, monitoring servers, and the portal server, use SPIPE as the protocol when you configure communications between the Tivoli Enterprise Portal Server and the hub Tivoli Enterprise Monitoring Server, between hub and remote monitoring servers, and between agents and monitoring servers.
Two additional protocols are used to secure communication between portal clients and the portal server:
- Secure Hypertext Transport Protocol (HTTPS) to retrieve files and Interoperable Object Reference (IOR). The integrated browser in the client provides HTTPS support on the client side; for the server, consider using a third party Web server that supports HTTPS, such as the IBM HTTP Server.
- Internet Inter-ORB Protocol (IIOP) to secure the communications between the portal server and client.
This uses Secure Sockets Layer (SSL) provided by MicroFocus. This secure communication uses public key cryptography.
HTTPS can also be used to secure communication between:
- tacmd Command-Line Interface and the hub Tivoli Enterprise Monitoring Server or portal server.
- Dashboard users and Dashboard Application Services Hub.
- Dashboard Application Services Hub and the dashboard data provider component of the portal server.
- tivcmd CLI for Authorization Policy and the Dashboard Application Services Hub where the Authorization Policy Server is installed.
- Performance Monitoring service provider and Registry Services, Security Services, and OSLC clients.
If an LDAP server is used with either the hub monitoring server or the portal server, SSL can used be used to secure this communication. See the Securing Communications in the IBM Tivoli Monitoring Administrator's Guide.
Parent topic:
Security options