Embed Size (px)
DESCRIPTION
Full session information and video available on successforce.com.
Citation preview
Developing an SOA Strategy
Cindy L. Warner, salesforce.com
David Linthicum, Linthicum Group
IT Exec: Chief Innovation Officer
Safe Harbor Statement
“Safe harbor” statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements including but not limited to statements concerning the potential market for our existing service offerings and future offerings. All of our forward looking statements involve risks, uncertainties and assumptions. If any such risks or uncertainties materialize or if any of the assumptions proves incorrect, our results could differ materially from the results expressed or implied by the forward-looking statements we make.
The risks and uncertainties referred to above include - but are not limited to - risks associated with possible fluctuations in our operating results and cash flows, rate of growth and anticipated revenue run rate, errors, interruptions or delays in our service or our Web hosting, our new business model, our history of operating losses, the possibility that we will not remain profitable, breach of our security measures, the emerging market in which we operate, our relatively limited operating history, our ability to hire, retain and motivate our employees and manage our growth, competition, our ability to continue to release and gain customer acceptance of new and improved versions of our service, customer and partner acceptance of the AppExchange, successful customer deployment and utilization of our services, unanticipated changes in our effective tax rate, fluctuations in the number of shares outstanding, the price of such shares, foreign currency exchange rates and interest rates.
Further information on these and other factors that could affect our financial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other filings we make with the Securities and Exchange Commission from time to time. These documents are available on the SEC Filings section of the Investor Information section of our website at www.salesforce.com/investor. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements, except as required by law.
Cindy L. Warner
SVP, Global Technology Services
salesforce.com
David S. Linthicum
SOA Thought Leader and Practitioner
All About The Linthicum, LLC
• INDUSTRY: Consulting
• EMPLOYEES: 6
• GEOGRAPHY: Global
• # USERS: 200
• PRODUCT(S) USED: Apex, Salesforce SOA, and
The Linthicum Group was established to provide quality SOA consulting services to product or end-user organizations who are seeking guidance beyond the SOA hype. The group seeks to understand your requirements first, and then define the correct solution to meet the particular needs of your organization. We leverage proven approaches and methodologies, using industry best practices.
The Challenge…
… but even after yesterday’s promises…
Copyright © 2007, ZapThink, LLC
… we still have the same IT mess, only worse
Companies require Business Agility…
Responding quickly to change, and
Leveraging change for competitive advantage
J
Why does a business need an SOA Strategy?
Agility is the key to innovationAgility is the key to innovation
Service Orientation: A Business Approach
It’s not about connecting things, it’s
about enabling business processes
& continual change
The core business motivation is
business agility
Rather than “rip and replace” old
systems – make them work better
together
It’s not about technology,
integration, or middleware
So What Does a SaaS SOA Strategy Entail?
David S. Linthicum
SOA Thought Leader and Practitioner
Core tenants of an SOA Strategy…
SOA is architecture – a set of best practices for the organization and use of IT, and the discipline to follow them
Abstracts software functionality as loosely-coupled, business-oriented Services
Services can be composed into applications which implement business processes in a flexible way, without programming
Just as a building architect is more concerned with the space, not the walls, the IT architect is concerned with how people use the
technology, not the technology itself
12
…which enable…
Leveraging of legacy systems – SOA does not mandate replacement of runtime infrastructure, but enable migration when needed
Metadata to control how the system behaves instead of code – business logic trumps application logic
The contracted interface to matter most, not the underlying runtime environment
SOA shifts the way we think
Traditional Distributed Approach
Service Oriented Approach
Designed to last Designed to change
Tightly Coupled Loosely Coupled, Agile and Adaptive
Integrate Silos Compose Services
Code Oriented Metadata Oriented
Long development cycle Interactive and iterative development
Middleware makes it work Architecture makes it work
Favor Homogeneous Technology Leverage Heterogeneous Technology
Emerging Web-Delivered Platform…a catalyst for change
We are moving in three clear directions: First, the movement from visual to service-
based interfaces
Second, the movement to outsourced or
virtualized business processes
Finally, the acceptance of an on-demand
platform for applications, services, and now
development and enterprise architecture
Advantages of a Web-Delivered Platform as part of an SOA Strategy While clearly a huge leap in thinking for many traditional developers
and architects, the use of an on-demand platforms makes logical
sense when considering the advantages of this model, including: The cost of the platform is always going to be less expensive than more
traditional platforms, and also provide more value.
The shareable nature of this platform allows designers, developers, and
architects to leverage best practices, reusing existing design, code,
configurations, metadata, and application architectures.
Services deployed on this platform are immediately sharable, intra- or
inter-enterprise, for any business purpose, including B2B partner
integration.
Services may be layered into an orchestration mechanism or process
layer for configuration into solutions.
16
Externally Managed Systems
Internal Systems
External Trading Partners
Internal Systems
Normalizing Authentication
Identity and Single Sign-On
Protocol TranslationSession ManagementData Format Mapping
TranslationError Handling
Integration MonitoringSystems Management
Business Process Workflow
Business Activity Monitoring
Service Providers
Service Providers
Approaching Integration UsingSaaS-Delivered SOA
17
Inside the Enterprise Outside the Enterprise
Integrating Applications, Services and Content
EnterpriseSystems
On DemandApplications &
Business Services
On Demand Content
DesktopApplications
18
Traditional Integration Approach• Costly to build, deploy and maintain• Complex, hard to change, doesn’t scale• Lengthy implementation
Different protocols
Different standards
Different data formatsFirewall issues
Multiple point-to-point connections
Multiple business rulesDifferent security models
Different applications
19
SaaS Delivered SOA Solves the Need for Shared Infrastructure
Simplifies the many to
many problem
Moves complexity to the
network
Increase value by
providing shared
infrastructure & services
Mediates technical and
business differences
20
System
System
The Basic Architecture
Web DeliveredSOA
21
Getting Ready
First, accept the notion that it's okay to leverage services that are hosted on the Internet as part of your SOA. Normal security management needs to apply, of course.
Second, create a strategy for the consumption and management of outside-in services, and use of a Web-delivered SOA, including how you'll deal with semantic management, security, transactions, etc.
Finally, create a proof of concept now. This does a few things including getting you through the initial learning process and providing proof points as to the feasibility of leveraging outside-in services.
22
B2B Exchange
Distributor
ServiceProvider
Partner
ServiceProvider
Web Services
Web DeliveredSOA
• Abstract back-end functions, screens, and data stores and expose them as services
• Mediate semantics through a transformation and routing layer
• Mediate security, accounting for the difference within the source and target systems
• Structure information for movement to and from the service provider
Existing Systems
What Needs to be Done
23
Remember, there are a few technical issues that you must address… Semantic and metadata management, or, the management of the
different information representations amount the external services and internal systems.
Transformation and routing, or, accounting for those data differences during run time.
Governance across all systems, meaning, not giving up the notion of security and control when extending your SOA to the global SOA.
Discovery and service management, meaning, how to find and leverage services inside or outside of your enterprise, and how to keep track of those services through their maturation.
Information consumption, processing, and delivery, or, how to effectively move information to and from all interested systems.
Connectivity and adapter management, or, how to externalize and internalize information and services from very old and proprietary systems.
Process orchestration and service, and process abstraction, or, the ability to abstract the services and information flows into bound processes, thus creating a solution
Approaching SOA Using an On-Demand Platform
Step 1: Accessing Current Enterprise
Architecture Issues
Step 2: Making the Business Case
Step 3: Understanding Semantics
Step 4: Understanding Services
Step 5: Understanding Processes
Step 6: Understanding the Technology
Step 7: Execution and Assessment
Starwood Hotels & Resorts
Let’s Review a Successful SOA Case Study..
Background
One of the world’s largest hotel and leisure
companies, brands include Sheraton, Westin, W
Over 730 owned, leased, managed and franchised
hotels
Centralized controls required to eliminate
redundancy
Speed and accessibility of applications are
increasingly important
SOA Environment
For four years, Starwood has been converting its IT environment to SOA
Core centralized reservation system remains a legacy mainframe-based application Unites geographically diverse holdings onto one
flexible, scalable framework Handle the traffic spikes & massive server loads in
hospitality business
IT department now needs to manage a large and growing set of Services
SOA Project Scope
Centralize its reservation system into one core
application
Allow for customization at the property level
Accessibility for all of its partnering travel agents
Technical Requirements
Flexibility & Speed Standards-based, platform independent, fast
environment Governance
Centralization, control and measurement features Customizability
Each hotel chain had different customization needs Reuse
Allow Services to be recognized and optimized for reuse
Compatibility Allow partnering travel agents to easily access and
use the reservations system
Deployment Summary
Phase 1 A small, project-based implementation in a central IT
location. Goal: set up a viable system, test it, & learn the new architecture
Phase 2 Learn the new features and capabilities for
governance & customization Phase 3
Train people across the company on the new features, functions, systems, and processes
Phase 4 Rollout to all 730 hotels
Technology Selections
HP Systinet Registry for capturing detailed SOA service
description & usage information into a centrally
managed, reliable, searchable business Services
registry
Progress Actional SOAPstation XML routing &
monitoring tool and Looking Glass Server management
console
Move from their legacy system to UNIX platforms on
HP-UX and Linux
Anticipated Benefits
Return On Investment (ROI) Reduce operating costs by $20 million annually
Governance Centralized controls for managing, tracking and
enforcing its processes Customization
Customization on the local level Easy Partner Accessibility
Platform independent solution that Starwood partners can easily access, regardless of their IT environment.
On-Demand Platform…the Future of SOA
While this is a huge step in the world of SOA, the value and fit to purpose are
clear when considering the core notions.
Truth-be-told, enterprise architectures today are in a state of disarray, and
are actually hindering the growth of the business, this due to years and
years of layering in expensive, static, and monolithic applications that have
hindered business agility, costing millions of dollars over the years.
The notion of an SOA leveraging an on-demand platform provides key
technology and business drivers that make this approach compelling for
enterprises both large and small.
This provides the enterprise architects with the ability to migrate over to the
on-demand platform, as needed, and without disrupting existing enterprise
IT operations.
The more processes, data, applications, and services moved to the on-
demand platform, the more value the enterprise will realize over time.
Session FeedbackLet us know how we’re doing!
Please score the session from 5 to 1 (5=excellent,1=needs improvement) in the following categories:
Overall rating of the session Quality of content Strength of presentation delivery Relevance of the session to your organization
We strive to improve, thank you for filling out our survey.
Additionally, please score each individual speaker on: Overall delivery of session
Cindy Warner
SVP, Global Technology Services
David S. Linthicum
SOA Thought Leader and Practitioner
QUESTION & ANSWER SESSION
salesforce.com
