Integration Service system requirements

Before installing the Integration Service, review the following requirements:

Hardware requirements

When determining the size of your environment for data event management and impact event management, consider the following hardware requirements for the Integration Service.


  • The recommended hardware requirements are valid, whether you use physical or virtual machines.
  • If you are installing the Integration Service in a virtual environment, ensure to reserve CPU and memory resources.
  • You can install a new version of the Integration Service on the same system as the previous Integration Service, provided the system has sufficient disk space to accommodate both versions.
EnvironmentConfiguration ItemData event management and impact event management


CPU: 2 vCPU, Frequency: 2.2 GHz


4 GB


50 GB of available disk space



CPU: 4 vCPU, Frequency: 2.2GHz


8 GB


50 GB of available disk space



CPU: 4 vCPU, Frequency: 2.2GHz


8 GB


50 GB of available disk space

Operating system requirements

Support for third-party products

To receive full support for a BMC product, you must have such 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

Microsoft Windows

User RightsAdministrative privileges
Supported versions of Microsoft Windows

Microsoft Windows 2019

  • Microsoft Windows 2019 Standard Edition (64-bit)
  • Microsoft Windows 2019 Datacenter Edition (64-bit)

Microsoft Windows 2016

  • Microsoft Windows 2016 Standard Edition (64-bit)
  • Microsoft Windows 2016 Datacenter Edition (64-bit)

Microsoft Windows 2012 

  • Microsoft Windows 2012 R2 Standard Edition (64-bit)  
  • Microsoft Windows 2012 R2 Datacenter Edition (64-bit)
  • Microsoft Windows 2012 Standard Edition (64-bit)  
  • Microsoft Windows 2012 Datacenter Edition (64-bit)  

Microsoft Windows 2008

  • Microsoft Windows 2008 R2 Standard Edition (64-bit)
  • Microsoft Windows 2008 R2 Datacenter Edition (64-bit)
  • Microsoft Windows 2008 R2 Enterprise Edition (64-bit)

Note: For Microsoft Windows 2008 and later, User Access Control must be disabled.


User Rightsroot privileges
Supported versionsof Linux

  • Red Hat Enterprise Linux 6.x and 7.x
  • SUSE Linux Enterprise Server 11.x, 12.x, and 15
  • Oracle Linux Server 6.x and 7.x

UmaskUmask must be set to 022.


On Red Hat Enterprise Linux, the following libraries must be installed before installing the Integration Service.   

The preferred method to add any missing libraries is to use the yum command to fetch the necessary library packages from the RHN (Red Hat Network) repository via the internet.  To use this method, a Red Hat subscription is needed. Register the system by clicking System->Administration->Red Hat Subscription Manager in the menu on the server itself.  After registering the system, you can use "yum install" to download and install the required libraries from the RHN.


Command to install the library on Red Hat Enterprise Linux

Command to install the library on SUSE Linux

libXtst (64-bit)

yum install libXtst.x86_64

glibc (32-bit)

glibc (64-bit)

yum install glibc.i686 glibc.x86_64
zypper install glibc-32bit glibc

libstdc++ (64-bit)

yum install libstdc++.x86_64 
zypper install libstdc++

compat-libstdc++-33 (64-bit)

yum install compat-libstdc++-33.x86_64 
zypper install libstdc++33

compat-libstdc++-296 (64-bit)

yum install compat-libstdc++-296.x86_64


pam (64-bit)

yum install pam.x86_64
zypper install pam
libfreebl3.soyum install libfreebl3.soN/A


  • To avoid errors while installing 32-bit libraries, BMC recommends that you install 32-bit libraries together with the 64-bit libraries.
  • After installing the libraries, run yum check to ensure that the libraries are not corrupt.

Guidelines and limitations for deployment

Follow these guidelines when planning the hardware deployment:

  • The load can be distributed across one or more Integration Services by keeping the total load on the server constant as per the deployment type. You can configure a maximum of 25 Integration Services per Infrastructure Management server.

  • You can configure a maximum of 500 PATROL Agents per Integration Service in a small deployment and 900 in medium and large deployments.
  • To distribute the load, you can configure up to three Integration Services on the same Integration Service host computer. For more information, see Sizing chart for multiple Integration Services running on the same Integration Service host.

Related topics

Was this page helpful? Yes No Submitting... Thank you


  1. Giles Day

    Do the medium and large environment really have same server specs?

    Dec 24, 2019 07:41
    1. Giles Day

      Also, this doesn't mention having java installed as a pre-req.

      Feb 24, 2020 09:57
      1. Harihara Subramanian

        Hi Giles Day,

        Separate Java installation is required only for 11.3.02 and 11.3.03. For all other versions, Java is bundled with a remote ISN installer and no separate installation is required.

        Oct 08, 2020 05:02
    1. Harihara Subramanian

      Hi Giles Day,

      We have different config specs for TSPS and TSIM. On the ISN side, they are both the same. The details are provided just to be consistent with TSPS and TSIM documentation for small, medium, and large.

      Oct 08, 2020 05:01