BizTalk Server 2006 - Karlstad University · 2009-05-15 · BizTalk Server 2006 Administration...

MGö, MBl, JEd C#.NET VT09 1

BizTalk Server 2006

VT 09


Literature

• These slides are based on information in the book:– Foundations of BizTalk Server 2006 By Daniel

Woolston


BizTalk Server 2006 Administration Console

• The center point of all activity– Through the main page you can access links that

drive other content– Application based

• In this version you have the concept of BizTalk as an application. In earlier versions it was more of a pool of ports, orchestrations, pipelines,..

• A default application has been created called ”Application 1” – It will have a folder for each of the application pieces– In earlier versions you had to use naming conventions to

organize the integration tools• This application view is only available through the

Administration Console– You also have easy access to the Event Viewer


BizTalk Server 2006Configuration

• Allows you to modify the current configuration.– Click Unconfigure before reconfiguring


BAM Portal Web Site

• Allows you to see the running processes at your server and their status– For example: Product waiting for approval

before shipping on..


Web Services Publishing Wizard

• Parts of the BizTalk Server structure can be published as web services– Orchestrations, schemas


Visual Studio 2005 Tools


Available Artifacts in Visual Studio


BizTalk Explorer

• View -> BizTalk Explorer

• Handy for quick lookups


More on Messaging

• If you can save it, send it, or serialiaze it– It can be a BizTalk message– BizTalk does not only accept XML-files

– But among the most common ones are XML-files and flat files


Message-Delivery Patterns

• Different ways the messages are consumed and produced

– Scatter-gather– Request-reply– Publish-subscribe


Scatter-gather

• Scenario: Your company is interested in the lowest price for a product among your vendors– A bid request is sent to BizTalk which in turn scatters

the request to the connected vendors. – BizTalk then wait and gathers the messages from the

vendors that responded– BizTalk then processes the messages and pass them

back to the business user who ordered the comparison


Request-reply

• Scenario: Communication with an organization with strict rules. – When sending a message to our BizTalk

server it will want to have an immediate reply indicating that we have received the message

• ACK/NACK


Publish-subscribe

• Scenario: You want to communicate updated information to vendors that are interested– You let BizTalk publish the message out to a

catalogue location that your vendors has access rights to

– The vendors that are interested has a process that monitors, subscribes to, the file folder

– When a message appear in the file folder, interested vendors pick it up


Message-Processing Patterns

• These patterns are aimed towards how BizTalk processes the messages that has arrived

– Aggregator– First in/First out– Splitter


Aggregator

• Aggregator: Collect sequence of incoming messages and consolidate into single message

– (Recipient-List “scatters”; Aggregator “gathers”)


First in / First out

• FIFO – messages are processed in the order they arrive– Not done by default, need to configure BizTalk

do FIFO


Splitter

• Pattern that splits one message into several, individual messages that are processed separatly


Creating your first Schemas

• In Visual Studio:1. Create a new Project

2. Choose to create an empty BizTalk Server Project and name it

3. In Solution Explorer, right-click on the project name and select Add->New Item

4. Select Schema Files then Schema in the right panel

5. Name the schema Note.xsd


Root node

• By default Visual Studio will add a Root node for you

• This node will need to be renamed to match our data– Right-click on the Root

node and select Rename

– Modify so that the root node is named Note


Adding Nodes

• Right-click on the root node (Note) and select Insert Schema Node

• We are going to add a Child Field Element, so choose that

• Rename and type in To• Do the same for the fields

From, Date, Heading and Body


Setting the Data Type

• By default all fields will have the data type string

• For the fields that we have added so far, except for Date– Right-click on Date

and choose/go to the properties pane

– Choose Data Type and xs:date


Final Result: Note.xsd


Creating a Sample XML File

• Good for testing purposes!– Right-click on Note.xsd in the Solution Explorer and select Properties– Set the output Instance Filename and where you want to place it, name

it SampleNote.xml


Creating a Sample XML File cont’d

• Right-click on Note.xsd again and select Generate Instance

• Your sample file will be generated and found in the catalogue you had chosen

• If you open the Output window you will see a link that leads to the xml-file


Final Result: SampleNote.xml


Generating a Schema from a XML File

• Let’s say you have an xml-file, and then want to generate a schema from that file..

<?xml version="1.0"?> <mail> <recipient>davb07</recipient> <from>Mari</from> <sent><year>2007</year><month>07</month><day>07</day></sent><subject>Reminder</subject> <body>Labs to be handed in no later than.. </body> </mail>


How to generate an XML Schema

• Right-click on your project and select Add -> Add Generated Items• Select Generate Schemas in both panels


How to generate a XML schema cont’d

• Click Add • Select Well-formed

XML

• Browse to find the file, in our case MailFromMari.xml

• Click OK and your schema will be generated

• You might have to change the data types


Generating a Flat File Schema

• Let’s say that instead of having a Note.xml file we have a noteFlatFile.txt that containts this:

Jane,Dave,2007-06-12,Hello,LalalaMia,Malin,2007-07-07,Reminder,TralalaOlle,Joppe,2007-01-01,Save,Joppe dead or alive


The Flat File Schema Wizard

• Right-click on the project name in the Solution Explorer and select Add->Add New Item

• Select Schema Files and then Flat File Schema Wizard

• Name the schema file noteFlatFile.xsd

• Click Add to continue


The Flat File Schema Information

• Click next when the welcome box appears• The Flat File Schema Information box appears. Locate the txt-file and fill in

as below


Selecting Document Data

• Select the text you want to use to create the schema• Click Next


Selecting Record Format

• Select By delimiter symbol


Specify properties of the delimited record

• Specify the delimiter used in the text file to separate rows. We used a carriage return/line feed (CR/LF) to end each row


Specify properties of the child elements

• On the first row: Tell the wizard that we are dealing with repeating records• Since we are interested in building a schema from the file, the rest of the

rows does not matter. Choose Ignore on the rest.


Delimiting the rest of the nodes


Selecting Document Data again

• But this time we are only interested in the first line, since we are interested in building up the schema structure, so highlight that.


Specifying how the record data is formatted

• The record data is separated by a delimiter symbol, so choose that


Selecting delimiter symbol


Name and declare data type for each child element - before


Name and declare data type for each child element - after


Final Schema View


Schema Mapping

• Often the schema that your own application uses does not match the schema your business partners use

• BizTalk has ha Mapper for this purpose

Source file schema

Destination file schema

Destination data file


Creating the Schema Map

• Right-click on the projects name and choose Add -> Add New Item

• Select Map Files and in the right panel Map

• Name your map file TestMap.btm


The BizTalk Mapper

• The three panels are– Left: Source Schema– Center: Manpulation of how the mappings are

done. These manipulations are done through what BizTalk call Functoids

– Right: Destination Schema


Adding Schemas

• We are going to use Mail.xsd as the Source schema, and Note.xsd as the Destination schema– Click on Open Source Schema and locate

Mail.xsd

– Click on Open Destination Schema and locate Note.xsd


Associating Schema Elements

• Now highlight an element and simply drag to the appropriate element in the destination schema


BizTalk Functoids

• So what is left? Correct, we still have to map the date element

• BizTalk offers a lot of predefined functoids for that purpose– Open the Toolbox for

the Mapper


Mapping the Date Element

• For this mapping we are going to use the String Concatenate functoid– Locate and highlight the functoid– Drag it onto the center pane of the Mapper– From the Source Schema pane drag year,

month and day to the functoid– From the Destination Schema pane drag date

to the functoid


Configure the Functoid

• Right-click on the functoid and choose Configure Functoid Inputs


Adding Extra Parameters

• Now, we want to add a delimiter, -, between the elements

• Click on the button marked by an arrow (the tooltip will also say ”Insert New Parameter”)


Adding Extra Parameters

• Double-click on the icon for the new parameter to change its value.

• Add ’-’


Testing the Map

• Right-click on the map file in the Solution Explorer and select Properties

• In TestMap Input Instance– Locate the file we created before: MailFromMari.xml– Click OK

• Right-click on the map file again and this time choose Test Map

• You will see the result in the Output pane– Click and follow the output file that has been created

for you


The Test Results

BizTalk Server 2006 - Karlstad University · 2009-05-15 · BizTalk Server 2006 Administration...

Documents

Transcript of BizTalk Server 2006 - Karlstad University · 2009-05-15 · BizTalk Server 2006 Administration...