System requirements

Operating system (OS)

one of the following operating systems:

• HP-UX
• Oracle ^® Solaris
• IBM ^® AIX ^®
• Microsoft Windows
• Linux Red Hat
• Linux SuSE
• CentOS

For a list of the versions of these products that are supported by PATROL for DB2 UDB, see the release notes for the version of PATROL for DB2 UDB that you are using.

Application managed by PATROL for DB2 UDB

one of the following databases:

• DB2 Universal Database EE
• DB2 Universal Database EEE
• DB2 Universal Database ESE

For a list of the versions of these products that are supported by PATROL for DB2 UDB, see the release notes for the version of PATROL for DB2 UDB that you are using.

PATROL products and components

• at least one of the following PATROL consoles:
  • PATROL Console for UNIX
  • PATROL Console for Windows
  • PATROL Central Operator - Microsoft Windows Edition
  • PATROL Central Operator - Web Edition
• PATROL Agent
• PATROL Console Server (if you use PATROL Central)
• PATROL installation utility

For a list of the versions of these products that are supported by PATROL for DB2 UDB, see the release notes for the version of PATROL for DB2 UDB that you are using. Some customizations to the Knowledge Module require the PATROL Console for Windows or UNIX in developer mode. See Determining the version of the installation utility

Browser

Netscape Navigator for UNIX platforms

Install Netscape Navigator on the computer where the PATROL console resides. See Installing the UNIX version of the Help browser

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.

See the following topics:

• Determining the PATROL security levels
• Firewall and port-forwarding considerations.

Optional PATROL products

The following PATROL products are optional:

• Distribution Server
• PATROL Configuration Manager
• PATROL Knowledge Module for Event Management

Distribution Server is required only if you plan to use it to distribute the Knowledge Module (KM). The PATROL Configuration Manager and the PATROL KM for Event Management are required only if you plan to use these products to modify PATROL for DB2 UDB.

Firewalls

See Firewall and port-forwarding considerations.

NA

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.

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 for agent is 3181. See Firewall and port-forwarding considerations.

Required disk space needed to install

130 MB

This number is approximate.

Disk space that is used after installation

20 MB

This number is approximate.

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)

Use one of the following authorizations for the configuration process:

• SYSADM
• SYSCTRL

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 EEE in a UNIX environment with a large number of physical nodes, you can install on NFS-mounted partitions to reduce the number of installations.