Three ways of deploying TADDM

You can deploy IBM® Tivoli Application Dependency Discovery Manager (TADDM) in a domain server deployment, a synchronization server deployment, or a streaming server deployment. The TADDM servers are different depending on the type of deployment you choose.

Table 1 indicates the TADDM servers and associated databases that are present according to which deployment type you choose.

The synchronization server deployment is obsolete. Therefore, in a new TADDM deployment, use either a domain server deployment or a streaming server deployment. If more than one server is needed, use the streaming server deployment. A synchronization server can be converted to become a primary storage server for a streaming server deployment.

Table 2 indicates the user interfaces that are associated with each TADDM server.

The following definitions describe the user interfaces in more detail:
Data Management Portal
The TADDM web-based user interface for viewing and manipulating the data in a TADDM database. This user interface is applicable to a domain server deployment, to a synchronization server deployment, and to each storage server in a streaming server deployment. The user interface is very similar in all deployments, although in a synchronization server deployment, it has a few additional functions for adding and synchronizing domains.
Discovery Management Console
The TADDM client user interface for managing discoveries. This console is also known as the Product Console. It is applicable to a domain server deployment and to discovery servers in a streaming server deployment. The function of the console is the same in both of these deployments.
Table 1. Servers and associated databases in each deployment type
Deployment type Servers Associated databases
domain server deployment one domain server The domain server has its own database.
synchronization server deployment one synchronization server

A synchronization server deployment also requires one or more domain server deployments, each of which has a domain server.

The synchronization server has its own database.
streaming server deployment at least one discovery server A discovery server does not have a database.
primary storage server The primary storage server has its own database.
one or more optional secondary storage servers The secondary storage servers share the database of the primary storage server.
Table 2. Servers and associated user interfaces in each deployment type
Deployment type Servers Associated user interfaces
domain server deployment one domain server Data Management Portal
Discovery Management Console
synchronization server deployment one synchronization server

A synchronization server deployment also requires one or more domain server deployments, each of which has a domain server.

Data Management Portal
streaming server deployment at least one discovery server Discovery Management Console
primary storage server Data Management Portal
one or more optional secondary storage servers Data Management Portal