headlinesdownload.microsoft.com/documents/australia/soa/systalk... · 2018-12-05 · to an soa...
TRANSCRIPT
Headlines
Recession risk keeps dollar on defensive
Tech sector facing most job cuts since 2003
China's bid to save its bacon
In a downturn, how will you behave?
Preserve the status quo, and hope for the
best
Blindly cut expenses across the board
Get Lean and be in a position to quickly move
How does an IT department get Foxy?
1. Reduce IT support costs
2. Reduce IT development costs
3. Agile IT systems
SysTalk
• Part of the LogicalTech Group
• Application Integration and BizTalk specialists since 2000
• Microsoft Gold Certified
• Team of MS certified BizTalk developers
ESB ROI
• 50% reduction in the time to implement an interface
• 75% reduction in time taken to rectify common data errors
• 50% reduction in maintenance effort
• Reduced salary costs
ESB ROI – Case Study
• Assume 5 interfaces are implemented per month $21,500
• Assume that each of the 5 new customer interfaces were previously manually serviced
• Maintenance now handed by one person rather than 2
• Assume you have 5 errors per day that can now be corrected by junior support staff
• That can now be implemented by your BA
$37,800
$15,000
$6,720
$5,500
Improved Customer Service
• Real time insight to business data.
Evolution of Enterprise Architecture
Evolution of Enterprise Architecture
Point to Point Integration
Integration Server ERP Server
Interface built specifically from system to system
Pros •Simple•Fast
Cons
Evolution of Enterprise Architecture
Multi Point to Point Integration
Ordering SystemIntegration Server
Warehouse
Payment GatewayCustomer
Information System
A natural evolution of the point-to-point model, as the Enterprise integrates new applications
Pros •Naturally evolves over time•Fast•100% fit for purpose
Cons •Maintainability•Is fragile•Low visibility of what is happening
Evolution of Enterprise Architecture
Hub and Spoke Architecture
Single system which acts as an interpreter between systems- Spokes handle passing data to and from the hub- The hub translates and routes the messages in between systems
Pros •Reduces number of interfaces for multi system solutions•Adds support for routing of messages•Much more code reuse
Cons •Can be difficult to scale. (Enterprise solution vssingle box)•Potential Single System point of failure.•The spaghetti has been contained, but not removed...#
Customer
Information System
Integration Server
Warehouse Payment Gateway
Ordering System
Evolution of Enterprise Architecture
Service orientated Architecture (SOA)
Systems exposes services that are well defined, implementation independent, and encapsulate Business functions.
Pros
Cons
Internet
Systems
Service
Endpoint
Organisation A
Systems
Service
Endpoint
Organisation B
Systems
Service
Endpoint
Organisation C
•Makes the enterprise understandable. •The more understandable the enterprise is the, the more re-use and innovation can happen.
•The enterprise will only be understandable if the vocabulary is documented•Can be a victim of its own success (overuse of service points)•Can be perceived as overly complex #
Evolution of Enterprise ArchitectureEnterprise Service Bus (ESB)
An extension of SOAAdds additional management, standardization and governance to an SOA framework.
Is generally a concept, however companies are releasing products with ESB in the name.Sonic Software was one of the first to use the phrase early in 2002Most mature organizations that have implemented SOA have inherently implemented some form of ESB
Pros •Adds standardization and enforces re-use of SOA frameworks.•Metrics and monitoring can be managed across the enterprise.•Endpoint monitoring to determine system stability. •Substantially reduces the amount of effort to implement new workflows. Business analysts can be utilized rather than developers to implement new integrations.
Cons •More development effort needed up front to set up.
Enterprise Service Bus
Payment Gateway
WarehouseCustomer
Information System
Ordering System
Submission Gateway
s
Router-Firewall
Evolution of Enterprise Architecture
So what the difference between ‘Hub and Spoke’ and ESB/SOA again?
Frameworks for Business people
How does a re-usable framework add value to an organisation ?
Frameworks for Business people
90% of all integration is point to point
System A
System B
System C
Add a Sender Party
An analyst's view of integration
Add a Document type
An analyst's view of integration
Add a Transformation
An analyst's view of integration
Add Recipient Party
An analyst's view of integration
Workflow Summary
An analyst's view of integration
Frameworks for Business people
Document Validation (Bad Data)
Frameworks for Business people
Typical validation error
System.Xml.Schema.XmlSchemaValidationException: The element 'item' has invalid child element 'codes'. List
of possible elements expected: 'code'.
at System.Xml.XmlValidatingReaderImpl.InternalValidationCallback(Object sender, ValidationEventArgs e)
at System.Xml.Schema.XmlSchemaValidator.SendValidationEvent(ValidationEventHandler eventHandler, Object
sender, XmlSchemaValidationException e, XmlSeverityType severity)
at System.Xml.Schema.XmlSchemaValidator.ElementValidationError(XmlQualifiedName name, ValidationState
context, ValidationEventHandler eventHandler, Object sender, String sourceUri, Int32 lineNo, Int32
linePos, Boolean getParticles)
at System.Xml.Schema.XsdValidator.ValidateChildElement()
at System.Xml.Schema.XsdValidator.ValidateElement()
at System.Xml.Schema.XsdValidator.Validate()
at System.Xml.XmlValidatingReaderImpl.ProcessCoreReaderEvent()
at System.Xml.XmlValidatingReaderImpl.Read()
at System.Xml.XmlValidatingReader.Read()
at XmlValidator.Form1.button1_Click(Object sender, EventArgs e) in C:\ESB\XmlValidator\Form1.cs:line 53
Frameworks for Business people
Typical error returned to the end user
System.Xml.Schema.XmlSchemaValidationException: The
element 'item' has invalid child element 'codes'.
List of possible elements expected: 'code‘.
Frameworks for Business people
Customer friendly error
Error location and context assists in diagnosis and correction
Frameworks for Business people
Self Help Portals (Document visibility)
Realtime document tracking (for internal staff & external vendors/clients)
Communication checks
Management of document issues
Frameworks for Business people
Real-Time document tracking
“The integration layer is down yet again!”
Frameworks for Business people
Communications checks
Customer A
Customer B
Customer C
Customer D
Frameworks for Business peopleManagement of Document Issues
Your KPI’s at a glance
Historical view of performance
Familiar web interface
Accessible both inside and outside the firewall
Level 1 Helpdesk can diagnose and support many issues
Frameworks for Business people
Is your organisation reactive or proactive ?
How much do you spend every week dealing with day-to day issues?
Why should you deal with data issues created by someone else? Issues are more effectively dealt with by the people who know the data.
Finally “The integration layer is down, yet again!” is a statement you don’t have to put up with.
SysTalk
Application Integration and BizTalk Experts