Communication Channels and Their Security Configurations
By default, some communication channels are not secure, but you can secure them by configuring channels and transports to use the Secure Socket Layer (SSL) or Transfer Layer Security (TLS) protocol. For information about how to configure a component for secure communication, see the TIBCO Hawk Installation, Configuration, and Administration guide.
For configuration information about specific Hawk Adapters and plug-ins, see the following documentation:
• | TIBCO Hawk SNMP Adapter |
• | TIBCO Hawk Database Adapter |
• | TIBCO Hawk JMX Plugin |
The following diagram illustrates the components and communication protocols in a typical Hawk deployment:
The following table describes the communication channels that can be configured, along with some references to more information, if applicable.
Key |
Communication Channels |
Connection |
Description and References |
||||||||||||||||||
1 |
Web GUI |
HTTPS |
User Interface |
||||||||||||||||||
2 |
API: RESTful |
HTTPS |
OpenAPI |
||||||||||||||||||
3 |
LDAP Authentication |
LDAP/S |
User Authentication |
||||||||||||||||||
4 |
JDBC |
JDBC (Hawk Console):
JDBC (Event Service)
|
Storing Hawk Alerts
Storing Hawk Events and Alerts
|
||||||||||||||||||
5 |
SMTP |
SMTP: TCP |
Alerting |
||||||||||||||||||
6 |
Forwarders
|
Syslog: UDP or TCP (TLS) ULDP (TLS) |
Data forwarding |
||||||||||||||||||
7 |
JDBC |
JDBC:
|
JDBC Adapter to monitor RDBMS databases, tables |
||||||||||||||||||
8 |
SNMP |
SNMP: UDP or TCP |
SNMP Adapter |
||||||||||||||||||
9 |
Hawk AMI Transport:
|
|
TCP Transport offers TLS/ SSL support. For more information, see the TIBCO Hawk Installation, Configuration, and Administration guide. |
||||||||||||||||||
10 |
Hawk Console API Transport:
|
|
TCP Transport offers TLS/ SSL support. EMS transport offers SSL. For more information, see the TIBCO Hawk Installation, Configuration, and Administration guide. |