TADDM server software requirements
Each TADDM server must be running a supported operating system and Java™ runtime environment (JRE). These servers might include domain servers, discovery servers, storage servers, synchronization servers, anchors, and Windows gateways.
- You must install the latest patches and updates from the operating system vendor before installing the TADDM server.
- The server hosts file must include the IP
address and host name of the local system. The hosts file
is in one of the following locations:
- Windows systems: c:\Windows\system32\drivers\etc\hosts
- Linux® and UNIX systems: /etc/hosts
Specify both the fully qualified host name and the short name of the server. The format of a hosts file entry is as follows:ip_address hostname [hostname_2 ... hostname_n] [#comment]
The fully qualified host name must occur before the short name in the hosts file.
Alternatively, you can configure the host name resolution order for your system to use DNS resolution before checking the hosts file. For more information about how to configure the host name resolution order, see the documentation for your operating system.
- The TADDM server supports only the IBM® Java runtime environment (JRE).
- The user ID under which the TADDM server runs must have read, write, and execute permissions for its installation directory and contents, and for the temporary directory of the system. By default, the installation directory is /opt/IBM/taddm on Linux and UNIX systems, or c:\ibm\taddm on Windows systems. Typically, the temp directory is %TEMP% on a Windows system and /tmp on Linux and UNIX systems.
- On UNIX systems, the user ID under which the TADDM server runs must have an open file limit of at least 8192 files. You can set the open file limit using the ulimit command.
- On UNIX systems, the user ID under which the TADDM server runs must have a limit of at least 4096 processes for the maximum number of processes running per user. You can set the limit of the number of running processes using the ulimit command.
- On Linux and UNIX systems, the TADDM server user ID must also have root execution permission for the nmap command. For detailed information about Nmap and the Stack Scan sensor, see Stack Scan sensor.
- On supported AIX® operating systems, you must have the unzip extraction utility available in the /usr/bin or /usr/local/bin directory. If not installed, you must install the extraction utility into one of those directories before beginning the TADDM server installation.
- lsof is required on AIX operating systems. Download it from the AIX Web Download Pack Programs website.
- AIX requires GNU tar version 1.14 or later.
- Discovered systems might be running operating systems and applications that are no longer supported by their vendors. While every effort is made to fix issues encountered on these targets of a discovery, you might have to reproduce the problem on a vendor-supported operating system or application, and use the vendors support.
Operating system and supported release | Support details |
---|---|
AIX 6.1 | Technology Level 5 is required. |
AIX 7.1 | Technology Level 1, Service Pack 2, or later is required. |
AIX 7.2 | Technology Level 0, Service Pack 1, or later is required. |
Red Hat Enterprise Linux 6 x86_64 | Update 1 is required. You must install the libgcc package in version 4.1.2 or later. You must also install ld-linux.so.2 library if it is not installed. Note: TADDM versions 7301 and above require 64 bit package for
libgcc.
You must install the libXft.so.2 library, because it is not installed by default on Linux systems. The Security-Enhanced Linux (SELinux) security system
must be disabled. To disable SELinux specify |
Red Hat Enterprise Linux 6 for SystemZ | |
Red Hat Enterprise Linux 7 x86_64 | You must install the libgcc package in version 4.1.2 or later. You must also install ld-linux.so.2 library if it is not installed. Note: TADDM versions 7301 and above require 64 bit package for
libgcc.
You must install the libXft.so.2 library, because it is not installed by default on Linux systems. The Security-Enhanced Linux (SELinux) security system
must be disabled. To disable SELinux specify |
Red Hat Enterprise Linux 7 for SystemZ | |
Red Hat Enterprise Linux 8 x86_64 | You must install the libgcc package in version 4.1.2 or later. You
must also install ld-linux.so.2 library if it is not installed. Note: TADDM versions 7301 and above require 64 bit package for
libgcc.
The libnsl package for x86_64 architecture must be installed during installation, uninstallation and upgrade process of TADDM. When you are upgrading to TADDM 7.3.0.8, libnsl is not necessary. You must install the libXft.so.2 library, because it is not installed by default on Linux systems. The Security-Enhanced Linux (SELinux) security system must be disabled. To disable SELinux specify
|
Red Hat Enterprise Linux 9 x86_64 | You must install the libgcc package in version 4.1.2 or later. You
must also install ld-linux.so.2 library if it is not installed. Note: TADDM versions 7301 and above require 64 bit package for
libgcc.
You must install the libXft.so.2 library, because it is not installed by default on Linux systems. The Security-Enhanced Linux (SELinux) security
system must be disabled. To disable SELinux specify |
SUSE Linux Enterprise Server 11 x86_64 | Service Pack 1 is required. |
SUSE Linux Enterprise Server 11 for SystemZ | |
SUSE Linux Enterprise Server 12 x86_64 | |
SUSE Linux Enterprises Server 15 x86_64 | |
Microsoft Windows Server 2008 Standard x86-64 Edition, Enterprise x86-64 Edition | Service Pack 2 is required. For Windows gateways, you must ensure that the hotfix at http://support.microsoft.com/kb/2028484 is applied. |
Microsoft Windows Server 2008 R2 Standard x86-64 Edition, Enterprise x86-64 Edition | Service Pack 1 is required. |
Microsoft Windows Server 2012 | .NET Framework 3.5 is required.
Note: If
you use TADDM 7.3.0.2, or later, you can install .NET Framework 4,
and 4.5.
|
Microsoft Windows Server 2012 R2 | .NET Framework 3.5 is required.
Note: If
you use TADDM 7.3.0.2, or later, you can install .NET Framework 4,
and 4.5.
|
Microsoft Windows Server 2016 |
|
Microsoft Windows Server 2019 |