Introduction

While you’re configuring Microsoft BizTalk Server 2006 which has a database server on a remote machine, you may encounter the problem below. The Group feature failed and hence the others which depend on it are also failed.

If you click on a red X icon in front of the failed Group feature, you’ll see the error message:
Exception of type ‘System.EnterpriseServices.TransactionProxyException’ was thrown.

This error indicates that MSDTC isn’t properly configured on the servers so you have to check if MSDTC has enabled on both BizTalk Server and SQL Server. You should first enable DTC, followed by MSDTC.

Step-by-step

1. First, enable network DTC access on BizTalk Server. Open Add/Remove Windows Components by click Start -> Settings -> Control Panel -> Add or Remove Programs -> Add/Remove Windows Components.
   
2. On Add/Remove Windows Components window, select Application Server -> click Details -> Check Enable network DTC access -> Click OK. Now DTC has been enabled.
   Note: This step may requires Windows Installtion CD.
   
3. Next, enable MSDTC. Open Component Services by Start -> Setttings -> Control Panel -> Administrative Tools -> Component Services.
   
4. On Component Services window, expand Component Services -> Computers. You’ll see My Computer.
   
5. Right-click on My Computers and select Properties.
   
6. On My Computer Properties window, select MSDTC tab and click on Security Configuration button in Transaction Configuration section.
   
7. On Security Configuration window, verify that check boxes are checked as the figure below. Then, click OK.
   • In Security Settings section, check network DTC Access.
   • In Client and Administration section, check Allow Remote Clients and Allow Remote Administration.
   • In Transaction Manager Communication section, check Allow Inbound, Allow Outbound and select No Authentication Required.
8. Check XA Transactions.



9. Click OK to restart the MSDTC service.
   
10. When the service is restarted, click OK again. Now you’ve finished on the BizTalk Server.
    
11. Next, enable MSDTC on the SQL Server by repeat step 3-10 on the SQL Server.
12. Then, try to re-configure on the BizTalk Server again. Now, it’s should be success.
    

Reference

• How to Enable MSDTC on the BizTalk Server on Microsoft.com

No related posts.

Problem

You’re configuring BizTalk Server 2006 which BizTalk databases are located on a remotely server. You may encounter the problem below.

On BizTalk Configuration Wizard, Group feature is failed so others that depend on Group will failed, too.

And if you double-click on the red X icon in front of the failed Group feature, you’ll see the error message similar as:
Failed to create SQL login for BizTalk Administrators Group on database server “Database Server Name“.
The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys.

Solution

The solution is to create local groups on the database server manually, see the step-by-step below.

1. Open Local Users and Groups on the database server. Right-click on My Computer -> Manage -> expand System Tools -> Local Users and Groups -> select Groups. You’ll see a list of groups on the server as the figure below.
   
2. Create the following groups as figure below. Right-click on Groups -> select New Group -> type the group name.
   • BizTalk Application Users
   • BizTalk Isolated Host Users
   • BizTalk Server Administrators
   • BizTalk Server Operators
   • SSO Administrators
   • SSO Affiliate Administrators

   

3. Re-configure Microsoft BizTalk again and the error is gone.
   

No related posts.

Microsoft BizTalk server provides a predefined set of macros to help in create output filenames on File send handler. If you working with sending output as a file, you’ll find these macros are really useful that you don’t have to coding any statement to get these value. These macros can be found on MSDN library but I sometimes find it’s time consuming to search on MSDN every time I forget the macro. Therefore, I decide to quote the table from MSDN to this post instead.

The useful macro is %SourceFileName% which I use most of the time. It returns filename with extension as the same name as when it received. Also, this macro allows me to customized the value dynamically,too. You can see the tutorial at BizTalkTraining3 – customize filename dynamically. Remember, this macro, it is case-sentitive.

To use macros, simply type macro in File name box.
Note: you can use more than 1 macro in the box.

Quoting Macros from MSDN

The following table lists the supported macros and describes how the File send handler substitutes them.

Macro name	Substitute value
%datetime%	Coordinated Universal Time (UTC) date time in the format YYYY-MM-DDThhmmss (for example, 1997-07-12T103508).
%datetime_bts2000%	UTC date time in the format YYYYMMDDhhmmsss, where sss means seconds and milliseconds (for example, 199707121035234 means 1997/07/12, 10:35:23 and 400 milliseconds).
%datetime.tz%	Local date time plus time zone from GMT in the format YYYY-MM-DDThhmmssTZD, (for example, 1997-07-12T103508+800).
%DestinationParty%	Name of the destination party. The value comes from the message context property BTS.DestinationParty.
%DestinationPartyQualifier%	Qualifier of the destination party. The value comes from the message context property BTS.DestinationPartyQualifier.
%MessageID%	Globally unique identifier (GUID) of the message in BizTalk Server. The value comes directly from the message context property BTS.MessageID.
%SourceFileName%	Name of the file from where the File adapter read the message. The file name includes the extension and excludes the file path, for example, Sample.xml. When substituting this property, the File adapter extracts the file name from the absolute file path stored in the FILE.ReceivedFileName context property. If the context property does not have a value, for example, if a message was received on an adapter other than the File adapter, the macro will not be substituted and will remain in the file name as is (for example, C:\Drop\%SourceFileName%).
%SourceParty%	Name of the source party from which the File adapter received the message.
%SourcePartyQualifier%	Qualifier of the source party from which the File adapter received the message.
%time%	UTC time in the format hhmmss.
%time.tz%	Local time plus time zone from GMT in the format hhmmssTZD (for example, 124525+530).

Reference: Restrictions on Using Macros in File Names

Related posts:

1. BizTalk Training 5 – using FTP Adapter
2. BizTalk Training 1 – basic send/receive xml message
3. BizTalk Training 2 – receive/send plain text

There are 9 tutorials in this topic.

Introduction

This topic will show how to use FTP Adapter to read and write files to FTP server.

There are 9 tutorials in this training.

1. BizTalk Training 1 – basic send/receive xml message
2. BizTalk Training 2 – receive/send plain text
3. BizTalk Training 3 – customize filename dynamically
4. BizTalk Training 4 – using Functiods in Map
5. BizTalk Training 5 – using FTP Adapter

Objective

• Learn how to use FTP adapter.

Prerequisites

• BizTalkTraining 4 project.
• Configuration on BizTalk Administration for BizTalkTraining application.

Topics

1. Run FTP server using IIS.
2. Configure to receive files from FTP server using FTP Adapter.

Step-by-step

1. Run FTP server using IIS.
   • Ensure that your FTP server is running.
     
   • Ensure that you have account to access FTP server with read/write permissions.
     
2. Configure to receive files from FTP server using FTP Adapter.
   • Open BizTalk Administration and double click a port in Receive Locations.
     
   • Change Type to FTP and click Configure.
     
   • Enter FTP information such as server name, account name and password, file mask, etc.

     Note: The account must have permission to delete the file if it’s a receive port and write file if it’s a send port.
     

   • You can also change the polling time in Polling section.
     
   • Click OK. Click OK. Restart server host instance, refresh the application.

Resources

You can download the configuration file (XML file) at here.
If you need source code of BizTalk project, you can download at the previous post on BizTalk Training 4.

Related posts:

1. BizTalk Training 3 – customize filename dynamically
2. BizTalk Training 2 – receive/send plain text
3. BizTalk Training 1 – basic send/receive xml message

Introduction

This topic will show how to use Functiods in BizTalk. Functiods are like functions, they are objects in Map Orchestration. The purpose of Map is to mapping values from source message to destination message. For instance, you can use concatenate functiod to concat two elements from source message and assign to destination message.

There are 9 tutorials in this training.

1. BizTalk Training 1 – basic send/receive xml message
2. BizTalk Training 2 – receive/send plain text
3. BizTalk Training 3 – customize filename dynamically
4. BizTalk Training 4 – using Functiods in Map
5. BizTalk Training 5 – using FTP Adapter
6. Working on…

Objectives

• Learn how to use functiod to get current date time.
• Learn how to use functiod to concat two fields.
• Learn how to use functiod to add customize code.

Prerequisites

• BizTalkTraining 3 project.
• Configuration on BizTalk Administration for BizTalkTraining application.

Topics

1. Create new person schema and message.
2. Create simple map.
3. Assign datetime functiod to map.
4. Assign concatenate functiod to map.
5. Assign scripting functiod to map.
6. Modify the orchestration.
7. Deploy the project and test result.

Step-by-step

1. Create new person schema and message.
   • Open BizTalkTraining project. And open Orchestration1.
     
   • Add new schema to the project name as “NewPersonSchema.xsd�?.
     
   • Alter the new schema as the following detail:
     Root name: NewPerson
     Element: Name Type: String
     Element: Position Type: String
     Element: Salary Type: Double
     Element: HiredDateTime Type: String
     Element: HiredYear Type: String
     Element: NameandSalary Type: String
     
   • Click save button.
     
   • Create new Message “msgNewPerson�? and assign message type to be “NewPersonSchema.xsd�?.
     
2. Create simple map.
   • Add new Map item to Orchestration1 name as “MapNewPerson.btm�?.
     
   • New Map window appears, set source schema for mapping.
     1. Click on Open Source Schema.
     2. Expand Schemas.
     3. Select “BizTalkTraining.Person1�? schema.

     

   • Set destination schema for mapping. Select “BizTalkTraining.NewPersonSchema�?.
     
   • Drag Name element in Source Schema to Name element in Destination Schema. Do these on Position and Salary elements, too.

     Or you can click on Person root in Source Schema and hold shift button and drag to NewPerson root in Destination schema to get the same result.

     

3. Assign functiod datetime to map.
   • On MapNewPerson map, you’ll see many functiods in Toolbox panel.
     
   • Now I’ll use datetime functiod to generate current date and time to HiredDate element on Destination Schema.
   • Scroll down to Date/Time Functiods, select Date and Time. Drag it to map between the Source Schema and Destination Schema area.
     
   • Double click on the functiod Date and Time, you’ll see Configure Functiod Inputs window. Fuctiod Data and Time doesn’t get any input, it’ll will generate current date and time in CCYY-MM-DDThh:mm:ss format.
     
   • Drag the functiod to HiredDate on Destination Schema to generate current date and time to HiredDate element.
     
4. Assign concatenate functiod to map.
   • Now I’ll concatenate Name and Salary element in Source to NameandSalary in Destination.
   • On MapNewPerson map, drag String Concatenate functiod to map area.
     
   • Drag Name and Salary element on Source Schema to concatenate functiod and drag concatenate functiod to NameandSalary element on Destination Schema.
     Notice that the inputs will be on left side of the functiod and output will be on right side.
     
5. Assign scripting functiod to map.
   • Scripting functiod allow you to customize your code. Now I want only year from datetime functiod to HiredYear element on Destination Schema.
   • Again, drag Scripting functiod in Advanced functiods to map area.
     
   • Click on Scripting functiod. On Properties, click on the rightmost button in Script to configure script.
     
   • Configure Functiod Script window appear, click on drop-down in Script type and you’ll see that there are many type of script you can use but now I’ll use Inline Visual Basic.NET.
     
   • Notice that when you click on Inline Visual Basic.NET, the comment code appear below in Inline script buffer. This is a simple script that does the concatenation of 2 inputs.
     
   • Replace all the code with the code below.
     Public Function GetYear(ByVal datetime As String) As String
     Return datetime.SubString(0,4)
     End Function
     
   • Drag the datetime functiod to the scripting functiod and also drag the scripting functiod to HiredYear element on Destination Schema.
     
   • Note that if you want one functiod to be input of another you must place it on left side on the functiod. For instance, you can’t place datetime functiod on the red area in the figure below if you want it to be input of the scripting functiod.
     
   • Save MapNewPerson map.
6. Modify the orchestration.
   • Create transform object.
     1. Drag Transform from Toolbox in “Construct msgPerson2�? upper the “Assign filename�? Message Assignment.
        
     2. Double click the transform object that you’ve just added. Transform Configuration window appears, select Existing Map and on Fully Qualified Map Name drop-down to select “BizTalkTraining.MapNewPerson�?.
        
     3. On Source, select “msgPerson”.
        
     4. On Destination, select “msgNewPerson”.
        
     5. Click on Source again to refresh the Destination and click OK.
   • Change Construct Message Properties and “Assign fileName�? Message Assignment.
     1. Click on “Construct msgPerson2�? Construct Message. On properties, uncheck the msgPerson2 out from Message Constructed since we don’t need msgPerson2 any more. And ensure that “msgNewPerson” is checked instead. Also, change Name to “Construct msgNewPerson�?.
        
     2. Double click on “Assign fileName�? Message Assignment to alter the code. Replace the entire code with code below.

        fileName = msgPerson(FILE.ReceivedFileName);
        fileName = fileName.Replace(“.txt”,”.xml”);

        msgNewPerson(FILE.ReceivedFileName) = “output_” + fileName;
        

   • Change message on Send_2 Port to “msgNewPerson”.
     1. Break the green line between Send_2 and Send XMLPersonPort.
     2. On Send_2 properties, change Message to msgNewPerson.
        
   • Change message type on send logical port.
     1. Click on Request on SendXMLPersonPort.
     2. On properties, change Message Type to “BizTalkTraining.NewPersonSchema�?.
        
   • Reconnect the green line between Send_2 and SendXMLPersonPort.
     
7. Deploy the project and test result.
   • Deploy the project
     
   • Open BizTalk Administration, restart the server host if it is running and refresh the application.
   • Test the result by copy person1.txt from C:\FILE2 to C:\FILE2\IN, you’ll see the result in C:\FILE2\OUT\person.xml

     Person1.xml
     

     Note: Again, ensure that you delete all files in C:\FILE2\OUT before.

Resources

You can download the example source code (zip file) at here.
The zip file contains

• BizTalkTraining folder which is the example project on Visual Studio 2005.
• FILE2 folder which contains IN and OUT empty sub folders for test receive and send message and person1.txt which is an example text message.
• binding.xml file which is a configuration file for import in BizTalk Administration.

Related posts:

1. BizTalk Training 1 – basic send/receive xml message
2. BizTalk Training 2 – receive/send plain text
3. BizTalk Training 3 – customize filename dynamically

Overview

This tutorial shows how to customize output filename inside orchestration.

There are 9 tutorials in this training.

1. BizTalk Training 1 – basic send/receive xml message
2. BizTalk Training 2 – receive/send plain text
3. BizTalk Training 3 – customize filename dynamically
4. BizTalk Training 4 – using Functiods in Map
5. BizTalk Training 5 – using FTP Adapter

Objectives

• Learn how to change filename of the output file.

Prerequisites

• BizTalkTraining 2 project.
• Configuration on BizTalk Administration for BizTalkTraining application.

Topics

1. Add variable in the orchestration.
2. Add msgPerson2.
3. Add Message Assignment to the orchestration.
4. Test application.

Step-by-step

Suppose that I want to change name of outgoing file. As in training 2, the input filename is *.txt format but I want the outgoing message type as xml format and also add “output_�? text before. E.g. incoming filename is “person1.txt�?, outgoing filename will be “output_person1.xml�?.

1. Add variable in the orchestration.
   • Open Orchestration1 in BizTalkTraining. (Project from BizTalk Training 2).
     
   • Switch to Orchestration View, right click on Variables and select New Variable.
     
   • Click on the variable.
     1. On Variable Property, change Identifier to “fileName�?.
     2. Change Type to “string�?.
        
   • Now you’ve add variable name “fileName�? as string to the Orchestration1.
2. Add msgPerson2.
   • Create new Message on the orchestration name “msgPerson2�? and set Message Type as the same as msgPerson (BizTalkTraining.FlatFilePersonSchema).
     
3. Add Message Assignment to the orchestration.
   • Drag Message Assignment from Toolbox to bottom of the Orchestration1.
     
   • Click on ConstructMessage_1 object. Notice that you highlights entire Construct Message object.
   • On Construct Message Properties, check msgPerson2 in Message Constructed and change Name to “Construct msgPerson2�?.
     
   • Click on Message Assignment (the object inside Construct Message) and change Name to “Assign fileName�? in Message Assignment Properties.
     
   • Double click on Message Assignment and fill in the code below and click OK.

     msgPerson2 = msgPerson;
      
     fileName = msgPerson2(FILE.ReceivedFileName);
     fileName = System.IO.Path.GetFileName(fileName.Replace(".txt",".xml"));
      
     msgPerson2(FILE.ReceivedFileName) = "output_" + fileName;

     The code above assigns msgPerson to msgPerson2 and assigns incoming filename to “filename�” variable, modify string and assign back to “msgPerson2�”.
     

   • Add new send component to the bottom of the orchestration and change Message to “msgPerson�?.
     
   • Create new send logical port.
     1. Right click on Port Surface area, select New Configured Port.
        
     2. Set name to “SendXMLPersonPort�?.
     3. Set Port Type as following configurations.
        Port Type: Create a new Port Type
        Port Type Name: SendXMLPersonPortPortType
        Communication Pattern: One-Way
        Access Restrictions: Internal
        
     4. Set Port Binding as below.
        Port direction: I’ll always be sending messages on this port.
        Port binding: Specify Now.
        Transport: FILE
        URI: C:\FILE2\OUT\%SourceFileName%
        Send pipeline: XMLTransmit
        
   • Connect green button from Send component to SendXMLPersonPort.
     
   • Deploy the project.
     
4. Test the application.
   • Open BizTalk Administration and restart BizTalk host.
     
   • Refresh BizTalkTraining application.
     
   • Test application by copy person1.txt from C:\FILE2\person2.txt to C:\FILE2\IN.
     Note: You must any delete files in C:\FILE2\OUT before.
   • You’ll see output in C:\FILE2\OUT.
     
   • Person1.txt
     
   • Output_person1.xml
     

Resources

You can download the example source code (zip file) at here.
The zip file contains

• BizTalkTraining folder which is the example project on Visual Studio 2005.
• FILE2 folder which contains IN and OUT empty sub folders for test receive and send message and person1.txt which is an example text message.
• binding.xml file which is a configuration file for import in BizTalk Administration.

Related posts:

1. BizTalk Training 4 – using Functiods in Map
2. BizTalk Training 2 – receive/send plain text
3. BizTalk Training 5 – using FTP Adapter

Overview

This tutorial shows how to receive plain text using FILE Adapter and map to xml message while in orchestration and finally send out using FILE Adapter as plain text.

There are 9 tutorials in this training.

1. BizTalk Training 1 – basic send/receive xml message
2. BizTalk Training 2 – receive/send plain text
3. BizTalk Training 3 – customize filename dynamically
4. BizTalk Training 4 – using Functiods in Map
5. BizTalk Training 5 – using FTP Adapter

Objectives

• Learn to create schema using Flat File Schema Wizard.
• Learn to receive file which is plain text to BizTalk.
• Learn to send file from BizTalk to plain text.

Prerequisites

• BizTalkTraining 1 project.
• Configuration on BizTalk Administration for BizTalkTraining application.

Topics

1. Create schema from plain text using Flat File Schema Wizard.
2. Add receive and send pipeline for receive/send plain text.
3. Modify orchestration.
4. Deploy the project.

Step-by-step

As from training 1, I have sample file which is an xml message. Now what if I want a plain text as an input, BizTalk can receive any file format which you can determine the schema in pipeline.
Suppose, I have the same data as in training 1 but it’s a plain text instead of xml in C:\FILE2\person1.txt.

1. Create schema from plain text using Flat File Schema Wizard.
• Open existing BizTalkTraining project, Add New Item to the project.
  
• Select Schema Files -> Flat File Schema Wizard and name the schema as “FlatFilePersonSchema.xsd�?.
  
• BizTalk Flat File Schema Wizard appears, click Next.
• On Instance file, click Browse and select the sample text file that you want to create schema from. Change Record name to ‘Person’ and click Next.
  
• On Select Document Data, leave the data highlight and click Next.
  
• Click Next.
  
• Ensure that Child delimiter is {CR}{LF} which means split data with new line characters. Click Next.
  
• Change Element Names and Data Types as in figure below.
  
• Click Finish.
  
• Now that you have created a schema file from plain text.
  
2. Add receive and send pipeline for receive/send plain text.
   • Add New Receive Pipeline.
     Right click on the project -> Add New Item -> select Pipeline Files -> Receive Pipeline -> name as ReceivePersonPipeline.btp.
     
   • New receive pipeline appears.
     
   • Drag Flat File disassembler to Disassemble stage.
     
   • Click on Flat file disassembler object that you’ve just dropped.
     On Properties, change Document schema to “BizTalkTraining.FlatFilePersonSchema�? which is the schema that we’ve created previously.
     
   • Now add new Send Pipeline.
     Right click on the project -> Add New Item -> select Pipeline Files -> Send Pipeline -> name as SendPersonPipeline.btp.
     
   • Drag Flat file assembler to Assemble stage.
     
   • Click on Flat file assembler object that you’ve just dropped.
     On Properties, change Document schema to “BizTalkTraining.FlatFilePersonSchema�? which is the schema that we’ve created previously.
     
   • Now you’ve configured receive pipeline for receive plain text and send pipeline for send to plain text.
3. Modify orchestration.
• Back to Orchestration1.
  
• Change the schema from person1.xsd to FlatFilePersonSchema.xsd on ports and receive/send components.
  1. Break the green link between ports and receive/send components by right click on the line and select Delete.
     
  2. Now orchestration will look similar below.
     
  3. Change message type for msgPerson.
     • On orchestration1, switch to Orchestration View.
     • Select msgPerson.
     • On Properties, change message type to “BizTalkTraining.FlatFilePersonSchema�? which is the schema that we’ve created recently.
       
  4. Change message type on both ports.
     • Click Request on RecvPersonPort. Be sure that you click on Request which inside the port, you’ll notice the highlight only around in Request not entire port.
     • On Properties, change message type to “BizTalkTraining.FlatFilePersonSchema�? which is the schema that we’ve created recently.
       
     • Repeat change message type on SendPersonPort, too.
  5. Connect ports and receive/send components back.
     
• Modify RecvPersonPort.
  • Click on RecvPersonPort and move to Properties window.
  • Change the Receive pipeline to “BizTalkTraining.RecvPersonPipeline�? which is the receive pipeline that we’ve created.
  • Change the URI (Receive location) to “C:\FILE2\IN\*.txt�?.
    
• Modify SendPersonPort.
  • Click on SendPersonPort and move to Properties window.
  • Change the Send pipeline to “BizTalkTraining.SendPersonPipeline�? which is the send pipeline that we’ve created.
  • Change the URI (Receive location) to “C:\FILE2\OUT\%SourceFileName%�?.
    
• You’ve just configured to receive plain text (*.txt) from a folder to send to another folder as plain text.
4. Deploy the project.
• Right click on Solution ‘BizTalkTraining’ and select Deploy Solution.
  
• The output window will show status of the deployment.
  
• If you have deployed this project before (in Training 1), you need to restart BizTalkServerApplication and refresh the application.
  1. Expand BizTalk Server 2006 Administration -> BizTalk Group -> Platform Settings -> Host Instances.
  2. Right click on the host which runs BizTalkTraining application (Host type as In-Process) and click Restart.
     
  3. Next, refresh the application by right click on BizTalk Training and select Refresh. Now your application on BizTalk is up-to-date.
     
• If you haven’t deployed this application before, go back to Training 1 for further detail.
• Now you can test by drop person1.txt to C:\FILE2\IN and wait for result come out in C:\FILE2\OUT.

Resources

You can download the example source code (zip file) at here.
The zip file contains

• BizTalkTraining folder which is the example project on Visual Studio 2005.
• FILE2 folder which contains IN and OUT empty sub folders for test receive and send message and person1.txt which is an example text message.
• binding.xml file which is a configuration file for import in BizTalk Administration.

Related posts:

1. BizTalk Training 1 – basic send/receive xml message
2. BizTalk Training 3 – customize filename dynamically
3. BizTalk Training 4 – using Functiods in Map

Overview

This tutorial shows how to create simple orchestration to send/receive xml messages using FILE Adapter.

There are 9 tutorials in this training.

1. BizTalk Training 1 – basic send/receive xml message
2. BizTalk Training 2 – receive/send plain text
3. BizTalk Training 3 – customize filename dynamically
4. BizTalk Training 4 – using Functiods in Map
5. BizTalk Training 5 – using FTP Adapter

Objectives

• Learn how to create schema from sample xml file.
• Learn how to send/receive xml message using FILE adapter.
• Learn how to deploy BizTalk project to BizTalk Administration.

Topics

1. Add new orchestration.
2. Create schema.
3. Create new Message.
4. Create logical ports.
5. Deploy the project.
6. Configure BizTalk Administration.

Step-by-step

Suppose that I want BizTalk to process xml message from folder A (C:\FILE1\IN\*.xml) to folder B (C:\FILE1\OUT\%SourceFileName%). The sample data of xml message is in C:\FILE1\person1.xml.

  <person>
     <name>Mr. A</name>
    <position>Sales Manager</position>
     <salary>10000</salary>
   </person>

1. Add new orchestration.
   • New BizTalk Project named ‘BizTalkTraining’.
     
   • Add New Item.
     
   • Select new orchestration to the project named as ‘Orchestration1.odx’.
     
   • On Orchestration1, drag Receive and Send components to the orchestration.
     
2. Create schema
• Now I need to create schema for receive and send component. If you don’t have schema file (.xsd file) that corresponds with xml message, you need either to create schema by using wizard to generate from xml message or create by yourself. By using wizard, it’s fast but it doesn’t work well if your xml message is too complex.
• Solution 1: using BizTalk Schema Generator
1. To use this wizard, you need to enable it before use once by execute VBScript file that is in BizTalk SDK Utilities directory. If you installed BizTalk on default directory, the files should be in C:\Program Files\Microsoft BizTalk Server 2006\SDK\Utilities\Schema Generator\. If your document type is DTD, execute InstallDTD.vbs. If your document type is standard XML (Well-formed XML), execute InstallWFX.vbs. Or you can execute both files.
   
2. Back to the orchestration, in solution explorer. Select Add Generated Items.
   
3. Select Generate Schemas on left side and select Generate Schemas on right side. Click Add.
   
4. On document type, select Well-Formed XML and select input file from sample xml message. Click OK.
   
5. Wait for a while and you will see your schema has been created.
   
6. You’ll need to clear target namespace because the sample file doesn’t have any target namespace by click on “Schema” and clear Target Namespace in Properties.
   
• Solution 2: create the schema manually
1. In solution explorer, select Add New Items.
   
2. Select Schema Files on left side and select Schema on right side. Also, named the schema as person1.xsd. Click Add.
   
3. Now you’ll see empty schema file. You can add new element by right click on root node -> select Insert Schema Node -> Child Field Element.
   
4. Try to create element as the same in sample xml message. Also, you can change data type in properties window.
   
5. You’ll need to clear target namespace because the sample file doesn’t have any target namespace by click on “Schema” and clear Target Namespace in Properties.
   
6. Change name of the root to Person and now you’ll get the schema for incoming message.
   
3. Create new Message
• On orchestration1, move to Orchestration View. Right click on Messages and select New Message.
  
• Highlight on Message_1, change Identifier to msgPerson and select Message Type as schema that you’ve created in 5). (Schema -> BizTalkTraining.person1)
  
• Change Message on receive and send components in the orchestration1 to msgPerson.
  
4. Create logical ports
• You have configured to receive msgPerson and send out msgPerson. Next you need to create logical ports to receive and send these messages from/to.
• Create receive port.
  1. Right click on Port Surface area (red rectangular) and select New Configured Port.
     
  2. Click Next. Named the port as RecvPersonPort. Click Next.
     
  3. Configure Port Type.
     Name Port Type Name as ‘RecvPersonPortType’. Leave Create a new Port Type, Communication Pattern as One-Way and Access Restrictions as Internal selected. Click Next.
     
  4. Configure Port Binding.
     • Ensure that “I’ll always be receiving messages on this port.” is selected.
     • Select Port binding as “Specify now”.
     • Select Transport as “FILE”.
     • Type URI: as path with file mask that you want to receive. In this sample, it is “C:\FILE1\IN\*.xml”. That means to read any .xml file in C:\FILE1\IN.
     • Select Receive pipeline as XMLReceive.
     • Click Next and Finish.

     

• Create send port.
1. Right click on Port Surface area (red rectangular) and select New Configured Port.
   
2. Click Next. Named the port as SendPersonPort. Click Next.
   
3. Configure Port Type.
   Name Port Type Name as ‘SendPersonPortType’. Leave Create a new Port Type, Communication Pattern as One-Way and Access Restrictions as Internal selected. Click Next.
   
4. Configure Port Binding.
   • Ensure that “I’ll always be sending messages on this port.” is selected.
   • Select Port binding as “Specify now”.
   • Select Transport as “FILE”.
   • Type URI: as path to destination file that you want to send. In this sample, it is “C:\FILE1\OUT\%SourceFileName%”.
     Note: %SourceFileName% is the mask that means using file name as it was receive.
   • Select Send pipeline as XMLTransmit.
   • Click Next and Finish.

   

• Now you have configured logical ports to map with physical paths. Next is to connect logical ports to receive and send components that you have created previously. Drag green button on RecvPersonPort (1) to green button on Receive_1 component (2). Also, repeat this on send port.
  
5. Deploy the project
• Click on Receive_1 component and change Activate to “True” in the properties.
  
• We have finished on the orchestration. Next, we are going to deploy the project on BizTalk Administration. On the solution explorer, right click on Solution ‘BizTalkTraining’ and select Properties.
  
• On Solution Property Pages
  1. Select Configuration in Configuration Properties.
  2. Change Configuration to Deployment.
  3. Ensure that Deploy has been checked.
  4. Click OK.

  

• Next create strong name key and assign to the project
  1. Open Visual Studio 2005 Command Prompt by select on Programs.
     
  2. Type in the command prompt ‘sn -k c:\FILE1\BizTalkTraining.snk’. Then the key will be created in c:\FILE1.
     
  3. Back to the BizTalkTraining project, right click on BizTalkTraining and select Properties.
     
  4. On Property Pages
     • Select Assembly in Common Properties.
     • Find Assembly Key File. Click … to browse.
     • Select file that you have just created “BizTalkTraining.snk”.
     • Click Open and OK.
       
     • To change name of the application when deployed, select Deployment in Configuration Properties.
     • On Application Name, change to “BizTalkTraining”.
     • Click OK.
       
• Now you’re ready to deploy the project to BizTalk Administration. Right click on Solution ‘BizTalkTraining’ and select Deploy Solution.
  
• You’ll see in output window if the deploy was succeeded.
  
6. Configure BizTalk Administration
• Open BizTalk Administration; expand BizTalk Server 2006 Administration -> BizTalk Group -> Applications. You’ll see BizTalk Training was deployed to here. Right click on BizTalkTraining and click configure.
  
• On Configure Application window, select Host to BizTalkServerApplication. Click OK.
  
• Now you can start your application, but you need to create folder as you have already configured in Visual Studio. For receive folder, C:\FILE1\IN. For send folder, C:\FILE1\OUT.
• Right click BizTalkTraining again; click start to start BizTalk application.
  
• Click Start again.
  
• Now BizTalkTraining application is running, you can test your application by copy person1.xml (sample xml file) to receive folder (C:\FILE1\IN). If the application is configured correctly, the file will be moved to send folder (C:\FILE1\OUT) with the same name as in receive folder.
• Result in C:\FILE1\OUT\Person1.xml.
  

Resources

You can download the example source code (zip file) at here.
The zip file contains

• BizTalkTraining folder which is the example project on Visual Studio 2005.
• FILE1 folder which contains IN and OUT empty sub folders for test receive and send message, BizTalkTraining.snk which is a strong name key file used in the example project and person1.xml which is an example xml message.
• binding.xml file which is a configuration file for import in BizTalk Administration.

Related posts:

1. BizTalk Training 2 – receive/send plain text
2. BizTalk Training 5 – using FTP Adapter
3. BizTalk Training 4 – using Functiods in Map