================================================================================
Product Name    : TIBCO ActiveMatrix(R) Platform 
Release Version : 3.3.0_hotfix021 
Release Date    : April 2018

================================================================================
Legal Notice

This Hotfix is provided pursuant to the terms and conditions of the
written maintenance and support agreement between you (or your
company) and TIBCO and use of the Hotfix is controlled by the terms of
such written maintenance and support agreement.

================================================================================
Introduction

Hotfixes are cumulative. This hotfix includes all previous generally
available hotfixes for TIBCO ActiveMatrix(R) Platform 3.3.0.

================================================================================
Applicable Products

This hotfix applies to the following products and versions:

   - TIBCO ActiveMatrix Service Bus 3.3.0 
   - TIBCO ActiveMatrix Service Grid 3.3.0 
   - TIBCO ActiveMatrix BPM 2.2.0, 3.0.0, 3.1.0, 4.0.0, 4.1.0, 4.2.0 
   - TIBCO Business Studio BPM Edition 3.6.0, 3.7.0, 3.8.0, 3.9.0, 4.0.0, 4.1.0
     4.2.0    
   - TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0 + Hotfix 005 (or
     higher).
   - TIBCO ActiveMatrix Policy Director 1.0.1 + Hotfix 001, 1.1.0
   - TIBCO Hawk ActiveMatrix(R) Plug-in for TIBCO Hawk(R) 5.2.0 with 
     TIBCO ActiveMatrix 3.3.0 Hotfix 018 and above. Platforms supported 
     are Microsoft Windows, Linux, and Solaris. For AIX support, refer to the
     "Known Issues" section of the TIBCO ActiveMatrix Readme Addendum.

NOTE: 
- With TIBCO ActiveMatrix 3.3.0 Hotfix 013 and above as the platform, 
  TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0 + Hotfix 006 (or higher) 
  can now use TIBCO Enterprise Message Service(TM) 8.2.2 for TLS 1.2 Support.
- TIBCO Service Performance Manager (SPM) Dashboard, that was originally
  part of TIBCO SPM Server is moved to TIBCO ActiveMatrix Platform, and 
  can now be installed using the TIBCO ActiveMatrix 3.3.0 Hotfix 010 or higher.
- TIBCO Service Performance Manager (SPM) Dashboard supports TIBCO Service
  Performance Manager versions 2.2.1 and 2.3.0.
- Existing TIBCO Service Performance Manager (SPM) Dashboard installations 
  can be upgraded using TIBCO ActiveMatrix 3.3.0 Hotfix 012 or higher. While
  upgrading, the existing Dashboard configuration is used, eliminating 
  the need for reconfiguring the Dashboard. To upgrade, install TIBCO 
  ActiveMatrix 3.3.0 Hotfix 012 or higher on the same <TIBCO_HOME> where the
  Dashboard has been installed. For more information, refer to the "Upgrading 
  TIBCO ActiveMatrix SPM Dashboard" section in the "TIBCO ActiveMatrix SPM 
  Dashboard" chapter in the TIBCO ActiveMatrix Administration Addendum.
- Existing TIBCO ActiveMatrix 3.3.0 customers who have been using
  TIBCO ActiveMatrix with TIBCO Service Performance Manager 2.1.0 are
  affected by Hotfix 010 or higher. After Hotfix 010 or higher is applied to the 
  TIBCO ActiveMatrix 3.3.0 installation, it is required that you use TIBCO
  Service Performance Manager 2.2.1.
- For TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0, HF005
  or above must be installed. TIBCO ActiveMatrix BusinessWorks 
  Service Engine 5.11.0 HF005 fixed issue BWSE-3886 (BWSE 
  application went in a 'Start failed' state after applying 
  3.3.0 Hotfix-008).
- The Administrator and Runtime for TIBCO ActiveMatrix 3.3.0 Hotfix 009
  and higher support JRE 1.8. Refer to the TIBCO ActiveMatrix Updater Tool for 
  Java Runtime Environment (JRE) Documentation to update the 
  JRE version to JRE 1.8.


================================================================================
Closed Issues in 3.3.0_hotfix021 (This release)

AMRP-5207    
Previously, running the "tibcohost spawn" command with the -clearCache option
resulted in the following error:
"Error reading tibcohost.tra file
TIBCO-AMX-HPA-CLI-000141: The tibcohost process failed to start. OS exit code 0. 
Try calling the tibcohost executable directly with the argument --debug to 
collect more information. Verify the location and accessibility of the JVM 
library in error."
With this fix, the "tibcohost spawn" works with the -clearCache option
as expected. The command successfully spawns the tibcohost in the background even 
when the -clearCache option is used. 

PD-4187
Previously in TIBCO ActiveMatrix Administrator configured with TIBCO Policy Director 
(PD), if the user ran the Sync utility located at 
<TIBCO_HOME>/administrator/3.3/scripts/governance/util/sync (executing delete and 
sync actions for Governed Objects), the Governed Objects of type "AgentInstance" 
were not being synchronized for Platform Applications "com.tibco.amx.platform" of 
each of the Runtime Nodes after the sync action. This was due to the fact that the 
utility iterated over all the level 1 Application Folders (such as "System"), and 
that the Platform Application is by default inside the Application Folder 
"System/amx.platform.apps", that is, level 2. This resulted in policy deployment 
failure with the error "Failed to resolve agent instance".

With this fix in Administrator when user runs the Sync utility, the data of all 
ActiveMatrix Administrator Entities gets collected by recursively traversing all 
Application folder levels, thus synchronizing the "AgentInstance" Governed 
Objects for Platform Applications.

PD-4250    
When creating a Proxy Application from a Concrete WSDL that contains <soap:header> 
elements in <wsdl:input> and <wsdl:output> messages in addition to <soap:body>, 
Message Context Parameters are created for each <soap:header> to map the messages.
In case a <wsdl:input> or <wsdl:output> message contained multiple headers 
referring to the same message (albeit different parts) as shown below, duplicate 
Message Context Parameters were being generated in the Proxy Application's 
composite. 

<wsdl:output>
    <soap:body parts="bodyPart" use="literal"/>
    <soap:header message="tns:headerMessage" part="header1" use="literal"/>
    <soap:header message="tns:headerMessage" part="header2" use="literal"/>
</wsdl:output>

As seen in above example, both <soap:header> elements point to the same <message> 
"tns:headerMessage".

This resulted in a failure to process the <soap:header> at runtime, which in turn 
caused the Proxy Application to not propagate the Headers received from the external 
service back to the invoking client.

With this fix, the Message Context Parameters generated for the Proxy Application 
are unique, thus addressing the issue of missing Headers.

PD-4261
Previously in TIBCO ActiveMatrix Administrator configured with TIBCO Policy Director 
(PD) when a dynamic Object Group was created and the initial list of members was 
added to the Object Group, it was observed that after an unknown duration of time, 
any new members that match the criteria of the Object Group were not being added to 
the existing or newly created Object Group(s). This was because the internal Governed 
Object cache did not get updated for the newly deployed Application due to the SQL 
error "ORA-01795: maximum number of expressions in a list is 1000". The Object Group
members are calculated based on this Governed Object cache.

With this fix, the issue is no longer seen and the expected members that match the 
criteria are seen in the Object Group. Above SQL error is also no longer seen.

PD-4307    
Previously in TIBCO ActiveMatrix Administrator configured with TIBCO Policy Director 
(PD), removing an Application from an Object Group did not remove the Governance 
Control on the Application, especially if there was another Application on the same 
Node that had the same Governance Control. As a result of the Governance Control 
still being present, the policy was still being incorrectly enforced on the removed 
Application, resulting in erroneous behavior.

With this fix, the underlying database entries are now being correctly updated for 
the removed Application and consequently, the policy will no longer be enforced on 
the removed Application. 

TAP-15374    
Previously in TIBCO ActiveMatrix Administrator, when a JVM argument was set with 
blank value for a Node, such as the following line in node_data.xml when using 
Administrator CLI approach:
jvmArg="-Damx.securitymanager.enabled="

the "Install or Sync" action failed with the java.lang.StringIndexOutOfBoundsException 
exception.

With this fix, the Node performs the "Install or Sync" action correctly without any
JVM arguments.
================================================================================

See attached Readme document (TIB_amx_3.3.0-HF-021_readme.txt) for installation instructions
and issues resolved in previous hotfix releases.

The TIB_amx_3.3.0_hotfix021, can be downloaded from the SFDC Customer Portal Web User Interface
using your username and password for the TIBCO Support Web.

Once logged on you can find the hotfix under the Downloads Menu:
AvailableDownloads/BusinessWorks/BW_Service_Engine/5.11/TIB_amx_3.3.0_hotfix021


You can also download the hotfix by clicking on the below link:

https://support.tibco.com/s/hotfixes?id=a011a000009RxYZAA0