Upgrading to a Future SWIFT Release Year

How to:

This section describes how you can upgrade your channel components to support a future SWIFT release year (for example, 2013 to 2014).

Important: This procedure must be performed on your UAT or test system, and not your production system.
Top of page
x
Procedure: How to Upgrade Your Channel Components for a Future SWIFT Release Year
  1. Import the Ebix file for the future SWIFT release year (for example, 2014) to iSM.
  2. Copy the inbound channel for the current SWIFT release year (for example, Swift2013ToXml_QS2_Pflow_Channel) to create a channel for the future SWIFT release year (for example, Swift2014ToXml_QS2_Pflow_Channel).
  3. Copy the preparser for the current SWIFT release year (for example, SwiftToXml_Preparser_EBIX_2013) to create a preparser for the future SWIFT release year (for example, SwiftToXml_Preparser_EBIX_2014).
  4. Change the year in preparser from the current year (2013) to the future year (2014).
  5. Remove the current SWIFT release year preparser (2013) in the Inlet of the future year channel and add the future SWIFT release year preparser (2014).
  6. From the inbound channel, remove the Ebix file for the current SWIFT release year (for example, 2013) and add the Ebix file for the future SWIFT release year (for example, 2014).
  7. Reset the channel SREGS to point to the appropriate testing locations.
  8. Build the inbound channel for the future SWIFT release year (for example, 2014).
  9. Copy the outbound channel for the current SWIFT release year (for example, XMLtoSWIFT_QS2_Pflow_Channel_2013) to create a channel for the future SWIFT release year (for example, XMLtoSWIFT_QS2_Pflow_Channel_2014).
  10. Copy the route for the current SWIFT release year (for example, XMLtoSWIFT_QS_Route_2013) to create a route for the future SWIFT release year (for example, XMLtoSWIFT_QS_Route_2014).
  11. Copy the process for the current SWIFT release year (for example, XMLtoSWIFT_QS_Process_2013) to create a process for the future SWIFT release year (for example, XMLtoSWIFT_QS_Process_2014).
  12. Add the process for the future SWIFT release year to the future year route. Remove the route for the current SWIFT release year. Add the future year route to the channel for the future SWIFT release year. Remove the old route for the current SWIFT release year.
  13. Remove the Ebix for the current SWIFT release year (2013) and add the Ebix for the future SWIFT release year (2014) to the future year outbound channel (2014).
  14. Edit the process for the future SWIFT release year (2014) with iWay Integration Tools (iIT). Change the year in the preemitter from 2013 to 2014. Save the process and then publish the process.
  15. Build the outbound channel for the future SWIFT release year (for example, 2014).
  16. In the iSM Administration Console, navigate to Server, Register Settings, and update SWIFT_Year and SWIFTVersion from the current year (2013) to the future year (2014).
  17. Restart iSM.
  18. Deactivate the current year channels and then deploy the future year channels.
iWay Software