Articles in this section

See more

Installing JetPatch Versions Prior to 4.2.8.x using RPM's

Overview

This article covers the installation process for JetPatch versions before 4.2.8.x using RPM packages. 

It includes network requirements, pre-installation configuration, installation of prerequisites, and application setup.

Installing JetPatch Overview

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

The JetPatch server itself should either have internet access or access to a local repo. 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.

Pre-Installation Configuration

Note: these steps assume that this server has internet access (at least initially to install Nginx, PostgreSQL, and JDK/OpenJDK).

Also, disable IPV6 on the JetPatch manager console server

Configure a server hostname 

see article

Installation Process

JetPatch Application Installation

Review Software Requirements (for supported JetPatch OS)

The default installation mount point is /usr/share (cannot be customized)

Prerequisites (internet access recommended):

  • Minimum NGINX 1.26.X (latest stable version supported)
  • Oracle JDK 11 or OpenJDK 11
  • Python3

You can use Yum to install all of these except Oracle JDK. The RPM package for Oracle JDK for Java 11 can be downloaded from the Oracle Java SE website. Alternatively, all prerequisites can also be downloaded from here.

To install the Controller on a new server:

1. Install all dependencies:

  • Java 11 (minimum minor version of 09+). Once downloaded, install:
rpm -i <package>
  • NGINX - Create the following file:  Copy the following in the file, and save it:  Run:
/etc/yum.repos.d/nginx.repo

[nginx-stable]

name=nginx stable repo

baseurl=http://nginx.org/packages/centos/$releasever/$basearch/

gpgcheck=1

enabled=1

gpgkey=https://nginx.org/keys/nginx_signing.key

module_hotfixes=true [nginx-mainline]

name=nginx mainline repo

baseurl=http://nginx.org/packages/mainline/centos/$releasever/$basearch/

gpgcheck=1

enabled=0

gpgkey=https://nginx.org/keys/nginx_signing.key

module_hotfixes=true

yum install nginx

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

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

Install JetPatch RPMs

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

yum install patch

JetPatch installation includes the following RPMs:

  1. intigua-server-base
  2. intigua-server
  3. intigua-connector-<version>
  4. intigua-connector-runtime
  5. intigua-nginx
  6. intigua-web
  7. intigua-python-client

Run the following commands in order:

rpm -ivh intigua-server-base*.rpm

rpm -ivh intigua-server*.rpm

rpm -ivh intigua-connector*.rpm

rpm -ivh intigua-nginx*.rpm

rpm -ivh intigua-web*.rpm

rpm -ivh intigua-python-client*.rpm

Note: 

Do not use wget to copy RPMs

EL9.X are fully compatible with the EL8 RPM packages

Since it is OS-specific, to verify that all RPMs have been installed. Use the following command:

rpm -qa | grep intigua

During installation, you may encounter the following error:

Hostname or IP address must be properly configured.

Before proceeding, please fix this and test your fix by running '/bin/hostname -f'.

If you see this, then please check your /etc/hosts file and verify that the hostname is at the end of the line starting with '127.0.0.1'.

If it's not, then add it and re-try installation with the above yum command.

Note: 1:

The application will take up about ~2GB

If you would like to install each RPM separately, skip the 'intigua-connector-runtime' installation.

Once installed, set NGINX and Tomcat to start automatically

systemctl enable nginx

systemctl enable tomcat

We also recommend enabling chronyd for the time protocol

systemctl start chronyd

systemctl enable chronyd

PostgreSQL Installation

Review PostgreSQL Version Support Table. Amazon RDS and Aurora for Postgres is also OK.

There are two ways for a simple PostgreSQL installation:

  • Using RPMs
  • Using Yum (EL8 Example Only)

JetPatch Application Configuration

Prior 5.0:

  1. Make sure permissions of /usr/share/tomcat/default/conf are 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:

Post 5.0:

  1. Modify the JetPatch server configuration in /usr/share/intigua/services/data/intigua-main/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.
Note: If using a service account, make sure it has access to the postgresql database (psql -h <db_hostname> -p 5432 -U <db_username> <db_name>)
db.url=jdbc:postgresql://localhost:5432/<db_name>

3. Restart Tomcat for versions before 5.0.

systemctl restart tomcat

Restart intigua-main for Post 5.0

docker restart intigua-main

Log in to the JetPatch Console

via Chrome or Firefox browser using https://<DNS Name>/

Note: 1: If there is an issue, please review proxy settings.
Note: 2: If you have your own certificate, see this article.

Next Step

  • Adding Endpoints to JetPatch
  • Alternatively, view this first-time setup video

Troubleshooting

See article

 

Related articles

Comments

0 comments

Please sign in to leave a comment.