Day 2 At Microsoft SOA and Business Process Conference

Today I will be following all sessions on SOA track. It will kick off with a customer’s panel: SOA Success Stories, which will be interesting how companies are successful with implementing a SOA in their organization. Next will be a session of avoiding 3 common pitfalls in Service Contract design. In the afternoon there will be two sessions; one is about building an ESB on the Microsoft Platform and the other is implementing change data capture as an event source for SOA.
Here are some notes from the customer panel:

First cutomer to speak was Ryan Garner from JetBlue (http://www.jetblue.com/)

Business Drivers

* Drive away from screen scrapping and work together with booking agents
* Show availability flights, hotel rooms, ect...

- Microsoft Service Model
- Web Service interface modeling
- Web Service Management Tool
- Governance; versioning

Low hanging fruit (gets things up and running fast)

Next speaker was Justin Myrick from Clearchannel (http://www.clearchannel.com/)

Business drivers

Lots of ERP (markets), varying different systems for everything, taking things out hands of people
Workflow for everybody, web services

- Managing web services
- Workflow K2
- System workflow BizTalk

Technology is not problem, it's the people (Changing organization, developers, how IT delivers solution)
Governance is a big deal, more web services than you think
SOA can't be bought, one size does not fit all

Last customer to speak was Rodney Turpin from HP (http://welcome.hp.com/country/us/en/welcome.html)

Business Drivers

reduction of legacy applications
balance workload

- BAM
- MOM
- BizTalk

disparate e-storefronts

aggregation BizTalk orchestrations

Tools Manage SOA

* Off the shelf tools, SLA Service Activity (Service Activity Store SQL Server)
* Team system, .NET 2.0 SOAP request/response (SOA) Service Management
* MOM for monitoring, BAM
* UDDI for registry for service

* Must haves for starting a SOA (heath monitoring security scalability availability)
- SOAP Reguest/Respone tracking
- body request/response tracking
- certificate based authentication
- log request/response times (SLA)
- tracking watch to not track everything
- clustering on the back-end
- track/tracing

* Fund SOA project

- Funded on backs on projects
- Invest in enabling technology by CIO (critical investment)
- separate funding

* Testing web service software

* SOA reusable enables agility
- reuse is there
- journal entry service (clear channel) reuse

* Happy Path SOA long running process exceptions consistency
- products ...
- no long running process
- no experience
- Exceptions management MOM

First technical session of the day the three comon pitfalls in service contract design from Tim Ewald (Foliage Software Systems). There are many challenges in systems integration for architects and developers, and the industry has focused on XML, web services, and SOA for solving integration problems by concentrating on communication protocols, particulary in regard to adding advanced features that support message flow in complex network topologies. However, this concentration on communication protocols has taken the focus away from the problem of integrating data. Flexible models for combining data across disparate systems are essential for succesful integration. These models are expressed in XML schema (XSD) in web service based systems, and instances of the model are represented as XML transmitted in SOAP messages. Here are the notes on this one:

Governance
Testability
Registry (Where is the service)

Silo-ed App

Designing contracts is a big challenge (data models)
- Maintain flexibility
- Single common data model

Canonical model approach, hard to maintain, change

3 systems with customer data (heterogeneous systems)
- Simple solution 3 systems 1 data store (hard almost impossible, mandatory adaptation, who have to use it) lose agility, transformation your way out off it
- Schema shared across systems add minOccurrs to elements (shape data if it is present)
- occurrence constraints at system level
- missing vs. null data
- no solution for versioning
- do not change namespace otherwise more mappings maintain compability
- It's about interfaces, changing by adding is no problem, new service type (new operations) no problem, but do not change existing service/data type then change the namespace. Nothing new here
- Service evolve so keep flexibility in mind
- Systems evolve so schema should evolve to, so flexible to change

First afternoon session was :

Building an ESB on the Micrsoft Platform Brian Loesgen/Lukas Cudridge

Here are my notes on this talk of both:

Top down approach

Business drivers

* Kaiser Permanente (http://www.kaiserpermanente.org/)

* show business value
* better way to integrate existing applications portfolio
* enabler for greater SOA strategy

TERM SOA lot of definitions (Fiorana group, sonic, IBM, Gartner)
Agreement on what an ESB is and what it does!!!

IDC research

Message broker
Message Transformation
Message validation
Message-Oriented middleware

Incl. adaptation and orchestration

ESB is important building block for SOA

Service Oriented Infrastructure

Preferred way service consumer standard service provider SOAP
Service Registry
Service Management
Security

Standard Service Provider/Consumer

WSDL defined SOAP
HTTP, JMS over WMQ
Support WCF and XMS
CIM/SIM Functionality

Service Registry second key component to SOA next to ESB (meta data, service portfolio)
Enterprise Service Catalog
Custom Publisher
Extended taxonomy

Web Service Management Amberpoint
Integration MOM

Who is in the ESB game

Cordys, Oracle, BEA, SUN, Sonic

Announcing ESB Guidance release to partners.

* Toolkit
* BizTalk 2006
* Architectural Guidance
* ESB Core Engine
* Sample On/Off Ramps
* Provisioning Framework

esbtlkt@microsoft.com

ESB Core Engine

On/Off Ramps (Get in/out of ESB) On ramp recieve location BizTalk, Off Ramp Send Port
dynamic routing, exception, transformation !!!!
Know more about the message before processing the message (context property)
Submit message set properties, so know to process message or route it;

- On/Off ramps
- Intermediary functions
- Standardized meta envelope
- resolution mechanism
- provisioning and administration

re-usable component for dynamic message transformation

more or less there is meta data in the envelope and in processing message it will through db lookup of bre ...
exception handling mechanism (enterprise library)
BizTalk message oriented environment --> publish exception --> message box --> handler listen to those message (subscribe to them0

Failed Message Routing (API --> create fault message)

Individual components

Demo ESB guidance and ESB Core Engine

ESB client meta data properties ...
Debug view

Through exceptions out to a SharePoint portal site, Infopath form to show error details
Retry port

SharePoint Portal and BI capabilities showing kind or exceptions

ESB Infrastructure

Flexible distributed architecture

Receiving NLB receiving
processing/Sending not in NLB
Message boxes clustered / Log shipping (data centers)
tracking db clustered
Separate locations

Developer SDK
VM with ESB core Engine installed
Sample application
Sample unit test
Sample automated build process

There is a role for SharePoint in ESB for monitoring

package pushed a few weeks

Last talk of the day for me was Implementing Change Data Capture as an Event Source for SOA from Doug Wheatin from Attunity (http://www.attunity.com/)

Here are some notes, it was not a lengthy presentation on the subject:

Why data capture?

SOA key to integration

Attunity provide adapter to connect to legacy systems looking for chaged data capture (lower level on SOA layer stack)

CDC where to use it; ETL data from legacy from one data source to another, include cleansing amongst other things
data sync, event driven BPM, BAM

CDC based ETL near real time updates to data warehouse, but in a SOA way ETL engine is BizTalk. Get data out fast into GW, and by continuous bulk loading (all of it) Amount of data will grow 500Gb + , so in that event by using CDC only changes on data is captured and loaded through ETL like of manner to DW. High frequency low volume so excellent for use for BizTalk. Changes are retrieved and noticed by services delivered by Attunity also adapters for these service so BizTalk can import this data in, transform and send to DW.

Services Extracting
BizTalk Transformation
Services Loading

CDC SOA way

Latency

Batch to near real time
pull mechanism

Real time event driven mechanism

That's it for today.

Labels: ,