One of Intigua 3.7's available installation formats is as RPMs for installation on a customer-maintained Linux host.
To install Intigua 3.7 on a Linux host:
- Prepare a Linux host with the following minimum specifications:
- Red Hat Enterprise Linux or CentOS 6.5, 64-bit
- CPU: 8 cores
- RAM: 16 GB
- Disk: 50 GB
- For a more detailed spec and optimal configuration, please see the sizing chart here
- Make sure networking is properly configured.
- Make sure the Linux host has the following prerequisites:
- Oracle Java JDK 8 (openJDK is not supported). Once downloaded, install:
rpm -i <package>
- OpenSSL version 1.0.1g (released 4/14) or above
- Install NGINX:
- Create the following file:
- Copy the following in the file, and save it:
yum install nginx
- When NGINX installation is complete, delete the following file (its settings will conflict with those defined by the Intigua RPMs):
- Install the following supplied Intigua RPMs, in the following order:
- In any order:
To install RPMs, run:
rpm -i <package(s)>
You can install all the RPMs in one command. For example:
rpm -i intigua-server-base-*.x86_64.rpm intigua-server-*.x86_64.rpm intigua-connector-installer-*.x86_64.rpm intigua-web-*.x86_64.rpm intigua-va*.x86_64.rpm
Configure a resolving hostname: Intigua 3.7 needs to access its host server by hostname. To enable this:
- Configure a server hostname:
- Log into the server, and open the following file for editing:
- Set the HOSTNAME to the new hostname. For example:
Save the file.
<hostname> is the new hostname. For example:
- Make sure the hostname is accessible by local applications:
If the correct hostname is returned, it is available to applications and you're done with this. Otherwise:
- Check if nss-myhostname is installed. If not, run:
yum install nss-myhostname
and wait for installation to complete.
- Open the following file for editing:
- Find the line beginning with
hosts, and add the new hostname to the end of the line. For example, change
hosts: files mdns4_minimal dns
hosts: files mdns4_minimal dns intigua.example.com
- Again run
hostname -f to confirm that the hostname is successfully resolved.
- Set up the database.
- Log into the Intigua Console and go to Settings > Advanced Settings. Configure the Core server URL: The URL used by endpoint connectors to communicate with the Intigua server. Must be a hostname (not IP address) that is resolvable and reachable from endpoints.
Intigua 3.7 is now installed.