TIBCO Silver(R) Fabric Enabler for ActiveMatrix BPM 1.4.0 HF003 has been released ===================================================================
Affected File for 1.4.0 HF003
The following files needs to be installed by this hotfix:
    SilverFabric_tibcoamxbpm_runtime_container_1.4.0_HF003_gridlib.zip
    SilverFabric_tibcoamxbpm_server_container_1.4.0_HF003_gridlib.zip
    SilverFabric_tibcoamxbpm_server_component.type_1.4.0_HF003.zip
Note: This hotfix is not platform-specific.
================================================================================
Closed Issues in 1.4.0 HF003 (This Release)

SFBP-386 (Customer Reported 01244922)
BPM upgrade failed to upgrade a multi-tenancy set up with more than two
BPM Environments.

SFBP-393
Patching of a BPM Server component failed if it was running in a multi-tenancy
mode. For Patching an existing multi-tenant BPM System, perform the following steps:
1) If the patch is not installed add the BPM distribution patch to the BPM
   Server 1.4.0 HF3 component running in 'AMX Administrator Only' mode.
   If the patch is installed then go to step 3.
2) Restart BPM Server 1.4.0 HF3 component running in 'AMX Administrator Only'
   mode.
3) Add the BPM Distribution patch to the BPM Server 1.4.0 HF3 component running
   in 'BPM Only' mode.
4) Restart BPM Server 1.4.0 HF3 component running in 'BPM Only' mode
5) If there are more than one  BPM Server 1.4.0 HF3 components running in the
   'BPM Only' mode, repeat step 3 and 4.
NOTE:
*BPM distribution patches cannot be downgraded once they are installed in the
 BPM Server 1.4.0 HF3 component running in 'AMX Administrator Only' mode
*BPM Runtime components do not need to install any BPM HF, as they are
 automatically upgraded from the BPM Environment.

SFBP-389 (Customer Reported 01453277)
In a multi-tenant system, when allocating a BPM Runtime component, the custom
WSS keystores and truststores were not being copied to ${FT_DIRECTORY}/keystores
folder. This is a requirement for the BPM System.
When upgrading from existing SFBP 1.4.0 component using any type of SSL
enforcement, perform the  following steps:
1) Upgrade existing SFBP 1.4.0 components, BPM Server and BPM Runtime to SFBP
   1.4.0 HF3, and publish the changes.
2) Edit any BPM Server component running in 'AMX Administrator Only' mode.
   Select the option 'Basic Configuration' from the
   component menu. Skip this step and go to step 4, if you do not have a BPM
   Server component in 'AMX Administrator only' mode.
3) If a component is running in 'AMX Administrator only' mode, provide a
   Fault Tolerance directory such as: /opt/mnt/shared.
 NOTE: If no Fault Tolerance directory is provided, then it is not be possible
       to copy files to the ${FT_DIRECTORY}/keystores directory.
       Example: If the folder /opt/mnt/shared is the selected as the Fault
	        Tolerance directory, the enabler creates a new folder at /opt/mnt/shared/keystores.
	        This is done to have all of the keystores accessible to all nodes in the cluster.
4) Restart the BPM Server component in 'AMX Administrator only' mode or the BPM
   Server component running in 'Administrator and BPM Server' mode.
5) Restart the rest of the BPM components in the cluster
6) Log in to the 'AMX Administrator' webpage.
7) Click 'Infrastructure', then'Nodes' and select the BPM node. Click 'Stop' to
   stop the node.
8) Click on tab substitution variables and change the substitution variables to
   point to the new shared location for keystores and truststore provided in
   step 3.
    Note : Adjust according your own requirements.
    Example: Change the substitution variable tibco.bpm.client.keystore from
             /opt/qa/engine/work/lin64vm348/fabric/bpmkeystore/bpm-keystore.jks
	     to /opt/mnt/shared/keystores/bmp-keystores.jks.
9) Save the changes and start the node that was stopped in step 7.
10) Repeat steps 7 to 9 for all BPM nodes in the BPM Environment until your
    requirements are satisfied.

Known Issues
TAP-14925 - Edit HTTP Connection Settings of HF-14 administrator server using
TCT fails with NPE
NOTE: Restarting the BPM Server component running in 'AMX Administrator only'
      mode using AMX 3.3.0 HF14 fails with a NPE, after applying this HF, if a
      Fault Tolerance directory is provided as in step 3.
Workaround: Do not use AMX 3.3.0 HF14 or do not provide a Fault directory in the
           'AMX Administrator Only' mode.