Description:
SOA or Mediation User Applications when deployed in a BPM Environment are 'Out of Sync', after ActiveMatrix (AMX) BPM has been upgraded from 2.1 to 3.1.

This issue is applicable when all of the following conditions are met -
- When upgrading AMX BPM from v2.1 or lower to v2.2 or higher
- SOA or Mediations apps have SVARs defined at the Environment Scope


Symptoms:
Even after a successful BPM upgrade, the SOA Apps deployed in the same environment are now Out of Sync. Substitution Variables (SVARs) that are being used by SOA Apps, are no longer available on the BPMEnvironment scope.

Cause:
BPM scripts when upgrading to v2.2 or higher move all SVARs from Environment scope to amx.bpm.app scope. This was required to handle the introduction of multi-tenancy. When SVARs are deleted by the upgrade script, any applications using them would become Out of Sync.

TIBCO ActiveMatrix SOA applications may become 'Out of Sync' after a TIBCO ActiveMatrix BPM product upgrade.

After the BPM upgrade completes, the following additional steps are required:

 

1).  Re-add the SVARs to the Environment Scope.

2).  Deploy the user apps. This step will result in the application to be In Sync.

3).  Delete the unwanted SVARs from the amx.bpm.app scope.