5.13 Running the Migration Utility for SWIFT, Fedwire and ISO20022

Use this migration utility to import and export the SWIFT and Fedwire message configurations. For information on configuring the SWIFT message parameters, see Configuring the SWIFT Message Parameters. For information on configuring the Fedwire message parameters, see Configuring the Fedwire Message Parameters.

The message types provided in this utility are available in the TF_Swift_Migration_Utility/ output/MSG_TYPES directory.

To export the configurations, follow these steps:

  1. Navigate to the TF_Swift_Migration_Utility/config or TF_Swift_Migration_Util- ity/TF_Swift_Migration_Utlity/config directory. For more information on configuring the migration utility see the readme.txt fie within the folder.
  2. Open the Dynamic.properties file and update the placeholders as shown:

    Table 5-7 Configurations required in the Dynamic.properties file when running the export file

    Placeholder Update with...
    ##jdbcurl## Your JDBC URL.
    ##username## The Atomic Schema user name using which you want to execute the files.
    ##password## The Atomic Schema password for the user name.
    ##infodom## Your Infodom name.
    ##SWIFT_MSG_ID##

    Your SWIFT ID. This is available in the n_sanction_swift_msg_id

    column in the dim_sanctions_swift_details table.

    If you are providing multiple IDs, add the IDs separated by commas. For example, 1,2,3,4.
  3. Navigate to the TF_Swift_Migration_Utility/bin directory and run the export.sh SWIFTMSGEXPORT MSG_TYPES command.

MSG_TYPES is the folder name of the folder to which you can export the configurations. Before you perform the export, change the folder name. For example, Exported.

WARNING

Do not change the folder name to MSG_TYPES. This will overwrite

the ready-to-use message types provided with the utility.

To import the configurations, follow these steps:

  1. Navigate to the FIC_HOME/Transaction_Processing/TF_Swift_Migration_Utlity/ config directory.
  2. Open the SWIFT_MSG_TYPES.txt file and add the message types that you want to import to the Exported folder mentioned in the export configuration steps.
  3. Open the Dynamic.properties file and update the placeholders as shown:

    Table 11:

    Table 5-8 Configurations required in the Dynamic.properties file when running the import file

    Placeholder Update with...
    ##jdbcurl## Your JDBC URL.
    ##username## The Atomic Schema user name using which you want to execute the files.
    ##password## The Atomic Schema password for the user name.
  4. Navigate to the TF_Swift_Migration_Utlity/bin directory and run the import.sh SWIFTMSGIMPORT MSG_TYPES command.

MSG_TYPES is the folder name of the folder from where you can import the configurations. Before you perform the import, change the folder name. For example, Imported.

WARNING

Do not change the folder name to MSG_TYPES. This will overwrite

the ready-to-use message types provided with the utility.

After you complete the export and import steps, restart the web server. To verify if the message types have been successfully imported or not, check if the message types are available in the Message Type Configuration field in the Message and Screening Configurations Window.