Hardware Requirements
Patch Repositories
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.
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
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 EL6 server: Open the following file for editing:
-
/etc/sysconfig/network
-
Within this file, set the HOSTNAME to the new hostname using the following example:
-
HOSTNAME="intigua.example.com"
-
- 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 or CentOS version 7.x.
Prerequisites:
- NGINX 1.16 recommended (1.9 and above supported)
- Oracle JDK 8 or OpenJDK 8 / Oracle JDK 11 or OpenJDK 11 (see RN: https://kc.jetpatch.com/hc/en-us/articles/360025793792-JetPatch-3-9-3-Release-Notes)
- 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. 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)
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>
- OpenSSL. Check current version:
openssl version -a
-
- 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 (Replaces intigua-va from JetPatch version 4.0.1) .
Please Note: intigua-python-client is an optional RPM and does not need to be installed
Learn more on JetPatch RPMs
Run the following command:
yum localinstall -y intigua*.rpm
rpm -qa | grep intigua*.rpm
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
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 11.X recommended (12.X not supported). Amazon RDS and Aurora 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-11.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
- Once edited, run the following commands:
systemctl daemon-reload
/usr/pgsql-11/bin/postgresql-11-setup initdb
systemctl start postgresql-11.service
systemctl enable postgresql-11.service
- 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 and change from localhost to accept all incoming requests):
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
- 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 = '*' - Restart the PostgreSQL service by typing "service postgresql-11 restart” (or the version that is installed)
- 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
- 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
Comments
0 comments
Please sign in to leave a comment.