Description:
Product Name     : TIBCO ActiveMatrix(R) Platform
Release Version  : 3.1.5_hotfix015
Release Date      : April 2015

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

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

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

This hotfix applies to the following products and versions:

   - TIBCO ActiveMatrix Service Bus 3.1.5
   - TIBCO ActiveMatrix Service Grid 3.1.5
   - TIBCO ActiveMatrix BPM 1.3.X, 2.0.0, 2.1.0
   - TIBCO Business Studio BPM Edition 3.5.3, 3.5.5, 3.5.10, 3.5.20
   - TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.3 + HF-006 or above
     (5.9.3-HF-006 or above is mandatory for use with this hotfix)

NOTE:

TIBCO ActiveMatrix 3.1.5 HF-015 Administrator and Runtime supports JRE 1.8.
Please 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.1.5_hotfix015 (This Release)

This hotfix contain fixes that apply to the following types of installations:
- Administration
- Runtime Host
- TIBCO Business Studio

AMRP-4411
With Java 1.7, a NullPointerException occurred when attempting to commit
a transaction, which caused the transaction to be rolled back. With this
fix, the transaction can be committed as expected, without any errors.

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 being
created for the application's upgraded version. With this fix, the
transactions for the combination mentioned above will be committed
and BPM instances will be 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", then "n" processes for "version 2" will not be
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" will never be committed.

With this fix, at step 4, if "n" processes were created for
"version 1", then "n" processes for "version 2" will be seen,
and the transactions will be committed as expected.

AMRP-4861
With this fix, generic JDBC connection properties such as
defaultRowPrefetch and oracle.jdbc.ReadTimeout can now be
set on an Oracle XA data source.

AMRP-4876
Previously, it was possible that the Transaction Manager
Recovery Module may cancel some of the ongoing transactions.
With this fix, the Recovery Module will no longer interfere
with ongoing transactions.

AMRP-5037
While scheduling a work item in TIBCO ActiveMatrix BPM, the
Process Engine (PE) component sends an EMS message to the
BRM component. This EMS message is lost and as a result, the
work item was never being scheduled. With this fix, the EMS
message will no longer be lost and the work item in
TIBCO ActiveMatrix BPM will be scheduled as expected.

AMX-14943
Threading policy timeout values are set in TIBCO Business Studio
during application design. Per existing system behaviour, no facility was
provided to modify these values during or after deployment time.
A new functionality has been provided that enables certain modifications
to update the timeout values. The units for timeout values must be
specified in milliseconds. This is enabled through a set of modifiable
system properties. The syntax for these properties
is 'java.property.<prefix>.invocationTimeoutInMilliseconds'.
The value of the prefix determines the granularity at which the
timeout values are applied.

The possible values for <prefix> are:
- <applicationName>: applicable for all threading policies inside  
  the application.  
- <applicationName>.<componentName>: applicable for all the
  threading policies defined for a specific component inside
  the application.  
- applicationName.componentName.service: applicable for threading
  policies for all services defined inside <componentName>.  
- applicationName.componentName.reference: applicable for threading
  policies for all references defined inside <componentName>.
- <applicationName>.<componentName>.service.<serviceName>: applicable
  for threading policies defined for service <serviceName> inside
  the application.
  NOTE: The word 'service' is a literal.
- <applicationName>.<componentName>.reference.<referenceName>:
  applicable for threading policies defined for reference
  <referenceName> inside the application.
  NOTE: The word 'reference' is a literal.
To modify timeout values for promoted services or references that
have been set at design time, you must specify the component
service name or component reference name which is promoted.

How to Set the Properties:
    These properties can be changed directly through the TIBCO ActiveMatrix Administrator
GUI or by setting them in the TRA file for the TIBCO ActiveMatrix Runtime Node on which the
application is deployed.
-Node’s TRA File
    1. Set the property in the Node’s TRA file with "java.property" as the prefix.
    2. Re-start the node.
-TIBCO ActiveMatrix Administrator GUI
    1. Navigate to Infrastructure > Nodes.
    2. Select the node on which the application is deployed.
    3. Navigate to Configuration > JVM Configuration. Specify the property name
    without "java.property" as the prefix. Specify the property value.
    4. Perform Install or Sync on selected node.
    5. Stop and start the node.

For example, consider an application with the following details:
- Application name: "weatherApp"
- Application has two Java components: "weatherComponent1" and
"weatherComponent2"
- Component "weatherComponent1" has exposed a component service, "weatherService1"
and a component reference with "weatherReference1"
- Threading policies are applied both at component service and component
reference

The following combination of properties is possible for this example:
- To modify timeout values for all references and services in application "weatherApp":
  weatherApp.invocationTimeoutInMilliseconds = 300
- To modify timeout values for all services and references in component "weatherComponent1":
  weatherApp.weatherComponent1.invocationTimeoutInMilliseconds = 300
- To modify timeout values for all references in component "weatherComponent1":
  weatherApp.weatherComponent1.reference.invocationTimeoutInMilliseconds = 300
- To modify timeout values for all services in component "weatherComponent1":
  weatherApp.weatherComponent1.service.invocationTimeoutInMilliseconds = 300
- To modify timeout value for service "weatherService1" in component "weatherComponent1":
  weatherApp.weatherComponent1.service.weatherService1.invocationTimeoutInMilliseconds = 300
- To modify timeout values for reference "weatherReference1" in component "weatherComponent1":
  weatherApp.weatherComponent1.reference.weatherReference1.invocationTimeoutInMilliseconds = 300
 
BJMS-1578
With this fix, the JMS connection pool will no longer grow beyond
the 'maxsize' as a result of closed idle connections.

DSS-809
TIBCO ActiveMatrix Platform now accepts direct reference to SAML
tokens so as to avoid STR-Transformations.
 
TAP-13123
Previously, with the TIBCO ActiveMatrix Administrator, the
"Save" button on the Upgrade screen could be clicked twice,
which caused two transactions to overlap, with one transaction's
post-commit hook reverting the file system to the older version,
and another transaction changing the Administrator database to
a new version, thus causing them to go out of sync. With this
fix, the overlapping of upgrade transactions is prevented.

TAP-13628
When viewing or rewiring a Reference Virtualization Binding from
TIBCO ActiveMatrix Administrator UI, if the Reference's Target
Service was upgraded with a different name, Administrator failed
to display the Reference "Configuration" screen with a
NullPointerException. With this fix, the Reference "Configuration"
screen is displayed without any errors.   

TAP-13934
In TIBCO ActiveMatrix Administrator, Application upgrade
no longer fails with a ClassCastException if the newer version
of the Application has eliminated the Service and/or Binding that
other Applications were wired to.

TAP-13936
The TIBCO ActiveMatrix Administrator was unable to delete an "Environment"
after applying TIBCO ActiveMatrix 3.1.5 HF14. With this fix,
an "Environment" can be deleted successfully.

TAP-13072
This applies to TIBCO ActiveMatrix BPM. TIBCO ActiveMatrix
Administrator used to incorrectly set the application to
"Out of Sync" after a deploy following an upgrade, where the
new version has fewer components than the previous running
version. With this fix, TIBCO ActiveMatrix Administrator
now correctly sets the application state to "In Sync" after
a deploy.

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

NOTE: See attached Readme document for installation instructions and issues resolved in previous hotfix releases.

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

TIBCO ActiveMatrix(R) BPM 1.3.X, 2.0.0, 2.1.0 and TIBCO Business Studio BPM Edition 3.5.3, 3.5.5, 3.5.10, 3.5.20 Hotfix,
TIB_amx_3.1.5_hotfix015 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 you have successfully logged into the server, you will find the hotfix packages under the following location(s):
AvailableDownloads/AMX_BPM/1.3.0/TIB_amx_3.1.5_hotfix015
AvailableDownloads/AMX_BPM/1.3.1/TIB_amx_3.1.5_hotfix015
AvailableDownloads/AMX_BPM/2.0.0/TIB_amx_3.1.5_hotfix015
AvailableDownloads/AMX_BPM/2.1.0/TIB_amx_3.1.5_hotfix015

AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.5.3/TIB_amx_3.1.5_hotfix015
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.5.5/TIB_amx_3.1.5_hotfix015
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.5.10/TIB_amx_3.1.5_hotfix015
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.5.20/TIB_amx_3.1.5_hotfix015

TIBCO ActiveMatrix(R) BPM 1.3.X, 2.0.0, 2.1.0 and TIBCO Business Studio BPM Edition 3.5.3, 3.5.5, 3.5.10, 3.5.20 Hotfix, TIB_amx_3.1.5_hotfix015, is now available.

Product: TIBCO ActiveMatrix BPM Version: 1.3.X, 2.0.0, 2.1.0 OS: All Supported Operating Systems -------------------- Product: TIBCO ActiveMatrix BPM Business Studio Version: 3.5.3, 3.5.5, 3.5.10, 3.5.20 OS: All Supported Operating Systems

TIB_amx_3.1.5_hotfix015_readme.txt