Description:
You can download this HotFix from the TIBCO Product Support FTP server using your eSupport username and password, at
      
       ftp://support-ftp.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under
       available_downloads/ActiveMatrix/ActiveMatrixServiceGrid/3.1.3/TIB_amx_3.1.3_hotfix001

Listed below is a summary of updates included. Please refer to the hot fix readme document for any additional information.

================================================================================
Closed Issues in 3.1.3_hotfix001 (This Release)

AMRP-3391
When a threading policy is configured in a provider application, a
NullPointerException is no longer thrown at runtime.

AMRP-3390
When a threading policy is configured in a provider application, under heavy
load, applications no longer become unresponsive.

AMRP-3371
The prepareForUndeploy and getServiceTarget callbacks for BPM components
are now called upon node restart.

AMRP-3417
SOAP reference bindings no longer drop XML prefixes.

AMRP-3416
Under load SOAP bindings no longer throw NPE when context parameters exist.

AMRP-3408
Redeployment of an application with a dependency now succeeds and does
not indefinitely display "In Progress". Unnecessary component JAR files are
correctly cleaned up from the node.

AMRP-3365
NPE is no longer thrown when attempting to undeploy a component in configured
state after node restart.

AMX-9590    
A post-install script has been provided that removes duplicate plug-ins from
TIBCO Business Studio to resolve issues when multiple products are installed in
the same &ltTIBCO_HOME>. See the section Post-Installation.

AMX-9761
The transaction log file no longer grows very large. The following Java
configuration properties are now available to control the maximum size and
number of transaction log files.

amf.node.txlogsize - The log size in KB, per log file. The minimum setting is 20.
amf.node.txlognum - The number of log files. The minimum setting is 2.

You can specify these properties in the node TRA file or set them in the Node
configuration screen in the Admininstrator UI.

BJMS-1035    
If an application has a SOAP-JMS reference, the SOAP binding now reconnects to
a JMS server if the server is restarted.

BJMS-1038    
Stopping an application or node now completes, even if a reference with a JMS
binding with a long timeout is waiting for a response from an unavailable service.
The fix causes a reference with a JMS binding to stop immediately. If you need
the reference with a JMS binding to stop gracefully while all the outstanding
requests are processed, add the following property to the node TRA file:

com.tibco.amf.binding.jms.closeEndpoint.gracefulShutdown=true

BJMS-1039    
JMS bindings now correctly handle reply messages with empty body.

SDS-5359    
Generated DAA for SOA projects can now be marked as derived in the preferences
page Window > Preferences > TIBCO SOA Platform > Runtime Artifacts, which
exposes a single checkbox (checked by default) that toggles whether
generated DAAs are marked as derived.

If a DAA is marked as not derived, Subversion will identify a changed DAA as a
candidate for checkin.

To verify if a generated DAA is derived, do the following:
1) Right-click the DAA in the Project Explorer and select Properties.

The dialog that displays has a checkbox Derived which should be
checked if the resource is derived, and unchecked if not.

SDS-5335
Installation of other products in the same &ltTIBCO_HOME> as ActiveMatrix Service
Grid no longer causes Administrator CLI generation to fail.

SDS-5295
The option to force refresh of the target platform from command line
when TIBCO Business Studio starts is now enabled.

To set the target platform, open
&ltTIBCO_HOME>/studio/3.5/eclipse/TIBCOBusinessStudio.ini in a text editor and
add the following line:

-DTARGET_PLATFORM_FILE_LOCATION=&ltabsolute path to the .target file>

SDS-5276
TIBCO Business Studio is now able to launch applications with optional
properties in RAD.

TAP-8851
This note only applied if you have upgraded to 3.1.3 from 3.1.2. If you have
installed 3.1.3 and are applying this hotfix to 3.1.3, this note does not apply.

A regression was introduced in the script that upgraded 3.1.2 to
3.1.3 or if your 3.1.2 installation had an hotfix applied, and then
you upgraded to 3.1.3.

The issue affects replicated Administrator server configurations.
It causes some actions related to application management to fail when executed f
rom a different Administrator instance. For example if you created an
application from Admin-instance-1, then deployment from Admin-instance-2 fails.
Running applications are not affected by this issue.

The issue occurred the because the upgrade script changed the configured
location of a folder. Files that were supposed to get created under the
original folder location &ltconfig-home>/admin/&ltenterprise>/shared/repo
instead were created under &ltconfig-home>/tibcohost/Admin-&ltenterprise>-&ltinstance>
/nodes/SystemNode/bin/SCMDetails-location.

The "shared" folder is the only folder on a shared file system accessible to
both Administrator replicas. Files created under "SystemNode/bin" are not
accessible by the second Administrator instance, and this causes deployment
actions to fail.

This issue is addressed by:
a) Correcting the configured folder location to again point to "shared/repo".
b) Moving files erroneously created under SystemNode/bin back to "shared/repo"
folder.
c) Making corresponding changes to the folder paths recorded in the
Administrator database.

TAP-8612    
Whitespace changes to a WSDL file no longer prevents an application from being
upgraded.

Note: The fix applies only to newly-built DAAs. After applying the hotfix,
you must regenerate existing DAAs for the projects affected by the defect.

TAP-8610    
Administrator now correctly handles an update action for a component that is
waiting for dependencies.

TAP-8614    
Warnings of type "Cannot resolve capabilities" are no longer issued when
performing application upgrade from TIBCO Business Studio.

TAP-8458
Internal application deployment files now get cleaned up from the disk on the
machine running the Administrator server.

TAP-8443
An application can now be undeployed even if the deploy or undeploy actions
did not complete successfully.

TAP-8239
In rare situations installing a new node in an existing environment or
deleting an existing environment fails. These actions now succeed.

TAP-8125
Editing a SOAP binding in the Administrator GUI to set a part ("hdr") to header
part type and then saving the binding configuration no longer results in an error.


TAP-8040    
Wiring a reference to a virtual service in the Administrator GUI no longer
requires significant time to complete.

TAP-7995    
A WSDL file can now be generated for a deployed application after an upgrade to
the application fails.

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