How to Patch JetPatch Server Itself

JetPatch server can be added to JetPatch manager console and can be updated as well as others servers.

As always, stay on the safe side of the things, and before updating, we recommend doing a backup or a snapshot. 

And the last, under no circumstances, do not update Tomcat

Step 1: Enable services

Before making any patching activities, need to make sure, the following services are enabled on the JetPatch server:

• Tomcat
• nginx
• PostgreSQL

If the JetPatch server was deployed on 2 different servers, one with the application, and the other one with the database, as long as the services are enabled, it doesn't make any difference.

In order to check if the service is up and running, this command could be run: 

systemctl status <service name>

Step 2: Deploy Connector

On the server (servers), deploy the connector. It can be done differently:

• Push it from JetPatch Manager console;
• Install it from the endpoint itself.

Step 3: Create a Separate Group for JetPatch server

In JetPatch Manager, a new group should be created with JetPatch server in it only (that includes both JetPatch servers if that is the case, as well as the JetProxy if there is one in the environment)

Step 4: Create a Maintenance Window dedicated for patching the JetPatch Server 

Create a maintenance window in separate time slots than the rest of the computer groups. Since most updates require a restart, we don't want such procedure to interfere with ongoing patching activities.