Description:
Product Name     : TIBCO ActiveMatrix(R) BPM
Release Version  : 2.2.0_HF-002
Release Date      : July 2014

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

Hotfixes are cumulative. This hotfix includes all previous generally available
hotfixes for TIBCO ActiveMatrix BPM 2.2.0. It includes the issues listed in the
Closed Issues section.

TIB_amx-bpm_2.2.0_HF001_addendum.pdf is available with this release. It is
located in TIBCO-HOME/bpm/2.2/doc/addendum.

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

Applicable Products

This hotfix applies to TIBCO ActiveMatrix BPM 2.2.0.

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

Closed issues in 2.2.0_HF-002 (This Release)

WRM-7009
TIBCO ActiveMatrix BPM displays the following Java linkage error when a user
application deploys a BDS bundle that provides duplicate packages:

java.lang.LinkageError: loader constraint violation: loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader)
previously initiated loading for a different type with name "com/tibco/n2/common/api/exception/ErrorLine"

WRM-6959
If EMF has not had a class registered, when it is serialized it can cause rogue
xsd:type="xsd:anyType".                     

WRM-6892
Remove virtualize policy on ProcessManager service.

WRM-6869
Missing class when using SSL enabled LDAP in association with LDAP Referral.

WRM-6773
Preview is not shown in Workspace and Openspace when a work-item is allocated
to a resource and was offered via RQL.

WRM-6716
Inactive organization model deployments are not removed on upgrade to TIBCO
ActiveMatrix BPM 2.2.

WRM-6610
TIBCO ActiveMatrix BPM 2.2.0 Hotfix installers should have profile selection in
the silent install files.

WRM-6609
Ensure that security context for OOSM has principals set if credentials are
missing.

WRM-6597
Upgrading from TIBCO ActiveMatrix BPM 2.2.0 + TIBCO ActiveMatrix Platform
3.3.0 Hotfix 002 to TIBCO ActiveMatrix BPM 2.2.0 Hotfix 001 fails with
error ": java.lang.ArrayIndexOutOfBoundsException".

WRM-6595
Upgrade to TIBCO ActiveMatrix BPM 2.2.0 is not idempotant when moving SVARS
from env to node.

WRM-6531
AsyncReschduleWorkItem API doesn't halt process instance for design style
failures.

WRM-6522
Preview is not shown in WorkSpace and OpenSpace when a work-item is allocated
by administrator user having privileges for Allocate WorkItem to the World.

WRM-6462
Reduce transactions used when BRM processes asynchronous messages, for example  
group management, scheduling work items and responding.

WRM-6403
Fixes to the following issues to the OOSM processing in BRM:
1. If an asynchronous schedule fails its transaction is always rolled back to
be retried by EMS. There is no need to write an OOSM for a failed schedule.
Originally this was checked for a cancel and if found the cancel was thrown
away. Cancel will be retried by the work item event thread later, after EMS
has retried the schedule until it fails or succeeds.
2. If a cancel is successfully run then it needs to remove all OOSMs that
might exist for the work item, not just the CANCEL_WORK_ITEM one.
3. If an exception, e.g. NullPointerException, is generated when a work
item event is being processed then the event will not be updated to indicate
that it has been attempted once. This means that the event will be retried
indefinitely. All exceptions should be caught and logged/written to Event
Collector so that the event will only be retried once more, in 20 minutes
time. OutOfSequenceException is already catered for in that the event gets
updated.
4. Only an OutOfSequenceException exception (missing work item) on
rescheduleWorkItem() will result in an OOSM being generated. All other
exceptions result in the transaction being rolled back. The
rescheduleWorkItem() method should behave (code-wise) the same as the resume
and suspend ones.

WRM-6391
SOAP API calls fail if ProcessManager and WebComponents logical nodes are not
co-located.

PVM-607
Force undeploy fails with
com.tibco.pvm.db.common.dao.util.fault.IpmPersistenceFault error.

PVM-606
Create a background job to handle potentially "lost" messages.

PVM-594
Bulk cancel of Inline subprocess is not working.

PVM-591
Stop processing work items after the engine shutdown.

PVM-587
Incrementally lower the priority of the process events whose module is not
ready.

PVM-579
Selecting non-existent user defined attributes with queryProcessInstances
should return results matching the filter with null value for the
non-existent user defined attributes.

PVM-560
Workaround to handle retry of start and the completion events of process
instances that failed with EC exception during the EMS failover.

PVM-537
TibQinException causing a NPE blocking the engine resumption after N2LF/EC
issue with EMS connection exception.

PVM-531
Disable lockOnInsert property for Quartz scheduler on SQL Server to help with
performance of scheduling and canceling timers.

OS-2443
Mobilespace CSS causing rendering issues in Forms.

FORM-6469
JSONP request need higher/configurable timeout.
The default timeout is increased to 1 minute. The timeout can also
be configured using the two URL parameters tibco_jsonp_tinterval and
tibco_jsonp_tmrc. The parameter tibco_jsonp_tinterval refers to the
number of seconds the timer need to wait before checking the status
of the request whereas tibco_jsonp_tmrc refers to the number of times
it need to execute the check. Thus if tibco_jsonp_tinterval set to
500(default) and tibco_jsonp_tmrc is set to 120(default), the JSONP
request will timeout in 120 * 500 = 60,000 ms i.e 1 minute.

FORM-6456
Support for iOS7 on Mobile Forms.

FORM-6441
'Always rendered' grid pane throws an error when adding a new row if the
'invisible' property is configured to be handled by the component.

FORM-6424
[Custom Controls] getFormattedValue() on the wrapper need to be invoked
when complex properties of the custom control are updated.

FORM-6302
Not able to remove the last element from the grid pane list when the element
is removed on a UI event of a bound control on that row.

BX-3278
BX related changes for the following - Force undeploy fails with
com.tibco.pvm.db.common.dao.util.fault.IpmPersistenceFault error.

BX-3273
Make locking operation on retry when receiving/retrieving a message optional.

Locking is enabled by default. Disabling it will help to avoid database row
lock contention when dealing with high volumes of correlation and event
handlers. It might introduce delays in processing messages when a message
being is delivered at the exact same time as a corresponding receiver task.

To disable locking system-wide set com.tibco.bx.lockOperation to false.
If locking is disabled then a background job that checks the messages that
have not been claimed yet will be started. To control its execution frequency
set com.tibco.bx.bpel.bg.unclaimedMsgProcessor.interval (default is 30
minutes, lowest possible value is 15 minutes - P15).

If system-wide locking is enabled then
com.tibco.bx.lockPerOperation=true can be used to enable finer-grained
control by using the following properties:
* module level: com.tibco.bx.lockOperation.ModuleName - if this property
is defined (whether it is true or false) then the operation level property
is not going to take effect.
* operation level:
com.tibco.bx.lockOperation.ModuleName.PortType.OperationName
(where PortType is in the form of {NamespaceURI}localPart).

Important: The background job will not be running when system-wide locking
is enabled, which introduces a possibility of an unclaimed message and a
stuck instance in case of concurrent processing as mentioned above.

BX-3231
Workspace process view takes too much time to load (due to performance of
process manager listProcessInstanceAttributes and queryProcessTemplates
operations).

BX-3216
Fix the waiting receiver cleanup on resume of halted instances.

BX-3170
Log entry and exit points for every public Process Manager API.

BX-3119
Database exception on the service virtualization thread while processing
the reply of a web-service task caused uncommitted transactions on the thread
subsequently.

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

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

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

The Hotfix 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/2.2.0/hotfix002

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

TIBCO ActiveMatrix(R) BPM 2.2.0 Hotfix 002 is available.

Product: TIBCO ActiveMatrix BPM Version: 2.2.0 OS: All Supported Operating Systems

TIB_amx-bpm_2.2.0_HF-002_readme.txt