Installation requirements

There are a few things to check on your side before you install the Integration Agent.

Supported operating systems

The Integration Agent supports the following operating systems:

Platform Manufacturer OS Description
64-bit AMD, Intel Windows

Server 2008 R2, Server 2012 R2


Various, including Red Hat / CentOS 6 and 7

Sparc Sun Solaris 10
Itanium HP HPUX


For HP-UX Itanium deployments, check the comments in the wrapper.conf file for more information.

POWER Processor IBM AIX 7.1

Things to set up or have at hand during the installation and configuration

Item Description
User account A user account on the server where you plan to install the Integration Agent. On Windows, this account must have permissions to create Services.
Hard disk space 500+ MB of free disk space
RAM 640+ MB of available memory
Proxy server setup If you want the Integration Agent to communicate with xMatters via a proxy server, make a note of your proxy server's IP address or hostname, port, and authentication details. If your proxy server uses NTLM v1 authentication, note the domain name to use for the proxy server (NTLM v2 is not currently supported).
Server hostname/IP Hostname or IP address of the Integration Agent server.
TCP ports

A free TCP port on the server for each of the following components:

  • Integration services (default: 8081)
  • IAdmin (default: 8082)
  • APClient (default: 2010)
  • Internal message broker (default: 61618)

We refer to some of these ports in our instructions. If you change the port, remember to replace the default port with the port you're using.

SMTP server details (if Health Monitor is enabled) If Health Monitor is enabled, you need the hostname/IP address and port (default is 25) of an SMTP server reachable without user/password authentication by the server where the Integration Agent is installed.
Email address (if Health Monitor is enabled) If Health Monitor is enabled, you need to provide the email address of the person who you want to receive Health Monitor messages from the Integration Agent.
X.509 certificate (if SSL enabled) If SSL will be enabled for integration services and the installed default self-signed certificate is not sufficient, an X.509 certificate in a keystore file is required.