Using ® BizTalk® Server 2004 and Microsoft® Office InfoPath™ 2003 for Financial Message Entry and Repair

Contents

3 Introduction

4 Overview

8 Understanding the Platform

11 Implementing a Solution Using InfoPath and BizTalk Server

24 Conclusion

Introduction

This white paper describes a solution for creating a low-cost, flexible interface for financial messaging using Microsoft® BizTalk® Server 2004 and Microsoft® Office InfoPath™, the Microsoft Office information gathering and management program. This solution provides financial institutions with the tools to manually enter and submit financial messages without expensive infrastructure and technical resources. It also helps them automatically synchronize the interface with evolving message formats and business rules associated with the messages. This new breed of integration solutions is low-cost, flexible, secure, and easy to deploy.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 3

Overview

FINANCIAL INSTITUTIONS REQUIRE INTEGRATION TO CONNECT DISPARATE BACK-END SYSTEMS AS WELL AS EXTERNAL SYSTEMS AND NETWORKS.

Financial institutions have long used enterprise middleware for machine-to-machine interfaces, to move data between numerous, complex, disparate legacy systems and external networks. Enterprise application integration (EAI) solutions act as hubs to transport data between various applications, simplifying the technical environment by reducing the number of interfaces between applications. Implementing integrated financial messaging can be a complex, expensive process, one that must continually evolve to support new standards, applications, and business opportunities.

One of the key benefits of integrated financial messaging is automation—the middleware enables back-end core processing systems to send out messages to a variety of systems without needing to modify the back-end system to support a particular message format or handle routing and other related functions.

Microsoft BizTalk Server is a leading EAI platform that is widely used in financial services. In fact, Microsoft has delivered messaging solutions for some of the world’s leading market infrastructures and financial institutions (FIs). For example, Microsoft has worked with Euro Banking Association (EBA) and Società Interbancaria per I'Automazione (SIA) to build a euro payment infrastructure for cross-border low-value payments (STEP2). Jih Sun Financial Holding Company, following a consolidation of its trading and securities operations, used Microsoft technologies to perform application integration. Microsoft has also contributed to solutions at organizations, including Schwab, Bank of New York, Bank of Montreal, Bank One, and more.

However, in some cases, a mechanism for manually creating and routing messages to the appropriate recipient is needed—a human-to-machine interface. For example, a remote branch office of a bank may occasionally need to send a payment message through an automated clearing-house, or a broker/dealer may need to follow up on a trade while on the road. In both cases, the information worker—a nontechnical business user—at the remote end does not have access to in-house applications to accomplish the task at hand.

Today’s solutions for manual message entry (or repair) are severely out of date, and IT departments are faced with a limited number of cumbersome implementation choices. These products are typically built using terminal emulation or thick-client interfaces. The product infrastructures present numerous challenges. For starters, they are often difficult to implement and operate, requiring emulation software, host interface systems, and constant connectivity.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 4 In many countries, connectivity between systems requires leased lines and can be very expensive. To keep these systems running requires dedicated IT staff who can keep the host interface up and running and up to date with the latest messaging standards. With the frequency of standards and application updates, updating legacy systems is a perpetual effort. EAI systems can help reduce the labor required to keep the system up to date, but most offerings lack a comprehensive and easily maintainable solution for manual or human workflow message entry.

Perhaps the biggest challenge is cost. All of these components are expensive. With the current downturn in the global economy, and the resulting impact on IT spending in financial services, most large organizations are feeling the pressure to lower operating costs. Given that FIs typically spend more than 50 percent more on IT than companies in other markets1, they are really feeling the pressure.

Unfortunately, the FIs that can most benefit from manual message entry solutions are the medium-sized and smaller institutions that do not have a large-scale automated solution or the budget to implement complex solutions.

Until recently, these companies were forced to either spend more money to implement these types of solutions or pay larger institutions to act as service providers (essentially selling capacity on their systems as a way to recoup costs).

Another alternative has been to use a series of disparate and inconsistent applications to provide entry features, based on either the type of transaction or the destination service of the message. This approach has always been difficult to master for the end user and is almost impossible to keep up to date with efficiency.

This issue is clearly evident in the arena of global financial networks, such as the Society for Worldwide Interbank Financial Telecommunication (SWIFT). SWIFT is the dominant financial network in the world, measured by the total number of customers, transaction volume, value of transactions, and global market presence. In 2002, almost 2 billion messages were sent across the SWIFT network, valued at more than $1 trillion per day. SWIFT has more than 7,500 customers around the world connecting to its network. SWIFT provides facilities for the exchange of numerous types of financial information and transactions, including payments, treasury, securities, and trade finance.

For more information on SWIFT, please visit http://www.swift.com.

This essentially means that all financial institutions need to be able to send and receive SWIFT messages. Technically, this requires the ability to take a message from the core processing system in its native format, convert it to SWIFT format, and route it to the SWIFT network (and to reverse the process to receive messages), including validation, auditing, and logging.

Financial institutions face the above challenges if they lack back-end systems to integrate with; require human-based workflow, as is the case for a remote branch; or wish to have backup/redundant solutions.

1. From Gartner “Financial Services Market Regains Momentum: Forecast Through 2006”, 26 February 2003.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 5

FIGURE 1 MONOLITHIC EAI

Local Connection Local Connection Foreign Exchange Department Payments Department

Shared Printer Local Connection Payments Application

Leased Line or Dial-Up Connection Hong Kong Branch Local Connection Green-screen Dedicated Trade Application terminal LAN/WAN

This illustration shows how this is done today—terminals which access back-end systems through mainframe connection. • Hard to use (poor UI, etc.) • Expensive to maintain • Requires dedicated connection SWIFTNet

Monolithic EAI solutions from the past are still in use. They are a mix of gateways and EAI, combined in a centralized service requiring dedicated interfaces. They are either very general ( just transport) or very specific, e.g., for a certain type of financial transaction like payments.

Those institutions who could not afford the monolithic solutions often were left with little or no EAI to support their applications. The picture below is typical. International transactions are processed by hand and entered into the gateway. Domestic payments may be directly connected to the clearing by an inflexible gateway provided by the central bank.

FIGURE 2 POINT CONNECTIONS

Foreign Exchange

International SWIFTAlliance Access SWIFTNet Payments

Domestic Payments Application

FedWire

FedLine for Business Branch Payments This illustration shows another way this is done today— point connections to each system or network. • Separate workstation for each network or application • Hard to use (poor UI, etc.) • Expensive to maintain • Requires dedicated connection and systems

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 6 And then there is EAI over the LAN—each destination or source presents its own image and graphical user interface (GUI) to the user, who must then deal with the disparate implementations. Even where there are automated steps, there are one-off interfaces, making maintenance a nightmare. This scenario is illustrated below.

FIGURE 3 EAI BY LAN

SWIFTAlliance Gateway

SWIFTNet

SWIFTAlliance Access Single user sees multiple presentations, manages files on LAN DTCC

Custody Application

Trade Application Directs own flows to SAG, SAA and custody application

USING MICROSOFT BIZTALK AND OFFICE

Using Extensible Markup Language (XML) forms that represent financial messages in conjunction with enterprise middleware capable of transforming the XML forms into native financial message formats, the Microsoft infrastructure provides an EAI implementation that is low cost, easy to manage and maintain. The main components of this architecture are Microsoft® BizTalk® Server 2004 and Microsoft® Office InfoPath™ 2003, which is included in Microsoft® Office Professional 2003 Enterprise Edition, and is also available as a standalone product.

A solution built on these components:

∑ Is easy and inexpensive to implement and maintain. ∑ Can be easily distributed to remote sites. ∑ Requires minimal infrastructure at remote sites.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 7 Local Connection Core Payments Processing Application

Local Branch Connection Office Other Application

Business Operations Activity Center Monitoring Dashboard BizTalk Server and Accelerator for SWIFT and Partner Adapter for FedWire

SWIFTAlliance Access FedWire

SWIFTNet

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 8

Understanding the Platform

MICROSOFT BIZTALK SERVER 2004

BizTalk Server 2004 is a full-featured integration server that enables you to efficiently and effectively automate and manage business processes that connect your internal systems with people and trading partners.

BizTalk Server 2004 provides a powerful orchestration engine along with versatile shared services that make it easier to orchestrate dynamic business processes within and between organizations. Using BizTalk Server 2004, business analysts, IT professionals, and developers can work in their respective environments to rapidly define, design, and deploy integrated solutions that work across applications, platforms, and organizations.

In particular, BizTalk Server 2004 focuses on these key areas of investment:

∑ Business process management ∑ Human-based workflow ∑ Business rules ∑ Single sign-on ∑ InfoPath™ integration Figure 1: BizTalk Editor

Figure 2: BizTalk Mapper

Figure 3: BizTalk Orchestration Designer

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 9

USING MICROSOFT OFFICE 2003 AS A HUMAN USER INTERFACE TO BIZTALK SERVER

As previously described, BizTalk Server is a middleware solution for integration and business process automation. BizTalk Server has no restrictions in what type of systems can be integrated, how integration is performed, and any user interfaces necessary to enter or generate data. Essentially, BizTalk treats every system as a black box and instead uses standard mechanisms for data encapsulation, communication, and process automation based on XML, Web Services support, and the Business Process Execution Language (BPEL).

The productivity tools provided in Microsoft Office 2003 suite fully complement BizTalk Server as a full feature user interface for data entry. Today, applications such as Microsoft Word, Excel, and InfoPath all support saving information as XML. By natively supporting XML, this makes it very simple for BizTalk to consume, transform, and transmit data created in these applications. InfoPath 2003 is a perfect tool for gathering information as XML and accomplishing this.

MICROSOFT OFFICE INFOPATH 2003

InfoPath 2003 is a new program in the Microsoft Office System that can help you gather information flexibly and efficiently in rich, dynamic forms. You can more effectively share, reuse, and repurpose information throughout your team or organization, improving collaboration and decision-making to positively impact your business.

The information collected can be integrated with a broad range of business processes because InfoPath supports any customer-defined XML schema and integrates with Web services. As a result, InfoPath can help connect information workers directly to organizational information and give them the ability to act on it, which leads to greater business impact.

Figure 4: Sample InfoPath Form Template

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 10

GATHER INFORMATION MORE FLEXIBLY AND EFFICIENTLY

InfoPath provides a flexible and efficient way to collect the information needed to make better-informed decisions.

∑ Make it easy to collect the right information—the first time—with data validation, screen tips, and conditional formatting.

∑ Personalize the information being captured. Add sections to the form as you go to make the information you gather more meaningful.

∑ Work with forms online or offline to conveniently gather and manage information anywhere, anytime.

∑ Enjoy the familiar Microsoft Office System environment, which minimizes training time and provides authoring features like the spelling checker, font formatting, and other familiar tools.

EASILY DEVELOP AND DEPLOY RICH, DYNAMIC FORMS

InfoPath makes it easy to create robust forms solutions and to deploy and maintain forms solutions across an organization. You can:

∑ Build your own forms for gathering information in the WYSIWYG (“what you see is what you get”) design mode or work with 25 ready-to-use samples.

∑ Include powerful features like data validation in your forms without writing code.

∑ Create forms solutions using existing customer-defined schemas.

∑ Publish your forms to a shared network folder, a Web server, or a Windows® SharePoint™ Services form library or send them by e-mail.

∑ Make sure the most up-to-date form is always available with silent and automatic downloads.

BIZTALK ACCELERATOR FOR SWIFT

The Microsoft BizTalk Accelerator for SWIFT extends the BizTalk Server platform to provide a reliable and scalable foundation for rapidly creating and deploying SWIFT-based financial messaging solutions. The BizTalk Accelerator for SWIFT (A4SWIFT) delivers cost- effective, reliable, and secure delivery of financial messaging using SWIFT formats and network. It provides full support for SWIFT messaging standards and network protocols.

An InfoPath-based solution addresses the needs of a human-based workflow, such as remote branches and message repair. By creating the InfoPath form templates from the same schemas that are used in an automated processing solution and by employing the same validations, the quality of the messaging is raised and there is only one place where changes need to be made as the standards evolve.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 11

Implementing a Solution Using InfoPath and BizTalk Server

DESCRIPTION OF THE MESSAGE FLOW OF MT103 TO THE SWIFT NETWORK

In the following scenario, we’ll be using InfoPath 2003 as the front-end application for data entry for a SWIFT payment message, MT103. An employee at a bank’s branch office needs to submit payment information to their central office payments application via the SWIFT network. The payments system accepts payment instructions in the form of a SWIFT MT103 (customer payment). Let’s assume that the branch office is in a remote location and has only occasional connection to the head office. Before InfoPath, the payment instruction had to be transmitted to the head office via fax and then be transcribed. With InfoPath and BizTalk:

1. A user at a workstation, running Microsoft Windows XP and Office Professional Enterprise Edition 2003, opens an InfoPath form corresponding to the message that needs to be transmitted. The user fills out the correct information and clicks the Submit button.

2. The document is then transmitted via file copy, http, or to BizTalk Server. BizTalk server securely receives the document, performs the necessary validation, and transforms the document into a properly formatted SWIFT FIN flat file message ready for delivery. (Note: After validation, the message could also be queued for visual verification by another user (at the remote office) or for approval at the head office, as is generally the requirement for financial messaging).

3. BizTalk Server then reliably delivers the message to SWIFT Alliance Access (SAA), typically via MQ Series using the BizTalk Adapter for MQ Series (or via RA for an XML delivery via FileAct).

4. Finally, SAA handles the process of placing the message onto the SWIFT network.

Branch Office PAYMENT

SWIFTAlliance Access Bank's data center running SWIFTNet Other BizTalk Server and Branch Office Accelerator for SWIFT

Figure 5: Message Flow of MT103 to SWIFT Network

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 12 CREATING THE SOLUTION

Through the following sections, we will walk through the steps of creating a simple solution for MT103 messaging, simulating the solution required for remote message entry. These steps include:

∑ creating a new BizTalk solution and project using ® .NET 2003,

∑ creating the XSD schema for the MT103 using the BizTalk Editor,

∑ creating and configuring a BizTalk Server pipeline component,

∑ deploying the solution,

∑ creating an InfoPath form, and

∑ testing the solution.

CREATING A BIZTALK PROJECT WITH VISUAL STUDIO

In the following steps, you will build a new EAI solution for your company by using Visual Studio .NET 2003. First you create a new blank solution and then you add a new project to the solution. This project contains the schemas that you create in the next exercises.

TASKS DETAILED STEPS

1. Create a blank solution. a. Click Start, point to All Programs, point to Microsoft Visual A solution may include only one Studio .NET 2003, and then click Microsoft Visual Studio BizTalk project if the solution is .NET 2003. relatively simple. The Visual Studio .NET 2003 splash screen appears and then A solution may include many Visual Studio .NET starts. BizTalk projects if the solution consists of numerous projects b. On the File menu, point to New, and then select Blank that are developed Solution. independently and then must be integrated later. c. In the New Project dialog box, select the Blank Solution template.

d. In the Name field, type SWIFTSolution as the solution name.

e. In the Location field, type C:\SWIFT.

f. Click OK to open the new solution.

An empty solution appears in the Solution Explorer, and a new blank solution is created in the C:\SWIFT folder.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 13 TASKS DETAILED STEPS

2. Add a new BizTalk project to a. In Solution Explorer, right-click Solution 'SWIFTSolution', the solution. point to Add, and then select New Project. Selecting the BizTalk project template exposes the BizTalk b. In the Add New Project dialog box, select the BizTalk tools, such as the BizTalk Projects folder. Mapper, within the Visual Studio c. In the Templates pane, select Empty BizTalk Server Project. .NET development environment. d. In the Name field, type SWIFTSchemas as the project name.

e. Click OK to open the new project.

A new project is added to the Solution Explorer, and the project folder and files are created in the C:\SWIFTSolution folder.

ADDING A SCHEMA TO A PROJECT

Now that we have a solution and a new project created, we can begin to add items to the TASKS DETAILED STEPS

1. Create the payment schema. a. In Solution Explorer, right-click the SWIFTSchemas project, point to Add, and then select Add New Item.

b. In the Add New Item-SWIFTSchemas dialog box, select Schema from the Templates pane.

c. In the Name box, type SWIFTMT103.xsd to name the schema.

d. Click Open to open the blank schema in the BizTalk Editor.

Selecting the Schema template The schema tree (left pane) and XSD view (right pane) appear in causes the BizTalk Editor to start. the BizTalk Editor. Also, the new schema (SWIFTMT103.xsd) is added to the Solution Explorer under the EAISchemas project.

e. From the File menu, select Save All to save your changes.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 14 TASKS DETAILED STEPS

2. Create the payment a. To create an MT103 schema based on the SWIFT document schema. documentation, you need to define each of the elements, This schema describes the fields, and groups using standard XML techniques. document format for a single credit transfer, as defined by an We provide schema for all of the SWIFT messages (FIN and XML) MT103. as part of our Accelerator for SWIFT. We have used the body of a sample schema in these examples (MT103.xsd).

The payment schema is shown below:

project. The first item we create is a schema for an MT103 SWIFT Payment message.

CREATING A CUSTOM SEND PIPELINE

In this section, we create a custom pipeline using the BizTalk Pipeline Designer. The customer pipeline is configured to use the Flat File Assembler. The Flat File Assembler

TASKS DETAILED STEPS

3. a. In Solution Explorer, right-click the SWIFTSchemas project, point to Add, and then select Add New Item.

b. In the Add New Item-SWIFTSchemas dialog box, select Send Pipeline from the Templates pane.

c. In the Name box, type SendMT103Pipeline.xsd to name the schema.

d. Click Open to open the blank pipeline in the BizTalk Pipeline Designer.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 15

TASKS An empty pipeline appears (left pane) in the pipeline designer. Also, the new pipeline (SendMT103Pipeline.btp) is added to the Solution Explorer under the SWIFTSchemas project.

e. From the BizTalk Pipeline Components Toolbox, drag the Flat file Assembler to the Drop Here box below the Assemble stage shape in the Pipeline Designer.

The flat file assembler component has been added to the Pipeline Designer.

f. Select the Flat File Assembler Component in the Pipeline Designer.

g. In the Properties windows, click the Document schema property and from the Drop-down menu, select “SWIFTSchema.SWIFTMT103.xsd”.

h. From the File menu, select Save All to save your changes.

CREATING A STRONG-NAMED BIZTALK ASSEMBLY

Next we need to create a strong name for the BizTalk assemblies to be deployed. A strong-named assembly provides several security benefits. A strong name helps protect the uniqueness of the assembly by assigning a digital signature and a unique key pair. This also protects the lineage of the assembly by ensuring that no one else can generate a subsequent version of the assembly. Finally, a strong name provides a strong integrity check to guarantee that the contents of the assembly have not been changed since it was built.

TASKS DETAILED STEPS

1. Create a key pair. a. Click Start, point to All Programs, point to Microsoft Visual This creates a public/private key Studio .NET 2004, point to Visual Studio .NET Tools, and pair, which is saved to a key file. then click Visual Studio .NET 2004 Command Prompt.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 16 b. From the command Prompt, type cd c:\SWIFT\SWIFTSolution and press Enter.

c. Type sn -k SWIFTSolution.snk and press Enter.

A message appears indicating the key pair has been written to SWIFTSolution.snk.

2. Assign strong names to the a. In Solution explorer, right-click the SWIFTSchemas project assemblies. and select Properties.

This assigns the key file to the b. In the SWIFTSchemas Property Pages page, expand Common Properties, and select Assembly. assembly. You must do this for each of the projects in this c. In the right pane, scroll down to the Strong name section, solution. click the field to the right of Assembly Key File, and then click the ellipses (…).

d. In the Assembly Key file dialog box, navigate to C:\SWIFT\SWIFTSolution\SWIFTSolution.snk, and click Open.

e. Click OK to save changes.

f. From the File menu, select Save All to save your changes.

BUILDING AND DEPLOYING THE ASSEMBLY

In this exercise, you build the project to generate an assembly that contains the resources (pipeline and schema) that were created in the previous steps. This also ensures that there are no compilation errors in the work you have created so far.

TASKS DETAILED STEPS

1. Build the project. a. From the File menu, click save all. The project is compiled into an assembly (DLL file) and saved in b. In the Solution Explorer, right-click SWIFTSolutions, and then the …\bin\Development folder click Build. within the project folder.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 17

2. Deploy the assembly. a. On the Start menu, point to Programs, point to BizTalk Server 2004, and then click BizTalk Deployment Wizard.

b. The Deployment Wizard Welcome page opens.

c. On the Welcome page, click Next.

d. On the Deployment Task page, check the Deploy BizTalk assembly to database radio button, and then click Next.

e. On the Configuration Database page, fill in the following fields:

SQL Server™ name—type, or browse for, the server name where the Configuration database is located.

Configuration database name—type, or browse for, the Configuration database name.

f. Click Next.

g. On the Deploy BizTalk Assembly page, fill in the following fields:

Assembly file—type, or browse for, the assembly you want to deploy.

The Install assembly to the GAC on this computer checkbox is selected by default.

Optionally check the Specify a binding file checkbox to select a binding (.dll) file.

Click Browse and select the relevant . file. The Import BizTalk Assembly Binding file page opens.

h. If you are not specifying a binding file, go to the next step.

i. On the Import BizTalk Assembly Binding file page, navigate to the required .dll file, click it to select, and then click Open.

j. The page closes, and you return to the Deploy BizTalk Assembly page.

k. Click Next.

l. The Ready page lists the information you entered.

m. Optionally click View to see details about the selected assembly.

n. Click Next to deploy.

o. The assembly is deployed.

p. If you want to run the wizard again, check the Run this wizard again checkbox.

q. Click Finish to close the wizard or to run it again.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 18 CREATING RECEIVE AND SEND PORTS

In this task, you can create one receive port and one send port. The receive port is used to receive MT103 XML messages, created by an InfoPath form, from an inbound file folder. The send port is used to send the MT103 Flat File message to an outbound file folder.

TASKS DETAILED STEPS

3. Adding a receive port. a. On the View menu, select the BizTalk Explorer. The receive port always has an associated receive location that b. In the BizTalk Explorer window, expand the BizTalk must be configured when you Configuration Database. add the receive port. A receive c. Right-click Receive Ports and then select Add Receive Port. location defines a specific address for an incoming d. Specify the type of receive port as One-Way Port, and click message and the pipeline that is OK. used to process the message. e. In the One-way Receive Port Properties—General Configuration dialog box, in the Name field type MT103_RecievePort, click Apply to bind the port and then click OK.

f. Right-click Receive Locations and select Add Receive Location.

g. In the Receive Location Properties—General Configuration page, type MT103_Receive_Location in the Name field.

h. To the right of the Transport Type, select File from the drop-down list.

i. To the right of Address URI, click the ellipsis (…) and type C:\SWIFT\SWIFTSolution\FileDrop\Inbound in the receive folder field.

Note: If this folder does not already exist, you should create it at this time.

j. In the File mask field, type *.xml, then click OK.

k. To the right of the Receive Handler, click the Drop-down menu to select BizTalkServerApplication.

l. To the right of Receive Pipeline, click the Drop-down menu and select Microsoft.BizTalk.DefaultPipelines.XMLReceive.

m. Click Apply, and then click OK to close the Receive Location Properties page.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 19 4. Configure the send port and a. In the BizTalk Explorer window, right-click Send Ports and send location. click Add Send Port.

The send port is used to define b. Specify the type of Send Port as a Static One-Way Port and click OK. how messages are sent out. In this case, you create a file folder c. In the Static One-Way Send Port Properties page, type location for sent messages. SendPort_MT103 as the name. d. To the right of Transport Type, select File from the Drop- down list.

e. To the right of Address URL, click the ellipsis (…).

f. In the FILE Transport Properties dialog box, type C:\SWIFT\SWIFTSolution\FileDrop\Outbound in the Destination Folder box, and then click OK.

Note: If this folder does not already exist, you should create it at this time.

g. In the left pane, click the Send node.

h. In the right pane, click the Drop-down list next to Send Pipeline, then select SendMT103Pipeline…

i. In the left pane, click the Filters & Maps node.

j. Set a Filter for BTSreceivePort Name == MT103_ReceivePort.

k. Click Apply and then OK.

CREATING AN INFOPATH FORM TEMPLATE

Creating the InfoPath form template is accomplished using the same schema created above. The schema is used as the data source for the template. The fields are dragged and dropped into position and incorporate all of the features and validations present in the schema automatically. The author may add formatting, etc., as desired. The submit actions are defined, and the template is published for use.

TASKS DETAILED STEPS

1. Initializing the template. a. On the Start menu, select Microsoft Office InfoPath 2003 An InfoPath form may be from the Microsoft Office submenu. created from scratch or may be initialized from a data source b. Select Design a Form from the Task Pane on the right-hand such as an XML schema, an side of the panel. instance, or other collection of c. Select New from Data Source under Design a New Form. data fields.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 20 d. Choose the radio button for XML Schema or XML Data File on the pop-up wizard and click Next.

e. Browse to the xsd file for the MT103 schema you created above and click Finish. The schema appears in the Work With Data Source window on the Task Pane.

2. Setting up the layout. f. Click Layout on the Task Pane. A selection of table layouts appears. Laying out an InfoPath form is similar to designing a Web page. g. Click Table With Title under Insert layout tables. A table You choose the overall layout and control appears on the Form Pane. color scheme, then add the h. Click Click to Add a Title and type the header for your form, controls. such as “MT103 Customer Transfer.” Click the centering icon to move the title to the middle of the column.

i. From the Format menu, select Color Schemes. A list of standard color schemes appears in the Task Pane. Click Blue under Apply a color scheme. The color scheme is applied to the form.

j. To highlight the text entered (message field contents), change the properties of the View. Click Color Schemes at the top of the Task Pane. The list of tasks appears. Select Views. At the bottom of the Task Pane, click View Properties. Select the “Text Settings” tab. For each control, select a color for the text (or select the same color for all of the controls). You can also change the font, bold, italic, underline, and font size if you want. When you are done, click OK.

3. Adding controls for the data. k. In our example, we set up our form with the field tags in the left column and the data in the right one of a two-column table. To set up the table, click Views at the top of the Task Pane. The list of tasks appears. Select Layout. Drag a two- column table to the second row of our form.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 21 You can let InfoPath default all l. To return to the data view, click Layout at the top of the Task of the formatting by dragging Pane. The list of tasks appears. Select Data Source. Your MT103 the entire schema over to the schema is again displayed in the Task Pane. data portion of the table. Or, you can add tags and options by dragging each group (or element if you want) individually. When you drag the items associated with a choice layout, InfoPath automatically creates sub-windows to accommodate the choice. InfoPath chooses the proper control options for each piece of data defined in the schema. m. Click the “+” beside each of the group icons to expand You may override the choice of the groups in the schema. control. n. For each group or set of groups representing a single field (like 52A and 52B), type the name of the group in the left column (or any descriptive name you want), then drag the group to the right column. InfoPath prompts you to add a section or controls in a table. Select Section With Controls. Hit Tab to add another row to the layout table for the next field. If you are adding a group that has multiple formats, you should choose Section With Controls (Choice). Do not press Tab until you have moved all of the relevant choice groups to that cell.

o. Continue in this manner until you have all of the fields for the message. Select the entire left column of your form. In the Task Pane, click the down arrow on the header line to expand the menu. Select Font. Choose Heading 3.

p. You can continue formatting the table borders, row heights, fonts, etc. to your organization standards. You may also designate which optional sections are to be included by default in the form when it is initially displayed. The user may add these sections if necessary from the Insert menu, or you may define screen buttons.

q. When you are done, save your template file. Do not close InfoPath or your file just yet.

4. Publishing your template. r. From the Tools menu, select Form Options. Click Enable Protection to disable the Forms Editing menu of the user accessing the published form. Uncheck Enable Forms Merging, as it does not apply to an MT103. Click OK.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 22 In our scenario, we are going to s. From the File menu, select Publish. The Publish Wizard use our template to create an appears. XML instance for BizTalk. The transfer mechanism is a file. We will publish the template to a shared location (in this case, just a folder on this machine). But it could be any share.

t. Click Next. Select To a shared folder on this computer or on a network. Click Next.

u. Browse to the location for the shared folder and append a file name. Enter MT103 as the form name. Click Next. Click Finish.

v. Click Notify Users to send an e-mail to one or more users containing the new location of the form. Click Send when you are done addressing the message. Click Close to end the wizard.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 23 FIGURE 3 A FINISHED MT103 TEMPLATE READY TO USE

RUNNING THE SCENARIO

a. Open the published form with InfoPath.

b. Fill it in.

c. Save the completed form to the inbound file folder defined above, C:\SWIFT\SWIFTSolution\FileDrop\Inbound. Use the file name MT103xx.XML, where xx is a counter to make the file name unique.

d. Browse to the outbound file folder, C:\SWIFT\SWIFTSolution\FileDrop\Inbound.

e. Open the newest flat file in Notepad to demonstrate that the transformation took place.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 24

Conclusion

This scenario demonstrates how BizTalk Server and InfoPath 2003 can be related through common schema. We created a simple orchestration to simulate the entry of a message by a user at a remote branch. We first defined the schema for the target SWIFT message (an MT103). We then built a BizTalk project and defined the receive port (an entered message generated using an InfoPath form) and the receiving port to stand for SWIFTNet FIN. Next, we constructed a simple InfoPath form based on the same schema used to validate automated traffic. To complete the demonstration, we entered a message using the InfoPath form, submitted it, and ran it through the BizTalk pipeline to produce a well- formed flat file (a FIN message).

The incorporation of InfoPath form templates with a BizTalk Server integration solution demonstrates the benefits of our approach to providing true Enterprise Application Integration (to include remote users as well as software).

Using InfoPath 2003 and BizTalk Server for manual message entry and repair, financial institutions achieve:

• Low-cost, flexible financial messaging integration

• Accessible, familiar user-friendly interface

• Automated synchronization with emerging message standards

• Use of common business rules engine validations

• Deployment capabilities for remote users

• Consistent validation against data sets

• Minimal code to maintain.

Talk to your Microsoft sales representative about how InfoPath 2003 and BizTalk Server can provide low-cost, flexible financial messaging solutions, or visit us on the Web at www.microsoft.com.

Using Microsoft BizTalk Server 2004 and Microsoft Office InfoPath 2003 for Financial Message Entry and Repair 25

FOR MORE INFORMATION: www.microsoft.com/biztalk

© 2003 Microsoft Corporation. All rights reserved.

This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. Microsoft, BizTalk, InfoPath, SharePoint, Visual Studio, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Microsoft Corporation l One Microsoft Way l Redmond, WA 98052-6399 l U.S.A.

Part No. 098-99003