tibco activematrix adapter for swift...† support for swift standards release 2010 this release...

Two-Second Adv

TIBCO ActiveMatrix® Adapter for SWIFT

Release NotesSoftware Release 5.11.0August 2013

antage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIBCO, Two-Second Advantage, TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO ActiveEnterprise, TIBCO Rendezvous, TIBCO Designer, TIBCO Administrator, TIBCO Adapter SDK, TIBCO Runtime Agent, TIBCO ActiveMatrix Adapter, TIBCO ActiveMatrix Adapter for MQSeries, TIBCO Enterprise Message Service, and TIBCO Hawk are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 1998-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Release 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Release 5.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Release 5.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Release 5.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

TIBCO ActiveMatrix Adapter for SWIFT Release Notes

iv | Contents

Release 5.9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 5.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 5.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Release 5.0.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Migration and Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29


| v

Preface

TIBCO ActiveMatrix Adapter for SWIFT software is a bidirectional gateway between the SWIFT Network and TIBCO applications.

This manual describes a list of new and changed features, and it also contains lists of closed issues and known issues for this release.

Topics

• Typographical Conventions, page vi

• Connecting with TIBCO Resources, page viii


vi | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

TIB_ADSWIFT_HOME

TIBCO products are installed into an installation environment. A product installed into an installation environment does not access components in other installation environments. Incompatible products and multiple instances of the same product must be installed into different installation environments.

An installation environment consists of the following properties:

• Name Identifies the installation environment. This name is referenced in documentation as ENV_NAME. On Microsoft Windows, the name is appended to the name of Windows services created by the installer and is a component of the path to the product shortcut in the Windows Start > All Programs menu.

• Path The folder into which the product is installed. This folder is referenced in documentation as TIBCO_HOME.

The product is installed into a directory within a TIBCO_HOME.

The Installation installs the product in the directory is referenced in documentation as TIB_ADSWIFT_HOME. The default value depends on the operating system. For example on Windows systems, the default value is C:\tibco\adapter\adswift\version.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin .

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable].


Preface | vii

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname.

Key combinations Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


viii | Connecting with TIBCO Resources

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, contact TIBCO Support as follows:

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a username and password. If you do not have a username, you can request one.


http://www.tibco.com/services/support


http://www.tibcommunity.com

http://docs.tibco.com

| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 9

• Deprecated and Removed Features, page 14

• Migration and Compatibility, page 19

• Closed Issues, page 21

• Known Issues, page 29



2 | Release Notes

New Features

This section lists features added since the last major release (5.0.0) of this product.

Release 5.11The following are new features in this release:

• Support for SWIFT MT and MX Standards Release 2013 This release adds support for SWIFT MT and MX Standards Release 2013.

• Added Platform Support This release adds new platform support for TIBCO ActiveMatrix BusinessWorks Plug-in for SWIFTNet - FIN:

— Solaris (SPARC) 11

Release 5.10The following are new features in this release:

• Support for TIBCO Universal Installer This release adds TIBCO Universal Installer. Users can install TIBCO ActiveMatrix Adapter for SWIFT by using this new installer.

• Support for SWIFT Standards MT 2012 This release adds support for SWIFT Standards MT 2012.

• Support for BICPlusIBAN Generation This release adds support for BICPlusIBAN generation to create an IBAN in an international payment message.

• Support for BICPlusIBAN Validation This release adds support for BICPlusIBAN validation to validate an IBAN in an international payment message.

• Added SOAP Sample This release integrates TIBCO products with SWIFT using SOAP interface. A sample using SOAP is added into samples of this release.

• Added Platform Support This release adds new platform support for TIBCO ActiveMatrix BusinessWorks Plug-in for SWIFTNet - FIN (BW Plug-in - FIN):

— Red Hat Enterprise Linux 6.x

— AIX 7.1


New Features | 3

Release 5.9The following are new features in Release 5.9:

• Support for SWIFT Standards Release 2011 This release adds support for SWIFT Standards Release 2011.

• Added Platform Support This release adds new platform support for TIBCO ActiveMatrix BusinessWorks Plugin for SWIFTNet - FIN (BW Plugin-FIN):

— Windows 2008 R2 and Windows 7





• Added Platform Support This release adds new platform support for the following components.

For TIBCO ActiveMatrix BusinessWorks Plugin for SWIFTNet - FIN (BW Plugin-FIN):

— AIX 6.1

— Windows Vista and Windows 2008

— Solaris 10 on x86

— Red Hat Enterprise Linux 4.x and 5.x on x86

— SUSE 10.x

For TIBCO ActiveMatrix Adapter for SWIFTNet - FIN:

— AIX 5.2 and 5.3 on 64-bit

• Support for ‘S’ Block Trailer The release adds support for ‘S’ block trailer for BW Plugin - FIN.

64-bit build does not support CASmf as CASmf is not available as 64-bit application from SWIFT.


4 | Release Notes

• Support for SWIFT System Messages This release adds support for SWIFT system messages MT009 , MT028 , MT029 , MT036 , MT042 , MT043 , MT047 , MT056 , MT062 , MT063 , MT067 , MT072 , MT077 , MT096 , and MT097 .



• Added Platform Support This release adds support for:

— HP-UX 11i V3 (IA64 Itanium) for TIBCO BusinessWorks Plug-in for SWIFT

— Red Hat Linux 4.6 on x86 for TIBCO BusinessWorks Plug-in for SWIFT



• Added New Product Component, TIBCO ActiveMatrix Adapter for SWIFTNet This component allows you to build SWIFTNet solutions based on InterAct. It acts as a standalone transparent gateway between TIBCO applications and SAG. For more information on the usage of this component, refer to the TIBCO ActiveMatrix Adapter for SWIFTNet User’s Guide and TIBCO ActiveMatrix Adapter for SWIFTNet Examples Guide.

To align product names with terminology that SWIFT is using, the TIBCO ActiveMatrix Adapter for SWIFT components have been renamed as follows:

— TIBCO ActiveMatrix Adapter for SWIFTNet - FIN

— TIBCO ActiveMatrix Adapter for SwiftNet

— TIBCO ActiveMatrix BusinessWorks Plug-in for SWIFTNet - FIN

— TIBCO Integration Manager Plug-in for SWIFTNet - FIN

• Support for CASmf 6.0 This release adds support for CASmf 6.0 for the TIBCO ActiveMatrix Adapter for SWIFTNet - FIN component.

• Support for HP-UX 11i V2 (IA64 Itanium) This release adds support for HP-UX 11i V2 (IA64 Itanium) for the TIBCO BusinessWorks Plug-in for SWIFTNet - FIN.


New Features | 5



• Uniform Handling of Acknowledgment Messages This release adds support for uniform parsing of acknowledgment messages (ACK and NACK) across the three modes: FTP, CASmf, and MQSA.

• Dynamic BIC Update This release adds support for dynamic refresh of the Bank Identifier Code (BIC) information, which is used for validation from the BIC list (FI.dat), without having to restart the adapter or TIBCO BusinessWorks.

• Added Platform Support This release adds support for:

— AIX 5.2 on POWER

— AIX 5.3 on POWER

— Red Hat Linux 3.0 on x86 (Only for TIBCO BusinessWorks Plug-in for SWIFT)

— Red Hat Linux 4.0 on x86 (Only for TIBCO BusinessWorks Plug-in for SWIFT)

— Solaris 10 on SPARC (Only for FTP and MQSA modes)


• Added Support for System Messages This release of the adapter supports system messages (MT0xx). The messages supported are FIN-to-user, user-to-FIN, FIN/GPA-to user, user-to-FIN/GPA, user-to-SWIFT headquarters, SWIFT headquarters-to-user, FIN and GPA acknowledgements.

• Added Support for Visual Studio .NET 2003 This release of the adapter supports building SwiftAdapter.dll , to work with CASmf, using Visual Studio .NET 2003 compiler.

• Added Support for Windows 2003 Server This release of the adapter now supports Windows 2003 Server.


6 | Release Notes


• Added Plug-in for TIBCO BusinessWorks The release adds a new plug-in, TIBCO BusinessWorks SWIFT Plug-in. The plug-in is available in the form of a SWIFT palette in TIBCO BusinessWorks.The plug-in enables you to parse, validate, and render FIN messages directly from your BusinessWorks processes, without having to run the adapter as a separate process. It also allows you to route FIN messages to different activities based on the message type.

• Added SWIFT Standards Release Support This release of the adapter now supports SWIFT Standards Release 2005.

• Added CASmf Support This release adds CASmf 2.2h support.

• Added SWIFT Alliance Access Support This release adds SWIFT Alliance Access version 5.5.

• Added Platform Support This release adds Solaris 9 platform support.


• Support for SWIFT 2002 and 2003 Message Standards The release of the adapter supports all SWIFT FIN message types defined according to the 2002 and 2003 SWIFT Message Standards, including message types conforming to ISO 15022 standards.

• Message Validation The release of the adapter can be configured to parse and validate messages at a granular level. For example, you can turn on or off validation for message character sets, data types, code words, BIC/BEI, and so on. In addition, you can use validation filters to ignore certain errors resulting from this validation.

• Support for TIBCO BusinessWorks 5.1.2 The release of the adapter can be used in a TIBCO BusinessWorks 5.1.2 process.

Release 5.0.1 The following are new features in Release 5.0.1:

• Support for Solaris 8 This release of the adapter also supports Solaris 8.

• Multiple Schema Support The release now supports 2002 Message Standard schemas as well as the 2003 Certification schemas. One instance of the adapter will support only one set of schema.


New Features | 7

• Support for switching off complete validation The release of the adapter now supports switching off complete validation both for Sender (Renderer) and Receiver (Parser) instance when the Validate flag at the instance level is set to False .

• Custom palette The release adds a custom palette for configuration. The previous release of the adapter used a generic palette.

• New installer The release of the installer program has three modes available for installation.

— GUI mode: The mode presents panels that allow you to make choices about product selection, product location, and so on.

— Console mode: The mode allows you to make installation choices from the command line.

— Silent mode: The mode either installs using the default settings or uses a response file that was saved during an earlier installation.

• Support for multi-file format projects TIBCO Designer 5.0 now allows you to save adapter projects in multi-file format at design-time. This format is useful if multiple adapter configurations are defined in the same project and are worked on by several developers. The adapter configuration files can be managed by a version control system such as Microsoft Visual SourceSafe.

• JMS Support In this release, the JMS (Java Messaging Service) transport is available in addition to the TIBCO Rendezvous transport. JMS transport is also available for the Design-time Adapter. An adapter service that uses the JMS transport can communicate only with the TIBCO Enterprise for JMS server.

• Connection Management The release adds support for flexible connection management is available. The adapter detects loss of connectivity to the CASmf or FTP server due to sudden network outages or due to the CASmf or FTP server going down. The adapter uses suitable connection management mechanisms that will ensure maximum adapter uptime and minimum impact on message transfer.

• Enhanced Error Management The release of the adapter uses an enhanced error reporting mechanism. Error messages provide more detail, are contextual and can be applied uniformly across adapters. Low-level exception messages like system and TIBCO Rendezvous messages now have appropriate adapter-level information.

• Delayed Acknowledgement The release of the adapter supports delayed acknowledgement for the subscription service, for certified messaging. It sends an acknowledgement of receipt of a message to the sender of the message only after the message is sent successfully to the CASmf interface,


8 | Release Notes

FTP server or TIBCO Adapter for MQSeries (depending upon the interface that is used).

• Support for SWIFT Alliance Access version 5.0 The release of the adapter now supports SWIFT Alliance Access 5.0 in addition to SWIFT Alliance Access 4.0 and 4.1.

• Support for Oracle 9i for optional database logging The release of the adapter now supports optional database logging for Oracle 9i.

• Support for SWIFT Message Types The release of the adapter supports all SWIFT FIN message types defined according to February 2002 SWIFT Message Standards including message types conforming to ISO 15022 standards.The adapter also supports Investment Fund messages such as MT502 , MT515 , MT509 , and MT535 .

• Support for BIC and BIC Plus file Message validation is carried out for the BIC Code against the BIC or the BIC Plus file specified in the adapter configuration file.

• Support for optional database logging for FTP and MQSA Interfaces This feature was supported for CASmf interface in the previous release. This is extended for MQSA and FTP interfaces. If the adapter is configured for database logging, the original inbound and outbound SWIFT messages will be logged to the database for future reference.

• Logical Definition for attributes of SWIFT Schema The adapter configuration contains a schema corresponding to each SWIFT Message type that needs to be handled by the adapter. Previously, the attributes of the schema contained only the alphanumeric representation of the Data Tags in the SWIFT message. In this release, the attributes of the schema contain the logical definition of the SWIFT Message Data Tags.

• The mandatory fields of a SWIFT Schema are displayed differently from the optional fields MANDATORY_ is appended to the mandatory fields in the SWIFT schema.


Changes in Functionality | 9

Changes in Functionality

This section lists changes in functionality since the last major (5.10) release of this product.

Release 5.11There are no changes in functionality in this release.

Release 5.10There are no changes in functionality in this release.

Release 5.9The following are changes in functionality in this release:

• Dropped Support for SWIFT Standards Release 2009 This release of the adapter does not support the SWIFT Standards Release 2009.

• Integration Manager Plugin Component Support Dropped This release does not support Integration Manager Plugin for SWIFTNet - FIN.

Release 5.8The following are changes in functionality in this release.




• Dropped Platform Support This release does not support the following platform:

— Windows 2000 (Only for BW Plugin-FIN)


10 | Release Notes



• Dropped Platform Support This release does not support the following platform:

— Windows 2000 (Only for TIBCO ActiveMatrix Adapter for SWIFTNet - FIN and TIBCO ActiveMatrix Adapter for SWIFTNet)

— Red Hat Enterprise Linux 3.0 on x86

• Database Platform Support The release does not support database logging using Oracle 8.1.7.






• TRA Support This release of the adapter supports TIBCO Runtime Agent (TRA) version 5.3.0 only. Earlier versions of the TRA are no longer supported.

• VisualStudio Support This release does not support VisualStudio 6.0. This release of the adapter now supports building SwiftAdapter.dll , to work with CASmf, using Visual Studio.NET 2003 compiler.




• Dropped Platform Support The release does not support the following platforms:

— Solaris 2.7

— Windows NT

• Dropped Support for CustomHeader and CustomTrailer The release does not support the CustomHeader and CustomTrailer functionality.

• UseSDK Flag no longer required It is no longer required to set the UseSDK flag in the TIBCO IntegrationManager property file to use the SWIFT custom activity.

• No TIBCO Rendezvous Transactional Quality of Service Option The TIBCO Rendezvous Transactional quality of service option is no longer available in the adapter’s palette.


• SWIFT Message API no longer supported The release does not support SWIFT Message API.


• Schema and Palette Changes Both the schema and palette change significantly to support the validation options changes. Because the schema has changed, the adapter is not backward compatible with previous versions. See Migration and Compatibility on page 19 for more information.

• Installer Changes For adapter installations on Microsoft Windows platforms, all DLLs are placed in the adapter installation lib subdirectory.

• Database Platform Support The release does not support database logging using Oracle 8.1.6.

• Changed TIBCO Hawk Methods


12 | Release Notes

The following TIBCO Hawk methods change parameters and are now available in the adapter’s class microagent:

— getActivityStatistics()

— getActivityStatisticsByOperation()

— getActivityStatisticsBySchema()

— getActivityStatisticsByService()

— getThreadStatistics()

— getQueueStatistics()

— getConnectionStatistics()

The following parameters for the above methods are new or have changed (where applicable). In addition, the parameter order for some of the above methods has changed.

— The new output parameter MeasurementInterval displays the time (in seconds) since last time the adapter was reset, or if never reset, since the adapter started.

— The Total , Success , and Failure output parameters type has changed from string to integer.

— The new output parameter LineIndex is used as an index for the method. Its value is a concatenated string of the Operation and ServiceName parameters separated by a comma.

— The new output parameter NumLostConnections displays the total amount of time the connection has been lost.

• TIBCO Hawk Class Agent Property The adswift.addCustomHawkMethodsToClassMAgent on/off property has been added to the adapter’s property file. The property is not set by default. Setting the property to off disallows adding custom methods to the adapter’s standard microagent. Setting to on allows custom methods to be added to the adapter’s standard microagent.

Release 5.0.1The following are changes in functionality in this release:

• Palette Changes A new custom palette is been introduced at the instance and service levels to make it more intuitive.

• Installer changes The adapter installation program no longer includes the TIBCO Runtime Agent software, which is required by the adapter. The software must be installed prior to installing the adapter. In previous releases,



TIBCO software could be uninstalled using the TIBCO Uninstaller program. In this release, each software component is uninstalled separately by navigating to the _uninst folder and running the Tibuninstall utility.

• Repository Server The repository server is now a component of TIBCO Administrator. Access control to the repository server can be set using TIBCO Administrator.

• SWIFT Alliance Access 5.0 supports both X.25 protocol and TCP/IP protocol SWIFT Alliance Access 4.1 and 4.0 supported X.25 protocol. SWIFT Alliance Access 5.0 supports both X.25 protocol and TCP/IP protocol. You can either select the X.25 protocol to connect to the SWIFT network or the TCP/IP protocol to connect to SWIFTNet.

• Support for optional database logging for FTP and MQSA Interfaces This feature was supported for CASmf interface in the previous release. This has been extended for MQSA and FTP interfaces. If the adapter is configured for database logging, the original inbound and outbound SWIFT messages will be logged to the database for future reference. The adapter also logs the logical replies, transmission reports and delivery reports received from SWIFT.


14 | Release Notes

Deprecated and Removed Features

This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features.

This section also lists features that are removed (if any).

Release 5.11

Deprecated Features

The following features are deprecated in this release:

• TIBCO ActiveMatrix Adapter for SWIFTNet - FIN and TIBCO ActiveMatrix Adapter for SWIFTNet This release deprecates TIBCO ActiveMatrix Adapter for SWIFTNet - FIN and TIBCO ActiveMatrix Adapter for SWIFTNet.

It is recommended to use TIBCO ActiveMatrix BusinessWorks Plug-in for SWIFT - FIN to parse and render SWIFT messages.

Removed Features

The following features are removed in this release:

• Dropped Support for SWIFT Standards Release 2011 This release of the adapter does not support the SWIFT Standard Release 2011.


For TIBCO ActiveMatrix BusinessWords Plug-in for SWIFTNet-FIN:

— Windows Server 2003


— AIX 5.3

For TIBCO ActiveMatrix Adapter for SWIFTNet-FIN:


For TIBCO ActiveMatrix Adapter for SWIFTNet:



Deprecated and Removed Features | 15

Release 5.10

Deprecated Features


• TIBCO ActiveMatrix Adapter for SWIFTNet - FIN The release deprecates TIBCO ActiveMatrix Adapter for SWIFTNet - FIN.

• Dropped Support for SWIFT Standards Release 2010 This release of the adapter does not support the SWIFT Standard Release 2010.


— Windows Vista

— Solaris 8

— AIX 5.2

— Red Hat 4.x

Removed Features

No features are removed in this release.

Release 5.9No features are deprecated or removed in this release.

Release 5.8

Deprecated Features


• Integration Manager Plugin Component Support This release deprecates Integration Manager Plugin for SWIFTNet - FIN. Users are encouraged to use BW-Plugin for SWIFTNet - FIN messages.

It is recommended to use TIBCO ActiveMatrix BusinessWorks Plug-in for SWIFT - FIN to parse and render SWIFT MT messages.


16 | Release Notes

Removed Features


Release 5.7

Deprecated Features


• Integration Manager Plugin Component Support This release deprecates Integration Manager Plugin for SWIFTNet - FIN. Users are encouraged to use BW-Plugin for SWIFTNet-FIN messages.

Removed Features








Deprecated and Removed Features | 17

Release 5.1

Deprecated Features


• TIBCO Rendezvous TX Support The TIBCO Rendezvous Transactional quality of service option is no longer supported. The option is still available in the adapter’s palette for backward compatibility with previous adapter releases.

• TIBCO Hawk Methods The following 5.0.1 and earlier TIBCO Hawk methods available in the adapter’s custom microagent have been deprecated:

— getActivityStatistics()

— getActivityStatisticsByOperation()

— getActivityStatisticsBySchema()

— getActivityStatisticsByService()

— getThreadStatistics()

— getQueueStatistics()

— getConnectionStatistics()

The above methods are now available in the adapter’s class microagent and have been enhanced (as described in Changes in Functionality on page 9).

If you use TIBCO Designer 5.1 to modify a 5.0 or earlier adapter configuration for use with a 5.0 or earlier run-time adapter, you must use the methods in the custom microagent, not the methods in the class microagent.

• SWIFT Message API The release deprecates SWIFT Message API.

Removed Features


Release 5.0.1

Deprecated Features


• Optional Database Logging Optional database logging using Oracle 8.1.6 is deprecated in release 5.0.1 and is supported using Oracle 8.1.7 and Oracle 9i.


18 | Release Notes

Removed Features



Migration and Compatibility | 19

Migration and Compatibility

This section provides information on adapter’s compatibility with and its data migration support for other TIBCO applications. It also discusses how to migrate your projects to the new SWIFT release standards.

For information on migrating to a newer version of TIBCO Runtime Agent (TRA), see the TIBCO Runtime Agent documentation set.

See TIBCO ActiveMatrix Adapter for SWIFTNet - FIN User’s Guide, Appendix B: Migrating to the Current SWIFT Standards for information on how to migrate your existing projects to the new SWIFT release standards.

Restore Mappings to BIC, BEI, BIC/BEI fields Manually

In SRG 2008 specification, BIC and BEI fields were renamed to Identifier Code . This change was reflected in the 5.7.0 release and is applicable for the specification year 2009 onwards.

As per SRG 2010 and later, all BIC and BEI fields were renamed again as follows:

• If a field could only have a BIC, then rename it as ‘a financial institution BIC’.

• If a field could only have a BIC or BEI, then rename it as ‘BIC’.

• If a field could only have a BEI, then rename it as ‘a non-financial institution BIC’.

This change is reflected in the 5.8.0 release of the TIBCO ActiveMatrix Adapter for SWIFT and is applicable for the specification year 2010 and later.

These field name changes affect the mappings for projects containing BIC/BEI fields.

Reload the Message Schema for adding the ’S’ Block

Support for ’S’ block Trailer was added in the 5.7.0 release of the adapter.

• Users migrating from 4.x versions of the adapter should contact TIBCO Support for instructions and tools to migrate to this version of the adapter.

• Users upgrading from version 5.1.1 or higher, open the previous project using TIBCO Designer.

If you open a project that was created prior to 5.7.0 release and change the specification year to 2009, or if you open any project and change the specification year to 2010 and later, you need to restore the mappings for all BIC and/or BEI fields manually.


20 | Release Notes

Projects created prior to the 5.7.0 release do not contain schema for ’S’ block and hence will fail during run-time. To prevent this failure, reload the message schema using the adapter version 5.7.0 or later.

Drop Mappings to MAC/PAC Trailers

In SRG 2009 specification, SWIFT has dropped support for MAC, PAC tags in the Trailer block.

Restore Mapping to PDE_PossibleDuplicateEmission field Manually

This release of the adapter supports multiple PDE fields in the trailer block. For this, the PDE_PossibleDuplicateEmission field under the SWIFTAdapter/BlockLibrary schema has been changed from scalar to sequence .

Restore Mapping to PDM_PossibleDuplicateMessage field Manually

This release of the adapter supports multiple PDM fields in the trailer block. For this, the PDM_PossibleDuplicateMessage field under the SWIFTAdapter/BlockLibrary schema has been changed from scalar to sequence .

If you open a project that was created prior to 5.7.0 release and the project included mappings to the MAC/PAC trailers, you need to drop these mappings manually.

If you open a project that was created prior to 5.5.0 and the project included mappings to the PDE field in the trailer block, you need to correct this mapping. This correction needs to be done manually.

If you open a project that was created prior to 5.6.0 and the project included mappings to the PDM field in the trailer block, you need to correct this mapping manually.


Closed Issues | 21

Closed Issues

The tables in this section list issues that were closed in the named releases.

Closed in Release Key Summary

5.11.0 SWFT-1044 When a valid MT300 message was parsed via SWIFT November 2012 specification in the Specification label, TIBCO ActiveMatrix BusinessWorks Plugin for SWIFTNet - FIN Parser rejected the message with a C5 rule error.

5.10.0 SWFT-871 The TIBCO ActiveMatrix Adapter for SWIFT Windows installer used 32-bit JRE by default. However, the installer failed before starting the TIBCO ActiveMatrix Adapter for SWIFT installer because the JAVE_HOME system variable was pointing to a 64-bit JRE.

5.10.0 SWFT-883 Context sensitive help was not working for any activity of TIBCO ActiveMatrix Adapter for SWIFT.

5.10.0 SWFT-884 On AIX 5.3 64-bit platform, SwiftCheck.bin threw an error message: Failed to load shared library, library name: /home/apps/tibco_swift/tibcojre/1.6.0/bin/j9vm/libjvm.

so .

5.10.0 SWFT-891 TIBCO Adapter for SWIFT 5.9 failed to capture the C06 error for Message Type 710.

5.10.0 SWFT-901 TIBCO ActiveMatrix Adapter for SWIFT 5.9 had a memory leak issue caused by the indefinite accumulation of com.tibco.swift2.metadata.MessageDescEventHandler$Chil

dState class instances in the stack.

5.10.0 SWFT-902 When you configured an adapter instance and selected SWIFT November 2011 specification in the Specification tab, in the Message56x.xml metadata file, the CETI qualifier in Message Type 564 sequence E, field 22F, contained an incorrectly named indicator TRPD , which was named TRBD .

5.10.0 SWFT-914 A memory leak error occurred because many redundant metadata files were generated when running numerous different SWIFT Plug-in activities in one BusinessWorks deployment. Each activity instance corresponded with one metadata file.


22 | Release Notes

5.10.0 SWFT-916 A leap year error occurred when validating the entered date "0229" in the Entry Date (MMDD) sub-field of field 61 that was representative of Statement Line.

5.9.0 SWFT-846 Parser threw T78 error when validating a correct MT 304 message.

5.9.0 SWFT-842 During design-time, the SWIFTNet-FIN Parser Plug-in encountered validation error.

5.9.0 SWFT-752 The metadata file Message56x.xml , showed the wrong indicator "TRPD" instead of "TRBD" in the Sequence E Field 22F Qualifier "CETI".

5.9.0 SWFT-749 In the SWIFT Specification 2010, the "user header" field is optional. However, SWIFTNET-Fin Renderer activity threw an error when this field was left blank.

5.9.0 SWFT-748 After installing TIBCO ActiveMatrix Adapter for SWIFT, the SWIFTNet Adapter palette was found to be missing in TIBCO Designer.

5.9.0 SWFT-746 The tag 70E in the sequence E of MT 564 message had an incorrect metadata. The metadata is now changed as specified in the SWIFT User HandBook.

5.9.0 SWFT-745 The tag 98 in the sequence E3 of MT 543 message can have option 'AC', but the current metadata had only 'A'.

5.9.0 SWFT-744 The tag 19B in the sequence D2 of MT 566 message had an incorrect metadata. The metadata is now changed as specified in the SWIFT User HandBook.

5.8.0 SWFT-740 Adapter parser activity did not throw an error when parsing the message type n98 in which 'CrLf-' appeared in the middle of field 77E .

5.8.0 SWFT-642

1-ACYUYE

Code/Common Reference validation for all SWIFTNet - FIN messages was failing.

5.8.0 SWFT-643

1-AEAHGT

TIBCO BusinessWorks process job was getting blocked during the SWIFTNet - FIN BW Plugin activity.



Closed Issues | 23

5.8.0 SWFT-646

1-AGSKEI

When the connection to CASmf was lost, SWIFTNet - FIN Sender did not attempt to reconnect to CASmf and recover the pending messages.

5.8.0 SWFT-639

1-A9XJ7M

In the 'S' block, the parser did not allow flexible sequencing of the tags.

5.8.0 SWFT-640

1-AAPLU1

ACK message threw a NullPointerException during Swift validation.

5.8.0 SWFT-637

1-A7FLML

Flexible sequencing for the PDM , DLM , and MRF Trailer tags for input to the parser was required.

5.8.0 SWFT-635

1-A78P29

ACK message was missing the newly added ’S’ block.

5.8.0 SWFT-636

1-A78P2Q

Tags INS , UNT, USR , and LAU were missing in the 'S' block.

5.8.0 SWFT-634

1-A5HZAP

When 'Validate Advanced Header' validation option was selected, the validator threw an error if either 113 or 108 tags were not present in the User Header. The correct usage as per the UHB is - "At least one of the tags 103, 113, 108, 119 or 115 must be present in the User Header".

5.7.0 SWFT-620

1-9VNCTX

For MT 536 , the Data Source Scheme REDM was not recognized by the adapter in SETR Qualifier and threw Error K22 during the validation.

5.7.0 SWFT-616

1-9RFZMA

In SRG 2008 specification, BIC and BEI fields were renamed to Identifier Code . This change has been reflected in the current release.

5.7.0 SWFT-608

1-9QDNLJ

Request for Cancellation schema for message type MTn92 had field name inconsistencies.

5.7.0 SWFT-606

1-9JWFN9

MT message fields with blank characters did not throw validation error.



24 | Release Notes

5.7.0 SWFT-605

1-9H382N

SWIFTNet - FIN Plugin did not validate the message length.

5.7.0 SWFT-597

1-9952YQ

When installing only the runtime component of BW Plugin-FIN, the adswiftplugin.jar file was not getting installed.

5.7.0 SWFT-599

1-9CDH2V

The MT535 message with more that one B1b subsequence failed to validate while parsing.

5.7.0 SWFT-600

1-9CZZ56

In MT499 and MT799 messages, field 79 was repetitive in SWIFT Standards 2008. The SWIFT Adapter however, treated it as non-repetitive.

5.7.0 SWFT-601

1-9D7H7X

The Network Validation Rule C3 incorrectly enforced the presence of 90a and 19A fields for MT535 message.

5.6.0 SWFT-549

1-8ERJ7Q

When TIBCO ActiveMatrix Adapter for SWIFTNet - FIN was stopped using TIBCO Administrator, it continued to show the status as "Shutting Down" even when it was stopped.

5.6.0 SWFT-581

1-93ZMYN

SWIFT messages with more than one PDM field in the trailer block failed validation.

This has been fixed. SWIFT messages with multiple PDM fields are now supported.

5.6.0 SWFT-562

1-91QT0S

When a message was sent using the "JMS queue sender" activity, the adapter did not log any information.

This has been fixed. Instead of sending the messages using the "JMS queue sender" activity, send a message to the adapter using the "Publish to Adapter" activity from the "ActiveEnterprise Adapter" palette.

5.6.0 SWFT-546

1-8EEVKJ

In the block TRADDET, in the message types: MT544 , MT545 , MT546 , and MT547 , the tag 22F::RPOR was defined as a repetitive tag in TIBCO ActiveMatrix Adapter for SWIFT 5.4.0. The change caused the TIBCO BusinessWorks process mappings to break.



Closed Issues | 25

5.5.0 SWFT-480

1-807SY8

The description of the PRPP and OFFR qualifiers in the 90A field under sequence E of message MT564 in the sample XML file (C:\tibco\adapter\adswift\5.4\bin\data\2006\Message56x.xml) was different from the actual SWIFT Standards Specification 2006.

According to the SWIFT Standards Specification 2006, the descriptions are:

• Qualifier OFFR — Generic Cash Price Received per Product

• Qualifier PRPP — Generic Cash Price Paid per Product

However, in the XML file, the descriptions specified were:

• Qualifier OFFR — Cash Price Received per Product

• Qualifier PRPP — Cash Price Paid per Product

The word Generic was missing.

5.5.0 SWFT-529

1-8BMRGN

SWIFT messages with more than one PDE field in the trailer block failed validation.

This has been fixed. This fix involves a schema change and you need to fix the mappings manually if you are mapping PDE tags prior to 5.5.0. See, Restore Mapping to PDE_PossibleDuplicateEmission field Manually, page 20 for more details.

5.5.0 SWFT-479

1-7U3FIO

In the CASmf mode, the Reference field in the LogicalReply received did not contain a value.

5.4.0 SWFT-444

1-6XGSA4

The adapter did not log trace messages if it detected duplicate messages in the remote FTP directory.

5.4.0 SWFT-461

1-77OCUV

The adapter does not validate 16R and 16S fields.

5.4.0 SWFT-462

1-78IJTH

The parsing of the messages: MT 066 , MT 082 , or MT 083 results in an error.

5.4.0 SWFT-454

1-76591M

The adapter does validate the Message Priority field in the application Header.



26 | Release Notes

5.4.0 SWFT-430

1-6Q5ZYP

The SwiftSender displayed the message, Shutting down in TIBCO Administrator even after it was stopped. The same behavior was observed when an exit message was sent to the sender.

5.4.0 SWFT-160

1-1H1GXB

The FTP mode did not contain the Test Connection button.

5.4.0 SWFT-457

1-768IIM

The tag 22F::RPOR that is inside the block TRADDET in message types: MT544, MT545, MT546, and MT547 was a non-repetitive tag.

This has been fixed. The tag 22F::RPOR is now defined to be a repetitive flag.

5.4.0 SWFT-433

1-6R3DUJ

There was an error in the variable names of ExtendedTIBMsg schema created by the TIBCO ActiveMatrix Adapter for SWIFT. Therefore when the schema was used with the MQ Adapter, the adapter displayed the error: MQSeries.ADMQ Error [Publisher] AEMQSC-930005 Data Conversion error: The Attribute is not defined in this class: putApplType.

5.4.0 SWFT-408

1-6HUDKG

The SWIFT messages of type MT96X (key exchanges) were not displayed by the TIBCO Designer.

5.3.0 SWFT-399

1-60CQZH

The Receiver did not publish a logical reply for the error messages that it processed.

This has been fixed. A logical reply is now published on the AdminPublisher.

5.3.0 SWFT-425

1-6OQUCN

In the CASmf mode, the SwiftSender did not publish a negative acknowledgement (NACK) when it encountered an invalid message.

5.3.0 SWFT-308

1-201UUX

The adapter did not support the "/" character in Group Global Variables. The error displayed was:AESWIFT-000015 Configuration property User with a value of %%swift/user%% can only consist of alphanumeric characters, the underscore character, or global variables.

This has been fixed. The "/" character can now be used as a separator in Group Global Variables. For example: %%MYGROUP/SUBGROUP/SUBVAR%%



Closed Issues | 27

5.3.0 SWFT-342

1-4DD7PE

When working in the CASmf mode, the SWIFTReceiver did not shut down as soon as the JMS server was down.

5.3.0 SWFT-407

1-6HUDJ0

Both SWIFT IntegrationManager Parser and SWIFT Check displayed the following error on parsing MT96X series of messages:

"Error T33 at line 4, column 6, length 46: extra characters in tag "91A""

5.3.0 SWFT-392

1-5DBNJF

Error in Network Validated Rule C5 implementation for MT564 has been fixed.

5.3.0 SWFT-381

1-4XE28T

The getStatus() Hawk method in the SwiftReceiver and SwiftSender microagent was not updated properly for messages sent or received for certified publishers and subscribers.

5.3.0 SWFT-134

1-1GJJ6A

An obscure error message displays when an incorrect configuration instance name is given in the adapter’s properties file. For example, if you rename an adapter instance in TIBCO Designer, but do not update the adapter’s tibco.configurl property in the properties file, the following error message was displayed:

Processing

/tibco/private/adapter/SwiftSenderConfiguration3/Swift

Adapter ... "Invalid assoc key:

/tibco/public/session/adapter/SwiftSenderConfiguration

/HawkSession/name/

This has been fixed. It now correctly displays the error message as "Invalid URL".

5.2.0 SWFT-363

1-4T6K81

TIBCO ActiveMatrix Adapter for SWIFT threw a validation error for a valid message conforming to the Network Rule C2 of Message Type 535.

5.2.0 SWFT-340

1-491REP

When the adapter processed messages using the MQSA interface, tracking information was not properly added to the message. Every SWIFT message had the same tracking ID and the tracking tree contained information of all the previous messages processed.



28 | Release Notes

5.2.0 1-30YC61 The SWIFT Migration tool did not map the custom schema and SWIFT schema properly when the BusinessWorks activities were grouped.

5.2.0 SWFT-307

1-1ZFHUU

A parsing error occurred when NOK was used as the currency.

5.1.1 SWFT-210

1-1HUD91

When using SwiftSender in FTP Mode, there was a possibility of duplicate messages going to SWIFT Alliance Access.

5.0.1 SWFT-695

1-N9P2A

When a message with a large value in the MESS field of datatype clob was inserted into the database, the adapter displayed the following error: Java.sql.SQLException: ORA-00600: internal error code, arguments: [kokleva], [], [], [], [], [], [], [] .

5.0.1 SWFT-696

1-NUK99

The SWIFT TIBCO IntegrationManager Custom Task for Renderer did not publish the SWIFT message when the UseSDK flag in the TIBCO IntegrationManager property file was switched off.

5.0.1 SWFT-684

1-G2WZ1

The adapter did not process enter characters present in fields.

5.0.1 SWFT-685

1-I5A7L

In the case of IBM AIX and Microsoft IIS FTP servers, the SWIFT Receiver used to hang when there were no files present on the FTP directory that was being polled. This has been fixed.

5.0.1 SWFT-691

1-IGX8L

A SWIFT message was not published and an error was thrown when NOK was used as currency.

5.0.1 SWFT-687

1-IGX73

The adapter did not start on machines containing the non en_US locale.

5.0.1 SWFT-688

1-IGX7K

The provided sample for TIBCO Integration Manager Custom Task was not working properly.

5.0.1 SWFT-690

1-IGX8A

Custom Task for parser did not publish an ActiveEnterprise object.



Known Issues | 29

Known Issues

The table in this section lists known issues in this release.

Defect # Summary/Workaround

SWFT-1045 Summary When migrating TIBCO ActiveMatrix BusinessWorks Plugin for SWIFT from an old version to a new version, if the SWIFT Scheme Loader shared resource is put into a directory (except the root directory), the SWIFT Scheme is not updated automatically.

Notes When updating from the version directly before the current version, this issue does not occur. For example, when migrate from the version 5.10 to 5.11, the issue does not occur.

Workaround To update the SWIFT Scheme, complete the following steps:

1. In the Specification label of SWIFT Schema Loader, change the current specification into another from the dropdown list and then save the project.

2. Change the specification back again from the Specification dropdown list and then save the project.

3. In the Message Types label of SWIFT Schema Loader, check the checkboxes for the old messages selected before.

SWFT-1019 Summary After installing TIBCO ActiveMatrix Adapter for SWIFT 5.10 successfully, it cannot be found in TIBCO Administrator.

Workaround Reboot the computer.

SWFT-743 Summary When migrating from a previous version of TIBCO ActiveMatrix Adapter for SWIFT to a new version without deleting the older version, the SWIFT Adapter data path of the new version TIBCO ActiveMatrix Adapter for SWIFT is appended in the property ADSWIFT_DATA in the bwengine.tra . However, when running the process containing the SWIFT plugin activity, it throws the "There was an error locating the Metadata." ] , Exception StackTrace: ["Please make sure that you have the 'data' folder in the metadata folder."] error.

Workaround Open file bwengine.tra and locate the property java.property.ADSWIFT_DATA .

and

Remove the data path of the previous installed version of TIBCO ActiveMatrix Adapter for SWIFT and keep the data path of the latest TIBCO ActiveMatrix Adapter for SWIFT version.


30 | Release Notes

SWFT-596

1-984SM3

Summary Occasionally, when the TIBCO ActiveMatrix Adapter for SWIFTNet is started from TIBCO Administrator, an internal security error is displayed.

Workaround From the lib directory of SWIFTAlliance Remote API’s installation (for example - C:\SWIFTAlliance\RA\lib), copy the files to the ADAPTER_HOME/bin directory.

SWFT-595

1-984SLL

Summary The adapter throws a Connection Exception as it is unable to find the SWNET_CFG_PATH environment variable even when it is defined in the shell session on UNIX platforms.

Workaround Add the SWNET_CFG_PATH environment variable to the adraha.tra file as follows:tibco.env. SWNET_CFG_PATH=<path to ra_config.properties file>

SWFT-541

1-8DBRLL

Summary Custom microagents have not been implemented for this release of the TIBCO ActiveMatrix Adapter for SWIFTNet. Only Standard and Class microagents are available.

Workaround None.

SWFT-445

1-6Y0Y5Q

Summary In CASmf mode, the adapter’s NetworkReport schema does not support the original message type and the receiver Bank Identifier Code (BIC).

Workaround The TIBCO ActiveMatrix Adapter for SWIFTNet - FIN provides an improved way to handle the parsing of acknowledgment messages. For more information, see TIBCO ActiveMatrix Adapter for SWIFTNet - FIN User’s Guide, Chapter 11: Processing Acknowledgment Messages.

SWFT-386

1-536W7D

Summary When the adapter receives a FIN string that cannot be parsed, it does not publish or log an error message that contains the entire offending message.

Workaround None.



Known Issues | 31

SWFT-145

1-3W62CM,1-1GQZI5,1-3WBNVR

Summary When using SwiftSender in CASmf Mode, SwiftSender does not shut down when it detects that CASmf is down.

Workaround

• Under normal shut down of CASmf or SAA:

a. Send an exit message to the adapter instances to shut them down.

b. Bring CASmf down.

• If CASmf crashes, stop the adapter manually.

Note that you can use a Hawk rule to automatically shutdown or restart the SwiftSender on detection of the CASmf crash but we recommend that you alert an administrator, evaluate the causes of CASmf crash, and then restart everything in the correct order.

SWFT-55

1-1DTEZZ

Summary SwiftReceiver does not poll or process files that contain spaces. For example, on receiving a file named Copy of MT400.txt , the adapter terminates with the following status messages:2003 Nov 25 18:48:19:160 GMT +5 SwiftReceiverConfiguration Error [Adapter] AESWIFT-000079 "SwiftReceiver (using FTP) could not poll remote directory: MT400.txt: No such file or directory." 2003 Nov 25 18:48:19:190 GMT +5 SwiftReceiverConfiguration Error [Adapter] AESWIFT-000007 "The SWIFT adapter is stopping"

Workaround Ensure that each file sent to SwiftReceiver has no spaces in its file name.



32 | Release Notes


tibco activematrix adapter for swift...† support for swift standards release 2010 this release...

Documents