Configuring TADDM communication

To establish TADDM communication, you must configure all necessary services, connections, and firewalls.

TADDM services

TADDM connectivity can be divided into three areas:

Public connectivity: Public connectivity covers network connectivity that is done from outside of the TADDM infrastructure. For example, Data Management Portal, Discovery Management Console, or API clients, which connect to the TADDM server. It is the highest level of connectivity.
Inter-server connectivity: Inter-server connectivity covers network connectivity between elements of the TADDM core infrastructure, that is, discovery servers and storage servers. It is the middle level of connectivity.
Local connectivity: Local connectivity covers network connectivity between local services on one machine. It is the lowest level of connectivity.

You can configure connectivity for each service during the installation phase, or later by changing configuration properties in the collation.properties configuration file.

Services default interface

To configure services default listen interface, change the com.ibm.cdb.global.hostname property in the collation.properties file.

Table 1. Services default interface settings
Name	Configuration property	Default interface
Global services host	com.ibm.cdb.global.hostname	0.0.0.0

Listen interface that depends on the type of communication

To configure listening interfaces separately for services for each connectivity area, change the appropriate property in the collation.properties file.

Table 2. Services default interface settings
Name	Configuration property	Default interface
Public connectivity services host	com.ibm.cdb.public.hostname	Defined by com.ibm.cdb.global.hostname
Inter-server connectivity services host	com.ibm.cdb.interserver.hostname	Defined by com.ibm.cdb.global.hostname
Local connectivity services host	com.ibm.cdb.local.hostname	127.0.0.1

Note: If no interface is specified or an interface has the 0.0.0.0. value, one local external network interface must be open to communication with itself. If an interface is specified, it must be open to communication with itself.

Listen interface for specific services

You can configure separate TCP port for each service during the installation phase, or later by changing respective property in the collation.properties file.

Service interface configuration

To configure a specific listen interface for each service, change the appropriate property with the host suffix in the collation.properties file.

Example for the TopologyManager service:

com.ibm.cdb.service.TopologyManager.host=192.168.1.5

Note: This naming convention does not apply to public or inter-server service registries.

Service port configuration

To configure a specific listen port for each service, change the appropriate property with the port suffix in the collation.properties file.

The following example is for the TopologyManager service:

com.ibm.cdb.service.TopologyManager.port=9550

SSL service configuration

To configure a specific listen interface or port for each SSL service, change the appropriate property with the secure infix in the collation.properties file.

The following example is for the SecureApiServer service:

com.ibm.cdb.service.SecureApiServer.secure.host=192.168.1.5
com.ibm.cdb.service.SecureApiServer.secure.port=9531

Web portal interface (HTTP and HTTPS) configuration

To configure a listen interface for a web portal (HTTP and HTTPS), change the com.ibm.cdb.service.web.host property in the collation.properties file.

Note: The HTTP and HTTPS host is configured by changing one property in contrast to other services.

Database connections

To configure a specific database connection, change the com.collation.db.port and com.collation.db.server properties in the collation.properties file.

For example:

com.collation.db.port=65432
com.collation.db.server=9.156.47.156

DNS connections

If you want to use fully qualified domain names (FQDN) for communication, ensure that the host that participates in communication can resolve the FQDN from DNS service.

Sensor connections

Configuration of the ports that are used by the ping sensor and the port sensor to make connections is included in the documentation of the ping sensor and the port sensor. Ensure that the ports to the services that you want to discover are opened.

Table 3. Ping Sensor and Port Sensor default ports
Port name	Default port	Protocol
SSH	22	TCP
Telnet	23	TCP
DNS	53	TCP
WMI	135	TCP
PowerShell	5985, 5986	TCP
LDAP	389	TCP
SMB	445	TCP
Oracle	1521	TCP
CiscoWorks	1741	TCP

Anchor connections

TADDM can connect to an anchor server by using one of the following connection types: ssh or direct. To configure a specific anchor connection type, change the value of the com.collation.discover.anchor.connectType property in the collation.properties file to either ssh and direct.

To configure a specific anchor connection type for a particular address, change the com.collation.discover.anchor.connectType property with the IP address as a suffix, in the collation.properties file, for example:

com.collation.discover.anchor.connectType.1.2.3.4=direct

Additionally, port 8497 is defined as the default port for connection to an anchor server. You can configure this port by using the Discovery Management Console.

In ssh mode, open ports for SSH communication on a public interface that is accessed from the TADDM server and from the anchor connection port on a loopback interface on the machine that is hosting the anchor server.
In direct mode, open ports for SSH communication and anchor connection on a public interface that is accessed from the TADDM server.

Gateway connections

TADDM can connect to a gateway server using a SSH connection.

On the gateway, the host SSH port must be open for communication on a public interface that is accessed from the TADDM server.

Resolving a server's host name to a fully qualified domain name

To ensure successful communication between servers, the host server must be able to resolve its host name to a fully qualified domain name (FQDN) by using the operating system's resolver library. One of the following conditions must be fulfilled:

In the search order of the operating system's host resolution, DNS must precede local files. To configure this setting, refer to the operating system documentation.
In the host file, the TADDM server's FQDN must precede the short name.

If neither of these conditions can be fulfilled, you can set the com.collation.serverID property in the collation.properties file to the IP or host name of the TADDM server. Also, ensure that the ServerID in Synchronization Server / Enterprise Server > Data Management Portal > Domain Management > Domain Host Name is set to the same value.

Ephemeral ports

TADDM communication includes the usage of ephemeral ports. These ports are temporary and are specific to an operating system. Each operating system has a defined range of port numbers from which specific ports are chosen randomly. TADDM does not define these ports. For information about the range of ports, necessary configuration and more details, see documentation of the operating system that you use.