Description:
You can download this HotFix from the TIBCO Product Support ftp server, mft.tibco.com. You will need to provide your TSC (TIBCO Support Central) credentials. Your username is your email address to access the server.

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, go to /AvailableDownloads/BusinessWorks/6.3.0/hotfix-01 to download the fix.

================================================================================
Closed Issues in 6.3.0_HF-001 (This Release)
AMBW-21391
When using the "JDBC Call Procedure" activity to call a stored procedure, which contained an Oracle Object with CLOB data type, a SQLException was thrown. This has been fixed.

AMBW-21434
Managed fault tolerance did not work if a schema used in an application process did not have a targetnamespace. This has been fixed. To recreate the database, use the
updated database scripts at <TIBCO_HOME>\bw\6.3\config\dbscripts\engine. For example, if you are using an Oracle database, execute the updated database scripts at
<TIBCO_HOME>\bw\6.3\config\dbscripts\engine\oracle.

AMBW-21437
Applications did not start properly when Managed Fault Tolerance was configured at the AppSpace level to use an external database and TIBCO Enterprise Messaging Service
for data persistence and transport. This has been fixed. To recreate the database, use the updated database scripts at <TIBCO_HOME>\bw\6.3\config\dbscripts\engine. For
example, if you are using an Oracle database, execute the updated database scripts at <TIBCO_HOME>\bw\6.3\config\dbscripts\engine\oracle.

AMBW-21543
If an "Invoke" activity timed out in an application configured to use SOAP/JMS binding, JMS Resources were not released and a memory leak was observed. This has been fixed.

AMBW-21603
If an "Invoke" activity timed out in an application configured to use SOAP/HTTP binding, HTTP Resources were not released and a memory leak was observed. This has been fixed.

AMBW-21652
Before using the bash scripts under <TIBCO_HOME>\bw\6.3\scripts\admin, update the appropriate database scripts under <TIBCO_HOME>\bw\6.3\config\dbscripts\admin.
   
MySQL
- If you are already storing data in a MySQL database, execute the following command:
ALTER TABLE BWProcess ADD diagramConfig longblob DEFAULT NULL;
- If you are not storing data in a MySql database, update the mysql_create.sql script at <TIBCO_HOME>\bw\6.3\config\dbscripts\admin\mysql by adding the following line to the "Table structure for table
BWProcess" section:
diagramConfig longblob DEFAULT NULL,

Postgres
- If you are already storing data in a Postgres database, execute the following command:
ALTER TABLE BWProcess ADD diagramConfig bytea DEFAULT NULL;
- If you are not storing data in a Postgres database, update the postgresql_create.sql script at <TIBCO_HOME>\bw\6.3\config\dbscripts\admin\postgresql by adding the following line to the "Table structure
for table BWProcess" section:
diagramConfig bytea DEFAULT NULL,

Oracle
- If you are already storing data in an Oracle database, execute the following command:
ALTER TABLE BWProcess ADD diagramConfig blob DEFAULT NULL;
- If you are not storing data in an Oracle database, update the oracle_create.sql script at <TIBCO_HOME>\bw\6.3\config\dbscripts\admin\oracle by adding the following line to the "Table structure for
table BWProcess" section:
diagramConfig blob DEFAULT NULL,

AMBW-21749
Higher thread counts caused lower engine speeds due to coarse grained synchronization. This has been fixed. To achieve a performance boost in the engine, finer grained synchronization was used.
================================================================================