Hardware Requirements

See article

Network Port Requirements

PostgreSQL

Port 5432 needs to be open so that the JetPatch server can connect to it (or this may be changed to your preference).

JetPatch Server

Port 443 should be opened for the UI and also for access by managed servers. When managed servers cannot find the JetPatch server at port 443, communication will be attempted using other methods as described above.

Active Directory Server

Port 636 (for TLS-secured connection) or 389 (for non-TLS) should be open on the Active Directory server, for access from the JetPatch  server. The port numbers can be changed if needed.

Public Cloud API Access

When managing servers in a cloud environment such as AWS or Azure, and having these servers discovered by JetPatch, appropriate network access must be open from the JetPatch servers into the API endpoints of the relevant public clouds.

Pre-Installation Configuration

1. Configure a resolving hostname: JetPatch 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:

       /etc/sysconfig/network

     • For RHEL server: Set the HOSTNAME to the new hostname using the following example:

       HOSTNAME="intigua.example.com"

     • For CentOS server: set HOSTNAME to the new hostname using the following example

#hostnamectl set-hostname intigua.example.com

1. • • Save the file.

     • Run:

       hostname <hostname>

       where <hostname> is the new hostname. For example:

       hostname intigua.example.com

   • Make sure the hostname is accessible by local applications:

     • Run:

       hostname -f

       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 the installation to complete.

     • Open the following file for editing:

       /etc/nsswitch.conf

     • 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

     • to
       

       hosts: files mdns4_minimal dns intigua.example.com

     • Again run hostname -f to confirm that the hostname is successfully resolved.

Installation Process

JetPatch  Application Installation

The JetPatch server runs on Red Hat Enterprise Linux or CentOS version 7.x.

Prerequisites: NGINX 1.16 recommended (1.9 and above supported), Oracle Java SE Development Kit (JDK) 8, and OpenSSL 1.1.1 recommended (1.0.1 or later supported). You can use Yum to install all of these except Oracle JDK. The RPM package for Oracle JDK for Java 8 can be downloaded from the Oracle Java SE web site. Our support team can help obtain the latest prerequisite installers if needed.

Note: If OpenJDK is used instead, a softlink between /usr/java/default must be created to the jre (eg: /usr/lib/jvm/java-version-openjdk-version)

mkdir /usr/java/default
ln -s /usr/lib/jvm/java-version-openjdk-version /usr/java/default

To install Controller on a new server:

1. Install all dependencies
   • Oracle Java JDK 8. Once downloaded, install:

     rpm -i <package>

   • OpenSSL. Check current version:

   • openssl version -a

1. • NGINX - Create the following file:

     /etc/yum.repos.d/nginx.repo

     Copy the following in the file, and save it:

     [nginx]
     
     name=nginx repo
     
     baseurl=http://nginx.org/packages/rhel/7/$basearch/
     
     gpgcheck=0
     
     enabled=1

     Run:

     yum install nginx

     When NGINX installation is complete, delete the following file (its settings will conflict with those defined by the RPMs):

     /etc/nginx/conf.d/default.conf

Before installing the JetPatch RPMs, verify that patch is installed:

 yum install patch

The RPMs should be installed in the following order:

1. intigua-server-base
2. intigua-server
3. intigua-connector-<version>
4. intigua-connector-runtime
5. intigua-web
6. intigua-va

Run the following five commands in order:

rpm -i intigua-server-base-*.x86_64.rpm 
rpm -i intigua-server-*.x86_64.rpm 
rpm -i intigua-connector-*.x86_64.rpm 
rpm -i intigua-web-*.x86_64.rpm 
rpm -i intigua-va*.x86_64.rpm

Note: the application will take up about ~2GB.

vi /usr/share/tomcat/service/tomcat.conf

From :
JAVA_HOME=/usr/java/default

To :
JAVA_HOME=/usr

Once edited, restart tomcat

service tomcat restart

PostgreSQL Installation

PostgreSQL: Version 10.X recommended (11.X and 12.X not supported. 9.5 and 9.6 OK). Amazon RDS for Postgres is also OK.

Here are the steps for a simple PostgreSQL installation on Red Hat Enterprise Linux or CentOS:

Install the PosgreSQL server by using yum or downloading directly.
See instructions for yum install at: https://wiki.postgresql.org/wiki/YUM_Installation
Or see RPMs at: https://yum.postgresql.org/rpmchart.php (then use the yum tutorial for the initialization of the DB).  If needed, PGSQL path change:

Go to custom mount point (eg: /u01) and  create a folder pgsqldata with postgres permissions

cd /u01
mkdir pgsqldata
chown postgres:postgres pgsqldata

systemctl edit postgresql-10.service

• Go to the custom mount point that has the majority of the disk space
• copy and paste the following into that file:

[Service]
Environment=PGDATA=/<custom mount point>/pgsqldata

• Modify the pg_hba.conf file in /<custom mount point>/pgsqldata/ to define what authentication method should be used from all networks to the PostgreSQL server and modify the localhost authentication method (change from indent to md5):

From
# IPv4 local connections:
host    all             all             127.0.0.1/32            ident

to
# IPv4 local connections:
host    all             all             0.0.0.0/0            md5

1. Modify the postgresql.conf (also in /<custom mount point>/pgsqldata/ ) file to allow connections from all hosts by uncommenting the following and adding an * instead of localhost:
   listen_addresses = '*'
   
   
2. Restart the PostgreSQL service by typing "service postgresql-10 restart” (or the version that is installed)
   
   
3. Create an empty database for JetPatch, and a user with full access to it:
   

   su -c "createuser --pwprompt <username>" postgres
   su -c "createdb -O <username> <dbname>" postgres

In a production environment, you should also set up TLS-secured communication, and you should consider setting up data replication or snapshot-based backups. Consult the PostgreSQL online manual for these settings.

JetPatch Application Configuration

1. Make sure permissions of /usr/share/tomcat/default/conf is all tomcat:tomcat (chown -R tomcat:tomcat)
2. Modify the JetPatch  server configuration in /usr/share/tomcat/default/conf/intigua.properties to configure the connection to the PostgreSQL server:

db.databasePlatform=org.eclipse.persistence.platform.database.PostgreSQLPlatform
db.driver=org.postgresql.Driver
db.url=jdbc:postgresql://<db_hostname_or_ip>:5432/<db_name>
db.username=<db_username>
db.password=<db_password>
db.showSQL=false 

NOTE: If DB is installed on the same server as JetPatch, use localhost instead.

db.url=jdbc:postgresql://localhost:5432/<db_name>

        3. Add the following lines in intigua.properties

db.limit.AgentTaskItem=100000
db.limit.LogEntry=100000

       4. Restart tomcat 

service tomcat restart

       5. Access the application on web browser (chrome and firefox) on port 8080.  Note: if there is an issue, please review proxy settings and port  8080 restriction