Using%20BizTalk%20Server

1

• Using BizTalk Server
• to build support for a new business model in the
  Dairy industry

Anders Kingstedt, Consultant Manager Alan Smith,
BizTalk expert and MS MVP
2
Road map

• Overview, the FRAS project
• The FRAS Hub, Technology Overview
• Integration Patterns in BizTalk Server 2004
• Lessons learned
• Q A
• Extras
• The Integration Factory - overview
• Using BizTalk to create SOA based Integration
  solutions

3
About us

• Alan Smith
• Senior developer, BizTalk Mentor at Know IT
• MCSD and MS MVP BizTalk. MCT BizTalk.
• Experience from several BizTalk 2004 projects
  Technical profile BizTalk, C
• Anders Kingstedt
• Responsible for Know ITs Integration offering
• Alliance manager with Microsoft
• Consultant manager
• Technical profile ltobsolete ?gt

4
FRAS Business Objective

• The Swedish Dairies will launch a new business
  model in 2005
• Using common transport capacity (logistics)
• Selling dairy products nation wide
• This called for
• An integration solution
• Support for various message formats
• Support for various business messages
• Support for future changes without having to do a
  complete rewrite of the solution
• Our solution
• Relies on MS BizTalk Server 2004 as the
  integration mechanisms allowing for changes in
  the underlying IT structure
• Provides a communications infrastructure that
  allows for future growth
• Provides web-access to operational status for
  critical information (stock, invoice, order etc.)

5
FRAS Business Process Support
6
FRAS Project Challenges

• Challenge No previous large scale BizTalk 2004
  experience
• Solution Hire the right people, invest in
  training, use MS, rely on a SOA architecture
• Challenge Many people and companies involved in
  the project
• Solution Establish a project planand stick to
  it, focus on risk, inform communicate
• Challenge Tough requirements on throughput and
  availability
• Solution Evaluate (test) various ways of
  communicating messages, bet on a multi server
  environment

7
FRAS Technical Overview
8
Integration Patterns in BizTalk Server 2004

• ltstartgt
• Alan Smiths presentation
• lt/startgt

9
Lessons learned

• Setting up an Integration Factory is definitely
  a great a idea for large scale integration
  projects
• Using checklists, templates, integration /
  enterprise patterns is an investment that pays
  off in the long run.
• Sharepoint provides project information
  exchange.
• Going from the test development environment to
  production is challenging
• Creating a reusable process to go from dev to
  test to release did the trick
• BizTalk Server 2004 is a rich but sometimes
  challenging integration environment
• Investing in a good architectural base crucial
• Training is a good idea - we recommend the
  DeepDive training program (provided by Microsoft)
• In our experience, it takes roughly a year to
  become a proficient BizTalk developer

10
Integration is about more than just integration
11
Contact information

• Alan Smith, alan.smith_at_knowit.se
• Anders Kingstedt, anders.kingstedt_at_knowit.se
• Thank you for listening!
• Ps. Dont miss our SOA seminar June 3 arranged by
• Know IT, SAP and Microsoft. For more information
• and registration visit www.knowit.se

12
Comments or questions?

• Q A

13
The Integration Factory
14
The Integration Factory - Offer

• The Integration Factory
• Relies on a set model for integration
• Is an integration On-stop-shop we provide
  solutions from start to finish
• Provides activity support
• Facilitates customer specific Integration
  Factories
• we help our clients to establish their own
  factories

15
The Integration Factory - Activities
Inception
Elaboration
Construction
Transition

• Supports activities such as
• Proof-of-concept / proof-of-product
• Security and access solution
• Process analysis development
• Message design
• Testing
• Implementation av integration enteprise
  patterns
• Mentoring technology, methodology and project
  support
• Maintenance and long-term support of the
  integration solution

16
The Integration Factory combines Pejl and RUP
17
Typical Integration Factory Artifacts
Inception
Elaboration
Construction
Transition
Status- rapport
Project Contract
Conclusionreport
Status report
Pejl
DeliveryAcceptance
Agreement
The Sales Process
Test spec.Test prot.
CodeDatabaseWeb Component
TestPlan
SoftwareArchitectureDocument
Use Case Model
User ManualOperation Manual
FunctionalDesign
K-RUP (integration)
Integration Patterns
Integration Use Cases
18
Use Case Model System Use Case
Integration Use Case
19
Integration General requirements

• Design and architecture
• Meddelandespecificering
• System- och informations- design
• IT-arkitektur

• Operations
• Kartläggning - behovsanalys
• Processutveckling
• Verksamhetsmodellering

• Mainenance
• Löpande underhåll
• Löpande utveckling och övervakning

Integration requirements

• Technology IT infrastructure
• Orkestrering
• Konstruktion Implementation
• Verktygsstöd (EAI-verktyg)
• Etablering av infrastruktur

• Test and Quality Assurance
• Etablering av testplaner och genomförande av
  test
• Konfigurering, kravhantering