This file provides important information you should read before using webMethods SWIFT FIN Module 6.1.
Documentation about how to install and upgrade webMethods SWIFT FIN Module 6.1 is located in the webMethods SWIFT FIN Module Installation and User's Guide on the webMethods Bookshelf.
2.0 Known Issues
3.0 Usage Notes
5.0 Deprecated Items
6.0 Globalization
6.1 Localization and Certification
6.2 Configuration
6.3 Known Globalization Issues
7.0 Documentation
7.1 Major Documentation Changes
7.2 Known Documentation Issues
10.0 Viewing the readme for the Previous Version
Check the "webMethods eStandards" section of the Critical Information page on the webMethods Advantage Web site for up-to-date information about running the webMethods SWIFT FIN Module with 6.5 versions of other webMethods components.
Due to a conflict with Java classes, webMethods SWIFT FIN Module cannot be installed on the same Integration Server as webMethods RosettaNet Module, webMethods Chem eStandards Module, or webMethods UCCnet Module. If you will be running any of these three modules you will need to install them on a separate Integration Server.
For other known issues and troubleshooting information relating to webMethods SWIFT FIN Module, see the Knowledge Base on the webMethods Advantage Web site.
None.
1-MDEU7 (FIN_6-0-1_FIX_1)
The webMethods SWIFT FIN Module was failing when parsing SWIFT messages on a
multi-CPU machine under a heavy load. The SWIFT FIN Module no longer fails
under these conditions.
1-QFUX0 (FIN_6-0-1_SP1_Fix2)
Some optional elements were missing from a number of message templates. These
elements have been added to the templates.
1-QG3H1 (FIN_6-0-1_SP1_Fix2)
Invalid data in SWIFT messages was passing Network Validation Rules because the
'isValid' variable was being dropped. This variable is no longer being dropped
and invalid data is correctly causing the Network Validation Rules to fail.
1-QDWNJ (FIN_6-0-1_SP1_Fix3)
The importFinItems service failed to run on Integration Server 6.1. The
importFinItems service now runs successfully on both Integration Server 6.0.1
and Integration Server 6.1.
1-QG3JY (FIN_6-0-1_SP1_Fix4)
The wm.fin.format:convertIDataToFIN service did not end the user-to-user block
with a hyphen('-') as it should. The wm.fin.format:convertIDataToFIN service
now ends the user-to-user block with a hyphen('-').
1-PZSGH (FIN_6-0-1_SP2)
The webMethods SWIFT FIN Module did not support parsing SWIFT messages to the
subfield level. The webMethods SWIFT FIN Module 6.0.1 Service Pack 2 supports
parsing SWIFT messages to the subfield level.
1-Q9IY9 (FIN_6-0-1_SP2_Fix5)
The sender BIC was being incorrectly picked up from Block {1:} for an outbound
message from SWIFT.
1-TSARJ (FIN_6-0-1_SP2_Fix7)
Corrected Network Validation Rule issue regarding Nov03 version of MT103 and
template issue regarding Nov03 version of MT210.
1-UK9LQ (FIN_6-0-1_SP2_Fix8)
Corrected SWIFT FIN Module 6.0.1 service wm.fin.validation:validateIData
Validation Error for the currency code starting with "N".
1-WCDUJ (FIN_6-0-1_SP2_Fix9)
When creating an ISO15022 to ISO775 map, certain loops are missing. This will cause the map not to function
properly.
1-X2MCU (FIN_6-0-1_SP2_Fix11)
WmFINDev package referred to a 'startup' service, which does not exist, in the
manifest.v3 file. This fix overwrites the incorrect manifest.v3 file with a
correct one.
1-X6XG2 (FIN_6-0-1_SP2_Fix12)
Enhance SWIFT FIN Module to add support for May 2005 System messages, Category
1 through Category 9 messages to the SWIFT FIN Module.
1-XS7L7 (FIN_6-0-1_SP2_Fix13)
Corrected issue that WmCASmf was not retrieving ACKs.
1-XZ8HM (FIN_6-0-1_SP2_Fix15)
The 15 tag is not properly converted during outbound processing.
Blocks in Category 3 messages are identified by a 15 tag. When an outbound map is created using the XMLTAG format, the 15 tag is not properly converted during outbound processing. This fix corrects this issue, allowing the 15 tags to be converted correctly.
None.
webMethods SWIFT FIN Module conforms to the international standards of webMethods, which require: operation in any country, locale, or language configuration as listed in the webMethods Installation Guide; support for character encodings; and proper formatting, display, and validation of data (such as number and date formats). These features have been tested in this release and any known issues are listed below.
SWIFT uses a custom character set, which is a subset of 7-bit ASCII (or optionally a subset of EBCDIC code page 037). This means that no field in a SWIFT document can contain accented or multibyte (non-ASCII) characters. The webMethods SWIFT FIN Module enforces this limit and will generate an error instead of sending the document to the SWIFT network. Users are cautioned to normalize their data to ASCII before mapping it to SWIFT documents.
SWIFT provides support for dates and numbers using a specialized internal representation. The webMethods SWIFT FIN Module automatically converts to and from these formats. It also performs time-zone normalization correctly.
SWIFT supports the use of multiple currencies through the use of ISO4217 three-letter currency identifiers. The webMethods SWIFT FIN Module does not currently validate data mapped by users to a currency type field. Therefore users should exercise caution when building flow services to ensure that the currency is handled properly.
webMethods SWIFT FIN Module is provided with an English user interface, messages, and documentation. Language packs containing support for other languages, when available, can be installed at any time using the webMethods Installer. webMethods SWIFT FIN Module 6.1 supports simultaneous multi-locale operation.
webMethods SWIFT FIN Module was tested with ASCII data from SWIFT’s custom character set. It was tested in common European and Far East Asian locales and is supported for operation in any locale provided by your operating environment. The tested environments included French and Japanese Windows.
If you expect to display non-English data in your webMethods tools, make sure an appropriate font is installed in your operating environment. If you see hollow boxes or black squares where you expect to see non-English data, modify your JRE font.properties file to reference an appropriate font. For information on modifying your font.properties file, go to Sun's Java website. For instructions, see:
http://java.sun.com/j2se/1.4.2/docs/guide/intl/fontprop.html
http://www.unicode.org/help/display_problems.html
The configuration of the Trading Networks database affects
the characters the database can contain. If you select a non-Unicode encoding
for the database, characters from outside that encoding will be lost when you
store data in the database. webMethods recommends that you use the most
appropriate Unicode encoding for your database character set. See the webMethods Installation Guide and your
database vendor
Because SWIFT documents contain only a subset of ASCII, they will not be affected by your choice of database encoding. However, you can use Trading Networks for other applications that are affected, and you should consider these issues when configuring your system.
The webMethods SWIFT FIN Module does not have any globalization limitations outside of the character set limitation of the SWIFT network itself.
For webMethods SWIFT FIN Module 6.1 technical documentation, go to the <webMethodsServerDirectory>\packages\WmFIN\pub\doc directory or the webMethods Bookshelf. The following manual is provided as a PDF file:
- webMethods
SWIFT FIN Module Installation and User
To view the documentation, you must have Adobe Acrobat Reader 4.0 or later.
For information regarding this release of webMethods SWIFT FIN Module, see the webMethods SWIFT FIN Module 6.1 Release Notes on the webMethods Bookshelf.
For information about technical support, see the webMethods General Support Statement.
None.
webMethods Administrator, webMethods Broker, webMethods Dashboard, webMethods Developer, webMethods Fabric, webMethods Glue, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Mobile, webMethods Modeler, webMethods Monitor, webMethods Optimize, webMethods Portal, webMethods Trading Networks, and webMethods Workflow are trademarks of webMethods, Inc. webMethods and the webMethods logo are registered trademarks of webMethods, Inc.
All other marks are the property of their respective owners. Copyright (c) 2005 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form.
SWIFT, S.W.I.F.T., Sibos, and SWIFT-derived product and service names (such as but not limited to SWIFTNet and SWIFTAlliance) and the SWIFT logo are trademarks of S.W.I.F.T. SCRL.
SWIFT is the trading name of S.W.I.F.T. SCRL. All other products or company names mentioned on this site are trademarks or registered trademarks of their respective owners.
Authorized technical support contacts can reach webMethods Customer Care for support via:
E-mail: support@webMethods.com
US Phone: 1-888-222-8215
Europe/EMEA Phone: +800-963-84-637 or +31-207783640
Asia/Pacific Phone: +612-8913-1198 or +656-389-3222
Self-service support is also available in the webMethods Advantage Knowledge Base and in the Advantage Customer Forums.
To view information about the previous release of webMethods SWIFT FIN Module, see the previous readme on the webMethods Bookshelf.
ESTD-SWIFTFIN-RM-6-1-20050729