Special tasks to consider when putting the WBI-FN SR2012 PTFs into production

Flash (Alert)


Abstract

This alert emphasizes two critical post-installation tasks which are required after the PTFs are activated in your production environment. This is the latest information regarding the November 18, 2012, SWIFT Standard Release changes that must be put into production.

Content

With SR2012, SWIFT mandates the use of ASP for FIN.

This means that information regarding how FIN messages need to be handled regarding use of RM filtering, signature handling and more now needs to be retrieved from the ASP.
This ASP data is needed for FIN processing. To make this ASP data available in WBI-FN, PTF UK79884 introduces database changes and an adapted importasp command.

This requires that every customer imports the ASP data after the SR2012 PTFs have been activated, independent of whether or not ASP data have already been imported.

With the use of ASPs for FIN, the handling for FINCopy messages has changed as well.
FINCopy service definitions are now retrieved from the ASP and no longer need to be configured in WBI-FN.

The only exception here is the FINCopy Service TPS.
As TPS is not a unique service, offered by only one Central Institution, but is offered by multiple TPS service providers, WBI-FN needs configuration of the central institution in order to find the appropriate definition in the ASP.

The following configuration is necessary to allow WBI-FN to determine the correct TPS configuration in the ASP:

If you are participating in the TPS service with exactly one TPS service provider:
> add -ou <BOU> -ct DnfFinCopyService -co TPS_LIVE -attr CentralInstitution -val <TPS service provider BIC>
You may additionally specify whether the configuration is to be used for send only or for both send and receive:
> add -ou <BOU> -ct DnfFinCopyService -co TPS_LIVE -attr TransferDirection -val SR

If you are participating in the TPS service with multiple TPS service providers, you need to define for each of the session BICs, which CID to use for TPS:
> add -ou <BOU> -ct DnfFinCopyService -co TPS_<SessionBIC 1>_LIVE -attr CentralInstitution -val <TPS service provider BIC>
> add -ou <BOU> -ct DnfFinCopyService -co TPS_<SessionBIC 2>_LIVE -attr CentralInstitution -val <TPS service provider BIC>
...

You may additionally specify whether the configuration is to be used for send only or for both send and receive:
> add -ou <BOU> -ct DnfFinCopyService -co TPS_<SessionBIC 1>_LIVE -attr TransferDirection -val SR
> add -ou <BOU> -ct DnfFinCopyService -co TPS_<SessionBIC 2>_LIVE -attr TransferDirection -val SR
...

If you are not participating in the TPS service but receive TPS FINCopy messages from any correspondents, you nevertheless now need to configure a Central Institution as a workaround.
You may use any of the TPS service Provider BICs listed in the ASP.
> add -ou <BOU> -ct DnfFinCopyService -co TPS_LIVE -attr CentralInstitution -val <any TPS service provider BIC>
> add -ou <BOU> -ct DnfFinCopyService -co TPS_LIVE -attr TransferDirection -val R

Note: in the case of Receive only, the TPS service provider BIC is only used to ensure correct internal processing, and no message processing is done based on this BIC. If this configuration is not available, any received TPS messages will be stuck in DNF_IAMS, and will not be delivered to the application.

This workaround is necessary until SWIFT defines a final solution regarding how the receive of TPS FINCopy message is to be handled. Once finally defined, IBM will provide the implementation of this solution in a future PTF.


Related information

A Japanese translation is available

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Business Integration for Financial Networks
PTFs

Software version:

3.1.1

Operating system(s):

AIX, z/OS

Reference #:

1617218

Modified date:

2012-11-13

Translate my page

Machine Translation

Content navigation