Release Notes for IBM WebSphere Transformation Extender Pack for SWIFT Version 4.3.3

Content

IBM WebSphere Transformation Extender Pack for SWIFT
Version 4.3.3 release notes

© Copyright IBM Corporation 2006, 2014. All Rights Reserved.

=======================================================================
CONTENTS
========================================================================

1. About this release
2. Installation and configuration information
3. Known limitations, problems and workarounds
4. New and changed behavior
5. Resolved Authorized Program Analysis Reports (APARS)
6. Contacting customer support
7. Notices and trademarks

=======================================================================
1. ABOUT THIS RELEASE
=======================================================================

This release is a full version of the product.

Where to find the software to download

To download the software for this release of the product, go to Passport Advantage Online.

For details about supported hardware and software, see the system requirements.

What's new in this release

• Support is provided for Standards Release 2014 (MT).
• Support is provided for MX schemas for Standards Release 2014 (MX).
• The MX Validation Framework supports Extended Validation for all MX supported in the pack.
• The MT and MX Translation Maps are now included as examples.

Documentation notes

Documentation for this product is provided in Portable Document Format (PDF) and in an IBM Eclipse help system called an information center. Instructions for accessing both the PDF documentation and the information center are provided below. For more information about WebSphere Transformation Extender product documentation, see the Documentation release notes.

PDF

PDF documentation installs with the product. After the installation is complete, you can access the documentation from the Windows Start menu.

Information center

Documentation for this product is also available in the WebSphere Transformation Extender information center which installs with the product and is accessed through the WebSphere Transformation Extender Design Studio Help menu and from the Windows Start menu. An on-line version of the documentation is also available.

Translated documentation

In this release of the product, documentation is provided in English (United States) only.



=======================================================================
2. INSTALLATION AND CONFIGURATION INFORMATION
=======================================================================

Before you install this version of the pack, one of the versions of WebSphere Transformation Extender listed in the following table must first be installed.

Install the pack using the executable (*.exe) file associated with your WebSphere Transformation base product as indicated in the table below:

WebSphere Transformation Extender base product required	ESD site executable file
8.3.0.6	swift4330_83.exe
8.4.0.4	swift4330_84.exe
8.4.1.2	swift4330_841.exe

Installing the pack

Follow these steps to install the pack on Windows systems:

1. Obtain the product media, or image, from the Support Downloads page.
2. Run the setup.exe command. If you are installing the pack from the ESD site, run the part_number.exe command (see the table above).
3. Follow the instructions in the installation program.

Uninstalling the pack

Follow these steps to uninstall the pack from Windows systems:

1. Click Control Panel > Add/Remove Programs.
2. Select the pack that you want to remove.
3. Click Change/Remove and follow the prompts.

Implement the Pack for SWIFT on WebSphere Message Broker

These notes apply when using JEXIT to invoke Java SWIFT Validation in the Pack for SWIFT when running under WebSphere Message Broker or IIB. The JAR files ( jval433.jar and jvcwrap.jar ) should be placed in the "shared-classes" directory for WebSphere Message Broker.

1. Copy jval433.jar and jvcwrap.jar to the WMB "shared-classes" directory.

a) The location of the "shared-classes" directories is dependent on WebSphere Message Broker's work path, To determine the work path, execute the following on the WebSphere Message Broker command console.

mqsireportbroker <my_broker_name>

See this link for details on determining the "shared-classes"

http://www.ibm.com/support/knowledgecenter/SSKM8N_7.0.0/com.ibm.etools.mft.doc/bk58210_.htm

2. Introduce DTX_SWIFT_CONFIG_DIR environment variable in Message Broker to store the location of the jvalnnn.prop.

a. Use the following Message Broker command to add the JVM Option to the Message Broker Execution Group.

mqsichangeproperties <BrokerName> -e <ExecutionGroupName> -o ComIbmJVMManager -n jvmSystemProperty -v"-DDTX_SWIFT_CONFIG_DIR=<absolute_directory>"

b. Use the following Message Broker command to check the jvmSystemProperty value of the JVM Option that is defined for the Message Broker Execution Group.

mqsireportproperties <BrokerName> -e <ExecutionGroupName> -o ComIbmJVMManager -n jvmSystemProperty


NOTE: Refer to the Known Issues section of these release notes for details on APAR PI24585 for using the shared classes directory.

3. Restart WebSphere Message Broker.

=======================================================================
3. KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS
=======================================================================

Patch required to implement the pack in WebSphere Message Broker

In order to implement the WebSphere Transformation Extender Pack for SWIFT JVC component on WebSphere Message Broker, contact IBM customer support to obtain the fix for APAR PI24584. This patch is needed in order to ensure that the jvcwrap.jar and jval433.jar files are invoked from the shared classes directory in WebSphere Message Broker. As a work around, update the CLASSPATH to include references to the jvcwrap.jar and jval433.jar files

Patch required in order to use new MX schemas

In order to use the new MX schemas with WebSphere Transformation Extender 8.3.0.6 or 8.4.0.4, contact IBM customer support to obtain the fix for APAR PI18257. This patch is needed in order to ensure correct XML parsing of the new MX schemas from SWIFT.


Sterling B2B Integrator requirements

In order to use the Pack for SWIFT with Sterling B2B Integrator, the following products are required:

• Pack for SWIFT 4.3.3
• WebSphere Transformation Extender for Integration Servers 8.4.0.4 and later
• Sterling B2B Integrator 5.2.4.1 and later

Supported BIC directory file formats

The WebSphere Transformation Extender Pack for SWIFT supports the TEXT (*.TXT) file format in the SWIFT BIC directory for the FI (BIC) and CU (Currency) files.


Patch required to support transition of Lituania to Eurozone on 1 January 2015

In order to support new network validation on the FIN network for the transition of Lithuania to the EURO currency zone on 1st Janaury 2015, contact IBM customer support to obtain the fix for APAR PI25456. This validation is due to go live on the SWIFT network on 16 November 2014 with the MT 2014 Standards Release. This patch is need to ensure the WebSphere Transformation Extender Pack for SWIFT JVC component will issue an E76 error message if currency LTL is used as settlement currency with a value date later than 31st December 2014. The patch consists of an updated jval433.prop configuration file.



=======================================================================
4. NEW AND CHANGED BEHAVIOR
=======================================================================

Updates to the JVC

The JVC has been updated to extend the use of common methods and error messages for network rule validation that applies to multiple MT messages. Because of this, some of the error messages have changed in order to make them more generic and more reusable across different message types.

MX Validation Framework

In the previous release the MX validation framework only supported MX Extended Validation for a limited subset of supported MX messages. In WebSphere Transformation Extender Pack for SWIFT 4.3.3, Extended Validation is now supported for all MX messages in the Pack. In addition, the Framework has been simplified, and no longer relies on a cross-reference file to match MX schemas with validation map names. The Framework now derives the validation map name from the schema name. Refer to the user documentation for more details.

MT and MX Validation maps

The MT and MX maps have been updated to use the latest available MT and MX Standards. However, since SWIFT no longer maintains the specifications for these translations, they now shipped as examples. This means that these maps are templates for illustration purposes, and are not guaranteed to be complete or fit for purpose, and as such are provided without support. These maps can be found in the folder:

<pack_install_dir>\mx\examples\mt_mx_translation

This folder also contains a readme.txt file. See the readme file for details.


=======================================================================
5. RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARs)
=======================================================================

For a list of the APARs that are fixed in this version of the product, see the Fix List.


=======================================================================
6. CONTACTING CUSTOMER SUPPORT
=======================================================================

Contact Customer Support at 1-800-IBM-SERV, or go to the support portal.


=======================================================================
7. NOTICES AND TRADEMARKS
=======================================================================

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
577 Airport Blvd., Suite 800
Burlingame, CA 94010
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the
names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information
Programming interface information, if provided, is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Privacy policy considerations
IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.

For more information about the use of various technologies, including cookies, for these purposes, see the IBM Privacy Policy, the IBM Online Privacy Statement section entitled "Cookies, Web Beacons and Other Technologies," and the IBM Software Products and Software-as-a-Service Privacy Statement.

Trademarks and service marks
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

• Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
• Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
• Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
• UNIX is a registered trademark of The Open Group in the United States and other countries.

This product includes software developed by the Eclipse Project
( http://www.eclipse.org/).