Installing BizTalk Server 2010 Accelerator
for SWIFT
BizTalk Technical Article
Writer: Maria Quian
Technical Reviewer: Andres Naranjo, Mandi Ohlinger
Published: June 2012
Applies to: BizTalk Server 2010 Accelerator for SWIFT
Summary: The foundation for a successful installation of Microsoft BizTalk Server 2010
Accelerator for SWIFT (A4SWIFT) is an understanding of the A4SWIFT features and the
BizTalk components on which each feature depends. Each A4SWIFT feature depends
on other properly configured BizTalk components. Other considerations that affect
building an A4SWIFT environment include an existing network infrastructure and an
already configured BizTalk Server environment. This document will refer and use the
existing documentation for building BizTalk Server environments. A4SWIFT inherits all
software and hardware requirements for BizTalk Server 2010.
An installation guide is available for each A4SWIFT related component but not a single
compiled document that elaborates on the installation/configuration steps. This
document will bring them together and identify some of the common issues encountered
during installation and configuration.
Copyright
This document is provided “as-is”. Information and views expressed in this
document, including URL and other Internet website references, may change without
notice. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are
fictitious. No real association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property
in any Microsoft product. You may copy and use this document for your internal,
reference purposes.
© 2011 Microsoft. All rights reserved.
Contents
Introduction ..................................................................................................................................... 5
SWIFT Overview .......................................................................................................................... 6
Windows Groups and Service Accounts ...................................................................................... 7
Common A4SWIFT Installation Issues ......................................................................................... 7
Users and Groups ........................................................................................................................ 9
Databases Used by A4SWIFT ..................................................................................................... 10
BizTalk Server 2010 ................................................................................................................... 11
Installing and Configuring BizTalk Server 2010 SWIFT Accelerator ............................................... 12
A4SWIFT 2010 Installation ........................................................................................................ 12
A4SWIFT 2010 Configuration .................................................................................................... 19
Installing and Configuring SWIFT Message Pack 2011 .................................................................. 26
Prerequisites.............................................................................................................................. 26
Preparing a Previously Configured Environment ...................................................................... 27
Installing Message Pack 2011 .................................................................................................... 28
Configuring Message Pack 2011 ................................................................................................ 36
Enabling SWIFT 2011 SRG Validation ........................................................................................ 42
Deploying and Undeploying Assemblies and Policies ........................................................... 42
Other Tasks ............................................................................................................................ 53
Publishing and Unpublishing InfoPath Forms ........................................................................... 54
How to Publish a Generated *.xsn forms .................................................................................. 54
Updating Custom MRSR ............................................................................................................ 59
Using the Custom MRSR SDK......................................................................................................... 60
Installing the Custom MRSR ...................................................................................................... 60
Prerequisite ........................................................................................................................... 60
Configuring SharePoint adapter in BizTalk Server 2010 for MRSR site ................................. 60
Building the Custom MRSR solution ...................................................................................... 64
Deploying the CustomMRSR Project ..................................................................................... 66
Step to deploy new SharePoint site ...................................................................................... 67
Step to add new MX message pattern in data base .............................................................. 67
Building the Profile Web Client Site ...................................................................................... 67
Step in IIS 6.0: ...................................................................................... 67
Step in IIS 7.0/7.5: ................................................................................ 68
Build Profile Web Client ........................................................................................................ 68
Steps in IIS 6.0 ...................................................................................... 69
Steps in IIS 7.0/7.5 ................................................................................ 69
Steps to Configure Integrated Security ................................................................................. 69
Registering the COM+ serviced component.......................................................................... 70
Certificates............................................................................................................................. 70
Profile Web Client User Manual ............................................................................................ 70
Introduction
This document is intended for experienced BizTalk Server 2010 users. It is also
recommended to have some level of familiarity with SWIFT Guidelines and its
implementation using Microsoft BizTalk Accelerator for SWIFT.
The foundation for a successful installation of Microsoft® BizTalk® Server 2010
Accelerator for SWIFT (A4SWIFT) is an understanding of the A4SWIFT features and
the BizTalk components on which each feature depends. Each A4SWIFT feature
depends on other properly configured BizTalk components. Additional considerations
that affect building an A4SWIFT environment include an existing network
infrastructure and an already configured BizTalk Server environment. This document
will refer and use the existing documentation for building BizTalk Server
environments. A4SWIFT inherits all software and hardware requirements for BizTalk
Server 2010.
An installation guide is available for each A4SWIFT related component but there is
not a single compiled document that elaborates on the installation/configuration
steps or how they relate to each other. This document will bring them together and
identify some of the common issues encountered during installation and
configuration. A4SWIFT is most commonly deployed in a multicomputer, distributed
environment and the recommendations will apply to both a single and multicomputer
environment.
You must install the same edition of A4SWIFT as your BizTalk Server 2010
installation.
A4SWIFT Enterprise can be installed on BizTalk Server 2010 Enterprise and
Developer edition.
A4SWIFT Standard can be installed on BizTalk Server 2010 Standard edition.
In addition each SWIFT Accelerator version must be installed with the appropriate
BizTalk Server version. The complete list is documented below. Message Pack
2011 only updates BizTalk Server 2009 and BizTalk Server 2010.
5
BizTalk Server version SWIFT Accelerator version
BizTalk Server 2004
A4SWIFT 2.1
BizTalk Server 2006
A4SWIFT 2.3
BizTalk Server 2006 R2
A4SWIFT 3.0
BizTalk Server 2009
A4SWIFT 2009
BizTalk Server 2010
A4SWIFT 2010
Because a successful A4SWIFT installation is dependent on a properly
installed/configured BizTalk Server, you must review and follow the installation
documentation for the appropriate BizTalk Server version.
The following categories of information are discussed in detail in the single server
and multicomputer environment; please review the installation guide that applies to
the environment you intend to build. Refer to the BizTalk Server 2010
Documentation (http://go.microsoft.com/fwlink/?LinkId=253153) for each section
below.

Choosing your BizTalk Server Features and Components

Feature Dependency Matrix

Hardware Requirements

Software Requirements

Considerations When Installing BizTalk Server 2010
SWIFT Overview
BizTalk Accelerator for SWIFT (A4SWIFT) extends the BizTalk Server environment to
provide the most comprehensive, reliable, and secure delivery of financial messaging
using the SWIFT format and network for customers in banking, capital markets,
payments, and corporate finance. A4SWIFT has been awarded the SWIFTReady Gold
Financial EAI label. To maintain compliance with the SWIFT Standards Release Guide
(SRG) specification, a Message Pack is released yearly. Download the latest
available BizTalk Server Accelerator for SWIFT Message Pack 2011 and installation
guide at BizTalk Server Accelerator for SWIFT Message Pack 2011
(http://go.microsoft.com/fwlink/?LinkId=253159).
Microsoft BizTalk Server 2010 FileAct and InterAct Adapters provide connectivity
between Microsoft BizTalk Server and the SWIFT secure IP network (SIPN) via the
SWIFTNet link (SNL) APIs. SIPN enables SWIFT customers to transfer messages and
files using InterAct and FileAct. This communication occurs over a secure, private
network and facilitates bilateral communication between financial industries, industry
infrastructures, and customers. The SWIFTNET FileAct and InterAct adapters are not
covered here. For more information on the adapters, please refer to: Microsoft
6
BizTalk Server 2010 FileAct and InterAct Adapters
(http://go.microsoft.com/fwlink/?LinkId=253159).
Windows Groups and Service Accounts
In a multicomputer installation, you must manually create all of the domain groups
and accounts before you configure A4SWIFT just like you did for BizTalk Server
installation in a multicomputer environment. The same information applies to the
domain groups and accounts as in a BizTalk Server 2010 installation except:

Domain Local Groups are not supported because their use requires that all of the
servers, including SQL Servers, in the BizTalk Server infrastructure must belong
to the same domain. When domain local groups are used, the installation
components: “A4SWIFT Components” and “Web Components for Message Repair
and New Submission” will not be available (grayed out) for installation. For more
information about Active Directory groups, see "Group Scope" in the Windows
Server® 2008 product Help at http://go.microsoft.com/fwlink/?linkid=93663.

A4SWIFT Users and A4SWIFT Administrators groups are needed for the A4SWIFT
installation. They must be domain level groups when installing/configuring in a
multicomputer environment.

User installing Microsoft BizTalk 2010 Accelerator for SWIFT should be part of the
BizTalk Server Administrators group.

Custom MRSR model requires a new group - A4SWIFT Department
Administrators. Create the A4SWIFT Department Administrators group as
appropriate: in a single server environment, it is a local group, and in a multiserver environment this group is a domain global group.

MRSR requires Windows SharePoint Services installed and configured. Refer to
Appendix A in Installing BizTalk Server 2010 on Windows Server 2008 R2 and
2008.docx (http://go.microsoft.com/fwlink/?LinkId=253153) for complete
instructions on prerequisites, installation and configuration instructions.
Common A4SWIFT Installation Issues
The causes of failed installation and configuration depend on the environment.
Below is a list of the most common installation and configuration problems. The
suggested items to check are to be considered based on your particular environment.
Behavior: One or both components (A4SWIFT Components and Web components
for Message Repair and New Submission) are grayed out during A4SWIFT
installation.
Check:
1. The required components such as BizTalk Server Runtime components are properly
configured.
2. The user account used for installation is part of the BizTalk Server Administrators group.
3. The groups used to configure BizTalk Server are global.
7
Behavior: Error message - Installation cannot be performed because the BizTalk
Server has not been configured or user account is not a member of the BizTalk
Server Administrators group.
Check:
1. Review the installation or configuration log. If the message is not enough to isolate the
cause then review steps 2-7 below.
2. You will need to capture a network monitor trace
(http://go.microsoft.com/fwlink/?LinkID=103158) (netmon) during the installation.
3. The Primary Domain Controller (PDC) must be reachable in order to complete the
installation/configuration. Review the netmon traces captured and validate that the
BizTalk Server gets a response when it sends a request for the PDC to validate the login
user against the BizTalk Server Administrators group.
4. A common issue is that the PDC is not reachable. One suggestion, if possible, is to
temporarily move the PDC emulator to the same network segment where BizTalk Server
is located.
5. You can modify the LMHOSTS file in the BizTalk Server to aid in name resolution and
domain validation. Please review http://support.microsoft.com/kb/314108.
6. If the issue is with name resolution of the PDC and adding the LMHOSTS file doesn’t
resolve the issue, verify that the local area connection properties (“Enable LMHOSTS
Lookup” and “Enable NetBIOS over TCP/IP”) for Internet Protocol are both checked. To
enable “Enable LMHOSTS Lookup” and “Enable NetBIOS over TCP/IP”, open the
Network and Sharing Center, select Change Adapter Settings, right-click the network
connection, and select Properties. Select Internet Protocol Version 4 (TCP/IPv4) and click
Properties then the Advanced button in the displayed. Click on WINS tab, check on
“Enable LMHOSTS Lookup” and select “Enable NetBIOS over TCP/IP” settings.
7. Once again depending on your network architecture, you might need to open UDP
ports: 137 and 138. As well as TCP ports: 139, 389 and 445. For a complete list, please
review http://support.microsoft.com/kb/832017.
8
Users and Groups
The following table lists the Windows® groups and their membership used by
A4SWIFT. It also identifies the SQL Server® Roles or Database Roles for the group.
Group
Group Description
Membership
SQL Server Roles or
Database Roles
A4SWIFT
Administrators of the
Administrators BizTalk Accelerator for
SWIFT Management
Console (MMC) for
configuration of the
Message Repair and
New Submission
workflow.
Contains only users
who are allowed
access to the MMC
component of
A4SWIFT and can
configure Message
Repair and New
Submission.
DBO role for the
A4SWIFT and MRSR
custom profile
(customMRSRprofile)
databases
A4SWIFT
Users
Contains users who
are assigned the
Create, Repair,
Verify or Approve
role and who have
access to the MRSR
(A4SWIFT Message
Repair & Submission
Runtime) folders in
SharePoint portal.
They have read
access rights.
a4swift_limited for
A4SWIFT and MRSR
custom profile
(customMRSRprofile)
databases.
Contains only users
that are allowed to
manage The
A4SWIFT Profile
Web Client
a4swift_limited for
the A4SWIFT and
MRSR custom profile
(customMRSRprofile)
databases
Users of the A4SWIFT
Message Repair and
New Submission
Workflow.
Administrators of the
A4SWIFT
A4SWIFT Profile Web
Department
Client
Administrators
Full control:
1. User Management
2. Department
Management
3. Message Workflow
Stage
Management
4. Profile
Management
5. Global
Configuration
Properties
A4swift_limited role
should be assigned
db_denydatawriter
role for the MRSR
profile database
(customMRSRProfile)
a4swift_deptadmin
(new role) in the
MRSR profile
(customMRSRprofile)
database
9
Databases Used by A4SWIFT
The following is the list of SQL Server databases used in BizTalk Server 2010.
Data
store
name
Default
database
name
Volume Growth Description
A4SWIFT A4SWIFT
(default
name)
Database
Low
Low
This database contains all of the settings for
message repair. It also contains the
currency and country information used
during message validation.
Custom
MRSR
Profile
Database
Low
Low
This database contains all the tables
necessary for the Profile website. For detail
information on the objects created in this
database review the SQL scripts included
with the Accelerator.
No
default
name
available
1.
2.
3.
4.
CreateCustomMRSRTables
CreateCustomMRSRStoredProcedures
InsertDefaultData
SetCustomMRSRDbPermissions
10
BizTalk Server 2010
Before installing A4SWIFT, your BizTalk Server Configuration must show properly
configured components. Follow the Installation guidelines documented for BizTalk
Server 2010 as well as the prerequisites:




Internet Information Services (IIS)
Enable IIS website to use ASP.NET
Windows SharePoint Services 3.0 with SP1/SP2 or SharePoint Server 2007.
SharePoint Foundation 2010 cannot be used to configure MRSR.
All the recommendations in the installation guides apply. Refer to the BizTalk Server
2010 Documentation (http://go.microsoft.com/fwlink/?LinkId=253153).
Successfully configured BizTalk Server:
11
Installing and Configuring BizTalk Server 2010 SWIFT Accelerator
A4SWIFT 2010 Installation
1. Run setup.exe to start the installation.
2. Click “Install Microsoft BizTalk 2010 Accelerator for SWIFT on this computer”.
3. Fill out the Customer Information fields (User Name, Organization and Product Key).
Accept the License Agreement.
4. Select Complete or Custom installation. For the rest of the screens, Complete is
selected.
Installation Options:
12


You can modify the install path
Click Next
13
Custom Installation:
Review the Description for each of the components to install:
The screen print shows the description for A4SWIFT Component. Below is a list of
the most important components and their description. You can pick and choose
which component to install based on your A4SWIFT implementation requirements.
A4SWIFT Components – A4SWIFT components are required for full processing of
SWIFT messages using BizTalk Server 2010. They are dependent on BizTalk Server
2010 runtime installed/configured.
Message Repair and Reconciliation – Provides pipeline components,
orchestrations, runtime schemas and an A4SWIFT database required for SWIFT
Message creation, repair and reconciliation.
Web Components for Message Repair and New Submission – Web Components
for Message Repair and New Submission will create Web Services for validation,
certificate security, history and BIC (Bank Identifier Code) lookup.
14
If you are not going to provide users an interface to repair, verify and approve
messages then you do not need the Message Repair and Reconciliation and/or Web
Components for Message Repair and New Submission.
A4SWIFT 2010 requires Windows SharePoint Services 3.0 SP1/SP2 or SharePoint
Server 2007 only if using the custom MRSR SDK. The BizTalk Server SharePoint
Adapter must be installed/configured.
With A4SWIFT 2010, the SWIFT Messages (xsd schemas and BRE validation policies)
are provided as part of the installation of Message Pack 2010. To validate after the
installation is complete, two new directories are created under <drive>:\Program
Files (x86)\Microsoft BizTalk Accelerator for SWIFT and <drive>:\Program Files
(x86)\Microsoft BizTalk Accelerator for SWIFT 2010 Message Pack.
5. Review the Summary. As stated earlier, Message Pack 2010 will be installed as part of
the A4SWIFT 2010 installation. If you need to comply to SRG (SWIFT Standards Release
Guide), you will need to install the latest Message Pack available. At the time of writing
this document, the latest available version is Message Pack 2011. Message Pack 2011
and installation guide are available at BizTalk Server Accelerator for SWIFT Message
Pack 2011 (http://go.microsoft.com/fwlink/?LinkId=253159).
15
Summary:
6. Installation Progress screen included just for reference.
16
7. Installation Completed, make sure you leave “Run Configuration Wizard” selected if you
want to complete the configuration. If you are going to complete the configuration
after installing Message Pack then uncheck “Run Configuration Wizard”.
17
18
A4SWIFT 2010 Configuration
These steps can be completed after Message Pack 2011 is installed.
1. On the Microsoft BizTalk 2010 Accelerator for SWIFT Configuration screen. You have
two options if a complete installation was selected: configure MCRR and WebService.
MCRR will only show if “A4SWIFT Components” was installed
WebService will only show if “Web Components for Message Repair and New
Submission” ” was installed
2. MCRR - Allows you to create or point to an existing A4SWIFT database. You also need
to specify the domain A4SWIFT Administrators and A4SWIFT Users. If single server then
the groups will be created during configuration. WebService – Allows you to submit
messages using the MRSR (Message Repair and New Submission) functionality.
Overview:
19
MCRR properties:
20
WebService properties:
21
3. The Summary screen is provided just for reference. To successfully complete the
installation, you must ensure that you complete the configuration wizard with a
Configuration Result of “Success”. If the configuration fails, take the time to understand
why by reviewing the generated log file. Otherwise, there will be other issues that will
be more difficult to identify later.
Summary:
22
Successful Configuration:
Click Finish, the Microsoft BizTalk Server Configuration displays next:
23
Post installation/configuration steps:
1)
2)
BizTalkServerApplication, the account under which this service runs needs to be part of
the A4SWIFT Users group because the host Message Repair runtime component needs
access to the BizTalk Server database.
The service account for the Web application that the A4SWIFT_MRSR Web service runs
under cannot be Network Services. You should change it to a local or domain account
that is a member of the A4SWIFT Users group.
At this point, you are ready to continue and finish installing the latest updates. You
can also validate the installation and configuration in the BizTalk Administration >
BizTalk Server 2010 > BizTalk Group > Applications <All Artifacts>.
After installation,
Resources listed:
-
Microsoft.Solutions.FinancialServices.SWIFT.MX.RuntimeSchemas
Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas
24
Orchestrations listed:
-
FrrOrchestration.FrrMain
After configuration,
Resources listed:
-
Microsoft.Solutions.FinancialServices.SWIFT.MX.RuntimeSchemas
Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas
Microsoft.Solutions.FinancialServices.SWIFT.FRROrchestration
Microsoft.Solutions.FinancialServices.SWIFT.FRRSchemas
Orchestrations listed:
-
FrrOrchestration.FrrMain
In IIS, it will create the Web service
-
A4SWIFT_MRSR
25
Installing and Configuring SWIFT Message Pack 2011
Installing Microsoft BizTalk Accelerator for SWIFT Message Pack 2011 guide is
available at http://go.microsoft.com/fwlink/?LinkId=253159.
Most of the text is from the Message Pack Installation guide but screen prints are
added only where necessary to include more detailed information.
As mentioned earlier, Message Packs provides industry-standard compliance with the
SWIFT Standards Release Guide (SRG) specification. Follow the steps below if you
need your environment to be industry-standard compliant with the latest available
Message Pack 2011.
The A4SWIFT Message Pack 2011 has the following features:




The repackaging of all SWIFT FIN FF message types and of all business rules.
Updates to schemas and to business rules to make the schemas and the business rules
fully compliant with the SWIFT 2011 standards.
All the hotfixes that are related to schemas and to business rules but that are not
outdated by the SWIFT 2011 certification requirements. BizTalk Accelerator for SWIFT
Message Pack 2011 does not contain any components other than schemas, business
rules, and Microsoft Office InfoPath forms.
Support for SWIFTNet Phase 2 PKI header information.
Prerequisites
For the full version of the installation guide, refer to Installing Microsoft BizTalk
Accelerator for SWIFT Message Pack 2011, at
http://go.microsoft.com/fwlink/?LinkId=253159. The document outlines the
prerequisites for A4SWIFT Message Pack 2011 which is only available for A4SWIFT
2009 and 2010 as previously stated.
The Message Pack 2011 is available as one downloadable package, MP_2011_v35.
Version requirement and prerequisites included for your reference:
26
Preparing a Previously Configured Environment
These steps are only necessary for environments that were previously using Message
Pack 2010 to process SWIFT messages.
1. If any schemas and Business Rule Engine (BRE) rules are deployed from an earlier
version of message pack, then run the BREDeployment utility and point it to the schema
assembly. Undeploy all existing (SWIFT 2010 SRG) BRE policies by running the BRE
Deployment utility. This utility is located by default at <drive>:\Program Files
(x86)\Microsoft BizTalk Accelerator for SWIFT\SDK\Tools.
2. Manually remove the A4SWIFT_Codelist and A4SWIFT_Functions vocabularies using the
Microsoft BizTalk Server 2010 Business Rule Composer Tool under Facts Explorer pane.
3. Back up the A4SWIFT database or any other database that is used for SWIFT. Also back
up your SWIFT message schemas. Refer to SQL 2008 product documentation on how to
back up a SQL Database, http://msdn.microsoft.com/en-us/library/ms187510.aspx.
27
Installing Message Pack 2011
Steps to install Message Pack 2011 on a previously configured or newly installed
A4SWIFT 2010 environment.
1. Run Setup.exe to install the Message Pack 2011.
2. On the “Customer Information” screen, fill out the name, organization and product key,
click Next. On the “License Agreement” screen click Accept.
28
Installation Options, select “Complete” or “Custom”.


You can modify the installation directory, and then click Next.
If you click on Custom Installation, you can select which components to install.
29
30
Summary:
31
The screens below were captured to show the installation progress for your
reference. You will see something similar to the screens below.
32
If installation seems to stop responding, check that the window above is not
pending to continue, as this dialog box tends to come up behind the setup
wizard. Click OK, and the installation will continue.
33
34
3. On the Installation Completed screen, click Finish.
35
Configuring Message Pack 2011
If this is a new environment, complete the section titled “A4SWIFT Configuration”
before configuring Message Pack 2011.
1. On the Microsoft BizTalk Accelerator for SWIFT Message Pack 2011
Message Pack Configuration screen, click DB Configuration in the left
pane.
2. In the DB Configuration pane, select “Do you want to create a new
database group” and enter/validate the data store and group information.
Clear the ”Do you want to create a new database group” checkbox in
order to join an existing database group.
NOTE: If you have already configured A4SWIFT, you will want to clear the “Do you
want to create a new database group” checkbox. If this is the first time you run the
configuration wizard, select the “Do you want to create a new database group”
checkbox. The recommendation is to clear it and create the additional tables in the
A4SWIFT database previously configured.
36
Verify that the Windows Group contains the correct information for your
domain\A4SWIFT Administrators Group and domain\A4SWIFT Users Group.
3. Click Apply Configuration.
4. On the Summary page, verify the configuration settings, and then click
Next.
Note
You can save the configuration settings as an XML file if desired.
37
5. On the Configuration Wizard page that indicates that you have successfully completed
the Configuration Wizard, click Finish.
38
Click Next. Microsoft BizTalk Accelerator for SWIFT 2011 Message Pack
Configuration screen provided as a reference. If successfully configured, you
will have the status shown below.
39
The database tables created during the A4SWIFT configuration are shown below in
the “Before” screen print. Once you run Message Pack Database configuration
steps, the “After” screen identifies the 3 tables created during Message Pack
Database Configuration. The 3 tables added are:



CountryCode_List
CurrencyCode_List
LegacyCurrencyCode_List
40
Before:
After:
Note
Installing the SWIFT Message Pack 2011 will not automatically validate
messages for SWIFT 2011 SRG compliance. Use the following procedure
to enable SWIFT 2010 SRG validation.
41
Enabling SWIFT 2011 SRG Validation
Deploying and Undeploying Assemblies and Policies
If this is a new environment, you do not have to perform steps: 1 and 2 above. You
only have to make sure you use the latest available DLLs from the Message Pack
when you create a new A4SWIFT application.
1. Undeploy all existing (SWIFT 2010 SRG) schema assemblies. In a multi-computer
environment, you must manually remove these schema assemblies from the global
assembly cache (GAC) on all run-time servers and the MRSR Site
(A4Swift2009/A4Swift2010). To uninstall the assembly from the GAC, you can Navigate
to the GAC, which is located at %systemdrive%\Windows\Assembly. Right-click each
assembly file that is included in your application, click Uninstall, and then click Yes to
confirm. You can also undeploy from a Visual Studio command prompt using the
command without quotes, “gacutil /u <fully qualified assembly name>”.
2. Rebuild and redeploy the schema assemblies with the schemas provided in the Message
Pack. Open your custom solution used to deploy the application, modify the updated
Message Pack schemas and the referenced assemblies to point to the new assemblies.
For updated schemas, the default directory is <drive>:\Program Files (x86)\Microsoft
BizTalk Accelerator for SWIFT 2011 Message Pack\SWIFT Messages\A4SWIFT-SRG2011.
For new assemblies, refer to default path <drive>:\Program Files (x86)\Microsoft BizTalk
Accelerator for SWIFT 2011 Message Pack\Assemblies.
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
2011 SRG schema assemblies with SWIFT 2010 SRG schema assemblies.
Message instances that were originally parsed with SWIFT 2010 SRG
schema assemblies may be suspended. Suspended messages can then be
resumed so that they use SWIFT 2011 SRG schemas and validation
policies.
42
NOTE: Use the DLLs included in the latest Message Pack 2011 to rebuild your
SWIFT projects in Visual Studio. You want to add a reference in Visual Studio to the
latest DLLs available in the latest installed Message Pack. The new assemblies are
located at %SystemDrive%\Microsoft BizTalk Accelerator for SWIFT <Current Year>
Message Pack\Assemblies.
If this is not a new environment, follow normal operation guidelines to allow active,
dehydrated or suspended instances to complete or resume using the updated
assemblies. In an ideal scenario, you want to be able to start the installation without
having any pending instances during a pre-scheduled system down time.
3. Back up the BREDeployment utility configuration file BREDeployment.exe.config from
the <drive>\Program Files (x86)\Microsoft BizTalk Accelerator for SWIFT\SDK\Tools
folder.
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 2011 installation
directory. For example:

<add key="BasePoliciesDirectory_MT" value="%Program
Files%\Microsoft BizTalk Accelerator for SWIFT 2011 Message Pack\SWIFT
Messages\A4SWIFT-SRG2011\Base Policies" />

<add key="SchemasDirectory_MT" value="%Program Files%\Microsoft BizTalk
Accelerator for SWIFT 2011 Message Pack\SWIFT Messages\A4SWIFT-SRG2011"
/>

<add key="VocabularyDirectory_MT" value="%Program Files%\Microsoft
BizTalk Accelerator for SWIFT 2011 Message Pack\SWIFT Messages\A4SWIFTSRG2011\Base Policies\Vocabulary" />

<add key="LogFileName_MT" value="C:\Documents and Settings\All
Users\Application Data\BREDeploymentLog.txt" />
Sample BREDeployment.exe.config file below depending on your installation path.
Verify that the paths are correct.
<?xml version="1.0"?>
<configuration>
<appSettings>
<add key="BasePoliciesDirectory_MT" value="C:\Program Files
(x86)\Microsoft BizTalk Accelerator for SWIFT 2011 Message Pack\SWIFT
Messages\A4SWIFT-SRG2011\Base Policies" />
<add key="SchemasDirectory_MT" value="C:\Program Files
(x86)\Microsoft BizTalk Accelerator for SWIFT 2011 Message Pack\SWIFT
Messages\A4SWIFT-SRG2011" />
43
<add key="VocabularyDirectory_MT" value="C:\Program Files
(x86)\Microsoft BizTalk Accelerator for SWIFT 2011 Message Pack\SWIFT
Messages\A4SWIFT-SRG2011\Base Policies\Vocabulary" />
<add key="LogFileName_MT" value="C:\Documents and Settings\All
Users\Application Data\BREDeploymentLog.txt" />
<add key="LogFileName_MX" value="C:\Documents and Settings\All
Users\Application Data\BREDeploymentLog_MX.txt"/>
<add key="VocabularyDirectory_MX" value="C:\Program
Files(x86)\Microsoft BizTalk Accelerator for SWIFT\SDK\MX Messages\Base
Policies\Vocabulary"/>
<add key="SchemasDirectory_MX" value="C:\Program Files
(x86)\Microsoft BizTalk Accelerator for SWIFT\SDK\MX Messages"/>
<add key="BasePoliciesDirectory_MX" value="C:\Program Files
(x86)\Microsoft BizTalk Accelerator for SWIFT\SDK\MX Messages\Base
Policies"/>
</appSettings>
</configuration>
The following section applies to errors you will experience if BREDeployment utility configuration
is not done correctly. Use them to troubleshoot.
Behavior:
Error message: The type initializer for
'Microsoft.Solutions.FinancialServices.SWIFT.BreValidator.BreValidator' threw an exception.
Check:
The BREDeployment.exe.config file might be improperly formatted or corrupt.
Behavior:
If you get an error like the below screen print when you attempt to use the BRE
Deployment Utility.
Check:
-
Make sure that the paths specified in the BREDeployment.exe.config in the previous
step are correct.
44
-
The BREDeployment.exe.config file cannot contain blank spaces in the incorrect places
or blank lines anywhere.
The error above displays only when the BREDeployment.exe.config contains invalid
paths, blank lines at the end of the file or is improperly formatted.
4. Run the BRE Deployment utility and point it to the schema assembly deployed in step 2.
NOTE: Postpone this step until steps 5-7 are done if this is a new installation. You
will run this step after you have your A4SWIFT application created.
5. If the section “Preparing a Previously Configured Environment” is not already done, you
can manually remove all existing (SWIFT 2010 SRG) Business Rule Engine (BRE) policies.
Manually remove the A4SWIFT_Codelist and A4SWIFT_Functions vocabularies using the
Business Rule Composer tool.
Behavior: After completing steps 5 above, you are unable to undeploy A4SWIFT_Codelist and
A4SWIFT_Funtions vocabularies because some policies remain deployed.
Check: The reason is because policies for obsolete message types fail to undeploy.
You must manually undeploy and remove them using the Business Rule Composer.
6. Go to <drive>:\Program Files (x86)\ Microsoft BizTalk Accelerator for SWIFT 2011
Message Pack\SWIFT Messages\A4SWIFT-SRG2011\Base Policies.
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 2011.
NOTE: “DATBASE SERVER” is actually “DATABASE SERVER” in the
DBConnection_Master_Policy.xml file. It is the server name where the default A4SWIFT
database exists.
7. Manually deploy policy DBConnection_Master_Policy.xml using the Business Rule
Engine Deployment Wizard. The file path to DBConnection_Master_Policy.xml is
<drive>:\Program Files (x86)\Microsoft BizTalk Accelerator for SWIFT 2011 Message
Pack\SWIFT Messages\A4SWIFT-SRG2011\Base Policies\.
For a new installation, the business rule composer has no policies deployed.
To manually deploy the DBConnection_Master_Policy.xml policy, from All Programs
select Microsoft BizTalk Server 2010 then select the Business Rule Engine
Deployment Wizard. The following screen prints is the set of windows displayed
while manually deploying the policy, DBConnection_Master_Policy.
45
Select “Import and publish Policy/Vocabulary to database from file”
46
47
Verify populated information.
48
Select Browse and point to <Drive>:\Program Files (x86)\Microsoft BizTalk
Accelerator for SWIFT 2011 Message Pack\SWIFT Messages\A4SWIFTSRG2011\Base Policies\DBConnection_Master_Policy.xml
49
50
After step 7 is completed and in a new installation, the Microsoft Business Rule
Composer only has the DBConnection_Master_Policy. The policy should be listed as
Deploy. If listed as Publish, change it to Deploy.
51
Behavior: If the DBConnection_Master_Policy is only Publish and not Deploy and
you submit a message, you will see a warning in the application event log:
Source: BizTalk Accelerator for SWIFT
Type:
Warning
Event ID: 4099
Description:
Unable to retrieve or an unexpected error occurred while executing BRE validation
policy. It this is unexpected, confirm that the policy has been deployed and try
again. Error: An exception occurred inside the rule engine instance executing policy
"DBConnection_Master_Policy".
Check: In the screen print above, change the DBConnection_Master_Policy Version
1.0 from “Published” to “Deployed”.
8. Run the BRE Deployment utility and point it to the schema assembly deployed in step 2.
It only needs to be done if you have previously configured the Custom MRSR.
Otherwise disregard.
52
If CustomMRSR is set up, run the SQL script below on your custom MRSR Profile
database:
• InsertDefaultData.sql.
Script Path: <Drive>:\Program Files (x86)\Microsoft BizTalk Accelerator for
SWIFT\SDK\Samples\CustomMRSRModel\DB\
Other Tasks
These steps are necessary to update any currently deployed or new pipelines with the latest
available pipeline components. The SQL script run in step 6 must be run to update the
default data inserted for MRSR Message Repair. If you are not using MRSR Message Repair,
you do not need to run steps 6 – 8.
1. Open the Pipeline project which you have already created in Microsoft Visual
Studio®. Undeploy the Pipeline project, delete the Swift Disassembler from the
Disassemble stage shape in Receive Pipeline and also delete it from the BizTalk
Pipeline Components Toolbox. Save the Pipeline project and close Visual Studio.
2. Reopen the Pipeline project in the Visual Studio then from the Tools menu, click
Choose Toolbox Items. In the Choose Toolbox Items dialog box, on the BizTalk
Pipeline Components tab, select SWIFT Disassembler, and then click OK.
3. From the View menu, click Toolbox. Under the BizTalk Pipeline Components
Toolbox, click SWIFT Disassembler and drag it to the Drop Here box below the
Disassemble stage shape in BizTalk Pipeline Designer. Leave the SWIFT
Disassembler shape selected in the BizTalk Pipeline Designer.
4. In the Properties pane, reset the properties of Swift Disassembler. Save your
changes.
5. Deploy the Pipeline project.
6. If CustomMRSR is set up in your system, run the below SQL script on your
custom MRSR Profile database: InsertDefaultData.sql. Script Path:
<Drive>:\Program Files\Microsoft BizTalk Accelerator for
SWIFT\SDK\Samples\CustomMRSRModel\DB\
7. Restart IIS by doing an "IISReset". This will restart all IIS-related services.
8. Restart BizTalk Host Instance services.
9. Test all scenarios that may be impacted.
53
Publishing and Unpublishing InfoPath Forms
This section is included for reference only. Before attempting to generate the forms
please contact Microsoft support to obtain the latest steps or InfoPath forms.
Generating InfoPath Forms using Form Generator Tool will support only Visual
Studio 2008 and Infopath Form 2007, Generated InfoPath Form with other than
above version will not work as expected.
1) Go to output folder <DestinationFolderPath>. In <DestinationFolderPath>, open the
folder of the InfoPath form template for which you want to generate the form. For
Example, if you want to generate the MT103 InfoPath form, then open the MT103
folder which is present at DestinationFolderPath and open the TemplateDS.sln.
2) In the Solution Explorer, double-click the manifest.xsf. It will open the design file of the
InfoPath form.
3) In the manifest.xsf, go to Tools, Form Options, Security and Trust" menu option. Check
the "Full Trust" option must be enabled for the permission.
4) Check the box "Sign this form Template". Click on "Select certificate". In this, select the
certificate with which you want to sign the form. Click OK.
5) Save the manifest.xsf.
6) Go to View, Design Tasks. On the Design Tasks pane, click "Publish Form Template"
option.
7) In the publishing wizard window, select "To a network location" and click next.
8) In the "Form template path and file name" textbox type :
“http://localhost/sites/BASSite/Templates/MTXXX.xsn” and type MTXXX in the Form
Template name textbox and click next.
9) Click Next.
10) Click Publish and close.
11) In Internet Explorer, open your SharePoint site at
http://localhost/sites/bassite/templates.
12) Point to MTxxx, click the down arrow next to it, and then click Edit Properties.
13) In the Templates: MTxxx window, in the Namespace box, type
http://schemas.microsoft.com/BizTalk/Solutions/FinancialServices/SWIFT/Envelope
MTxxx, and then click Save and Close.
How to Publish a Generated *.xsn forms
1) Open Microsoft InfoPath Designer 2010
2) File Open InfoPath Form Template (*.xsn)
3) Click OK
54
4) In the File Tab, under Form Information select Advanced form options.
5) On Form Options and select Security and Trust
6) Create Certificate then Select Certificate, Click OK
7) In the File Tab under Publish select Network Location
8) If you get this warning, you can click Ignore:
55
In Microsoft Office 2010 install Visual Studio Tools for Applications
9) If you get this warning, you can click Ignore
After clicking Ignore then click OK
56
57
Under Server Manager, click Configure IE ESC, on Set Internet Enhanced Security
Configuration (IE ESC) window turn off for Administrators.
58
Go to http://servername/sites/BASSite/Templates
Select the form just published, right click Edit Properties – add Description and
Namespace
Note
Generating InfoPath Form using Form Generator Tool on Environment
which has vs2010 and InfoPath 2010 require XSN Template which is
generated and published to any network location by using Visual
Studio 2008 and InfoPath 2007. InfoPath Template (XSN) available at
network location for given Message will be published using InfoPath
2010.
Test MRSR by Dropping Invalid Instance at specified location mentioned in End To
End Scenario.
Note
Refer A4SWIFT Documentation to know functionality of MRSR and
Preparation of E2E (End to End) Scenario which were required to gain
basic understanding on MRSR before using of MRSR feature of
A4SWIFT.
Updating Custom MRSR
If you are using custom MRSRs located in the <drive>:\%Program Files%\Microsoft BizTalk
Accelerator for SWIFT \SDK\Samples\CustomMRSRModel folder, you must update the tables
in the custom MRSR database to make the Message Pattern feature compatible with changes in
the SWIFT 2011 Standards Release Guide specifications.
To update the custom MRSR tables, run the UpdateDefaultDataSRG2006.sql script located in the
<drive>:\Program Files\Microsoft BizTalk Accelerator for SWIFT Message Pack
2011\SDK\Samples\CustomMRSRModel\DB\SRG2006\ folder.
If you do not run the script, you will not be able to create patterns specific to the SRG 2011
update. Patterns related to non-SRG2011 changes will continue to function.
59
Using the Custom MRSR SDK
The MRSR SDK is not a complete solution. The steps below document how to set up MRSR in a
single server environment.
Only complete this section if you need to provide users with a repair site for messages that fail
validation. The content below is from the documentation included after installing A4SWIFT 2010.
Go to <drive>:\Program Files (x86)\Microsoft BizTalk Accelerator for
SWIFT\SDK\Samples\CustomMRSRModel\:
-
Readme.txt – Installing the Custom MRSR SDK
ProfileWebClientUserManual – Includes instructions on how to setup users, department,
profiles used during message repair.
Installing the Custom MRSR
Prerequisite
1. Windows SharePoint Services 3.0 with SP2 – Refer to the BizTalk Server Installation guide
(http://go.microsoft.com/fwlink/?LinkId=253153) for instructions on setting up SharePoint for use
with BizTalk Server.
2. Verify that SharePoint 3.0 Central Administration is configured.
Configuring SharePoint adapter in BizTalk Server 2010 for MRSR site
1. Validate that SharePoint is configured correctly.
Open BizTalk Server 2010 configuration, click on SharePoint adapter, verify
Windows SharePoint Services Adapter website has "Default Web Site" value
selected, otherwise reconfigure SharePoint adapter with Windows SharePoint
Services Adapter website value with "Default Web Site".
For instructions on how to configure and extend the Default Web Site please
refer to Installing BizTalk Server 2010 on Windows Server 2008 R2 and
2008.docx – Appendix A. Download document from
http://go.microsoft.com/fwlink/?LinkId=253153.
60
2. Setting up NT groups, SQL Permissions, and MRSR profile database:
The A4SWIFT Users and the A4SWIFT Administrators should already have
been created by the A4SWIFT 2010 installation or at the directory domain
level. The custom MRSR model requires a new group - A4SWIFT
Department Administrators, for the custom MRSR sample. Create the
A4SWIFT Department Administrators group appropriately - in a single
server environment, this group is a group on the local server, and in a
multi-server environment this group is a domain global group in the
domain.
Note
61


In a single server environment, this group is a group on the local server,
and in a multi-server environment this group is a domain global group in
the domain.
In a distributed server environment, this group should be present in all
servers; if not present, these groups need to be created manually. This
is needed due to an issue with MRSRSPUtility.exe that must be run later
to create and configure SharePoint Site. They can be deleted once all
the steps in this document are completed including the Profile Web
Client configuration.
NOTE: The information below is also included in the section above, Users and
Groups.
Add A4SWIFT Department Administrators as a login to the SQL Server:
1. In SQL Enterprise Manager, select Security / Logins. Right-click, Add Login, and then
enter <Server Name/Domain> A4Swift Department Administrators. Click OK.
2. Add the A4SWIFT Department Administrators group as a user in the A4SWIFT database,
with the role a4swift_limited.
62
3. Create the custom MRSR profile database - needs to be separate from the A4SWIFT
database.
4. Add a4swift_limited (case sensitive) role to the custom MRSR profile database, select
the db_denydatawriter role.
5. Create a new role called a4swift_deptadmin (case sensitive) in the custom MRSR
database.
6. Grant privileges to the A4SWIFT Users, A4SWIFT Administrators and A4SWIFT
Department Administrators groups to the custom MRSR profile database.



For the A4SWIFT Users, assign the a4swift_limited role.
For the A4SWIFT Administrators group, assign DBO role.
For the A4SWIFT Department Administrators group, assign a4swift_deptadmin role.
63
Run the following SQL scripts in the following order on your custom MRSR Profile
database found in the DB folder. The DB folder default location is <drive>:\Program
Files (x86)\Microsoft BizTalk Accelerator for
SWIFT\SDK\Samples\CustomMRSRModel\DB.
1. Create database objects using the script CreateCustomMRSRTables.sql.
2. Create database stored procedures using the
scriptCreateCustomMRSRStoredProcedures.sql.
3. Set appropriate permissions for the database objects using the script
SetCustomMRSRDbPermissions.sql.
4. Run the InsertDefaultData.sql script.
Building the Custom MRSR solution
On a development machine, open a visual studio command prompt.
NOTE: Building the Custom MRSR solution (You only need to do this step
once in your environment and use it as necessary to deploy to all A4SWIFT
servers in the group).
1. cd <Swift 2010 Install directory>\sdk\samples\CustomMRSRModel\ProfileMgmt
2. Extract the public key from the key file using the command “sn -p CustomMRSR.snk
publickey” without quotes.
3. Now the file publickey contains the public key of the key pair generated.
4. Extract the public key token from the public key using the command “sn -t publickey”
without quotes.
This will display the public key token in the line reading "Public key token is
................" The hex-number in the message is the public key token.
64
1. cd <Swift 2010 Install directory\sdk\samples\CustomMRSRModel\db
2. Open the file SetCustomMRSRConfigParameters.SQL in notepad.
The first Insert statement in this SQL file contains the fully qualified name of the
ProfileFinder assembly. Replace the string
__USE_YOUR_PUBLIC_KEY_TOKEN_HERE__ in this command with the public key
token extracted above.
The 2nd Insert statement in this SQL file contains the connection string to the Custom
MRSR database that stores the profiles. Change "localhost" to the name of the SQL
Server that is hosting the custom MRSR profiles database. Change the database
name ("CustomMRSR") to the name of the database that is used for the Custom
MRSR functionality.
The 3rd, 4th and 5th Insert statement in this SQL file contains the A4Swift Windows
Group Names. Change “localhost” to the local server name (in the case of a single
server installation) or the name of the domain (in the case of a multi-server
installation).
Save the SetCustomMRSRConfigParameters.SQL file
3. Run SQL Query Analyzer (isql/w) and run the SetCustomMRSRConfigParameters.SQL
against the A4SWIFT database (not the MRSR profile database).
65
Deploying the CustomMRSR Project
1. Open CustomMRSRModel.sln and verify the paths of the referenced assemblies in the
projects. Change these paths as appropriate in your installation environment.
The following are the referenced assemblies and their corresponding paths:
Assembly
Folder
Microsoft.Solutions.FinancialServices.SWIFT.* <Swift 2010 Installation directory>Microsoft BizTalk
Accelerator for SWIFT\Assemblies folder
Microsoft.BizTalk.ExplorerOM
<BizTalk Server 2010 installation
directory>\Microsoft BizTalk Server 2010\Developer
Tools
Microsoft.XLANGs.BaseTypes
<BizTalk Server 2010 installation
directory>\Microsoft BizTalk Server 2010
Microsoft.BizTalk.Bam.EventObservation
<BizTalk Server 2010 installation
directory>\Microsoft BizTalk Server 2010\Tracking
2. Set the active configuration for the solution to be Release. Right-click on the
CustomMRSRModel solution and select Configuration Manager. Select Release from the
Active Solution Configuration.
3. Rebuild the CustomMRSRModel solution. If you experience any errors during the build,
check the following:
a) Make sure that MRSRSiteConfiguration project in the solution is built first.
b) Check MRSRProfileManager, ProfileFinder and WorkflowHelper projects in the solution
contain a reference to
‘Microsoft.Solutions.FinancailServices.SWIFT.MRSRSiteConfiguration.dll’
c) Make sure that MRSRProfileManager, ProfileFinder and WorkflowHelper are built
successfully.
d) Check that CustomMRSR project in the solution contains a reference to
‘Microsoft.Solutions.FinancialServices.SWIFT.CustomMRSR.WorkflowHelper.dll’
4. Deploy the CustomMRSR project using either BizTalk Explorer in Visual Studio or with
BizTalk Server deployment tool BTSTask.exe or BizTalk Server DeploymentWizard.
5. Ensure that all servers have in their global assembly cache (GAC) the following
assemblies. If the assemblies are not present then manually GAC them.
Microsoft.Samples.BizTalk.Solutions.FinancialServices.SWIFT.CustomMRSR.MRSRService.dll
Microsoft.Samples.BizTalk.Solutions.FinancialServices.SWIFT.CustomMRSR.ProfileEngine.dll
Microsoft.Samples.BizTalk.Solutions.FinancialServices.SWIFT.CustomMRSR.ProfileManagement.dll
Microsoft.Samples.BizTalk.Solutions.FinancialServices.SWIFT.CustomMRSR.WorkflowHelper.dll
66
Microsoft.Solutions.FinancialServices.SWIFT.MRSRSiteConfiguration.dll
Step to deploy new SharePoint site
1. <Swift 2010 Install directory>\SDK\Samples\MRSRSiteDeploymentUtility>
2. Open configuration file MRSRSPUtility.exe.Config, replace localhost and port no (8080)
with machine and port used to bind ProfileWebClient website.
3. Run MRSRSPUtility.exe, it will deploy a sharepoint site in current machine (localhost is
your current machine). http://localhost/sites/bassite
4. Open BizTalk Server 2010 Administration Console, open Application node and open
BizTalk Application 1.
Set receive port (Sts.OutBox) in the following orchestrations
a. MainMessageHandler
b. NewMessageHandler
c. UnparsedMessageHandler
5. If any orchestration has a Status = Unenlisted, then open its properties, go the Bindings
tab and select Host = BizTalkServerApplication or the host of your choice. Enlist and
start the Custom MRSR orchestrations in the following order:
a. SendFinalMessage orchestration
b. HandleFailedMessage
c. NewMessageHandler
d. UnparsedMessageHandler
e. MainMessageHandler
f. CustomMRSR
Step to add new MX message pattern in data base
1. To add new message pattern in data base, run following query in CustomMRSR data
base
2. Insert Into MsgType(MsgTypeID,MsgTypeNameSpace,MsgTypeName) Values ("message
type","/*[local-name()='Document']/*[local-name()='message type']","message type")
3. Replace message type with message name (for example, replace message type with
pacs.001.001.02).
Building the Profile Web Client Site
Step in IIS 6.0:
1. Open Internet Information Services Manager (inetmgr) and create a new website called
ProfileWebClient and point to the <install
directory>\SDK\Samples\CustomMRSRmodel\ProfileWebClient\.
2. Check the run scripts checkbox.
67
3. Ensure that anonymous access to the website is disabled (it is enabled by default)
4. Bind the site to an unused port.
5. Modify the website to run under the same application pool that the BAS site is running
under.
6. On the website properties and navigate the documents tab and add home.aspx to the
default documents
Step in IIS 7.0/7.5:
1. Open Internet Information Services Manager (inetmgr) and create a new website called
ProfileWebClient and point physical to the <install
directory>\SDK\Samples\CustomMRSRmodel\ProfileWebClient\> directory
2. Add an unused port number in Port option (Note this port number).
3. Click on site and open Authentication option, ensure that anonymous access to the
website is disabled (it is enabled by default) and enable Windows Authentication.
4. Add home.aspx to the Default Document Property.
5. Modify the website to run under the same application pool that the new SharePoint site
is running under in application pool.
6. If you are not able to browse the ProfileWebClient, right click Application pool, select
properties then verify identity account. The identity (user) must be part of the A4SWIFT
Department Administrators and A4SWIFT Administrator groups. The application pool
used for Profile Web Client is shown below:
If you unable to browse to the Profile Web Client, try to modify the website to run
under the same application pool that the new SharePoint site (BAS Site) is running
under. This is the application pool for the extended SharePoint Site (Default Web Site).
Build Profile Web Client
1. Open the ProfileWebClient.sln in notepad and modify the second line port number to
the number assigned when you created the site. Save this file.
2. Open the ProfileWebClient.sln in Visual Studio and resolve any references and then
build.
68
3. If you don't have Visual Studio installed on the Machine, you can compile the solution
on a different Machine and then run DeployProfileWebClient.bat located in <Swift 2010
Install directory>SDK\Samples\CustomMRSRModel\ProfileWebClient, using the
following instructions:
4. Run the DeployProfileWevClient.bat using the command DeployProfileWebClient.bat
DestinationFolder, where DestinationFolder is a folder where the website will be
deployed.
5. Copy the contents of the DestinationFolder and deploy it on the machine with IIS and
BAS.
The next step in setting up the ProfileWebClient is to set its authentication mode.
SiteID is required to set NTLM Authentication for the site. These are the steps to look
up the site id.
Steps in IIS 6.0
1. Open Internet Information Services Manager (inetmgr)
2. Right-click on your website and select Properties.
3. Navigate to the Web Site tab
4. Locate ActiveLogFormat at bottom of the screen and Click on Properties
5. On General tab you will see Log File Name as W3SVC<number>\exyymmdd.log
6. This Number is your Site ID. Note this site ID. It is required in the next step.
Steps in IIS 7.0/7.5
1. Open Internet Information Services Manager (inetmgr)
2. Click on Sites node.
3. In features View get ID of ProfileWebClient, this Number is your Site ID. Note this site ID. It is
required in the next step.
Steps to Configure Integrated Security
1. Go to command prompt
2. cd <drive>:\Inetpub\AdminScripts
3. Type the command (all in one line):
cscript adsutil.vbs set w3svc/<Site Id (from the step above)>/NTAuthenticationProviders "NTLM"
4. Verify it by using the following command
cscript adsutil.vbs get w3svc/<Site Id>/NTAuthenticationProviders
It should return
NTAuthenticationProviders
: (STRING) "NTLM"
5. IISReset
Please read ProfileWebClientUserManual.doc on how to use the Web client application
to create and manage profiles, users and departments.
NOTE: The document can be found at <drive>:\Program Files\Microsoft BizTalk
Accelerator for
SWIFT\SDK\Samples\CustomMRSRModel\ProfileWebClientUserManual.doc
69
Registering the COM+ serviced component
Custom MRSR code includes a serviced component that saves audit trail information
in the CustomMRSR database for the messages.
This component needs to be registered with COM+ from a Visual Studio command
prompt using the following commands:
cd <Swift 2010 Install
directory>\SDK\Samples\CustomMRSRModel\WorkflowHelper\bin\Release
regsvcs /fc
Microsoft.Samples.BizTalk.Solutions.FinancialServices.SWIFT.CustomMRSR.Workflow
Helper.dll
The regsvcs.exe can also be found under the
%WINDOWS%\Microsoft.NET\Framework\v2.0.50727 folder.
Certificates
For each user with a role (Repair, Verify and Approve) must have a “Client
Authentication Certificate”. This document is beyond installation/configuration of a
Certificate Authority.
Tasks needed if using an in-house CA:
1) Install a Certificate Server for Windows 2003 or add Certificate Service role in Windows
2008.
2) Submit a request for a “Client Authentication Certificate” for each user/role in MRSR.
3) Export the certificate.
4) Add the client certificates to the “Personal folder in the Certificates – Current User
store”.
5) Add the client certificates to the “Other People folder in the Certificates – Local
Computer store”.
6) If using your Certificate Authority to generate the certificates, you must import the
Certificate Authority’s certificate into the client computer. Import the Certification
Authority's certificate into the Trusted Root Certification Authority folder in the
Certificates (Local Computer) node as well.
Profile Web Client User Manual
All the steps above will help you install, configure and get your A4SWIFT server
ready to process messages. In order to repair a message you must also review the
Profile Web Client User Manual and the E2E Solution in the product documentation.
All prerequisites to obtain a working repair process application have been
documented and completed in the steps above. To complete the custom MRSR
application setup, review the <drive>:\Program Files (x86)\Microsoft BizTalk
70
Accelerator for
SWIFT\SDK\Samples\CustomMRSRModel\ProfileWebClientUserManual.doc document.
This documents the usage of the A4SWIFT Profile Web Client. The Web client allows
you to create and set up security for the users, department, profiles and patterns in
the system.
Using the Profile Web Client you must:
1. Add users. Under user management, select Add User, add the same user or users for
Repair Approver Verifier role.
2. Add department CustomMRSR (select Type Generic).
In addition, you might find the Product documentation section, Getting Started with
Microsoft BizTalk Accelerator for SWIFT, End-to-End Tutorial, Module 8: Repairing an
Invalid Message as a good reference on how to actually repair an invalid message
located at http://msdn.microsoft.com/en-US/library/ee350595(v=BTS.10).aspx.
Documentation Feedback and Updates
Microsoft® values your feedback. To send feedback and comments about this guide
to the documentation team, click here.
71