Description:
Product Name     : TIBCO ActiveMatrix(R) Platform
Release Version  : 3.3.0_hotfix008
Release Date      : January 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_hotfix008, 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_hotfix008
AvailableDownloads/AMX_BPM/3.0.0/TIB_amx_3.3.0_hotfix008
AvailableDownloads/AMX_BPM/3.1.0/TIB_amx_3.3.0_hotfix008
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.6.0/TIB_amx_3.3.0_hotfix008
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.7.0/TIB_amx_3.3.0_hotfix008
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.8.0/TIB_amx_3.3.0_hotfix008
AvailableDownloads/AMX_BPM/BusinessStudioBPMEdition/3.9.0/TIB_amx_3.3.0_hotfix008

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

Closed Issues in 3.3.0_hotfix008 (This release)

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

- Administration
- Runtime Host
- TIBCO Business Studio

AMRP-5026
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.

For additional information, refer to the TIBCO ActiveMatrix Administration
Addendum.

AMRP-4812
This applies to TIBCO ActiveMatrix BPM. In the BPM node log files,
recurring errors "unique constraint violated" reported for database
table 'BRM_WORK_ITEMS' no longer occur shortly after recovering from
stressed conditions such as database failures. The errors would tend
to fill up the log file and looked like below (example for Oracle database):

ORA-00001: unique constraint (BPMUSER220GAWINDOWS.PK_BRM_WORK_ITEMS)
violated

The errors occurred due to improper duplicate messages delivered by
TIBCO Enterprise Message Server (EMS) to a BPM node, even when another
BPM node had already processed the original messages and created the
work items.

To get this fix, you must use this Hotfix in conjunction with at
least version 7.0.1 or a higher version of the TIBCO Enterprise Message
Server (EMS) that is used for the messaging bus configuration in your
BPM environment.

AMRP-4971
In TIBCO ActiveMatrix Administrator, the node naming syntax did not
allow node names to begin with a digit. This restriction is now relaxed.

AMRP-5008
For certain Implementation Types connected over SOAP/HTTP or SOAP/JMS,
the ActiveMatrix Message flow logger did not log response events when
declared or undeclared SOAP faults were received. This issue has been
fixed.

CL-2699
Use of the JMS Appender with the ActiveMatrix Message flow logger resulted in
high CPU and memory utilization. The JMS appender uses an internal buffer
to store log messages received from the application. Performance is
also affected by the delivery mode; only the persistent mode of
delivery having lower throughput was available.

This has been solved by providing two configuration options to the
user to select two trade-offs:
- Memory consumption versus thread blocking
- Speed versus reliability of message delivery

Specifically, the two configuration parameters are:

Log Buffer Size (logBufferSize="1000") - Upon receiving a burst of
messages, the log buffer can get full and block the application threads
until the buffer is freed. This slows down the logging process.The size
of the buffer should be configured considering the maximum number of
simultaneous messages expected and the heap memory available to the
application.

The default value of this parameter is set to 1000.

Non Persistent Delivery (nonPersistentDelivery="false") - JMS offers
two delivery options, Persistent and Non Persistent. Persistent option
provides reliable delivery, but is slower due to persistence layer. On
the other hand, Non Persistent delivery offers higher speed at the cost
of occasional message loss such as at broker restart. Selection of Non
Persistent delivery option can significantly improve performance.

The default value of this parameter is set to false.

For additional information, refer to the TIBCO ActiveMatrix
Administration Addendum.

DSS-929
In TIBCO Distributed Security Services, a new functionality has been
provided that enables the user to implement a simple in-memory cache
for catching replayed username tokens. The replay stores only tokens
that were sent during the past 300 seconds and a token can be up to
60 seconds in the future. Tokens with Create timestamps outside this
window are rejected as too old or too far in the future. To increase
this window, at the cost of more memory consumption, overwrite any
of the two parameters by setting the following properties in seconds.

java.property.com.tibco.trinity.wss.UT_TTL
java.property.com.tibco.trinity.wss.UT_FutureTTL

To disable the whole username token cache, set
java.property.com.tibco.trinity.wss.NoReplayCacheForTimestamps=true
(case insensitive).

To disable all caches, including the one for signature nonces,
set java.property.com.tibco.trinity.wss.NoReplayCache=true
(case insensitive).

DSS-930
In TIBCO Distributed Security Services, a new system-wide property
has been provided to configure XML Signatures to not use
InclusiveNamespaces construct listing the SOAP-ENV prefix. The
property is provided only for compatibility with any old software
which gets confused by the ec:InclusiveNamespaces construct. To use it,
set java.property.com.tibco.trinity.wss.DontAddInclusivePrefixes=true
(case insensitive).

HKAM-316
In certain cases, TIBCO Hawk microagents monitoring different ActiveMatrix
nodes erroneously showed data for the same specific node. This issue has
been fixed. TIBCO Hawk now monitors the different ActiveMatrix nodes
correctly.

HKAM-319
In certain cases, TIBCO Hawk was not able to load the microagents
for some of the nodes thus preventing their monitoring. The issue has
been fixed and ActiveMatrix monitoring works as expected.

MED-3324
In Mediation Implementation Type, a connection between source and
target operations can be configured to execute data transformation,
routing, and various other operations. In certain situations, upon
restarting TIBCO Business Studio, the connection between
source and target operations was lost. This issue has been fixed.
The connection between source and target operations is now preserved.

PER-1163
In TIBCO Policy Director, a new functionality has been provided for
supporting WSS authentication using Username Tokens with a password
digest mode. The #PasswordDigest format does not send the password.
Instead, it sends a hash of the password, the Nonce, and the Created
time. This, however, requires that that the verifier have access to
the plain text password. When verifying against an LDAP server, this
means you need to log in as an administrative user. Note that the
default policies of many LDAP servers do not permit saving passwords
in clear text whereas some other servers (example Active Directory)
do not provide access to the passwords at all. The Created and Nonce
fields of the Username tokens of type password digest are mandatory.

SDS-7498, SDS-7499
A regression introduced in ActiveMatrix 3.3.0 HF006 caused
TIBCO Business Studio CLI Generation to drop the attribute
'version' for the tag ‘AppTemplate’ and ‘ApplicationTemplate’ in
the configuration file ‘config.xml’. This issue has been fixed.

TAP-13123
In TIBCO ActiveMatrix Administrator, in certain situations during
application upgrade, a race condition caused the new version of
the application template to be removed from the staging area. This
issue has been fixed.

TAP-13327
It was possible to create nodes with invalid names using the
out-of-the-box CLI scripts shipped with the product. An attempt
to install these nodes would subsequently fail.

This issue has now been fixed so that an attempt to create nodes
with invalid names fails immediately. The following constraints
describe valid node names:
- The node name can start with either a letter or a digit (0 to 9).  
- The node name can contain the following punctuations (but cannot start
  with these punctuations):
  a. "."  
  b. "_”
  c. "-"
- The node name cannot end with a period.  
- The node name cannot have two consecutive periods.
- All other punctuations and characters, except for the ones described
  above, are invalid. Node name creation throws an exception for these
  invalid characters.

TAP-13341
TIBCO ActiveMatrix Administrator did not allow nodes with the same name
to be used on same TIBCOHost even if they happened to be on
different environments. This was limiting certain use-cases. This
restriction can now be overcome by setting the following property in the
SystemNode.tra file:

java.property.com.tibco.admin.nodeservice.duplicate.node.name=true

The old behaviour continues to be supported as the default behaviour.
For additional information, refer to the TIBCO ActiveMatrix Hotfix Readme
Addendum.

TAP-13842
When using the Export/Import feature of TIBCO ActiveMatrix Administrator
on Linux systems, the remote_props.properties and build.properties
files generated after the export operation were not usable because
they contained ^M characters. While it was possible to manually edit
and remove these characters, this was unnecessary burden placed on the
user.

The issue is now fixed and users can directly use the generated files.

TAP-13886
An out of memory issue was caused on the System node because of an
uncontrolled growth in the number of HTTP sessions in the HTTP
internal connector. This was due to an effective default value of
infinity for the session time-out. As a result HTTP session objects
did not expire and continued to grow causing a memory leak.
 
The issue has been fixed by setting the default time-out value to the
commonly used 30 minutes thus limiting the number of unused HTTP
sessions.

TAP-13917
Deployment of an application whose reference wire is in a broken
state now gets validated correctly and an error is reported in
TIBCO ActiveMatrix Administrator. Previously, the deployment
proceeded without validation, causing the application to go into
'Waiting for Dependencies' state. An application will have a
broken wire when the wire's target application, target service
or target binding are removed (or undeployed).

For example, say, an application "my.consumer" has its reference
is wired to another application named "my.provider", and
specifically wired to its target service "ValidationService"
via a SOAP binding. Later, "my.provider" is upgraded to a
newer version, but the newer version no longer provided the
"ValidationService". Upgrading "my.provider" will cause the
wire from "my.consumer" to be broken, as you would expect,
indicating that your consumers will no longer work as before.

To fix a broken wire, you will need to wire to another target
service matching your reference contract, or you must modify
"my.consumer" such that it no longer needs to call the
"ValidationService" (and eliminate the reference).

TAP-13934
This applies to TIBCO ActiveMatrix BPM. The product upgrade of
TIBCO ActiveMatrix BPM from 2.1 (or older) to 2.2 (or a newer)
version no longer fails in the presence of a BPM process (user
application) making a web service call to the BPM API (shown
as a wire in TIBCO ActiveMatrix Administrator, originating
from the user application and pointing to the 'amx.bpm.app'
application). The exact error for this upgrade failure used
to be as below, and no longer occurs:

"Caused by: java.lang.ClassCastException: com.tibco.amf.adminmodel.impl.
AmfApplicationImpl cannot be cast to com.tibco.amf.adminmodel.BaseComponent"

TAP-13981
CLI action would fail to load application objects from a
specified application path. This has been fixed by implementing
correct application path parsing logic that supports all legal
formats for application paths.

WSBT-996
SOAP/JMS binding does not formally provide support for topics;
only JNDI-based queues are formally supported as a destination type.
However, for SOAP/JMS reference bindings containing one-way operations
(exclusively), if the JNDI name referred to a topic instead of a
queue, the basic functionality used to work. To prevent this
unintended use, a validation at deployment time resulted in a
deployment failure.

This restriction is now relaxed to support topics in a limited
way. Now, SOAP/JMS reference bindings containing one-way operations
(exclusively) with topics as destinations can be enabled by adding
the following line to the node's TRA and restarting the node:

java.property.com.tibco.amf.bindingtype.soap.suppressTopicUnsupportedError=true

The user is cautioned about the limited support for topics
through the following warning message:

SOAP/JMS Reference Binding "<binding-name>" does not fully
support Topics, but per the user preference, deployment will
continue as this is a Binding containing only ONE-WAY Operations.
This may result in inconsistent or incorrect runtime behavior.
(Specified Topic destination: "<topic-name>").

WSBT-1001
The SOAP Fault messages for ConnectTimeout Exception and
ServiceUnavailable Exception did not have the full contextual
information and hence were not very informative. The SOAP Fault
messages have now been enhanced to include the following contextual
information:
- Reference URL that resulted in the timeout
- Time out value that was in effect
- Name of the originating service
- Hostname where the call originated
- Reference and Reference Endpoint Names
- Timestamp when the timeout occurred

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

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

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_hotfix008, is now available.

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 Policy Director 1.0.1 + Hotfix 001, 1.1.0 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 008. After Hotfix 008 is applied to the TIBCO ActiveMatrix 3.3.0 installation, it is required that you use TIBCO Service Performance Manager 2.2.0. - This hotfix is incompatible with TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0. Do not apply 3.3.0-Hotfix-008 to a TIBCO Host that manages BWSE nodes. A known issue, BWSE-3886, in the TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0 causes the BWSE application to go in 'Start failed' state after this hotfix is applied.

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-008_readme.txt