Performing Post-Upgrade Tasks

You must perform various tasks after upgrading an ActiveMatrix BPM system.

1. Run the nodeutil utility to identify and (if necessary) fix any missing application dependencies.

   See "Missing Application Dependencies" in ActiveMatrix BPM Troubleshooting for detailed information on how to do this.

2. On each machine that is part of the BPM system:
   1. Using a text editor, open the following file:

      CONFIG_HOME\tibcohost\Admin-ActiveMatrixEnterpriseName-ActiveMatrixServerName\nodes\BPMNode\bin\tibamx_BPMNode.tra

   2. Remove the following entry from the java.extended.properties:

      -Dcom.tibco.amf.sharedresource.runtime.core.sv.ems.factory.MessageSenderPool.size=-1

   3. Save the file.
3. If you want to configure BDS to use an external content management system for the case folder feature, see the TIBCO ActiveMatrix BPM Administration guide. By default, this is not configured on upgrade.
4. Update the ec-event-rules.xml file.
   Note: This task is applicable only if you have upgraded from ActiveMatrix BPM version 4.0, or later, to the latest version.

   This task ensures that the doPurgeAudit operation (in the EventCollectorManagementService) purges all process instance-related data when Statistics Collection is disabled.

   Locate the managedobjectlifecycle target in the CONFIG_HOME\bpm\amx.bpm.app\configuration\ec-event-rules.xml file, and replace the existing definition with the following definition:

   <channel name="default_lifecycle" target="managedobjectlifecycle">
       <rules>
          <rule name="BaseLifecycleRule" ruleOrder="1000">
             <filter>
                <messageIds>
                  <messageId>BX_INSTANCE_PROCESS_STARTED</messageId>
                  <messageId>BX_INSTANCE_PROCESS_CANCELLED</messageId>
                  <messageId>BX_INSTANCE_PROCESS_COMPLETED</messageId>
                  <messageId>BX_INSTANCE_PROCESS_FAILED</messageId>
                  <messageId>BX_INSTANCE_PROCESS_FAILED_WHILE_CANCELLING</messageId>
                  <messageId>BX_INSTANCE_PROCESS_CANCELLED_WHILE_CANCELLING</messageId>
                </messageIds>
             </filter>
             <action>
                <messageProcess>TriggerProcess</messageProcess>
             </action>
          </rule>
       </rules>
   </channel>

   Note: The StagingAreaTrigger channel in the ec-event-rules.xml file MUST also contain the BX_TEMPLATE_DEPLOYED messageId. Do NOT delete this channel, nor the BX_TEMPLATE_DEPLOYED messageId in this channel.

   <channel name="default_stagingareatrigger" target="StagingAreaTrigger">
        <rules>
           <rule name="TriggerMessages" ruleOrder="800">
              <filter>
                  <messageIds>
                      .
                      .
                   <!-- BX SC Messages -->
                      .
                      .
                   <messageId>BX_TEMPLATE_DEPLOYED</messageId>

5. If you use the ActiveMatrix BPM SSO certificates in the default keystores (amx-bpm-wss-keystore.jks and amx-bpm-wss-truststore.jks) for SSO authentication, you must manually replace the existing keystores with new, compliant versions that are supplied with ActiveMatrix BPM 4.2. See Replacing the Default ActiveMatrix BPM SSO Certificates.
6. Perform any other relevant post-installation tasks.