Configuring JetPatch 5.0 Migration When Databases Are on Separate Servers

Overview

This document describes how to configure PatchRepositoryDB and IntiguaDB when they are hosted on separate systems during the migration from JetPatch 4.2.8 (monolithic) to JetPatch 5.0 (microservices).

These configuration updates must be completed before executing the migration script (migrate_monolith_to_microservices.sh) that is already covered in the main migration documentation.

When Is This Required?

Follow this document only if:

• PatchRepositoryDB and IntiguaDB or anyone of DB  are running on dedicated or remote database servers

• The databases are not hosted on the JetPatch Manager system

• You want the database connection details to be automatically carried forward during migration

Pre-Requisites

• JetPatch Manager upgraded to 4.2.8

• JetPatch 5.0 deployment package extracted
  (example: jetpatch-deploy-5.0-56)

• Database host, port(5432), credentials confirmed

• Backup of existing configuration files

PatchRepositoryDB Configuration

This must be done before running the migration script

1. Open the following file for example:

   ./jetpatch-deploy-5.0-56/config/conf-service/patch-repository/application.properties

2. Locate the commented properties:

   #spring.datasource.url=
   #spring.datasource.username=
   #spring.datasource.password=

3. Uncomment and update the values with your PatchRepositoryDB details:

   spring.datasource.url=jdbc:postgresql://<PATCH_REPO_DB_HOST>:<PORT>/<DB_NAME>
   spring.datasource.username=<USERNAME>
   spring.datasource.password=<PASSWORD>
   

4. Save the file.

IntiguaDB Configuration

This must be done before running the migration script

1. Open the following file for example:

   ./jetpatch-deploy-5.0-56/config/services/intigua-main/intigua.properties

2. Locate the commented properties:

   #db.url=jdbc:postgresql://<host>:<port>/<database-name>
   #db.username=USER
   #db.password=PASSWORD

3. Uncomment and update the values with your IntiguaDB connection details:

   db.url=jdbc:postgresql://<INTIGUA_DB_HOST>:<PORT>/<DB_NAME>
   db.username=<USERNAME>
   db.password=<PASSWORD>

4. Save the file.

How This Works During Migration

• When the migration script is executed (as documented in the main migration guide):

  • The updated database configurations are automatically detected

  • PatchRepositoryDB and IntiguaDB details are migrated into the JetPatch 5.0 microservices configuration

• No additional manual database reconfiguration is required after migration.

Important Notes

• These changes must be completed before running the migration script

• Skipping this step may result in:

  • Database connection failures

  • JetPatch 5.0 services not starting correctly

• Always back up configuration files before making changes

Related Documentation

• Main Migration Guide:
  Migrating from JetPatch 4.2.8 Monolithic Deployment to JetPatch 5.0 Microservices