Creating a Filter for Environment Level Substitution Variables That Should Not be Moved When Upgrading From a Pre-Version 2.2 ActiveMatrix BPM System

If you are upgrading from a pre-version 2.2 ActiveMatrix BPM system, the upgrade process moves all ActiveMatrix substitution variables from Environment scope to Application scope. If your system also contains any non-BPM applications that use Environment level substitution variables, you need to configure the upgrade process to ignore those variables.

Procedure

  1. Create a new text file, upgrade_1.6.0_svarsFilter.txt, in the TIBCO_HOME\bpm\version\scripts\deployer\upgrades folder.
  2. Add a line-separated list of Environment-scoped substitution variables that you want the ActiveMatrix BPM upgrade to ignore.
    For example, suppose you have a SOA application that uses the HTTP Client resource template. You have defined two Environment-scoped substitution variables - hostSvar and portNo, which are used to define the Machine Name and Port used by that resource template. To ensure that these variables are not moved, save the contents of the upgrade_1.6.0_svarsFilter.txt file as: 
    hostsvar
portNo

Result

When you run the Upgrade TIBCO ActiveMatrix BPM Instance wizard, and upgrade the ActiveMatrix BPM Instance Application, the upgrade process ignores the substitution variables listed in the upgrade_1.6.0_svarsFilter.txt file, leaving them at the Environment scope. An INFO message is written to the upgrade log file indicating which substitution variables were not moved. For example: 
INFO - Processing 35 Environment Level SVARS
INFO - Found environment level SVAR hostSvar in supplied filter file, so skipping.
INFO - Found environment level SVAR portNo in supplied filter file, so skipping.