Before installing the Integration Service, review the following 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.
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.
Note
- 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.
| Environment | Configuration Item | Data event management and impact event management |
|---|---|---|
| Small | Platform | CPU: 2 vCPU, Frequency: 2.2 GHz |
RAM | 4 GB | |
Storage | 50 GB of available disk space | |
| Medium | Platform | CPU: 4 vCPU, Frequency: 2.2GHz |
RAM | 8 GB | |
Storage | 50 GB of available disk space | |
| Large | Platform | CPU: 4 vCPU, Frequency: 2.2GHz |
RAM | 8 GB | |
Storage | 50 GB of available disk space |
Operating system requirements
Microsoft Windows
| Component | Requirement |
|---|---|
User Rights | Administrative privileges |
Supported versions of Microsoft Windows |
|
Linux
| Component | Requirement |
|---|---|
User Rights | Administrative privileges |
Supported versions of Linux |
|
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.
Library | Command to install the library on Red Hat Enterprise Linux | Command to install the library on SUSE Linux |
|---|---|---|
libXtst (32-bit) libXtst (64-bit) | yum install libXtst.i686 libXtst.x86_64 libXtst-1.0.1-3.1 libX11-devel-1.0.3-11.el5 | N/A |
glibc (32-bit) glibc (64-bit) | glibc-2.12.x86_64 glibc-2.12-1.107.el6.i686 glibc-devel-2.5-65 | zypper install glibc-32bit glibc |
libstdc++ (32-bit) libstdc++ (64-bit) | yum install libstdc++.i686 libstdc++.x86_64 | zypper install libstdc++-32bit libstdc++ |
compat-libstdc++-33 (32-bit) compat-libstdc++-33 (64-bit) | yum install compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 compat-libstdc++-33-3.2.3-69.e16.i686 | zypper install libstdc++33-32bit libstdc++33 |
compat-libstdc++-296 (32-bit) compat-libstdc++-296 (64-bit) | yum install compat-libstdc++-296.i686 compat-libstdc++-296.x86_64
| N/A |
pam (32-bit) pam (64-bit) | yum install pam.i686 pam.x86_64 pam-1.1.1-13.e16.i686 | zypper install pam-32bit pam |
| libgtk-x11-2 (32-bit) | yum install libgtk-x11-2.0.so.0 | N/A |
| libfreebl3.so | yum install libfreebl3.so | N/A |
Note
- 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 checkto 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.
- 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
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
3 Comments
Michael Ashall
Michael Ashall
Michael Ashall