Installing JetPatch Overview
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)
1. Configure a server hostname
- For EL7: set HOSTNAME to the new hostname using the following command
-
hostnamectl set-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, Oracle Linux, or CentOS version 7.x/8.x
Default installation mount point is /usr/share (cannot be customized)
Prerequisites (internet access recommended):
- NGINX 1.21.X recommended (previous stable versions supported - eg: 1.19.X)
- 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 8 can be downloaded from the Oracle Java SE web site. Alternatively, all prerequisites can also be downloaded from here.
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)
ln -s /usr/lib/jvm/java-<version-openjdk-version>/jre /usr/java/default
Replace <version-openjdk-version> with the required OpenJDK Java version (see example below)
Important - the source link (the first path in the "ln" command) should be located just above the Java bin folder.
Example for upgrading to "java-1.8.0-openjdk-1.8.0.265.b01-0.el6_10.x86_64"
ln -s /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.265.b01-0.el6_10.x86_64/jre /usr/java/default
To install Controller on a new server:
1. Install all dependencies:
- Oracle Java JDK 8 (recommended minor version of 251+) or Java 11 (recommended minor version of 09+). Once downloaded, install: Once downloaded, install:
rpm -i <package>
-
- NGINX - Create the following file:
/etc/yum.repos.d/nginx.repo
Copy the following in the file, and save it:[nginx]
Run:
name=nginx repo
baseurl=http://nginx.org/packages/rhel/7/$basearch/
gpgcheck=0
enabled=1yum 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
- NGINX - Create the following file:
Install JetPatch RPMs
Before installing the JetPatch RPMs, verify that patch is installed:
yum install patch
JetPatch installation includes the following RPMs:
- intigua-server-base
- intigua-server
- intigua-connector-<version>
- intigua-connector-runtime
- intigua-web
- intigua-python-client
Learn more on JetPatch RPMs
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-web*.rpm
rpm -ivh intigua-python-client*.rpm
rpm -qa | grep intigua
Hostname or IP address must be properly configured.
Before proceeding, please fix this and test your fix by running '/bin/hostname -f'.
If it's not, then add it and re-try installation with the above yum command.
Notes:
- The application will take up about ~2GB
- If you would like to install each RPM separately skip 'intigua-connector-runtime' installation.
systemctl enable nginx
systemctl enable tomcat
systemctl start chronyd
systemctl enable chronyd
gvi /usr/share/tomcat/service/tomcat.conf
And change the "JAVA_HOME" line to:
JAVA_HOME="/path/to/java/home"
Example:
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
In this example, when the system will use $JAVA_HOME/bin/java it will redirected to the actually binary of Java.
Once edited, restart tomcat
service tomcat restart
PostgreSQL Installation
PostgreSQL: Version 12.X recommended (11-13 supported). Amazon RDS and Aurora for Postgres is also OK.
There are two ways for a simple PostgreSQL installation on Red Hat Enterprise Linux or CentOS:
JetPatch Application Configuration
- Make sure permissions of /usr/share/tomcat/default/conf is all tomcat:tomcat (chown -R tomcat:tomcat)
- 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
NOTE1: If DB is installed on the same server as JetPatch, use localhost instead.
NOTE2: 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
service tomcat restart
Login to the JetPatch Console
via chrome or firefox browser using https://<DNS Name>/
Note1: If there is an issue, please review proxy settings.
Note2: If you have your own certificate, see this article.
Next Step
-
- Adding Endpoints to JetPatch
- Alternatively, view this first-time setup video
Troubleshooting
Comments
0 comments
Please sign in to leave a comment.