System requirements

PATROL products

IBM DB2 database version

TrueSight Operations Management

11.x

Operating systems

• Microsoft Windows Server 2022, x86_64
• Microsoft Windows Server 2019, x86_64
• Microsoft Windows Server 2016, x86_64

• Red Hat Enterprise Linux 8.x, x86_64
• Red Hat Enterprise Linux 7.x, x86_64

• HP-UX 11i 31 (B11.31), 64-bit, Itanium 2
• Oracle Solaris 11.x
• SUSE Linux Enterprise Server 12, 15, x86-64
• IBM^® AIX^® 7.x, 64-bit hardware, 64-bit kernel, 64-bit ABI

For SUSE Linux Enterprise Server, references to x86-64 include AMD64 (which includes Opteron) and Intel 64 architecture (formerly known as Intel Extended Memory 64 Technology, or Intel EM64T).

Java Runtime Environment (JRE)

Microsoft .Net Framework (remote computer with Microsoft Windows OS)

.NET Framework 4.0 or later is required on the PATROL Agent system and the remote DB2 system

PowerShell (remote computer with Microsoft Windows OS)

PowerShell 2.0 or later is required on the PATROL Agent system and the remote DB2 system

Ports

If you are migrating a PATROL Agent or console with PATROL for DB2 UDB, you must specify the port number to connect to all the agent computers.

The default port number is 3181.

Minimum hardware requirements

2 CPUs, 4 GB RAM

 OS accounts on UNIX

PATROL account for UNIX (used for PATROL for DB2 installation)

Use the following guidelines when setting up the PATROL UNIX account:

• Create a dedicated user account before you install PATROL. This default account for PATROL can be a local account or a domain account.
• The account .login, .profile, .cshrc, and.kshrc files should not contain any customizations such as aliases, nondefault prompts, or unmask settings other than 022.
• Do not use the root account.
• The account must have permission to create directories and write the installation logs to the $HOME and*/tmp* directories on the computer where you are installing products.
• The account must have access to a root account on the computer where PATROL will be installed.
• (recommended ) Install PATROL on local partitions. If PATROL is installed on NFS-mounted partitions, the root account must have root access permissions on the NFS server.
• If you are installing PATROL to monitor DB2 UDB in a UNIX environment with a large number of physical nodes, you can install on NFS-mounted partitions to reduce the number of installations.

OS accounts on Windows

PATROL account for Windows (used for PATROL for DB2 installation)

Use the following guidelines when setting up the PATROL Windows account:

• Create a dedicated user account before you install PATROL. This default account for PATROL can be a local account or a domain account.
• The account must be a member of the local Administrators group of the computer where the agent will reside.
• The account on a domain controller must be a member of the domain Administrators group.
• Do not use a built-in Administrator account.
• If you are using a domain account, you must specify the Windows NT domain with the user name.
• Stand-alone workgroup servers must use a local user account.
• Servers that are trusted members of a domain can use a local or domain account.
• If an Access Control List (ACL) is used to control access to the PATROL Agent, the default accounts must have C-configure privileges.

OS account for PATROL for DB2 UDB (used for configuration of the instances to be monitored by PATROL). For more information, see User-account-requirements.

Security

Do not use Security level 3 or higher if you are using Enterprise Configuration or the PATROL Advisor. These security levels require passwords to be entered every time the host is accessed.

License

You must have a valid demonstration license (typically good for 30 days) or a permanent license to run your PATROL products. If you do not have a permanent license, contact your BMC Software sales representative or the BMC Software Contract Administration department for licensing information.