Additional pre-upgrade step for BPM 3.x to 4.2

Additional pre-upgrade step for BPM 3.x to 4.2

book

Article ID: KB0079097

calendar_today

Updated On:

Products Versions
TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) 3.x, 4.x

Description

Note: This Article only applies to systems being upgraded from BPM 3.x to the following BPM versions:

- 4.2 GA, HF1 or HF2
- 4.1 GA
- 4.0 GA or HF1

During BPM 4.x upgrade process, the task "Wait for empty queues" can fail if

  • BPM Environment's Messaging Bus configuration is wrong in AMX Admin; or
  • BPM Environment is not named BPMEnvironment

Symptoms

TCT log (for Upgrade BPM) will show stacktraces in the "Wait for empty queues" task, followed by:
WARN - Failed getting queue details null

TCT will proceed with the upgrade.
TCT may loop (or even timeout) with an unchanging "pending tasks" count, because BPM Nodes have hang during shutdown/startup.
The upgrade may end with BUILD SUCCESSFUL - but this could give false confidence: upgrading BPM DB schema with a non-empty workqueue may cause database corruption/inconsistency, which can manifest as a variety of seemingly-unrelated errors in the BPM/Node logs.

If your upgrade from 3.x exhibits any of these symptoms:
  1. Revert system to the pre-upgrade backup
  2. Apply the fix described below
  3. Retry the BPM upgrade using TCT

Environment

BPM 3.x, any OS/DB combination upgrading from BPM 3.x to 4.2, or 4.1 (GA), or 4.0 (GA, HF1)

Resolution

To avoid the problem when upgrading to BPM 4.0 or 4.1, install the latest Hotfix (of the target BPM version) before performing BPM Upgrade using TCT.

Note: The fix for issue WRM-9149 is not included in BPM 4.2 GA, Hotfix 1 or Hotfix 2.
Upgrading to 4.2 from BPM 3.x (or earlier) will encounter this problem, whenever the BPM Environment is not named BPMEnvironment

To avoid this problem, edit the following file before running Upgrade BPM wizard in TCT:
TIBCO_HOME/bpm/4.2/scripts/deployer/upgrades/upgrade_1.9.0_build.xml

Copy line 87:
<AmxBpmModifiyObjectParam name="envName" value="${tibco.bpm.environment}"/>
Paste this at line 99, just before:
    </Parameters>
</amx.bpm.ems.queues.task>

Alternatively, just replace that file with the version attached to this Article.

Issue/Introduction

How to avoid upgrade failure when upgrading from 3.x to 4.2, when BPM Environment is NOT named "BPMEnvironment"

Additional Information

Fault reference is WRM-9149 which is addressed in BPM 4.0 Hotfix 2 (& later) / BPM 4.1 Hotfix 1 (& later) but not in BPM 4.2 GA, Hotfix 1 or Hotfix 2
 

Attachments

Additional pre-upgrade step for BPM 3.x to 4.2 get_app
Powered by Wolken Software