TADDM server requirements
A TADDM deployment might require several types of servers, depending on the type of deployment you want to use.
Number of servers
- configuration item (CI)
- A component of IT infrastructure that is under the control of configuration management and is therefore subject to formal change control. Each CI in the TADDM database has a persistent object and change history associated with it. Examples of a CI are an operating system, an L2 interface, and a database buffer pool size.
- server equivalent (SE)
- A representative unit of IT infrastructure, defined as a computer system (with standard
configurations, operating systems, network interfaces, and storage interfaces) with installed server
software (such as a database, a web server, or an application server). The concept of a server
equivalent also includes the network, storage, and other subsystems that provide services to the
optimal functioning of the server. A server equivalent depends on the operating system:
Operating system Approximate number of CIs Windows 500 AIX 1000 Linux 1000 HP-UX 500 Network devices 1000
For Level 3 discovery applications, 2000 CIs per SE must be assumed.
Types of servers
- Domain servers
TADDM domain servers discover and track the configuration items (CIs) in your environment. A domain server is part of a stand-alone domain server deployment or a synchronization server deployment.
Each domain server, and its associated database, should be limited to approximately 10,000 SEs (or 10,000,000 CIs). If your environment is larger than this, use multiple servers. You can also improve performance by limiting each server to a few sources and types of discovered data. For example, you might want one server to discover a single type of managed software system regardless of location, rather than organizing the servers according to geography.
Note: The synchronization server deployment type is obsolete. If you need to install a new deployment with multiple servers, use a streaming server deployment.- Discovery servers
Discovery servers discover and track the configuration items (CIs) in your environment. A discovery server is part of a streaming server deployment.
Each discovery server should be limited to approximately 10,000 SEs (or 10,000,000 CIs). If your environment is larger than this, use multiple discovery servers. You can also improve performance by limiting each server to a few sources and types of discovered data. For example, you might want one server to discover a single type of managed software system regardless of location, rather than organizing the servers according to geography.
- Storage servers
Storage servers process the discovery data from discovery servers. A storage server is part of a streaming server deployment.
A streaming server deployment has at least one storage server, called the primary storage server; there might also be additional storage servers, depending upon the size of the environment and the number of items that need to be discovered.
If you are not sure how many storage servers you need, you can deploy TADDM with only one storage server and then add more storage servers as needed to improve performance.
- Database servers
The TADDM database stores the discovered information about configuration items and their relationships, represented using the Tivoli® Common Data Model. Each TADDM domain server or primary storage server has a corresponding database; in a synchronization server deployment, the synchronization server also has a database.
For testing or evaluation purposes, you can install the TADDM database on the same system as the domain server, synchronization server, or primary storage server. However, in production environments, a separate database server is recommended.
- Anchors
If any of the components you need to discover are separated from the TADDM domain server or discovery server by firewalls, you must configure one or more anchors.
To discover components, each TADDM server must communicate with other computer hosts and network devices. If a firewall prevents direct access to certain hosts or devices, you can configure an anchor. An anchor is a TADDM server running on a system that has direct access to the hosts or devices behind the firewall and acts as a proxy to assist in the discovery process.
You do not need to configure anchors during the installation process, but you must include anchors in your installation plan and verify the system requirements for candidate systems. After the installation, you can use the Discovery Management Console to configure hosts to serve as anchors on your network.
- Windows gateways
If your network contains Windows systems, you must specify a Windows system to serve as a gateway server to discover information about the Windows systems that are running in your environment. This gateway server should be in the same firewall zone as the discovered Windows hosts, and must have SSH access from the server.
You do not need to configure Windows gateways during the installation process, but you must include gateways in your installation plan and verify the system requirements for candidate systems. After the installation, you can use the Discovery Management Console to configure hosts to serve as Windows gateways on your network.
An anchor and a gateway can run on the same Windows system.