Installing Microsoft BizTalk Accelerator for SWIFT 2007 Message Pack

In order to provide industry-standard compliance with the SWIFT 2007 Standards Release Guide (SRG) specification, Microsoft has released the Microsoft® BizTalk® Accelerator for SWIFT 2007 Message Pack (A4SWIFT 2007 Message Pack).

Upgrading to this new release provides the compatibility required for ongoing use of the SWIFT standard to be imposed starting in October 2007.

This document provides upgrade guidance to ensure minimum downtime. It also describes the behavior changes in the release so you can plan accordingly.

The A4SWIFT 2007 Message Pack 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 to be fully compliant with SWIFT 2007 certification requirements.
Support for SWIFT Net Phase 2 PKI header information.
Carries forward all hotfixes related to schemas and business rules that are not superseded by 2007 requirements.

The Microsoft BizTalk Accelerator for SWIFT 2007 Message Pack does not have any components outside of schemas, business rules and Microsoft Office InfoPath® Forms.

Prerequisites

The A4SWIFT 2007 Message Pack requires that users also apply 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 the user has deployed.

The A4SWIFT 2007 Message Pack is available as two distinct downloadable packages. You can download both packages from http://go.microsoft.com/fwlink/?LinkId=99620. Which package you choose is dependent on the version of BizTalk Server you have.

BizTalk Server Version	A4SWIFT Version and Service Pack (if required)	A4SWIFT 2007 Message Pack Download to apply
BizTalk Server 2004	A4SWIFT 2.1 as well as Service Pack 1 for A4SWIFT 2.1	BizTalk Accelerator for SWIFT 2.1 2007 Message Pack
BizTalk Server 2006	A4SWIFT 2.3 as well as Service Pack 1 for A4SWIFT 2.3	BizTalk Accelerator for SWIFT 2.3 and 3.0 2007 Message Pack
BizTalk Server 2006 R2	A4SWIFT 3.0	BizTalk Accelerator for SWIFT 2.3 and 3.0 2007 Message Pack

Installing A4SWIFT 2007 Message Pack

To install A4SWIFT 2007 message pack

Back up the A4SWIFT database and your SWIFT message schemas.

Install the A4SWIFT 2007 Message Pack on all computers in the deployment that have A4SWIFT components installed.

Note
Installing the A4SWIFT 2007 Message Pack will not automatically validate messages for SWIFT 2007 SRG compliance. Follow the procedure in the next section to enable SWIFT 2007 SRG validation.

Enabling SWIFT 2007 SRG Validation

On October 27, 2007, the SWIFT Network will enforce mandatory compliance with SWIFT 2007 SRG specifications. You will need to coordinate your A4SWIFT 2007 Message Pack deployment efforts with the SWIFT Network SRG enforcement.

Rebuild and deploy the schema assemblies with the schemas provided in the Message Pack under <installation drive>:\\Program Files\ Microsoft BizTalk Accelerator for SWIFT 2007 Message Pack\SWIFT Messages\A4SWIFT-SRG2007. The rebuilt schema assemblies will have 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 your 2006 schemas, the same changes must be made to the A4SWIFT 2007 Message Pack schemas after adding them to the schema projects.

Note
The A4SWIFT 2007 Message Pack does not support side-by-side deployment of SWIFT 2007 SRG schema assemblies with SWIFT 2006 SRG schema assemblies. Message instances currently being processed that were parsed with SWIFT 2006 SRG schema assemblies may be suspended depending on the level of change between 2006 and 2007 for the message type in question. Any suspended messages can then be resumed so that they use SWIFT 2007 SRG schemas and validation policies.

Note

The A4SWIFT 2007 Message Pack does not support side-by-side deployment of SWIFT 2007 SRG schema assemblies with SWIFT 2006 SRG schema assemblies. Message instances currently being processed that were parsed with SWIFT 2006 SRG schema assemblies may be suspended depending on the level of change between 2006 and 2007 for the message type in question. Any suspended messages can then be resumed so that they use SWIFT 2007 SRG schemas and validation policies.

To enable SWIFT 2007 SRG validation

Undeploy all existing (SWIFT 2006 SRG) schema assemblies. In a multi-computer environment, you must manually remove these schema assemblies from the GAC of all run-time servers and the Business Activity Services (BAS) server.
Undeploy all existing (SWIFT 2006 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.
Back up the BREDeployment utility configuration file BREDeployment.exe.config from the <installation drive>:\\Program Files\Microsoft BizTalk Accelerator for SWIFT\SDK\Tools folder.

Open the configuration file in an editor and modify the values of the following keys to point to the appropriate directories in the SWIFT 2007 Message Pack installation directory. For example:

<add key="BasePoliciesDirectory" value="C:\Program Files\Microsoft BizTalk Accelerator for SWIFT 2007 Message Pack\SWIFT Messages\A4SWIFT-SRG2007 \Base Policies" />                      <add key="SchemasDirectory" value="C:\Program Files\Microsoft BizTalk Accelerator for SWIFT 2007 Message Pack\SWIFT Messages\A4SWIFT-SRG2007 " />                                    <add key="VocabularyDirectory" value="C:\Program Files\Microsoft BizTalk Accelerator for SWIFT 2007 Message Pack\SWIFT Messages\A4SWIFT-SRG2007 \Base Policies\Vocabulary" />

Save this version of BREDeployment.exe.config before starting the BREDeployment utility.
Run the BRE Deployment utility and point it to the schema assembly deployed in step 1.
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.
1. At a command prompt, navigate to the <installation drive>:\\Program Files\Microsoft BizTalk Accelerator for SWIFT 2007 Message Pack\Tools folder.
2. Run FormPublish.exe with the –d option. This will unpublish your previous forms.
3. Then publish the SWIFT 2007 Message Pack InfoPath forms by running FormPublish.exe again with the –p option.
Configure your assemblies using the .NET 1.1 Configuration Wizard. For more information about configuring the assemblies, see Configuring .NET Framework 1.1/2.0 Assembly Bindings later in this document.

Note
This indirection must be performed on each computer that has BizTalk Accelerator for SWIFT 2007 Message Pack installed.

Note
This indirection must be performed on each computer that has BizTalk Accelerator for SWIFT 2007 Message Pack installed.

Disabling SRG 2006 Validation

To disable SRG 2006 validation

Rebuild and deploy the schema assemblies with the schemas provided in the original SWIFT Accelerator under one of the following locations:
- <installation drive>:\\Program Files\Microsoft BizTalk Accelerator for SWIFT\SWIFT Messages\A4SWIFT 2.1
- <installation drive>:\\Program Files\Microsoft BizTalk Accelerator for SWIFT\SWIFT Messages\A4SWIFT 2.3
- <installation drive>:\\Program Files\Microsoft BizTalk Accelerator for SWIFT\SWIFT Messages\A4SWIFT 3.0
- <installation drive>:\\Program Files\Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack\SWIFT Messages\A4SWIFT-SRG2006.
Rebuild and deploy schema assemblies to the GAC on all runtime servers and the BAS server in your deployment environment.
Undeploy all existing SRG 2007 schema assemblies and remove them from the GAC on all runtime servers and the BAS server in your deployment environment.

Undeploy all SWIFT 2007 Message Pack BRE policies by running the BRE Deployment utility. Manually remove the A4SWIFT_Codelist and A4SWIFT_Functions vocabulary using the Business Rule Engine Composer tool.

Note
Before rebuilding and redeploying your schemas project, remove all 2007 Message Pack schemas and replace them with schemas from A4SWIFT 2.1/A4SWIFT 2.3/2006 Message Pack. Any custom changes made to those schemas may not be preserved.

Go to the <installation drive>:\\Program Files\Microsoft BizTalk Accelerator for SWIFT\SDK\Tools folder and back up the existing BREDeployment.exe.config file.
Replace the BREDeployment utility configuration file that was backed up in step 3 of the Enabling SWIFT 2007 SRG Validation section of this document, such that the following keys now point to the appropriate directories in the A4SWIFT 2.1/A4SWIFT2.3/A4SWIFT3.0 or the 2006 Message Pack installation directory. For example:

<add key="BasePoliciesDirectory" value="C:\Program Files\Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack\SWIFT Messages\A4SWIFT-SRG2006\Base Policies" />                       <add key="SchemasDirectory" value="C:\Program Files\Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack\SWIFT Messages\A4SWIFT-SRG2006\A4SWIFT 2.1" />                         <add key="VocabularyDirectory" value="C:\Program Files\ Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack\SWIFT Messages\A4SWIFT-SRG2006\Vocabulary" />

Run the BREDeployment utility and point it to the schema assembly deployed in step 1.
If you published any InfoPath forms previously, you will have to unpublish and republish the forms present in the A4SWIFT 2.1, A4SWIFT 2.3, A4SWIFT 3.0 or 2006 Message Pack installation directory on the BAS server.
1. At a command prompt, navigate to the <installation drive>:\\Program Files\Microsoft BizTalk Accelerator for SWIFT\SDK\Tools folder.
2. Run FormPublish.exe –d. This will unpublish your previous forms.
3. Then publish the InfoPath forms with the following command: FormPublish.exe –p.
Remove the assembly configuration using the .NET 1.1 Configuration Wizard. See Configuring .NET Framework 1.1/2.0 Assembly Bindings for details.

Note
This configuration must be removed on each of the run-time computers and the BAS server in your deployment.

Note
This configuration must be removed on each of the run-time computers and the BAS server in your deployment.

Rebuild and deploy any projects or assemblies that you had previously used with A4SWIFT 2.1, A4SWIFT 2.3 or A4SWIFT 3.0 or 2006 Message Pack as applicable.

Note
For BizTalk Server 2006 and A4SWIFT 2.3 customers, and BizTalk Server 2006 R2 and A4SWIFT 3.0 customers: In BizTalk Server 2006 and BizTalk Server 2006 R2, to facilitate distributed deployments, the BizTalk Management database stores a binary copy of each of the deployed assemblies. This is later used in the Windows Installer package creation that can be reused to deploy any BizTalk application on a large scale. In case you choose to GAC an assembly instead of deploying 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.

Note

For BizTalk Server 2006 and A4SWIFT 2.3 customers, and BizTalk Server 2006 R2 and A4SWIFT 3.0 customers: In BizTalk Server 2006 and BizTalk Server 2006 R2, to facilitate distributed deployments, the BizTalk Management database stores a binary copy of each of the deployed assemblies. This is later used in the Windows Installer package creation that can be reused to deploy any BizTalk application on a large scale. In case you choose to GAC an assembly instead of deploying 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.

Uninstalling A4SWIFT 2007 Message Pack

To uninstall A4SWIFT 2007 message pack

Using Add or Remove Programs, select Remove for Microsoft BizTalk Accelerator for SWIFT 2007 Message Pack.
Restart the computer to ensure the GAC has been updated to reflect the older assemblies now registered. Until the computer is restarted, you may see the higher file versions still in the GAC.

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 SWIFT 2.1 environment) or 2.0 (in SWIFT 2.3/SWIFT 3.0 environment).

To configure the assembly bindings for computers using .NET Framework 1.1/2.0

In Control Panel, open Administrative Tools.
Double-click Microsoft .NET Framework 1.1/2.0 Configuration.
Click the Configured Assemblies node in the left pane of the configuration tool.
In the Configured Assemblies section in the right pane, click Configure an Assembly option under Tasks.
Click Choose an assembly from the assembly cache, and then click Choose Assembly.
Select the following assembly from the assembly cache: Microsoft.Solutions.FinancialServices.SWIFT.CommonFunctions. Ensure the version selected is 3.1.0.0, then click Select, and then click Finish.
On the Binding Policy tab, enter 2.0.0.0 in the Requested Version column and 3.1.0.0 in the New Version column.
Click OK to complete the assembly configuration of the Microsoft.Solutions.FinancialServices.SWIFT.CommonFunctions assembly.
Repeat steps 4 through 8 to configure the Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas assembly.

Note
The configured assemblies can be viewed by clicking the View List Of Configured Assemblies option on the screen discussed in step 4.
Restart the BizTalk Host service instances and the Business Rule Engine update service.

Note
The configured assemblies can be viewed by clicking the View List Of Configured Assemblies option on the screen discussed in step 4.

Known Issues

Problem

A4SWIFT 2006 Message Pack folder and shortcut remains after upgrade to A4SWIFT 2007 Message Pack.

Cause

After upgrade to A4SWIFT 2007 Message Pack, the folder for A4SWIFT 2006/MPR2 does not get deleted. During upgrade from A4SWIFT 2006 Message Pack to A4SWIFT 2007 Message Pack, there is no option to install A4SWIFT 2007 Message Pack at a non-default location.

Resolution

Install the product at default location only and then you can safely delete the A4SWIFT 2006 Message Pack folder after upgrading to A4SWIFT 2007 Message Pack.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

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.

Microsoft, BizTalk, and InfoPath are trademarks of the Microsoft group of companies.

SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, SWIFTNet, SWIFTAlliance, SWIFTStandards, SWIFTReady and Accord are trademarks of S.W.I.F.T. SCRL. Other SWIFT-derived product and service names, such as but not limited to SWIFTSolutions and SWIFTSupport, are tradenames of S.W.I.F.T. SCRL.

All other trademarks are property of their respective owners.