Description:
Product Name     : TIBCO ActiveMatrix(R) Platform
Release Version  : 3.3.0_hotfix009
Release Date      : April 2015

================================================================================

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

================================================================================

TIBCO ActiveMatrix(R) BPM 2.2.0, 3.0.0, 3.1.0 and TIBCO Business Studio BPM Edition 3.6.0, 3.7.0, 3.8.0,
3.9.0 Hotfix, TIB_amx_3.3.0_hotfix009, can be downloaded from the TIBCO Product Support file
transfer server, mft.tibco.com, using your username and password for the TIBCO Support Central website.
Please note you should use an FTP or SFTP client or command-line FTP.
TIBCO employees must use a secure protocol.

Server name: mft.tibco.com
Credentials: use your TSC (TIBCO Support Central website) login.
Browser:  https://mft.tibco.com
FTP: port 21
SFTP: port 22

Once logged on you can find the hotfix under:

AvailableDownloads/AMX_BPM/2.2.0/TIB_amx_3.3.0_hotfix009
AvailableDownloads/AMX_BPM/3.0.0/TIB_amx_3.3.0_hotfix009
AvailableDownloads/AMX_BPM/3.1.0/TIB_amx_3.3.0_hotfix009
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.6.0/TIB_amx_3.3.0_hotfix009
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.7.0/TIB_amx_3.3.0_hotfix009
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.8.0/TIB_amx_3.3.0_hotfix009
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.9.0/TIB_amx_3.3.0_hotfix009

================================================================================

Closed Issues in 3.3.0_hotfix009 (This release)

This hotfix contains fixes that apply to the following types of installations:

- Administration
- Runtime Host
- TIBCO Business Studio

AMX-14823
The health of application(s) can now be assessed in terms of their back-end
Services and Shared Resource instances. For additional information, refer to
the TIBCO ActiveMatrix Administration Addendum.

TAP-13892
The date display for node features listed in the 'Feature List' of each node
in the TIBCO ActiveMatrix Administrator UI under Infrastructure > Nodes >
Configuration > Feature tab has changed. For additional information, refer to
the TIBCO ActiveMatrix Administration Addendum.

TAP-13966
Using the TIBCO ActiveMatrix Administrator CLI, features from a TIBCO
ActiveMatrix Runtime Node can be uninstalled or deleted by specifying the
version as a wildcard (*). For additional information, refer to the TIBCO
ActiveMatrix Administration Addendum.

SDS-7115
TIBCO ActiveMatrix Business Studio now supports adding of Features by extending
the Target Platform. As a result, the Debugger can now provision features from the
extended Target Platform. For additional information, refer to the TIBCO
ActiveMatrix Administration Addendum.

SVCP-205
The TIBCO ActiveMatrix Probe for Service Performance Manager can now use the
HTTP "X-Forwarded-For" header from an incoming request to emit statistics about the
Client (sender of the request), regardless of Proxies or Load Balancers being
in the path of invocation. To enable this feature, set the following Java
property in the TRA file for the TIBCO ActiveMatrix Runtime Node on which the
Application is deployed:
java.property.com.tibco.amf.bindingtype.soap.isXFFHeaderPresent = true

AMX-14941
TIBCO ActiveMatrix now supports Internet Explorer version 11.
NOTE: While uploading a DAA file, you may encounter a known issue with
Microsoft Internet Explorer 11. Internet Explorer 11 puts a lock on a file
being uploaded from the file system. Upon completion of the upload, it does
not remove the lock, thus preventing the write/modify/delete operations on
the file. The workaround is to refresh the browser which automatically
releases the lock.

AMSG-9700
Previously, at the end of a typical Export operation, the path where the
exported archive was located on TIBCO ActiveMatrix Administrator's local
file system was provided. With this feature, an additional URL is provided
from where the exported archive can be downloaded. For additional information,
refer to Chapter 1 ("Export and Import") of the TIBCO ActiveMatrix Administration
Addendum.  

SDS-7517, SDS-7520
For TIBCO ActiveMatrix BPM Applications containing Resource Templates, the CLI
Scripts generated from an off-line server contained incorrect references to the
default node named "DevNode". This caused deployment failures in the default
setup, as "DevNode" does not exist in the default setup of a TIBCO ActiveMatrix
BPM environment. With this fix, the default node name can now be overridden
to match your environment, thus preventing deployment failures.  

TAP-14006
In a replicated TIBCO ActiveMatrix Administrator setup, file system writes to
TIBCO ActiveMatrix Administrator Shared Repository were slow, causing product
upgrades to take several hours to complete. With this fix, the file system
writes to the TIBCO ActiveMatrix Administrator Shared Repository are buffered,
thus reducing the total upgrade time by a substantial factor.
        
WSBT-1009
Previously for One-Way operations, TIBCO ActiveMatrix Service Grid 3.3.0
returned a SOAP fault to the invoking client in case of an error. This was not
in strict compliance with the Basic Profile 1.1 Specification. Strict
compliance with this specification was introduced in TIBCO ActiveMatrix Service
Grid 3.3.0 Hotfix 006. However, since certain usecases relied on the optional
faults that were returned originally, this behaviour is being reinstated to
maintain backward compatibility. Strict adherence to Basic Profile 1.1
specification (of suppressing the faults for One-Way operations) can be now be
achieved by setting the following Java property in the TRA file of the TIBCO
ActiveMatrix Runtime Node on which the Application containing the SOAP Binding
is deployed:
java.property.com.tibco.amf.bindingtype.soap.disallowFaultsForOneWayMEP = true

WSBT-1010
In scenarios where the External Providers returned custom fault codes via
Proxy Applications, TIBCO ActiveMatrix Runtime replaced the custom codes with
"Server". This resulted in the end-to-end invocation failing, as the Clients
relied on the specific custom codes. With this fix, the fault code is
transmitted as-is by the Platform, without any modifications.

AMSG-9698
For JMS Service Bindings that contain a single In-Only Operation, the JMS
Message Selector was not applied correctly in the TIBCO ActiveMatrix Runtime.
As a result, messages were not consumed by the JMS Service Binding, causing
a failure. With this fix, the JMS Message Selector is applied correctly for
a WSDL containing single In-Only operation and the messages are consumed by
the JMS Service Binding as expected.

AMRP-4848
Previously, transactions were not committed for the combination of Global
Managed Transaction policy, Threading policy, and Stateless Async policies.
As a result, BPM process instances were not created for the application's
upgraded version. With this fix, the transactions for the combination
mentioned above are committed and BPM instances are created for the
application's upgraded version.

For example, say "version 1" of the BPM process contains an IN-ONLY service
(thus configured with a Transacted One-Way Policy), and "version 2" of the BPM
process contains an IN-OUT service (request and reply, thus configured with
At Least Once policy).

If these steps were followed:
    1) deploy "version 1" of the process
    2) create "n" processes which will remain Active
    3) upgrade to "version 2" of the process
    4) create some more processes

Then, before this fix:
At step 4, if "n" processes were created for "version 1", "n" processes for
"version 2" are not seen. This is because requests were previously being
sent to both processes of "version 1" and "version 2" in a round-robin
fashion. Since "version 1" and "version 2" have different policies,
the requests that went through "version 1" are never committed.

Now, with this fix:
At step 4, if "n" processes were created for "version 1", then "n" processes
for "version 2" are seen, and the transactions are committed as expected.

TAP-13457
Previously, with TIBCO ActiveMatrix Administrator, TIBCO Host or Runtime Node
logs could not be downloaded if the Internal HTTP Connector was secured (HTTPs).
With this fix, the logs can be downloaded in all the scenarios listed below
(for both local and remote host):
- Both Internal HTTP Connector and JMX is not SSL enabled.
- Internal HTTP Connector is SSL enabled but JMX is not SSL enabled.
- JMX is SSL enabled but Internal HTTP Connector is not SSL enabled.
- Both Internal HTTP Connector and JMX are SSL enabled.

TAP-12764
When a substitution variable used by a resource template was deleted and if a
Resource Instance was created, it failed with an unclear error message.
With this fix, the root cause with the correct error message is shown.
This fix is applicable to all resource templates.

TAP-13481
Previously, TIBCO ActiveMatrix Administrator failed to save the default driver
information for JDBC Resource Templates during Resource Instance installation
using Administrator CLI. With this fix, if the default driver information is
provided in the CLI data file of the Resource Instance, then the information is
correctly saved for the corresponding Resource Template. Subsequent Resource
Instances installed from the Resource Template, will now use the provided default
driver.

If the user tries to install a Resource Instance from a Resource Template that
was created prior to TIBCO ActiveMatrix 3.3.0 Hotfix 009, the default driver
information will NOT be saved for subsequent use. In the event that multiple
drivers are available during Resource Instance installation, Administrator will
be unable to resolve which driver to choose (since the information will not be
available), thus causing a failure.

To resolve this Resource Instance installation failure and update the Resource
Template with the default driver information, the user will have to locate the
values for 'driverFeatureName' and 'driverFeatureVersion', and then manually add
'driverFeatureName', 'driverFeatureVersion' and 'setDriverAsDefault="true"'
attributes on all the <ResourceInstance> elements in the CLI data file, as
summarized below.
- To locate the values for 'driverFeatureName' and 'driverFeatureVersion':
  1) Open the following properties file:
  <TIBCO_HOME>/components/shared/1.0.0/plugins/com.tibco.tpcl.gen.<JDBC_VENDOR>.
  jdbc_<VERSION>/META-INF/com.tibco.amx.instantiated.thirdparty.shell/
  com.tibco.tpcl.gen.<JDBC_VENDOR>.jdbc/<VERSION>/shell.instantiated.properties
  2) Find the property named 'instantiated.tpcl.shell.rpfID'. The value for this
  property is a concatenation of the driver feature name and driver feature
  version. For example, in the snippet below:
  instantiated.tpcl.shell.rpfID=com.tibco.tpcl.gen.oracle.jdbc.feature\:11.2.100.001
  the 'driverFeatureName' is "com.tibco.tpcl.gen.oracle.jdbc.feature" and
  'driverFeatureVersion' is "11.2.100.001".        
- To manually add the 'driverFeatureName', 'driverFeatureVersion' and
  'setDriverAsDefault="true"' attributes on all the <ResourceInstance> elements in
  the CLI data file, see CLI data snippet below:
    <ResourceInstance xsi:type="amxdata:ResourceInstance"
        name="oracleResourceInstance"
        resourceTemplateName="oracleResourceTemplate"
        driverFeatureName="com.tibco.tpcl.gen.oracle.jdbc.feature"
        driverFeatureVersion="11.2.100.001"
        setDriverAsDefault="true"/>
- Once the attributes are added on all the <ResourceInstance> elements and Resource
  Instances are installed, the default driver information will be saved for the
  corresponding Resource Template. Subsequent Resource Instances installed from the
  Resource Template, will now use the specified default driver, with a successful
  installation.

PER-2068
A request with WS security header failed if a policy was applied on
the reference endpoint of the application, even when the Java property
'com.tibco.governance.agent.enforce.mustUnderstand' was set to false.
Due to this, a request with the WS security header could not be forwarded.
With this fix, when the Java property
'com.tibco.governance.agent.enforce.mustUnderstand'
is set to false, a request with a WS security header does not fail when
a policy is applied at the service endpoint.
        
PER-2062
When a HTTP request is sent with mutual SSL, the client certificate was added
to the security context cached in the HTTP session. This caused processing
overhead because authentication was done to convert the certificate to an
assertion. With this fix, when a request is sent with mutual SSL, if the
HTTP session already has a valid security context, the certificate from
the SSL is added to that security context thereby reducing the overhead.
            
TAP-14019
The "Work Thread Pool" configuration was missing for a Resource Template in
the exported data file. As a result, "Work Thread Pool" configuration was
missing from the imported environment also. With this fix, "Work Thread Pool"
configuration is exported with a Resource Template, if it is present.
        
TAP-13967
Application deletion failed because orphaned endpoints could not be
deleted. With this fix, orphaned endpoints are handled properly,
and an application can be deleted successfully using the force option.
        
BWSE-3886
After installation of TIBCO ActiveMatrix 3.3.0 Hotfix-008, TIBCO ActiveMatrix
BusinessWorks Service Engine 5.11.0 Hotfix 003 and below could not be correctly
deployed and went into 'Start failed' state. To fix this issue, install
TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0 with Hotfix-005 or above
for use with TIBCO ActiveMatrix 3.3.0 Hotfix-008 or above.  

TOOL-1741
Previously, when TIBCO Configuration Tool (TCT) was launched from the
<TIBCO_HOME>\bpm\3.x\bin directory on the following setup, two options
were not visible in the TCT wizard.
  - TIBCO ActiveMatrix BPM 3.0 or 3.1 Hotfix installed on a
    TIBCO ActiveMatrix BPM 3.0 or 3.1 setup
  - TIBCO ActiveMatrix 3.3.0 Hotfix-006, 007, or 008
The options that were not visible in the TCT wizard were:
  - Upgrade TIBCO ActiveMatrix BPM Instance
  - Configure TIBCO ActiveMatrix BPM Server Node Type
With this fix, the above options are visible in the TCT wizard when TCT is
launched from <TIBCO_HOME>\bpm\3.x\bin directory.

================================================================================

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

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 - TIBCO Business Studio BPM Edition 3.6.0, 3.7.0, 3.8.0, 3.9.0 - TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0 + Hotfix 005 - TIBCO ActiveMatrix Policy Director 1.0.1 + Hotfix 001, 1.1.0 - TIBCO Hawk ActiveMatrix(R) Plug-in for TIBCO Hawk(R) 5.1.1 with TIBCO ActiveMatrix 3.3.0 Hotfix 008 and above. Platforms supported are Microsoft Windows, Linux, and Solaris. NOTE: - 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 009. After Hotfix 009 is applied to the TIBCO ActiveMatrix 3.3.0 installation, it is required that you use TIBCO Service Performance Manager 2.2.0. - 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). - TIBCO ActiveMatrix 3.3.0 Hotfix 009 Administrator and Runtime 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.

TIBCO ActiveMatrix(R) BPM 2.2.0, 3.0.0, 3.1.0 and TIBCO Business Studio BPM Edition 3.6.0, 3.7.0, 3.8.0, 3.9.0 Hotfix, TIB_amx_3.3.0_hotfix009, is now available.

tib_amx_3.3.0-HF_administration_addendum.pdf
tib_amx_3.3.0-HF_installation_addendum.pdf
tib_amx_3.3.0-HF_readme_addendum.pdf
TIB_amx_3.3.0-HF-009_readme.txt