==============================================================================
==============================================================================
  Licensed materials - Property of IBM

   5724-D96

   (C) Copyright IBM Corp. 2002, 2014  All Rights Reserved.

   US Government Users Restricted Rights - Use, duplication
   or disclosure restricted by GSA ADP Schedule Contract
   with IBM Corp.

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

  README for

   IBM(R) WebSphere(R) Business Integration for Financial Networks
   for Multiplatforms V3.1.1 Base (3.1.1.20)

   PTF UI19670 for APAR PI17958

   Driver level: 4320

   Date 2014-08-22

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

Table of contents
-----------------

A About this document
B Summary of changes
C Planning
D Installation
E APAR details
F Other changes
G Known issues


A. About this document
----------------------

  Only the online version of this readme document is current.
  Before you install the corresponding PTF, download the latest version from:
    http://www.ibm.com/software/integration/wbifn/support

  Download the latest version of the WebSphere BI for FN product documentation
  from:
    http://www-01.ibm.com/support/docview.wss?uid=swg27041133

  The structure of WebSphere BI for FN readme documents is identical for all
  PTFs. Sections that are not applicable are left blank.

  If you install more than one PTF at a time, combine the readme documents by
  merging the contents of each section.

  During the installation phase of this PTF your system cannot process messages.

  This readme document uses the following variables:
   <inst_dir>        The installation directory of WebSphere BI for FN.
                     The directory /opt/IBM is used in examples.
   <instance>        The name of the WebSphere BI for FN instance.
                     The name INST1 is used in examples.
   <ou>              The name of the organizational unit. Depending on the
                     context, this might be SYSOU, DNFSYSOU, or the name of a
                     business OU.

  The names of users, groups, files, and directories are the same as those used
  in WebSphere BI for FN for Multiplatforms Planning, Installation, and
  Customization. If you use different names, use those names instead of the
  names shown here.


B. Summary of changes
---------------------

  APARs addressed by this PTF:

    PI17958 Base SWIFT SR2014: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN
                 MESSAGE VALIDATION
    PI18052 Base MESSAGE VALIDATION IN DOMAIN DNIMX FAILS, WHEN WHITESPACES ARE
                 INCLUDED IN THE MESSAGE
    PI20172 Base MATHEMATIC EXPRESSIONS IN EVENTS AND RESPONSES SHOULD BE AVOIDED
    PI17993 Base THE DOCUMENTED COMPRESSION ENUMERATION VALUES AND THE VALUES OF
                 THE RELATED XML SCHEMA ARE CAUSING PROBLEMS.
    PI19647 Base 0D (CR) GETS LOST IN AN MT021, WHEN PROCESSED BY A DNQERQUEUEINPUT
                 NODE IN MER

  Additional functional changes:

    - S.W.I.F.T. Standard Release 2014 (SR2014) changes for FIN
      This PTF contains the message definition set 'fin2014' for S.W.I.F.T. 
      Standard Release 2014 (SR2014) changes. 
      The WebSphere BI for FN activation date and time for S.W.I.F.T. SR2014 
      changes is 15 November 2014, 16:10:00 GMT. 
      You can install this PTF before this date and time and continue to process
      messages according to the SR2013 message definition set. 
      The SR2014 message definition set is automatically activated on the planned 
      activation date. How to activate the message definition set 'fin2014' before
      its activation date in a test environment is described in this readme in 
      section D12.1. Activate the message definition set for SR2014 for FIN.

    - S.W.I.F.T. Standard Release 2014 (SR2014) changes for MX
      This PTF contains the message definition set 'mx2014' for S.W.I.F.T. 
      Standard Release 2014 (SR2014) changes. 
      The WebSphere BI for FN activation date and time for S.W.I.F.T. SR2014 
      changes is 15 November 2014, 16:10:00 GMT. 
      You can install this PTF before this date and time and continue to process
      messages according to the SR2013 message definition set. 
      The SR2014 message definition set is automatically activated on the planned 
      activation date. How to activate the message definition set 'mx2014' before
      its activation date in a test environment is described in this readme in 
      section D12.2. Activate the message definition set for SR2014 for MX.

  Documentation updates:

    The following manuals have been changed:
    - Application Programming
    - Concepts and Components
    - Messages and Codes
    - System Administration

  The following modules have been changed:
      <inst_dir>/dniv311/admin/toolkit/dni.project.interchange.zip
      <inst_dir>/dniv311/admin/toolkit/dni.schemas.comibmdni.zip
      <inst_dir>/dniv311/admin/toolkit/dni.schemas.swiftFin2010.zip
      <inst_dir>/dniv311/admin/toolkit/dni.schemas.swiftFin2011.zip
      <inst_dir>/dniv311/admin/toolkit/dni.schemas.swiftFin2012.zip
      <inst_dir>/dniv311/admin/toolkit/dni.schemas.swiftFin2013.zip
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.ibmapi.CommonMessageDomainService.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.bulkpmt21.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.cashrep50.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.clearing20.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.collmgmt20.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact10.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact12.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact13.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.einvoice10.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.eni12.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2010.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2011.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2012.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2013.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.funds40.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.funds41.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.funds42.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.funds43.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.funds44.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.funds45.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.mx2012.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.mx2013.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.proxyvote11.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.proxyvote12.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.swiftrem20.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.sys63.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.sys70.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.transrep10.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.transrep10_2013.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIBULKPMT.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNICASHREP.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNICLEARING.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNICOLLMGMT.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNICORPACT.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIEINVOICING.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIENI.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIFIN.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIFUNDS.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIMX.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIPROXYVOTING.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNISNSYS.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNISWIFTREMIT.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.domain.DNITRANSREP.xml
      <inst_dir>/dniv311/run/classes/dni.msgstds.api.jar
      <inst_dir>/dniv311/run/classes/dni.msgstds.impl.jar
      <inst_dir>/dniv311/run/classes/dnicvcks.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_seni1.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfmtxml10.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfmtxml11.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfmtxml12.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfmtxml13.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfunds40.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfunds41.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfunds42.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfunds43.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfunds44.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfunds45.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_ssys63.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_ssys70.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_swiftmx.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_all2012.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_all2013.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_bulkpmt21.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_cashrep50.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_clearing20.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_collmgmt20.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_corpact10.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_corpact12.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_corpact13.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_einvoice10.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_proxyvote11.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_proxyvote12.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_swiftrem20.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_transrep10.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_transrep10_2013.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_seni1.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfmtxml10.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfmtxml11.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfmtxml12.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfmtxml13.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfunds40.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfunds41.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfunds42.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfunds43.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfunds44.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfunds45.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_ssys63.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_ssys70.jar
      <inst_dir>/dniv311/run/classes/dnp.nls.util.jar
      <inst_dir>/dniv311/run/classes/dnp.util.model.jar
      <inst_dir>/dniv311/run/classes/dnp.util.services.jar
      <inst_dir>/dniv311/run/doc/dni.msgstds.api.doc.zip
      <inst_dir>/dniv311/run/jplugin/dni.msg.stds.node.jar
      <inst_dir>/dniv311/run/msg/dnicymsg.cat
      <inst_dir>/dniv311/run/msg/DNIY_Msg.properties
      <inst_dir>/dniv311/run/res/dnicymsg.xml

  The following are new modules:
      <inst_dir>/dniv311/admin/toolkit/dni.schemas.swiftFin2014.zip
      <inst_dir>/dniv311/run/classes/butil.jar
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact14.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2014.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.funds47.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.mx2014.xml
      <inst_dir>/dniv311/run/classes/dnicvcks_sfmtxml14.jar
      <inst_dir>/dniv311/run/classes/dnicvcks_sfunds47.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_all2014.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_corpact14.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfmtxml14.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfunds47.jar
      <inst_dir>/dniv311/run/classes/msgstds.jar


C. Planning
-----------

C0. Announcement of future SR Maintenance starting with SR2015
--------------------------------------------------------------

  Starting with SR2015 IBM will provide message definition sets for 2 additional
  years to the new message definition set. For example, with SR2015, the message
  definition sets for SR2014 and SR2013 will be maintained.
  Older message definition sets and for FIN messages the related MTXML schema 
  files originating in 2010, 2011 or 2012 might get deleted then.

C1. Checks to be done >>BEFORE<< installing a new PTF
-----------------------------------------------------

  1. Check if you have any efixes (emergency fixes) applied in your WebSphere BI
     for FN installation. In case you have efixes installed after your previous
     WebSphere BI for FN PTF installation and migration contact your IBM support
     before installing and migrating this PTF.

  2. Ensure that all previously prepared deployment instructions were carried
     out.

  3. Ensure that all previous CDD changes were implemented using the CDP. To
     check this, log on to AIX on the customization system as a customizer
     (ucust1) and enter the following command on your customization system:

      <inst_dir>/dniv311/admin/bin/dnicdpst -i <instance> -cdefs <cust_defs_dir>

     where
       <instance>       The name of the WebSphere BI for FN instance
       <cust_defs_dir>  The name of the customization definitions directory as
                        specified in the CDP ini file, for example:
                          /var/dni_03_01/cus/defs

     If the response to this command indicates that a customization operation is
     still pending and it was carried out in:
      - Customization mode (dnicdp), implement the pending operation before
        continuing.
      - Migration mode (dnicdpm):
        - Ensure that you have not yet shared the files contained in this or
          any other PTF as described in section D5 step 2.
        - Implement the pending operation before continuing.

  4. Until the migration for this PTF has been completely finished, ensure that
     no changes are made to the currently implemented CDD.

  5. Ensure that all configuration administration changes have been deployed.
     To check this, enter the following commands:
       dnicli -s DNI_SYSADM -ou SYSOU
       > list -ou % -qo amorz
       > list -cos % -qo amorz
       > list -ct % -qo amorz
     Each list command should result in 'No [OU/COS/CT] match search criteria'.

  6. Ensure that all security administration changes have been approved. To
     check this, enter the following commands for each OU:
       dnicli -s DNI_SECADM -ou <ou>
       > list -ro % -qo mor      [only for SYSOU]
       > list -rg % -qo mor      [only for SYSOU]
       > list -user % -qo mor
     The list command should result in 'No roles/role groups/users found that
     match specified criteria'.

C2. Prerequisite and supersede information
------------------------------------------

    This PTF requires the following PTFs:
    - UI19589 for APAR PI21299 (Base 3.1.1.19, COMPLETE RM IMPORT DOES NOT WORK
                                AS EXPECTED)

C3. Roles involved
------------------

    The activities in this PTF involve the following roles:
    - Installer (root)
    - WebSphere MB administrator (uwmba1)
    - First WebSphere BI for FN system configuration administrator (sa1)
    - Second WebSphere BI for FN system configuration administrator (sa2)


D. Installation
---------------

D1. Stopping all sessions and services you use
----------------------------------------------

  Stop all sessions and services, for example:
   - Stop all applications that send requests to WebSphere BI for FN.
   - Log out SIPN FIN LTs.
   - Close MSIF SnF input and output channels.
   - Release SWIFTNet SnF queues.
   - Stop the MSIF Message Transfer service.
   - Stop the Enhanced InterAct service.
   - Close all dnicli sessions.

  For further information, see "Administering and operating components,
  sessions, and services" in "WebSphere BI for FN for Multiplatforms:
  System Administration".

D2. Stopping all application servers
------------------------------------

  NOT APPLICABLE.

D3. Stopping all WebSphere BI for FN message brokers
----------------------------------------------------

  Stop all WebSphere BI for FN message brokers.

D4. Backing up your system
--------------------------

  We recommend to backup your AIX LPAR so that in case of migration issues you
  can revert to your previous system setup and continue to process workload.

D5. Installing PTF by InstallAnywhere
-------------------------------------

  1. Install this PTF using IAW based on the chapter "Installing WebSphere BI
     for FN" in "WebSphere BI for FN for Multiplatforms Planning, Installation,
     and Customization". Please be aware of the directory containing the
     installation data for this PTF has changed compared to the directory
     documented in this chapter, use the path Disk1/InstData/NoVM instead of
     Disk1/InstData/VM.

  2. Ensure that the group ownership of the <inst_dir>/dniv311/admin
     directory and all of its subdirectories and files, is set to group
     dniadmin. To do this, enter the following command in AIX:

     chgrp -R dniadmin <inst_dir>/dniv311/admin

  3. Set the group ownership of the runtime directories and its files to group
     dnilpp. To do this, enter the following command in AIX:

     chgrp -R dnilpp <inst_dir>/dniv311/run


D6. Steps on a customization system
-----------------------------------

  NOT APPLICABLE.

D7. Following the deployment instructions created in step D6
------------------------------------------------------------

  NOT APPLICABLE.

D8. Additional activities
-------------------------

D8.1. DB2 related activities
- - - - - - - - - - - - - - -

  NOT APPLICABLE.

D8.2. WebSphere MB related activities
- - - - - - - - - - - - - - - - - - -

  1. Update the WebSphere MB environment for SR2014 changes for FIN:
  - - - - - - - - - - - - - - - - - - -   - - - - - - - - - - - - - 
    If you have configured the CLASSPATH environment variable in the broker
    configuration as described in "Planning, Installation and Customization"
    the new message definition set libraries:
      <inst_dir>dniv311/run/classes/dnicvrls_sfmtxml14.jar
      <inst_dir>dniv311/run/classes/dnicvcks_sfmtxml14.jar
    and the new configuration file:
      <inst_dir>dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2014.xml
    are automatically recognized as soon as you restart the message broker.

    Activation of the SR2014 message definition set for FIN:

    Note for production environment:
    The WebSphere BI for FN activation date and time for S.W.I.F.T. SR2014 
    changes is 15 November 2014, 16:10:00 GMT.  
    Before this date and time the new message definition set should not be 
    activated on a production environment.

    Note for test environment: 
    To activate the message definition set for SR2014 in a business OU for 
    the test environment refer to section D12.1. in this readme.

  2. Update the WebSphere MB environment for SR2014 changes for MX:
  - - - - - - - - - - - - - - - - - - -   - - - - - - - - - - - - -
    If you have configured the CLASSPATH environment variable in the broker
    configuration as described in "Planning, Installation and Customization"
    the new message definition set libraries:
      <inst_dir>/dniv311/run/classes/dnicvcks_sfunds47.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_all2014.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_mx_corpact14.jar
      <inst_dir>/dniv311/run/classes/dnicvrls_sfunds47.jar
    and the new configuration file:
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact14.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.funds47.xml
      <inst_dir>/dniv311/run/classes/com.ibm.dni.msgstds.defset.mx2014.xml
    are automatically recognized as soon as you restart the message broker.

    Activation of the SR2014 message definition set for MX:

    Note for production environment: 
    The WebSphere BI for FN activation date and time for S.W.I.F.T. SR2014 
    changes is 15 November 2014, 16:10:00 GMT.  
    Before this date and time the new message definition set should not be 
    activated on a production environment.

    Note for test environment:
    To activate the message definition set for SR2014 in a business OU for the
    test environment refer to section D12.2. in this readme.

D9. Restarting all WebSphere BI for FN message brokers
------------------------------------------------------

  Restart all WebSphere BI for FN message brokers.

D10. Customize BAR files when using mqsideploy or the Toolkit to deploy them
----------------------------------------------------------------------------

  NOT APPLICABLE.

D11. Redeploy updated BAR files
-------------------------------

  NOT APPLICABLE.

D12. Migrating configuration data
---------------------------------

D12.1. Activate the message definition set for SR2014 for FIN
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  Activate the message definition set for SR2014 in a business OU for the
  test environment:

  Note for test environment:
  To activate the message definition set for SR2014 in a business OU for the
  test environment:
  1. On the runtime system, log on to AIX with the user ID
     of WebSphere BI for FN system configuration administrator
     (sa1 or sa2).
  2. Execute your profile for the runtime environment, e.g.:
      . /var/dni_03_01/run/dniprofile
  3. Start the command line interface (CLI):
      dnicli -ou SYSOU -s DNI_SYSADM
  4. Enter the following commands in your CLI session to set the SR2014
     message definition set attribute value and commit the change:
      add -ou <ou> -ct DniMsgDomain -co DNIFIN -attr TestMsgDefSet -val fin2014
      com -ou <ou>
  5. Log on to AIX with the user ID of another WebSphere BI
     for FN system configuration administrator.
  6. Execute your profile for the runtime environment, e.g.:
      . /var/dni_03_01/run/dniprofile
  7. Start the command line interface (CLI):
      dnicli -ou SYSOU -s DNI_SYSADM
  8. Enter the following commands in your CLI session to approve
     and deploy the changes:
      app -ou <ou>
      dep -ou <ou>
   Note: In the previous steps, replace <ou> with the business OU for
         which you want to activate the SR2014 message definition set.

D12.2. Activate the message definition set for SR2014 for MX
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  Activate the message definition set for SR2014 in a business OU for the
  test environment:

  Note for test environment:
  To activate the message definition set for SR2014 in a business OU for the
  test environment:
  1. On the runtime system, log on to AIX with the user ID
     of WebSphere BI for FN system configuration administrator
     (sa1 or sa2).
  2. Execute your profile for the runtime environment, e.g.:
      . /var/dni_03_01/run/dniprofile
  3. Start the command line interface (CLI):
      dnicli -ou SYSOU -s DNI_SYSADM
  4. Enter the following commands in your CLI session to set the SR2014
     message definition set attribute value and commit the change:
      add -ou <ou> -ct DniMsgDomain -co DNICORPACT -attr TestMsgDefSet -val corpact14
      add -ou <ou> -ct DniMsgDomain -co DNIFUNDS -attr TestMsgDefSet -val funds47
      add -ou <ou> -ct DniMsgDomain -co DNIMX -attr TestMsgDefSet -val mx2014
      com -ou <ou>
  5. Log on to AIX with the user ID of another WebSphere BI
     for FN system configuration administrator.
  6. Execute your profile for the runtime environment, e.g.:
      . /var/dni_03_01/run/dniprofile
  7. Start the command line interface (CLI):
      dnicli -ou SYSOU -s DNI_SYSADM
  8. Enter the following commands in your CLI session to approve
     and deploy the changes:
      app -ou <ou>
      dep -ou <ou>
   Note: In the previous steps, replace <ou> with the business OU for
         which you want to activate the SR2014 message definition set.

D13. Updating the WebSphere BI for FN enterprise application
------------------------------------------------------------

  NOT APPLICABLE.

D14. Restarting all sessions and services
-----------------------------------------

  Restart all of the sessions and services that you use. How to do this depends
  on which WebSphere BI for FN features you use. For example:
   - Log in SIPN FIN LTs.
   - Subscribe MSIF to SAGs to enable file transfer and session monitoring.
   - Start the MSIF Message Transfer service.
   - Start the Enhanced InterAct service.
   - Acquire SWIFTNet SnF queues.
   - Open MSIF SnF input and output channels.
   - Start the applications that send requests to WebSphere BI for FN.

  For further information, see "Administering and operating components,
  sessions, and services" in "WebSphere BI for FN for Multiplatforms:
  System Administration".

D15. Updating the Toolkit development environment
-------------------------------------------------

  You must update your Toolkit environment if you use:
   - WebSphere BI for FN sample message flows as foundation for your own
     flow development
   - WebSphere BI for FN nodes in your own message flows
   - WebSphere BI for FN message set projects containing XML schema
     definitions, that, for example, are utilized by the XPath wizard

  Furthermore, you have to rebuild and redeploy your message flows that are
  based on the WebSphere BI for FN API.

  The following resources are changed by this PTF:
   - WebSphere BI for FN nodes:
      - DniStandardsProcessing
   - WebSphere BI for FN message sets:
      - dni.schemas.comibmdni.zip
      - dni.schemas.swiftFin2010.zip
      - dni.schemas.swiftFin2011.zip
      - dni.schemas.swiftFin2012.zip
      - dni.schemas.swiftFin2013.zip
      - dni.schemas.swiftFin2014.zip
   - WebSphere BI for FN message set projects:
      - DNI_DniMsgSetMqrfh2 contained in dni.project.interchange.zip

  To install the new versions of the Toolkit resources, follow the instructions
  of the listed sections provided in "Preparing the WebSphere Message Broker
  Toolkit workstation" in WebSphere BI for FN Application Programming:
   - Transferring the WebSphere BI for FN resources
   - Installing the WebSphere BI for FN Eclipse plug-ins

  If you use WebSphere BI for FN sample message flows as foundation for your own
  flow development follow the instructions provided in "Using the sample routing
  flows" in WebSphere BI for FN Application Programming.

  Otherwise, continue with the instructions provided in "Preparing the WebSphere
  Message Broker Toolkit workstation" in WebSphere BI for FN Application
  Programming:
   - Importing WebSphere BI for FN Base sample projects
   - Importing the message sets and sample routing flows

  Additionally, if you use WebSphere BI for FN message set projects containing
  XML schema definitions for your own flow development follow the instructions
  provided in section "Preparing the WebSphere Message Broker Toolkit
  workstation" in WebSphere BI for FN Application Programming:
   - Importing the message sets and sample routing flows
   - Importing XSD files for SWIFT message payloads

D16. Verifying your Installation
--------------------------------

  NOT APPLICABLE.

*------------------------------------------------------------------------------*
*     End of Installation                                                      *
*------------------------------------------------------------------------------*

E. APAR details
---------------

Fixes for the following APARs are contained in this PTF:

 PM17957 Base SWIFT SR2014: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN
              MESSAGE VALIDATION.
              This PTF delivers support for checking FIN messages according to
              the S.W.I.F.T. Standard Release 2014.

 PI18052 Base MESSAGE VALIDATION IN DOMAIN DNIMX FAILS, WHEN WHITESPACES ARE
              INCLUDED IN THE MESSAGE
              Formerly, when whitespaces were included in an MX message for
              message domain DNIMX, validation failed with DNIY0038E.
              Now, whitespaces are allowed.

 PI20172 Base MATHEMATIC EXPRESSIONS IN EVENTS AND RESPONSES SHOULD BE AVOIDED
              Formerly, some events and responses from the message validation,
              for example DNIY0064E, contained mathematic expressions like !=,
              > or <.
              Now, this has been corrected.

 PI17993 Base THE DOCUMENTED COMPRESSION ENUMERATION VALUES AND THE VALUES OF
              THE RELATED XML SCHEMA ARE CAUSING PROBLEMS.
              The documented compression enumeration values in WebSphere BI for
              FN manuals were changed from ZIP, GZIP to Zip and Gzip. In the
              XML schema the values ZIP and GZIP were changed to Zip and Gzip.

 PI19647 Base 0D (CR) GETS LOST IN AN MT021, WHEN PROCESSED BY A DNQERQUEUEINPUT
              NODE IN MER
              Formerly, when node DnqErQueueInput was used during routing in
              MER, the "0d" (CR) was lost from a "0d0a" (CRLF) within an MT021.
              Now, this has been corrected.

F. Other changes
----------------

  - Message updates:
    * Messages changed:
      DNIY0031E, DNIY0032E, DNIY0063E, DNIY0064E, DNIY0109E, 
      DNIY6015E, DNIY6021E, DNIY6022E
    * Messages new:
      DNIY5100E, DNIY6023E - DNIY6026E

G. Known issues
---------------

  NOT APPLICABLE.

++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++