• Spaces
  • Collections
  • Help
    • ×
     
     
    •  
    BMC PATROL for Sybase 20.02

    Page tree

    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.

    Support for third-party products

    To receive full support for a BMC product, you must have that product installed in a supported environment, as specified in the BMC product documentation. If a third-party vendor cancels support for one of its products (such as an operating system or subsystem), and that third-party product integrates or interacts with the BMC product you have licensed, you must upgrade to a supported version of that third-party product before BMC Customer Support can provide you with support for the affected BMC product. For further information, see BMC's product support policy. Open link


    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.1, 64-bit
    • 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 8.x, x86_64
    • Red Hat Enterprise Linux 7.x, x86_64
    • Red Hat Enterprise Linux 6.x, x86_64, zSeries


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

    • IBM AIX 7.x, 64-bit hardware, pSeries

    • Microsoft Windows Server 2019, R2, x86_64
    • Microsoft Windows Server 2016, R2, x86_64
    • Microsoft Windows Server 2012, R2, x86_64
    • Microsoft Windows Server 2008 R2, SP1 64-Bit

    • Oracle Solaris 11.x, x86_64, SPARC
    • Oracle Solaris 10.x, x86_64, SPARC

    • SUSE Linux Enterprise Server 12.x, 64-Bit, x86_64
    • SUSE Linux Enterprise Server 11.x, x86_64, zSeries
    • SUSE Linux Enterprise Server 10.x, SP4, zSeries, x86_64

    BMC TrueSight Operations Management
    • 11.x
    • 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 Open link


    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.
    • (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

    See Determining PATROL security levels.


    • No labels

    3 Comments

    1. ALEJANDRO CORTES

      Hi, Is still supported in BHOM?

      1. Sandip Modi

        Yes, it is still supported in BHOM.

    2. ALEJANDRO CORTES

      Thank you Sandip Modi 

    © Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.