BizTalk 2009

Biswojit Kumar Sahu (Architect)

C3: Protected
 About the Author

Created By: <Enter the name of the author, along with the Associate ID>

Credential <Enter the technical qualification and experience of the author>

Information:

Version and <Enter the version number and date of the PPT>
Date:

© 2007, Cognizant Technology Solutions Confidential 2

 Icons Used

Hands on
Questions Tools Exercise

Coding Test Your

Reference
Standards Understanding

A Welcome
Demonstration Contacts
Break

© 2007, Cognizant Technology Solutions Confidential 3

 Table of Contents

 Introduction on different types of Application Integrations

 Types of integration implementation
 Business challenges for integration.
 BizTalk Server 2009 Architecture
 Host
 Host Instances
 Adapters
 Pipelines
 Routing Services
 Transformations services
 Delivery services
 Business Process Services
 Tracking services
 Single sign on
 Business Rule Engine
 BizTalk Server 2009 installation and trouble shooting
 Configuration of BizTalk Server 2009 with SQL server 2008 and trouble shooting
 Features of BizTalk Editor with VS2008

© 2007, Cognizant Technology Solutions Confidential 4

 Table of Contents

 Creating Document Schemas

 XML Schemas
 FlatFile Schemas
 FlatFile Schemas generation wizard.
 EDI Schemas
 Property Schemas
 Implementing Debatching using Envelop Schemas
 Creating Transformation documents
 Document Mapping
 Debugging Maps in VS2008
 Exploring built in funtiods for mapping.
 Developing custom funtiod components

 Designing Orchestrations
 Features of orchestration designer
 Designing workflows using orchestration designer
 Exploring different shapes available
 Exploring different components of orchestration
 Applying transformation in orchestration
 Using .Net library inside Orchestration
 Exception Handling in Orchestration
 Developing BizTalk assemblies using Visual studio

© 2007, Cognizant Technology Solutions Confidential 5

 Table of Contents
 Configuring BizTalk runtime
 Working with Co-relation sets
 Consuming web service inside orchestration
 Exposing orchestration as web service
 Exposing orchestration as WCF Service
 Using info path
 Implementing Parallel Convoy
 Implementing Sequential Convoy
 Debugging orchestration
 Packaging BizTalk artifacts as a MSI file.
 Configuring ports at deploy time
 Creating pipelines
 Creating custom pipelines
 Creating custom pipelines components

 Using different Adapters

 Configuring different adapter’s native adapters
 Configuring different adapters for WCF service
 Using RFID and Swift adapters

 Business Rule Framework

 Composing Rules
 Deploying Rules
 Importing and Exporting Rules

© 2007, Cognizant Technology Solutions Confidential 6

 Table of Contents

 Administration
 Using BizTalk type Browser.
 Using Web Service Publishing Wizard
 Using WCF Service Publishing Wizard
 Working with BizTalk Explorer
 Using BizTalk Administration Console
 Working with Health and Activity tool
 Debugging BizTalk Orchestration
 Tracking messages

 Working with Business activity monitoring

 Creating different BAM artifacts
 Deploying BAM
 Administration of BAM

 Working on Use Cases

© 2007, Cognizant Technology Solutions Confidential 7

 Transaction Script Pattern:
Objectives
 Objective:
After completing this chapter you will be able to:
 Define Transaction script Pattern
 Identify When to apply Transaction Script Pattern
 Explain the flexibility the pattern offers
 Explain the shortcomings
 How to implement in .NET

© 2007, Cognizant Technology Solutions Confidential 8

 Transaction Script Pattern

 Transaction Script is a domain logic pattern where the logic is

primarily organized by the transaction that you carry out
with the system.

 The word transaction here generically indicates a business

transaction you want to carry out. The word script indicates
that you logically associate a sequence of system-carried
actions (namely, a script) with each user action.

 It organizes all the logic primarily as a single procedure

making calls to database directly or through thin wrapper.

© 2007, Cognizant Technology Solutions Confidential 9

 Transaction Script pattern

 TS is extremely easy to understand and explain. Each required

user action proceeds from start to finish within the boundaries
of a physical transaction. Data access is usually encapsulated
in a set of components distinct from those implementing the
actual script.
 TS doesn't have any flavors of object-oriented design. Any logic
you model through a TS is expressed using language syntax
elements such as IF, WHILE, and FOR. Adding a new feature to
an existing user action mostly means adding a new branch or
subroutine somewhere in the existing code.

© 2007, Cognizant Technology Solutions Confidential 10

 Transaction Script Pattern

 When to use this pattern ?

 TS is suited for simple scenarios where the business logic is

straightforward and, better yet, not likely to change and evolve.

 TS seems to be the perfect choice for a Web portal that relies on an

existing back office. In this case, you end up with some pages with
interactive elements that trigger a server action. Each server action is
resolved by making some data validation, perhaps making some trivial
calculations, and then forwarding data to the back-office system.

© 2007, Cognizant Technology Solutions Confidential 11

 Transaction Script Pattern

 Working with the pattern

 Where you put the TS depends on how the layers are organized. It is
always better separate subroutines/classes separate from presentation
and data source
 One way of implementing the TS pattern is to have several Scripts in a
single class where each class defines a subject area of related TS.
 Other way is to have a separate class for each TS and make use of
Command Pattern (GoF) to call the scripts.
 Avoid calling the TS Classes from presentation layer to enable it easier
to code and test the script

© 2007, Cognizant Technology Solutions Confidential 12

 Active Record Pattern – Key
Strengths
 Strengths of TS Pattern
 This pattern presents the application logic as a collection of logical
transactions. It has no startup costs for the team and works well with
rapid application development (RAD) environments.
 TS is ideal for projects with only a small amount of logic, tight deadlines,
and access to rich IDE such as Visual Studio.
 A high-level transaction can be broken down into simpler and reusable
routines and layers. For e.g. The persistence layer, where you find
smaller components that handle data access and other chores.

© 2007, Cognizant Technology Solutions Confidential 13

 Transaction Script Pattern- Key
Weaknesses
 Weaknesses of TS Pattern
 TS has remarkable potential for code duplication and thus affect
maintainability
 As the volume and content of requirements grow, it usually gets harder
to re-factor.
 Regression Testing is a bigger challenge

 Related Patterns
 Table Data Gateway Pattern
 Row Data Gateway Pattern

© 2007, Cognizant Technology Solutions Confidential 14

Transaction Script Pattern- A
sample implementation

© 2007, Cognizant Technology Solutions Confidential 15

 .NET Implementation

 Designing domain logic according to TS is not a hard task. The

list of required transactions by looking at the actions available
in the presentation layer or, more generally, look at the use
cases defined for the system.
 Once the list of transactions is ready, implement each
transaction in a method housed in a component. In the
Microsoft .NET Framework, a component is essentially a class
compiled to an assembly.

© 2007, Cognizant Technology Solutions Confidential 16

 Transaction Script Pattern

 Designing Business Components

 The basic idea is that each transaction has its own method in some
component
 Can have all the code in one place; or you can delegate the execution of
child steps to some shared helper objects. These helper objects
collectively form specific layers, such as validation, formatting, and
persistence.
 All classes that implement transaction scripts can be referred to as
business components. You can derive all business components from a
unique to have a common base behavior like error handling,
authorization ,logging etc.,
 Build the base class to support dependency injection and thus receive
and consume external objects that supply a service to the script.

© 2007, Cognizant Technology Solutions Confidential 17

 Transaction Script Pattern
Sample Code implementation
 A Sample code to book hotel room & Ordering a product
public
public class
class ApplicationAPI
ApplicationAPI
{{

public
public int
int CreateOrder(OrderInfo
CreateOrder(OrderInfo order) order)
{{
//
// Start
Start the
the transaction
transaction
//
// Retrieve
Retrieve andand check
check product
product information
information
//
// Check if the amount of
Check if the amount of goods
goods being
being ordered
ordered is
is available
available
//
// Check
Check credit
credit status
status
//
// Calculate
Calculate price,
price, including
including tax,
tax, shipping,
shipping, and
and freight
freight
//
// Add
Add aa new
new record
record toto the
the Orders
Orders database
database
//
// Add
Add new
new records
records to to the
the OrderDetails
OrderDetails database
database
//
// Commit
Commit the the transaction
transaction
//
// Return
Return the
the order
order ID
ID
}}
public
public string
string BookHotelRoom(Customer
BookHotelRoom(Customer guest, guest, DateTime
DateTime checkIn,
checkIn, DateTime
DateTime checkOut)
checkOut)
{{
//
// Start
Start the
the transaction
transaction
//
// Check
Check room
room availability
availability for
for requested
requested stay
stay
//
// Check
Check customer
customer information
information (already
(already guest,
guest, payment
payment method,
method, preferences)
preferences)
//
// Calculate
Calculate roomroom rate
rate
//
// Add
Add aa new
new record
record toto the
the Bookings
Bookings database
database
//
// Generate
Generate the the confirmation
confirmation number
number
//
// Commit
Commit the the transaction
transaction
//
// E-mail the customer
E-mail the customer
//
// Return
Return the
the confirmation
confirmation number
number
}}
}}

© 2007, Cognizant Technology Solutions Confidential 18

 Time for a Break !

© 2007, Cognizant Technology Solutions Confidential 19

 Questions from participants

© 2007, Cognizant Technology Solutions Confidential 20

 Test Your Understanding

 <List set of questions that you would like the audience to

answer.>
 <These questions should be inline with the objective.>

© 2007, Cognizant Technology Solutions Confidential 21

 Hands-on Exercise

 <List set of questions that you would like the audience to

practice or provide link for such questions.>
 <These questions should be inline with the objective.>

© 2007, Cognizant Technology Solutions Confidential 22

 <RIO Name>: Summary

 Summarize important points here

© 2007, Cognizant Technology Solutions Confidential 23

 <RIO Name>: Source

 <List the sources from where you have taken the content for
this RIO. This could be books, Web sites, or articles>

Disclaimer: Parts of the content of this course is based on the materials available from the Web sites and books
listed above. The materials that can be accessed from linked sites are not maintained by Cognizant Academy and
we are not responsible for the contents thereof. All trademarks, service marks, and trade names in this course are
the marks of the respective owner(s).

© 2007, Cognizant Technology Solutions Confidential 24

You have successfully completed
Transaction Script Pattern
Click here to proceed
Additional Resources
 Additional Resources

 The next set of slides contain resources for including different

types of figures and tables.
 Use them to enhance the concepts of your presentation.

© 2007, Cognizant Technology Solutions Confidential 27

 Cycle Diagram

Add Your Text

Text
Text

Text
Cycle name

Text

Text

© 2007, Cognizant Technology Solutions Confidential 28

 Cycle Diagram

Add Your Text

Text
Text

Text
Cycle name

Text

Text

© 2007, Cognizant Technology Solutions Confidential 29

 List items

1.
1.List
List Item
Item

2.
2.List
List Item
Item

3.
3.List
List Item
Item

4.
4. List
List Item
Item

5.
5.List
List Item
Item

© 2007, Cognizant Technology Solutions Confidential 30

 List items

1.
1.List
List Item
Item

2.
2. List
List Item
Item

3.
3.List
List Item
Item

4.
4.List
List Item
Item

5.
5.List
List Item
Item

© 2007, Cognizant Technology Solutions Confidential 31

 Progress Diagram

Phase
Phase 11 Phase
Phase 22 Phase
Phase 33

© 2007, Cognizant Technology Solutions Confidential 32

 Progress Diagram

Step
Step 11 Step
Step 22 Step
Step 33 Step
Step 44

© 2007, Cognizant Technology Solutions Confidential 33

 Process Diagram

Phase
Phase 11 Phase
Phase 22 Phase
Phase 33

© 2007, Cognizant Technology Solutions Confidential 34

 Block Diagram

TEXT TEXT TEXT TEXT

TEXT TEXT TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 35

 Block Diagram

TEXT TEXT TEXT TEXT

TEXT TEXT TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 36

 Block Diagram

TEXT TEXT TEXT TEXT

TEXT TEXT TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 37

 Table

TEXT TEXT TEXT TEXT TEXT

Title A

Title B

Title C

Title D

Title E

Title F

© 2007, Cognizant Technology Solutions Confidential 38

 Table

TEXT TEXT TEXT TEXT TEXT

Title A

Title B

Title C

Title D

Title E

Title F

© 2007, Cognizant Technology Solutions Confidential 39

 Table

TEXT TEXT TEXT TEXT TEXT

Title A

Title B

Title C

Title D

Title E

Title F

© 2007, Cognizant Technology Solutions Confidential 40

 Table

TEXT TEXT TEXT TEXT TEXT

Title A

Title B

Title C

Title D

Title E

Title F

© 2007, Cognizant Technology Solutions Confidential 41

 Comparison Table

TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 42

 Comparison Table

TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 43

 Comparison Table

TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 44

 Comparison Table

TEXT TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 45

 Comparison Table

TEXT TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 46

 Comparison Table

TEXT TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 47

 3-D Pie Chart

TEXT

TEXT
TEXT

TEXT

TEXT
TEXT

© 2007, Cognizant Technology Solutions Confidential 48

 3-D Pie Chart

TEXT

TEXT
TEXT

TEXT

TEXT
TEXT

© 2007, Cognizant Technology Solutions Confidential 49

 Marketing Diagram

Title

TEXT TEXT TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 50

 Marketing Diagram

Title

TEXT TEXT TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 51

 Marketing Diagram

Title

TEXT TEXT TEXT TEXT

© 2007, Cognizant Technology Solutions Confidential 52