================================================================================
Affected File for 1.4.2 HF003

The following files needs to be installed by this hotfix:

  SilverFabric_tibcoamxbpm_server_container_1.4.2_HF003_gridlib.zip
  SilverFabric_tibcoamxbpm_server_component.type_1.4.2_HF003.zip
  SilverFabric_tibcoamxbpm_runtime_container_1.4.2_HF003_gridlib.zip
  SilverFabric_tibcoamxbpm_runtime_component.type_1.4.2_HF003.zip

Note: This hotfix is not platform-specific.
================================================================================
Closed Issue for SFBP 1.4.2 HF003 (This release)

SFBP-463 Support for patching AMX Hosts to a hotfix  immediately after AMX upgrade to a new version before BPM is upgraded 

The classic AMX/BPM environment upgrade is a two-step process 
1) The AMX environment will be upgraded to the new version 
2) Followed by the BPM environment upgrade to the new version.

Currently, the SFBP enabler automates this two-step upgrade process in such a way that these two steps are performed sequentially one after the other once the upgrade is initiated from Silver Fabric, offering no flexibility to upgrade to an AMX HF before the BPM upgrade is started.
This would cause the entire upgrade to fail in scenarios where the BPM upgrade is dependent on fixes in a particular AMX hotfix. This fix in the enabler helps remove this constraint by allowing AMX to be patched to a hotfix first before starting the BPM upgrade, once the distribution upgrade is initiated from the SFBP enabler.  

For example, let us consider upgrading an existing AMX-BPM environment from AMX 3.3.0 HF23/BPM 4.1.0 to AMX 3.4.0 HF2/BPM 4.3.0.
Note: Before running an upgrade it is required to backup installation files and databases. Some issues during the upgrade can only be resolved by rolling back the environment.

Pre-Upgrade Steps to do:
Note: These steps must be performed on both the BPM Server (regardless of run mode) component and the BPM Runtime component.
Under the component wizard of each of the components,
 1. Update the distribution version on all three components under ‘Choose TIBCO ActiveMatrix BPM Distribution Version:’ menu.
 2. Navigate to ‘Add/edit Container-specific runtime context variables’ menu and add the environment variable ‘ENABLE_PATCHING_AFTER_HOST_UPGRADE’ and set the value to ‘true.’
 3. Navigate to ‘Add, remove, or reorder patches’ menu and add the AMX-3.4.0 HF2 distribution into the component.
 4. Finish and publish the components.

To upgrade AMX 3.3.0 HF23/BPM 4.1.0 to AMX 3.4.0 HF2/BPM 4.3.0 restart the components in the following order:
 1. Restart the BPM Server component in ‘Activematrix Admin Only’ or ‘ActiveMatrix Administrator and Server’ mode. 
 2. Restart the BPM Server component in ‘BPM Server Only’ mode. 
	Note: Skip this step if the component restarted in step 1 is in ‘ActiveMatrix Administrator and Server’ mode and go to step 3 directly.
 3. If you have one or more Runtime components restart all of them one by one.
 4. Restart the BPM Server component (in ‘Activematrix Admin Only’ or ‘ActiveMatrix Administrator and Server’ mode) from step 1 again. This will complete the AMX upgrade to AMX 3.4.0 HF2 and trigger the BPM upgrade to BPM 4.3.0.