System requirements


Note

To get complete compatibility information for BMC PATROL for Sybase, use the BMC Solution and Product Availability and Compatibility Utility on the Product Availability and Compatibility page.

Before installing BMC PATROL for Sybase, verify that the target computer meets the following installation requirements:

Resource

Minimum requirements for full support

Comments

Applications managed by BMC PATROL for Sybase

One of the following applications:

  • Sybase Adaptive Server Enterprise 16, 64-bit
  • Sybase Adaptive Server Enterprise 15.7, 32-bit and 64-bit
  • Sybase Replication Server 15.7.1, 64-bit
  • Sybase Replication Server 15.7.0 with Embedded Replication Server System Database (ERSSD) support
  • Sybase IQ Server 16, 64-bit
  • Sybase IQ Server 15.4, 64-bit
  • Sybase SQL Anywhere 11, 64-bit


Operating system

  • Red Hat Enterprise Linux 7.x, x86_64
  • Red Hat Enterprise Linux 6.x, x86_64 and 32-bit, zSeries
  • Red Hat Enterprise Linux 5.x, x86_64, zSeries

Red Hat Enterprise Linux 7.x is supported up to version 7.6.

The Red Hat Enterprise Linux 7.6 support is available in PATROL for Sybase version 11.0.20 and later.

  • HP-UX 11.31 64-Bit Itanium 2, 64-Bit


  • IBM AIX 6.1, 64-bit hardware, pSeries
  • IBM AIX 7.1, 64-bit hardware, pSeries


  • Microsoft Windows Server 2012, R2, x86_64
  • Microsoft Windows Server 2008 R2, SP1 64-Bit
  • Microsoft Windows Server 2008 Enterprise Edition, 64-Bit
  • Microsoft Windows Server 2008 R2, SP1, 64-Bit, Itanium 2


  • Oracle Solaris 11.2, 64-Bit, SPARC
  • Oracle Solaris 10, x86_64, SPARC
  • Oracle Solaris 11, x86_64, SPARC


  • SUSE Linux Enterprise Server 12.0, 64-Bit, x86_64
  • SUSE Linux Enterprise Server 10, SP4, zSeries, x86_64 and 32-bit
  • SUSE Linux Enterprise Server 11, x86_64 and 32-bit, zSeries


PATROL Agent

PATROL Agent version 9.6.00 or later

 

Other PATROL products

 

BMC PATROL Installation Utility version 9.6.00 or later


Use the following PATROL products to configure and modify BMC PATROL for Sybase:

  • PATROL Configuration Manager 1.7.00 or later
  • PATROL Knowledge Module for Event Management 2.9.00 or later

 

Central Monitoring Administration

  • BMC ProactiveNet Performance Management version 9.6
  • BMC TrueSight Operations Management 9.6
  • BMC TrueSight Operations Management 10.x

 

Java Runtime Environment (JRE)

Supports any of the following Java versions:

  • Oracle Java 8.x
  • OpenJDK 8.x
  • OpenJDK 11.x

Note: For the latest announcement on BMC’s Java Support policies for TrueSight monitoring solutions, see Java support for TrueSight monitoring solutions


Disk space (approximate)

If you are downloading PATROL for Sybase from the Electronic Product Download (EPD) website, the initial EPD image can require up to 13 MB of space. After it is installed and deployed, PATROL for Sybase can use up to 12 MB of space, but will most likely use less than that.

PATROL for Sybase contains separate binary files for each of the UNIX operating systems. As a results, the amount of space necessary on UNIX systems varies. The space given is the maximum amount of space required.

Ports

If you are installing an agent or console with PATROL for Sybase, you must specify the port number to connect to all the agent computers.

The default port number is 3181.

PATROL account for Windows

  • Use a dedicated user account that is created before PATROL is installed. The PATROL default account can be either a local or a domain account.
  • Stand-alone workgroup servers must use a local user account.
  • Servers that are trusted members of a domain can use either a local or domain account.
  • PATROL default accounts cannot exist as a local account and a domain account under the same name.
  • The account on a domain controller must be a member of the domain Administrators group.
  • The PATROL account must be a member of the local Administrators group of the computer where the agent will reside.

Warning: Do not use a built-in Windows domain or local Administrator account as the PATROL default account. Doing so causes files created by PATROL to be owned by the Administrator, which could result in security or file access problems.

PATROL account for UNIX

  • 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 FTP and Telnet enabled.
  • 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.


Security levels


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*