It seems you may have completed the following migration steps with a BPM project:
- install a new SAG 9.6 platform (IS+PE+MWS+DB) side-by-side the old 8.2.2 platform
- migrated the old 8.2.2 platform’s data to the new platform
- install the new SAG 9.6 Designer tool
- import the 8.2.2 BPM project to the new 9.6 Designer and updated to the new format as requested
- changed the project’s version number, saved, built and deployed on the new platform
- enabled for execution the new process version and disabled the old version
This should ensure all new instances of the process will be created with the new version.
Depending on certain conditions, existing running process instances of the old version can be still allowed to run to completion using that version’s configuration; those same instances can be upgraded to the new version if specific conditions are met (no missing steps on the new version and others).
However, it seems the migration steps still disregard certain legacy settings which my hinder your successful migration procedures, namely the stricter naming conventions for process names.
To have a better grip on the problem you must go through the following steps:
- capture the broker documents in the broker server using MWS (lock the broker client queue and list its contents - you should save the queue to file)
- list all the conditions the broker trigger
Handle_PCRB_Lots.EarlyLotRelease.Hosting:subscriptionTrigger has (on the Designer - the MWS/broker view will only show you the conditions the broker can handle directly - the IS may be dealing with a larger set)
- compare values of the broker document with those conditions
- you may even debug the trigger, injecting the values you retrieved from the broker queue
You may have more detailed troubleshooting techniques here: https://empower.softwareag.com/sl24sec/SecuredServices/document/java/Troubleshooting/atg/Process_Engine_Troubleshooting.html
POSSIBLE ROOT CAUSE:
I suspect you will find the process new version’s PROCESSKEY will be different from the previous version’s.
That is easily checked in the following places:
- in the created process package in the Integration Server (packages//config/wmprt/*.xml)
- in the PRT database’s table WMPROCESSDEFINITION, the PROCESSKEY field
This is because your process name has underscores in it. It is not an error, and they are allowed (but a small note somewhere warns you should only use alphanumeric characters) but SAG chose to change the way they are encoded from 7.1.2 onwards and versions up to 8.2.1 may have been keeping the compatibility flag without warning.
Before 8.2.2 (and possible even before) the PROCESSKEY of a process would be computed from their name by ‘punyencoding’ following a strategy close to RFC3492, but now they are just simple copied over.
A simple sign is the PROCESSKEY having the form ‘pq__<something similar to the process’ name>__pq’ and not ‘<process’ name>’. See if creating processes with and without underscores ‘_’ makes any difference.
But none of the migration manuals I have read so far explicit warn of this situation.
Now, for the solution I have found (when migrating from 7.1.2 to 8.2.2 but should be applicable here), I’m basing my actions on these references
- make certain you have the absolute most updated fixes on the SAG platform, including Integration Server, Processing Engine, Database configuration, Deployer AND Designer
- Delete the latest version from the database (could be impossible if you have already run new instances) - this means changing table MWPROCESSDEFINITION and others by hand – PROCEED WITH EXTREME CAUTION!
- If that is not possible, start with the db state before migration and migrate it again to the new platform’s db
- add the compatibility flag in the 9.6 Designer and start it.
- for testing the flag is running: create a new empty process with a similar name to the actual process you are dealing, create, build and upload, and check its PROCESSKEY as before
- if the test is satisfactory, proceed with opening the old process, as you already did, converting to the new version, saving, building and uploading