Description:
TIBCO Adapter for MQSeries now supports TRA 5.2.0 and 5.2.1
and BusinessWorks 5.2.0 and 5.2.1, in addition to the
currently supported TRA and BusinessWorks versions listed in
the product documentation.  The only TRA and BusinessWorks
features supported by the adapter are those included in the
documentation for TIBCO Adapter for MQSeries.

Configuration:
==========

No adapter configuration changes are required to use TRA
5.2.0 or 5.2.1 or Business Works 5.2.0 or 5.2.1 with version
5.2.0 of MQSeries Adapter.

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

Known Issues for TRA 5.2.0/5.2.1 and BusinessWorks 5.2.0/5.2.1


1. The adapter repository gets corrupted in Designer
    5.2.0 when transport type has been changed from RV to
    JMS.

Symptoms:
=========
After the transport type for a service is changed from
RV to JMS, if the project is saved and re-opened, the
following error is seen.
"AEADMQS-200083 Error reading serivce information.
Could not read the following service:-
RequestResponseInvocationService.  This service exists
under the NQSeriesAdapterConfiguration instance and
might be corrupt."

Impact:
======
Loss of Functionality

Cause:
======
This is caused due to a defect in the Designer library.

Workaround:
==========
Delete the service and create a new service with JMS
as transport and save the project.

---------------------------------------------------------------------------------


Known Issues for TRA 5.2.0 and BusinessWorks 5.2.0


1. The transport tab of 'Publish to Adapter' activity
     in TIBCO BusinessWorks 5.2.0 does not get refreshed
     when QoS is changed to 'RVCMQ'

Symptoms:
=========
Due to this, the BusinessWorks activity cannot be
configured for that particular adapter service.

Impact:
======
Data Loss

Cause:
======
This is caused due to a defect in the Designer library.

Workaround:
==========
Remove the reference of adapter service and select the same
adapter service for 'Publish to Adapter' activity

---------------------------------------------------------------------------------

2. MQSeries Adapter v 5.1.0 crashes when it is
    configured with JMS as transport type and Request
    Response Invocation as adapter service in BW 5.1.3.

Symptoms:
=========
Due to this, the request response invocation service
scenario cannot be run.

Impact:
======
Loss of Functionality

Cause:
======
SDK does not handle the closure data in the MQSeries reply
message.

Workaround:
==========
None

Resolution
==========
Apply TRA 5.2.0 HF2 and BW 5.2 HF2 to resolve
this issue. Please refer to TRA 5.2.0 HF2
LBN# LBN1-4TTMUV  and BW 5.2 HF2 LBN#
LBN1-4ZZXKC for more details.

---------------------------------------------------------------------------------

3. MQSeries adapter crashes when it is configured as a JMS
    subscriber with BusinessWorks 5.2.0.

Symptoms:
========
Due to this, the adapter will fail and stop processing.

Impact:
======
Loss of Functionality

Cause:
======
While BW sends an 'Any' type, it is not setting the
datatype in the message and hence SDK is not able to create
an instance.

Workaround:
===========
a. Open a new repository and drag and drop a MQSeries
    Adapter instance.
b. Export this repository (for example, MQ1.dat) and
    save it.
c. Import the dat file created in the previous step
    (MQ1.dat) into another repository.
d.  In the repository, go to
    AESchemas\ae\MQSeries\classes\ExtendedBinaryTIBMsg
e. Click on MQSeriesMessage and select the type as
    'Binary' from the drop-down list.
    The above steps are needed to unlock the schemas so
    that you can change the value of the MQSeriesMessage
    field to binary.
f. Configure the rest of the project as required.

Please note that the MQSeries Message in BW Activity
Input also has to be a binary.

Resolution
==========
Apply TRA 5.2.0 HF2 and BW 5.2 HF2 to resolve
this issue. Please refer to TRA 5.2.0 HF2
LBN# LBN1-4TTMUV and BW 5.2 HF2 LBN#
LBN1-4ZZXKC for more details.

---------------------------------------------------------------------------------