Description:
This hotfix doesn't need any TRA hotfix. The patch can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /available_downloads/ActiveEnterprise/BusinessWorks/BW/5.6.3/hotfix-03/  to download the appropriate hotfix for your OS/platform.

======================================================================
Closed Issues in 5.6.3_hotfix03 (This Release)

1-96594D
The ActiveMatrix BusinessWorks Service Agent and Partner Link
Configuration failed to load the referred concrete WSDL when it was
built in a Design Time Library. This has been fixed.

1-96ZX3H
The JMS activities in a sub-process failed if the same sub-process was
used earlier in a JMS local transaction group. This has been fixed.

1-9AXCRY
The InvokePartner activity hung when a WSDL which defined an InOnly
operation and transport as JMS was used. This has been fixed.

1-9BFIRO
A service configured to use JMS as the transport threw an exception
'javax.naming.CannotProceedException' if a queue and a topic with the
same name existed on the EMS Server. This has been fixed.

1-9C1PRH
When "Expose Security Context" was checked and a SOAP message
containing a WSS Username token with either plaintext or digest was
sent from a SOAP UI, a NullPointerException was thrown. This has been
fixed.

1-9D0V74
An exception was thrown by JMS Sender/Publisher when it was part of a
JMS Local Transaction along with other activities. Also, when a JMS
Receiver Activtiy and JMS Get Message Activity were a part of a JMS
Local Transaction, the following exception was thrown on or after the
second job: 'javax.jms.IllegalStateException: Session is closed'.
This has been fixed.

1-9ELBHD
The JDBC Call Procedure activity did not run if one of the input
parameters was a nested table type. This has been fixed.

1-9GZGMU
TIBCO ActiveMatrix BusinessWorks could not insert CLOB data into
Oracle 10.x using the Oracle OCI 10.x driver and threw an exception.
This has been fixed.

1-9HQQZD
The performance of Get JMS Queue Message activity has been improved.

1-9IS817
JDBC Call Procedure activity threw an exception when a stored
procedure containing multiple Oracle table types was called. This
has been fixed.

1-9JFEHL
A JDBC Call Procedure activity with TABLE type input parameter failed
if the procedure was in a different schema than the one being used in
the connection. This has been fixed.

1-9JQ06I    
When there was no message in the queue for GetJMS activity inside a
XA Transaction group and when the specified timeout expired, the
ActivityTimedOutException was not thrown. This has been fixed.