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/2.2.1/TIB_amx_mediation_020201_1

Listed below is a summary of updates included. Please refer to the associated readme document for additional information.
================================================================================

Closed Issues in hotfix tib_amx_mediation_020201_hotfix01 (This Release)

1-9W2MSC: This hotfix addresses the issue of service assembly deployment hanging in the case of mediation flows referring to a WSDL that define multiple in-line schemas that refer to one another.

1-9Y6G01: In the event of One-way message, if the reference component does not exist or is not running, Mediation IT now provides mechanism to put the message in the error queue ($sys.undelivered).

1-A0KG0F: When a user configures a ThrowFault to throw a declared fault, now a fault path is created with a Catch and a Send for the declared fault.

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

Additional Notes :-

The Tibco Universal Installer version to be used for this hotfix is 2.5.0 V37.
You can download this from available_downloads/ActiveMatrix/ActiveMatrixServiceGrid/2.2.1/TIBCOUniversalInstaller_250v37 directory.

CR1-9Y6G01:-
For In-Only mediation operation the End mediation task in a mediation path can be configured with an "Error" option. When the End task configured with an "Error" option is executed, the mediation container will notify the ActiveMatrix framework that an error has occurred in the mediation flow. Depending on the ActiveMatrix node configuration, the message will get logged or written to the error queue. Please refer to ActiveMatrix documentation for node configuration details (Appendix-B of tib_amx_administration guide).

CR1-A1ERJT:-

After a hotfix/SP is installed on a AMSG/AMSB/BWSE installation, existing nodes are not automatically upgraded. Existing nodes will continue to run as before, as if no hotfix/SP has been applied. But if an attempt is made to deploy a new Service assembly into an existing node, the following exception is thrown :
Ex:

org.osgi.framework.BundleException: The bundle could not be resolved.
Reason: An

other singleton version selected: com.tibco.&ltxxx>.&ltyyy>_2.2.101.001

at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:294)

at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:256)
...
...

You may see unexpected behaviour.

Workaround/solution : Leave existing nodes untouched i.e do not attempt  any new deployments into an existing node. Or upgrade existing nodes after a hotfix/SP has been installed. Refer to the hotfix readme for instructions on how to upgrade an existing node.

TIBCO ActiveMatrix(R) Service Grid 2.2.1 Hotfix "TIB_amx_mediation_020201_1 " is now available.

Product: TIBCO ActiveMatrix Service Grid Version: 2.2.1 OS: --------------------