22
Motorola SOA Toby Redshaw Corporate VP - IT Strategy, Architecture, Emerging Tech and eBusiness

Motorola SOA Toby Redshaw Corporate VP - IT Strategy

  • Upload
    zubin67

  • View
    325

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

Motorola SOA

Toby RedshawCorporate VP - IT Strategy,

Architecture, Emerging Tech and eBusiness

Page 2: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA

• So what ? Who cares ?

• What happens if you are 25% less efficient in IT than your direct competitor ?

• What happens if you are 25% less efficient in customer acquisition and retention or supply chain ?

Page 3: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA – What We’ll Cover

• We will cover a lot – you will have answers but you will have even more questions….

• What the heck is it … and what does that mean and why you should invest…

• Lessons learned • The New Big Picture• The New New Big Picture – BAM !• SOA and BAM status• SOA Infrastructure Components – why they are important• Some examples• Buying / Consuming Software – why that changes

• Important to note we are still in the early days• This is a small slice of Motorola’s IT world … today

Page 4: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

Why Motorola is Investing in SOA

• It is faster, better, cheaper …because of standards-based reusable components

• Reuse drives down development costs exponentially over time

• Standards-based solutions (XML Web Services) across the layers, not just integration

• It uses a new way to develop prototypes using Business Process Mapping rather than the old spec approach to designing and prototyping

• Rapid application development with composite application tools

• Leverages existing solutions - does not replace them

• Gartner estimates that it is 63% more efficient & will be mainstream by 2005

Presentation Layer : Portals, Web Apps, Mobile Apps & Thick Clients

Orchestration Layer : Composite Applications , BPM and Workflow

Integration Layer : EII, EAI and Web Services

Data Layer : Systems of Record , Enterprise Applications and Data Systems

Business Logic Layer : Web Services-based Business Objects

Oracle SAP SQL i2 Compass

Order Customer Product Supplier Forecast

Page 5: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA Pilots: Lessons Learned

The Good: Business / IT Alignment & Re-use

• For IT teams – development using composite application tools allowed rapid delivery of projects

• For business teams – projects have been built top-down from existing processes, not from overly complex tech spec docs

• For both teams – projects delivered by IT were exactly what the business teams asked for, the first time

• Components built had re-use potential across the project, business group and enterprise

Page 6: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA Pilots: Lessons Learned

The Bad: Standards, Security, Performance, Visibility

• For the first few years, immature and incomplete standards slowed adoption

• Security concerns- loosely coupled architecture can introduce new security challenges

• Performance concerns caused by loosely coupling software components and bandwidth-intensive XML

• Without a web services directory (UDDI), any reusable components built had no visibility outside of the projects

Page 7: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA Pilots: Lessons Learned

The Ugly: The most pressing need to build an SOA infrastructure was Web Services Mgmt & Security

• Performance and availability monitoring

• Auditing, logging, and metering of transaction and performance data

• Security of web services and transactions

• Availability and Fault Tolerance of Web Services

• Intelligent Routing of Web Services traffic

• Interoperability between various enterprise platforms

• Provisioning, Subscriptions, Versioning and Services life-cycle operations

Page 8: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA Pilots: Lessons Learned

The Ugly: The most pressing need to build an SOA infrastructure was Web Services Mgmt & Security

• Start soon – long journey

• Start soon – technologically not complex on the surface but complicated to execute

• This is a big behavior change – serious change management needed

• Use an intervention change model

• Invest in communications / training

• Make process work and contextual understanding more important

• Understand the tipping points – re BPM

Page 9: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA – The New Big Picture

Page 10: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA & BAM – The New New Big Picture

Page 11: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA & BAM Current Status

SOA

• Over 180 services utilizing SOA framework with new project opportunities identified each week

• Refining SOA Architecture with maturing orchestration, nomenclature and governance guidelines

• Creating an ROI model

• Created SOA adoption strategy, guidelines, and best practices

Page 12: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA & BAM Current Status

BAM

• Over 175 BAM monitors deployed spanning:

– Siebel to Oracle

– Webchannel to Siebel

– Siebel to Oracle EAI integration

• Averaging over 50 rules per BAM project

• Two BAM projects near completion with multiple slated for later this year

Page 13: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA Infrastructure Components

• UDDI & Metadata Repository

• Web Service Management (WSM)

• Web Services Security (WSS)

• Web Services Governance

Page 14: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

Why is UDDI Important?

• Cornerstone of Service Oriented Architecture

• Drives down costs of new development efforts

• Drives web service adoption and increase developer productivity by allowing developers to search and reuse services

• Enables reduction in development time

• Provides developers with information on how to integrate with business processes

• Drives and enforces standards for organization and categorization of service assets

Page 15: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

Why is Web Services Mgmt. Important?

• Automatic provisioning of new services upon being published

• Template applications security and management policies and service level agreements based on the service’s category, business entity, etc.

• Finer grained authentication and authorization policies than available in UDDI alone

• … all transparent from the developer or consumer of the service

Page 16: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

Why is Web Services Security Important?

• Web services require message level security.

• Web services increase points of attack within a service oriented architecture

• Service to service authorization and authentication required

• Need for Identity management to secure complex web service applications

• Traditional firewalls cannot detect ‘malicious’ XML coming through port 80 or 443

Page 17: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA Examples – Business Services

• UDP Warrant Service– Determines customer warranty in real-time to

determine possible charges for repair

• UDP Data Services – Multiple Services from all regions utilizing UDP data

real-time

• Certificate Download service – Provisions users for downloads with their phone with

the appropriate security certificate

• WLAN Services – Base stations deployed in the field can auto register

and download security certificate

Page 18: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA Examples – Utility Services

• Directory Authentication– Provides single service to authenticate users against

LDAP directory

• Email and SMS Notifications– Provides multiple methods to send email and SMS

notifications through web applications and mobile clients

• Credit Card Validation (CyberSource)– Provides real-time credit card validation for online

orders.

Page 19: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

SOA Examples – Operational Solutions(construction time)

• Displays up-to-date Motorola Legal Entity data, relevant country & location information, and display entity financial information and reports within our portal environment by retrieving data from multiple, disparate systems of record.

MotDirectory(LDAP)

GRRO Portal

FTT

GRROServices

CountryService

GRROData

Law DeptCorporation

Manual

DirectoryService Currency

ConverterCIA WorldFactbook

InternetServices

Asia FacilitiesDatabase

ISO Codes(Country,

Currency, etc)

Netegrity

EmailService

SMTP

GRRO Application

Oracle GLCodes

Page 20: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

The role of Motorola IT

• What we were…– Support Infrastructure– Little perceived business value– Mountains of spaghetti– Noah’s Ark approach to software

• What we strive to be… (AND not OR)– Reduce costs– Promote Re-use– Reduce system complexity– Provide increased business value– Accelerate the speed of business– Expand the world of what’s possible– Enable Seamless mobility

Page 21: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

Consuming Software?

• Your vendors’ architectures

• Software as a service

• Real platform thinking

• Rearden Commerce…

• Standards are still evolving but we have critical mass

• ‘Small Agile’ kills ‘Big Slow’

– Big Agile is just scary…

Page 22: Motorola SOA Toby Redshaw Corporate VP - IT Strategy

Conclusion

• If you have not started you are in reverse• This is competitively important• Conceptually simple – but BIG change• Evolving space that is learning intensive• Build the infrastructure – avoid meta spaghetti• Change the way you buy and consume software • Get expert help…• Find partners / phone a friend

– (Rearden, Amberpoint, Reuters)