Installing Microsoft BizTalk Accelerator for SWIFT Message Pack 2009
Microsoft Corporation Published: September 2009
Contents
Prerequisites...... 3 Installing Message Pack 2009...... 4 Configuring Message Pack 2009...... 5 Enabling SWIFT 2009 SRG Validation...... 5 Deploying and Undeploying Assemblies and Policies...... 5 Publishing and Unpublishing InfoPath Forms...... 7 Configuring .NET Framework 1.1/2.0 Assembly Bindings...... 7 Disabling SRG 2009 Validation...... 9 Updating Custom MRSR...... 11 Known Issues...... 11 Uninstalling the Message Pack 2009...... 12
Installing Microsoft BizTalk Accelerator for SWIFT Message Pack 2009
In order to provide industry-standard compliance with the SWIFT 2009 Standards Release Guide (SRG) specification, Microsoft® has released the SWIFT Message Pack 2009 for Microsoft BizTalk® Accelerator for SWIFT (A4SWIFT) 2.1, the SWIFT Message Pack 2009 for Microsoft BizTalk Accelerator for SWIFT (A4SWIFT) 2.3, the SWIFT Message Pack 2009 for Microsoft BizTalk Accelerator for SWIFT (A4SWIFT) 3.0 and 0 and the SWIFT Message Pack 2009 for Microsoft BizTalk Accelerator for SWIFT (A4SWIFT) 2009. Upgrading to this new release provides the compatibility required for ongoing use of the SWIFT standard that is to be imposed starting in November 2009. This document provides upgrade guidance to ensure minimum downtime. It also describes the feature updates in the release so you can plan accordingly. The A4SWIFT Message Pack 2009 contains the following: Complete re-packaging of all SWIFT FIN FF message types and business rules (not just net change). Updates to schemas and business rules that are fully compliant with SWIFT 2009 certification requirements. Support for SWIFT Net Phase 2 PKI header information. Note
Carries forward all hot-fixes related to schemas and business rules that are not superseded by 2009 requirements.
The Microsoft BizTalk Accelerator for SWIFT Message Pack 2009 does not have any components outside of schemas, business rules and Microsoft Office InfoPath® Forms. Prerequisites Ensure that the following prerequisites are installed prior to running setup:
Microsoft Windows Server® 2003 SP2 or Microsoft Windows Server® 2008 depending on the Microsoft BizTalk Server used.
Microsoft BizTalk Accelerator for SWIFT 2.1 Service Pack 1, or Microsoft BizTalk Accelerator for SWIFT 2.3 Service Pack 1, depending on the version of SWIFT you have deployed.
The A4SWIFT Message Pack 2009 is available as two distinct downloadable packages. You can download one, or both of the packages. Which package you choose is dependent on the version of BizTalk Server you have.
A4SWIFT Version and Microsoft Visual C++ 2005 SP1 Microsoft .NET BizTalk Server Version Service Pack Redistributable Framework (if required) Package BizTalk Server 2004 A4SWIFT 2.1 Service Yes 2.0 Pack 1
BizTalk Server 2006 A4SWIFT 2.3 Service No 2.0 Pack 1
BizTalk Server 2006 R2 A4SWIFT 3.0 No 2.0
BizTalk Server 2009 A4SWIFT 2009 No 3.5
Microsoft Visual C++ 2005 SP1 Redistributable Package can be downloaded from http://go.microsoft.com/fwlink/?LinkID=107086
Microsoft .NET Framework 2.0 can be downloaded from http://go.microsoft.com/fwlink/? LinkID=62451
Install the hot fix corresponding to the A4SWIFT version you are working with. This installs the fix for the validation of Country/Currency codes and messaging of MT202COV and MT205COV. A4SWIFT Version Hot fix KB Article Number A4SWIFT 2009 971999 A4SWIFT 3.0SP1 960914 and 972031 A4SWIFT 3.0 954731 and 971998 A4SWIFT 2.3 954730 and 971996 A4SWIFT 2.1 954729 and 971997
Installing Message Pack 2009 To install Message Pack 2009
1. Back up the A4SWIFT database or any other database that is used for SWIFT. Also back up your SWIFT message schemas.
2. Unzip the package corresponding to the A4Swift version you are working with:
A4Swift Version Package Name A4SWIFT 2009 MP_2009_v35 A4SWIFT 3.0 MP_2009_v11 A4SWIFT 2.3 MP_2009_v11 A4SWIFT 2.1 MP_2009_v11 3. Run Setup.exe to install the Message Pack 2009.
4. On the Installation Completed page, click Finish.
Note
As long as Run Configuration Wizard is selected on the Installation Completed page (the default), the Message Pack 2009 configuration wizard will run automatically when you click Finish.
5. After the installation completes, continue to the following section, Configuring Message Pack 2009, to configure the Message Pack as it is mandatory for BRE Validations. Configuring Message Pack 2009 To configure Message Pack 2009
1. On the Microsoft BizTalk Accelerator for SWIFT Message Pack 2009 Configuration page, click DB Configuration in the left pane.
2. In the DB Configuration pane, select Do you want to create a new database group to create the groups shown in the Group pane. Clear Do you want to create a new database group to join an existing database group.
3. Click Apply Configuration.
4. On the Summary page, verify the configuration settings, and then click Apply Configuration.
Note
You can save the configuration settings as an XML file if desired.
5. On the Configuration Wizard page that indicates that you have successfully completed the Configuration Wizard, click Finish.
Note
Installing the SWIFT Message Pack 2009 will not automatically validate messages for SWIFT 2009 SRG compliance. Use the following procedure to enable SWIFT 2009 SRG validation.
Enabling SWIFT 2009 SRG Validation
Deploying and Undeploying Assemblies and Policies To deploy and undeploy assemblies and policies
1. Rebuild and deploy the schema assemblies with the schemas provided in the Message Pack under
The rebuilt schema assemblies need to be installed in the global assembly cache (GAC) on all computers that have the A4SWIFT run-time components installed.
Note
If any custom changes have been made to these schemas, the same changes must be made to the Message Pack schemas after adding them to the schema projects.
Note The Message Pack does not support side-by-side deployment of SWIFT 2009 SRG schema assemblies with SWIFT 2008 SRG schema assemblies.
Message instances that were originally parsed with SWIFT 2008 SRG schema assemblies may be suspended. Suspended messages can then be resumed so that they use SWIFT 2009 SRG schemas and validation policies.
2. Undeploy all existing (SWIFT 2008 SRG) schema assemblies. In a multi-computer environment, you must manually remove these schema assemblies from the GAC on all run-time servers and the Business Activity Services (BAS)/ MRSR Site (A4Swift2009) server.
3. Back up the BREDeployment utility configuration file BREDeployment.exe.config from the
Open the configuration file in Notepad and modify the values of the following keys to point to the appropriate directories in the SWIFT Message Pack 2009 installation directory. For example:
4. Run the BRE Deployment utility and point it to the schema assembly deployed in step 1. 5. Undeploy all existing (SWIFT 2008 SRG) Business Rule Engine (BRE) policies by running the BRE Deployment utility.
Manually remove the A4SWIFT_Codelist and A4SWIFT_Functions vocabularies using the Business Rule Engine Composer tool.
6. Go to
Open the file DBConnection_Master_Policy.xml. Change the “DATBASE SERVER” and “DATABASE NAME”. Ensure that “DATABASE NAME” is the same as you have entered when configuring the Message Pack 2009.
7. Manually deploy policy DBConnection_Master_Policy.xml using the Business Rule Engine Deployment Wizard. The file path to DBConnection_Master_Policy.xml is
8. Run the BRE Deployment utility and point it to the schema assembly deployed in step 1.
Publishing and Unpublishing InfoPath Forms
If Microsoft Office InfoPath 2003 forms have been published previously, they need to be unpublished and republished with the forms in the Message Pack on the server that hosts BAS.
In a command prompt, navigate to the
To work with A4SWIFT 2009 and Message Pack 2009, user needs to generate the InfoPath forms 2007 manually using FormGenerator utility and publish them onto the SharePoint site. The steps to achieve the generation and publishing of forms can be followed from the Form Generator help documentation. Form Generator utility and the related help guides can be downloaded from:
"http://download.microsoft.com/download/F/6/F/F6F63F8A-5505-4D28-91BE-5DF6ECCCE364/Form Generator MT help Guide.docx"
"http://download.microsoft.com/download/F/6/F/F6F63F8A-5505-4D28-91BE- 5DF6ECCCE364/Form_Generator_help_Guide.docx"
"http://download.microsoft.com/download/F/6/F/F6F63F8A-5505-4D28-91BE- 5DF6ECCCE364/FormGenerator.zip"
"http://download.microsoft.com/download/F/6/F/F6F63F8A-5505-4D28-91BE- 5DF6ECCCE364/FormGenerator_MT.zip"
Note: BAS Site has been deprecated in the BizTalk 2009. So, to run the Message repair in SWIFT 2009, user will have to run the MRSR 2009 scenario.
Configuring .NET Framework 1.1/2.0 Assembly Bindings You must configure the assembly bindings on all computers in your environment using .NET Framework 1.1 (in A4SWIFT2.1 environment) or 2.0 (in A4SWIFT2.3/A4SWIFT3.0 environment). Note: If you are using Message Pack 2009 with A4Swift 2009, you can skip this section. To configure .NET Framework assembly bindings
1. In the Control Panel, open Administrative Tools.
2. Double-click Microsoft .NET Framework 1.1/2.0 Configuration.
3. Click the Configured Assemblies node in the left pane of the configuration tool.
4. In the Configured Assemblies section in the right pane, click Configure an Assembly under Tasks. 5. Click Choose an assembly from the assembly cache, and then click Choose Assembly. 6. Select the following assemblies from the assembly cache: Microsoft.Solutions.FinancialServices.SWIFT.CommonFunctions. Ensure the version selected is 2.0.0.0.
Click Select, and then click Finish.
7. On the Binding Policy tab, enter “2.0.0.0” in the Requested Version column and “3.2.0.0” in the New Version column.
8. Click OK to complete the assembly configuration of the Microsoft.Solutions.FinancialServices.SWIFT.CommonFunctions assembly.
9. Repeat steps 4 through 8 to configure the Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas assembly and Microsoft.Solutions.FinancialServices.SWIFT.ValidationMessages.ErrorResources assembly.
10. The configured assemblies shown below can be viewed by clicking the View List Of Configured Assemblies option shown in the screen in step 4.
11. Restart the BizTalk Host service instances and the Business Rule Engine update service.
Disabling SRG 2009 Validation To disable SRG 2009 validation 1. Undeploy all SWIFT Message Pack 2009 BRE policies by running the BRE Deployment utility. Manually remove the A4SWIFT_Codelist and A4SWIFT_Functions vocabulary using the Business Rule Engine Composer tool. 2. Undeploy all existing SRG 2009 schema assemblies and remove them from the GAC on all runtime servers and the BAS server/MRSR site server in your deployment environment. Note
Before rebuilding and redeploying your schemas project, remove all Message Pack 2009 schemas and replace them with schemas from A4SWIFT 2.1/A4SWIFT 2.3/ A4SWIFT 3.0/Message Pack 2008. Any custom changes made to those schemas may not be preserved.
3. Rebuild and deploy the schema assemblies with the schemas provided in the original SWIFT Accelerator under one of the following locations:
This configuration must be removed on each of the run-time computers and the BAS server/MRSR site server in your deployment.
. 8. Rebuild and deploy any projects or assemblies that you had previously used with A4SWIFT 2.1, A4SWIFT 2.3 or A4SWIFT 3.0 or Message Pack 2008 as applicable. Note
For BizTalk Server 2006 and A4SWIFT 2.3, BizTalk Server 2006 R2 and A4SWIFT 3.0, and BizTalk Server 2009 and A4SWIFT 2009:
To facilitate distributed deployments in BizTalk Server 2006 and BizTalk Server 2006 R2, the BizTalk Management database stores a binary copy of each deployed assembly. These copies can be used later during the Windows Installer package creation to deploy any BizTalk application on a large scale.
If you choose to GAC an assembly instead of deploy it, you will not be able to use the Windows Installer feature provided by BizTalk Server 2006. For more information about installing BizTalk Server 2006 in a multi-server environment, see http://go.microsoft.com/fwlink/?LinkId=73512.
Updating Custom MRSR
If you are using custom MRSRs located in the
To update the custom MRSR tables, run the UpdateDefualtDataSRG2006.sql script located in the
If you do not run the script, you will not be able to create patterns specific to the SRG 2009 update. Patterns related to non-SRG2009 changes will continue to function. Known Issues 1. Uninstalling the SWIFT Message Pack 2009 leaves behind the root folder.
Issue: When you uninstall the SWIFT Message Pack 2009, you might notice that the following folder is not deleted: Microsoft BizTalk Accelerator for SWIFT Message Pack 2009.
Resolution: You can safely delete this folder manually after uninstalling the Message Pack.
2. Upgrade from previous version of SWIFT Message Pack to SWIFT Message Pack 2009.
Issue: Upgrade from SWIFT Message Pack 2006 to SWIFT Message Pack 2009 is not supported in following platform:
1. BizTalk2006(Pathfinder) platform (A4swift 2.3 +Sp1,Sql2005,VS2005)
2. BizTalk2004(Voyager) platform (A4swift 2.1+Sp1,Sql2000,VS2003)
Resolution: First uninstall SWIFT Message Pack 2006 and then install SWIFT Message Pack 2009.
3. Failed upgrade
Issue: During Upgrade, upgrade will fail if prerequisite is missing otherwise upgrade will be successful but Upgrade will not show prerequisite missing dialog. Setup Log file will contain particular prerequisite missing statement in case of prerequisite missing.
Resolution: Install prerequisite software mentioned in the Prerequisite section above.
4. Unconfiguring MessagePack deletes A4Swift Database.
Issue: If you don’t close MessagePack configuration wizard before unconfiguring MessagePack, the A4Swift database gets deleted.
Resolution: After configuring MessagePack, close the configuration wizard and start the wizard to unconfigure MessagePack.
5. FSA schema's
Issue: In field 98E (Date Time UTC Indicator) Sign character "N" is not getting validated incase of UTC indicator.
Because of the limitation we have with the schema, we cannot validate the Sign unit. If the user enters any character other than "N", this will not be validated by the schema and the instance will pass successfully and If Sign character is not present in the instance than schema will take first digit of SignFirstPart as a Sign Character.
6. Issue: All the validations for field 98E (Date Time UTC Indicator) have been incorporated except for the one where in we put the Sign character "N" in case of UTC indicator. Because of the limitation we have with the schema, we are not able to validate the sign unit. If the user enters any character, this will not be validated by the schema and the instance will pass successfully and also one more positive instance (:98E::PREP//20080513123548/0215) fails to pass validation.
In the above instance /0215 is the UTCIndicator Sub field. The instance fails validation because it treat 0 as sign unit,21 as SignFirstPart and throw error for secondPart i.e 5. SecondPart field is optional and of length two.
This limitation was pre existing in other MT's (provided by the customer) as well. Uninstalling the Message Pack 2009
1. Click Start, go to Control Panel, and then click Add or Remove Programs.
2. In Add or Remove Programs, click Microsoft BizTalk Accelerator for SWIFT Message Pack 2009, and then click Remove. Copyright Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft, BizTalk, InfoPath, Windows Server are trademarks of the Microsoft group of companies.
SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, SWIFT Net, SWIFT Alliance, SWIFT Standards, SWIFT Ready and Accord are trademarks of S.W.I.F.T. SCRL. Other SWIFT-derived product and service names, such as but not limited to SWIFT Solutions and SWIFT Support, are trade names of S.W.I.F.T. SCRL.
All other trademarks are property of their respective owners.