Enterprise Software Productivity

1
Enterprise SoftwareProductivity

• Eric Newcomer, CTO
• IONA Technologies

2
Eric NewcomerChief Technology Officer, IONA
Technologies

• Joined IONA in November 1999, after 16 years at
  Digital/Compaq, mostly in DB and TP
• Responsible for IONA's technology and standards
  strategies
• Involved in Web services from the beginning
• Co-submitter of SOAP and founder of the XML
  Protocols Working Group at W3C
• Editor of the W3C Web Services Architecture
  specification
• Co-author and editor of the Web Services
  Composite Application Framework (WS-CAF) at OASIS
  
• Co-author of WS-Transactions specifications
  co-chair of OASIS WS-Transactions technical
  committee
• Co-author of Principles of Transaction Processing
  (1997), author of Understanding Web Services
  (2002), co-author of Understanding SOA with Web
  Services (2004)

3
at a glance
Solid business with a history of profitable growth
Customers include worlds largest firms

• 80 of Global Telecom
• 70 of Financial Services in Global 100
• Blue Chip System Integrator Partners

• Founded in 1991
• Publicly traded since 1997
• 50 million cash on hand
• No debt

NASDAQIONA
Our Approach Making Software Work Together

• Deliver high performance integration software for
  mission critical applications
• Make heterogeneity an asset, not a liability
• Deliver on the value proposition of standards

Worldwide presence

• EMEA HQ in Dublin, Ireland
• US HQ in Massachusetts
• APAC HQ in Tokyo, Japan

4
Software is a craft industry

• Relying on the skills of individuals
• Creating applications one by one
• Stitching integration solutions by hand
• Labor the biggest cost

5
Software needs mass production
6
How can this be accomplished?
Very simple answer but The industry has been
trying unsuccessfully for years The answer is
standardization
Standard Application Programming Interface WSDL
Standard Network Interconnect Protocol SOAP
Application Service
Underlying Platform
Network
7
Learning from the Success of the Web

• Human to computer interactions resolved
• Standards in place for programming (HTML) and
  interoperability (HTTP)
• Highly productive, low cost
• Software added at the network endpoints

8
Web of Services Not Yet Complete

• Industry and business requirements not yet met
• What needs to happen to make this a reality?
• How can we apply lessons from the Web?
• To improve software inside the company or between
  companies

CICS
IMS
C, C, COBOL, PL/I, Java, C
9
Pioneer of SOA

• 1500 services in production
• 100,000 users
• 1B txns/year, 5M/day
• 73 cost reduction for systems development and
  integration
• Reuse of 70 of services
• Secure / Reliable
• Proves it works

10
SOA Is Technology Neutral
Home Grown
MQSeries

• Architecting SOA has historically meant
  trade-offs
• CORBA Well defined contracts, Auto-generate
  proxies/skeletons, Multi-language bindings, Open
  standard, Enterprise QoS out of the box, CORBA
  required at both ends
• MQ Low coupling, Enterprise QoS, Not designed
  as a service platform, Proprietary
• J2EE No contract language, Uni-lingual, Open
  standard, Enterprise QoS, Large developer
  community, Java required at both ends
• HomeGrown Have it your way, Ranges from
  Useless to Comprehensive, Always expensive

Web services and SOA Infrastructure have emerged
to address these issues
11
WSDL as the Unifying Standard
CORBA IDL
WSDL

• Extensibility
• Handles Both Internet and Existing Networks
• Strong Developer Interest / Multi-vendor support
• Designed for multi protocol, multi data

Interface
PortType
Method
Operation
Logical Contract
in/out/inout
Message
Parameter
Part
Class/Type
XML Data Type
IIOP (not in IDL)
Binding
Physical Contract
Port
Service
WSDL - Web Services Definition Language
Home Grown
MQSeries
12
Add services to the endpoints

• Where applications need to share data
• Use service enablement
• Reuse existing data formats and communication
  protocols
• Then bridge qualities of service
• Security
• Transactions
• Reliability
• Availability

CICS
IMS
13
Endpoint Oriented Infrastructure
Fully DistributedArchitecture
Standardize on Service Interactions

• Lower cost of entry
• Faster time to ROI
• Adaptable infrastructure

• Services reside within applications
• Endpoints are configurable
• Endpoints are dynamic

14
Enterprise Qualities of Service
.NET Client
Java Client
Mobile Device
Reliability Services
Systems Management
Transaction Services
H/A Services
Directory Services
Security Services
C
Java Server
CORBA Server
C Server
Mainframe
15
Broad Platform Support
16
Leave and Layer Existing Applications

• Leave existing assets in place and include them
  as part of a SOA
• Eliminates the disruption and upfront costs
• Allows organizations to move forward and benefit
  from the efficiency and agility of a SOA

Multi-Protocol Compatibility
Distributed Services
WSDL
WSDL
WSDL
WSDL
WSDL
WSDL
J2EE or.NETServices
CeltixServices
COTSServices
Application Endpoints
17
Example Standalone Switch
Eclipse Designer
Design Time
Runtime
Other ESB
Artix Intermediary Switch
18
Example Co-Located Switch
Eclipse Designer
Design Time
Runtime
Other ESB
Artix Co-Located
19
Example Generic Web Services
Eclipse Designer
Design Time
Runtime
Artix Intermediary Switch(Can also be co-located)
Web Services
20
Industry and Open Source Initiatives

• Complete Web Services standardization
• E.g. WS-Policy, WS-Transactions
• Service Component Architecture (SCA)
• Java Business Integration (JBI)
• Developer tooling with Eclipse SOA Tools Project
• Support open source projects for SOA
• Celtix
• Geronimo
• ActiveMQ

21
Future Directions Moving SOA into the Network
SOA Tools Project
SOA Business Store
Service Intermediaries
DataServices
BusinessProcesses
CompositeServices
ManagementServices
Services
BusinessServices
Policy
Meta Data Model
Config
Contracts
Repository
22
Summary
SOA
XML/ Web Services
Productivity
Supported By