SNP Glue upgrades are delivered in the same transports as a new installation. To upgrade, you simply need to import the new version using STMS. All created replication objects are preserved during the upgrade.

Glue releases are generally backward compatible, and you don’t need to apply all previous versions (you can skip releases). However, if you are upgrading from an especially old release (e.g., older than 1.5 years), consult with Glue support first.

You should apply the upgrade to your environments as any other SAP change, starting in development, testing your scenario, and then progressing to higher environments. Please note that if you are actively developing new objects, transporting objects might not be possible until the upgrade is finished on all environments (e.g. New replication developed on the Dev system running 2305, can’t be imported to Q and Prod running 2302).

In general, Glue upgrade is fairly easy, takes <1h, and only a few manual activities are involved.

Before the upgrade

Apply these steps before importing Glue transports:

1. Check Glue release notes for breaking changes, known issues, or additional upgrade steps.

2. Stop Glue scheduler /DVD/GLS and any other Glue-related scheduled jobs (legacy schedulers, watchdogs, etc.).

3. Wait for all running jobs to finish /DVD/GL_REQ_MON.

4. Deactivate triggers on /DVD/* tables.

5. Stop the Java connector /DVD/JCO_MNG.

During upgrade

Add Glue transports to the import queue and run the import using STMS.

After the upgrade

After the imports are all successfully finished:

1. Upgrade the Java connector. Follow these steps.

2. Run Process Regeneration on all objects (/DVD/GLUE > Tools > Mass Operations > Process Regeneration).

3. Perform manual upgrade steps for the release from the release notes (if any).

4. Activate triggers that were deactivated before the upgrade.

5. Start the Glue scheduler /DVD/GLS.