Artix 4.0

1
Artix 4.0

• Think Big.
• Start Small.
• Scale Fast.

2
IONA and Artix in 2005

• Launched 3.0
• Open Source Celtix
• Eclipse STP
• Thought leadership with JBI and SCA
• Artix Customers
• 50 Total Customers, 29 New Customers in 2005
• Focus on Telecom Vertical Has Been Successful
• Expanding Partner Ecosystem
• Satyam, Wipro, CSC, Bearing Point, Sun
  Microsystems, NEC,
• Artix Revenue Growth 120 Year Over Year
• Artix is 20 of IONAs Revenue and Growing

3
Today Artix 4.0

• Artix Capabilities continuing to promote
• Generate Greater ROI
• Decrease Operating Costs
• Streamline IT to Be More Responsive to Changing
  Business Needs
• New Features
• Service Orchestration
• Reliable Messaging
• Data Services
• New Mainframe Capabilities Including Unified UI

4
Customer MandateWhat Customers are Telling IONA

• I invested significantly in software over the
  past 10 years and didnt get my moneys worth. I
  require a greater ROI on my existing and future
  IT assets and investments
• I need to offer my clients and customers new
  products and services while driving down my
  annual IT operating costs
• I have to modernize and streamline my IT
  environments to make them more agile without
  ripping out and replacing my existing mission
  critical systems

5
What is Artix, Why it can help

• Artix is an ESB.
• So what? What's the difference?
• Artix is
• Light weight
• High performance
• Extensible
• How light weight is light weight?
• How High Performance is High Performance?
• How extensible is extensible?

6
Light, Fast, and Extensible

• Less is More!
• Memory usage as small as 20M-30M
• 3x to 4x Faster
• compared to EAI/J2EE Adapters
• All features are plug-ins
• Load only the features you need, buy only the
  features you need
• Message Format
• Routing
• Transport
• Transformation

7
Plug-in Architecture/Multi-channel
8
Before Artix - Server-centric, Hub-based
9
After Artix Supporting Diversity
10
But Why is distributed better than Hub?

• EAI vendors promoted the hub approach for
  integration
• Because it "looks" cleaner on paper
• But if you think about it more, it does not make
  sense
• Why did we get away from mainframe to network
  (and then internet) computing?
• Why did we changed from client-server to P2P,
  grid computing
• Answer Distributed is more efficient, low cost
  then centralized computing

11
Still not convinced?

• Michael Herr, IT Director of Deutsche Post,
  envisions SOA as "City Planning"
• Let's look at a real world comparison between Hub
  vs. Distributed Architecture

12
City Planning, a real world example
Paris
Vancouver
13
Fully Distributed Approach

• Distributed Standards-Based Approach Provides 3
  Key Benefits. Artix is
• Technology-Neutral
• Use any messaging system or protocol
• Employ best-of-breed solutions from different
  vendors
• For Incremental SOA Adoption
• Technical Service-enable existing systems one at
  a time
• Economic Pay as you grow, buy just what you
  need when you need it
• Dynamic Adaptable
• Change endpoint functionality in-place
• Add features when theyre needed

14
Product Principles Address Customer Need
Customer Mandate
Lower IT Operating Costs
Streamline Modernize
Increase ROI
Fully Distributed Approach
Dynamic Adaptable
Incremental SOA Adoption
Technology-Neutral
15
New Features in 4.0
16
Service Orchestration

• What One service from many

17
Service Orchestration BPEL Artix Integration

• Who discussing versioning or refactoring,
  code-free. Sometimes confused with BPM
• Value Reduces costs to assemble composite
  services (save 4 figures / service), eases
  repartitioning with BPM, decreases capacity
  requirements for hubs (save 6 figures)
• End result allows greater set of use cases to be
  end-point oriented with superior QoS no coding

18
Reliable Messaging

• What Guaranteed message delivery

19
Reliable Messaging

• Who customers emphasizing loose coupling between
  endpoints
• Value eliminate license fees otherwise paid to
  IBM, Tibco, or Sonic (save 4-5 figures / CPU),
  saves additional administration costs (4 figures
  / CPU)
• End result Use built-in JMS or WS-RM to get away
  from relying on MOM's proprietary protocols
• Things to note
• JMS standardizes the API and the capabilities,
  not the wire protocol
• WS-ReliableMessaging standardizes the wire
  protocol, not the API we ship our own engine

20
Data Services

• What Present databases as services

21
Data Services

• Cues wants code-free solution for DB apps
• Value
• Cost to develop, test, and maintain service
  enablement (4 figures/service)
• Eliminates cost for database upgrades needed to
  get service enablement (save 4 - 5 figures / CPU)
  plus other costs and politics
• End result Make your most valuable data assets
  more accessible and useful Visually define
  database connectivity without code

22
Web Services Management

• What Monitoring and Policy Enforcement for Web
  Services

23
Web Services Management

• Cues IT Governance and SLA concerns
• Value Eliminates cost to hand-tool SLA and
  address Compliance concerns
• End result Different levels of Management
  Strategy (next slide)
• Things to Note
• We provide plugins for policy enforcement and
  basic management console
• Partnering with AmberPoint (Nano Agent)

24
The Artix Management Story

• Enterprise
• Managing the Enterprise through Artix plug-ins
  that connect to BMC Patrol, Tivioli, HP OpenView
• Web Services
• SOA Management through Partnership with
  AmberPoint and support for CA-WSDM
• Support for Developer
• Eclipse Management Console for low level
  Lifecycle management of Artix Container and
  Services
• JMX Instrumented Artix Services - interestingly
  JMX is being adopted by major EMS vendors

25
Artix 4.0 - new levels of QOS

• Massive increases in Performance since 3.0
• Transport Neutrality with WS-Addressing
• Connect SOAP, MQ, TUXEDO, JMS, CORBA together
  using W3C Standard
• Required for WS-ReliableMessaging - also in 4.0
• Service Lifecycle and Performance Monitoring
• Artix Management Console
• JMX Instrumentation for Artix Services and
  Endpoints
• Transaction Enhancements
• designed to be compatible with a variety of
  different underlying transaction systems
• FTP Transport
• Major IT systems still rely on Batch Processing
  using FTP
• Artix Security Advanced
• hides the complexity of using 3rd party backend
  Security systems e.g. JAAS, RACF, TLS, HTTPS,
  Kerberos, Microsoft Active Directory

26
Improved Support for z/OS

• Customers want to leverage their existing
  mainframe PL/I, CICS and IMS services, via
  SOAP/HTTP or SOAP/MQ
• IONA has the expertise to service-enable
  mainframes in a secure and extensible way
• Promotes use of mainframe assets as equal
  citizens in SOA and expands customer ability to
  take holistic view of SOA
• Common tooling and no requirement to change
  existing applications

27
Commitment to Standards

• Successfully demonstrated Artix at the Microsoft
  Windows Communication Foundation
  Interoperability Plug-Fest (March 2006)
• Only vendor with working WS-AtomicTransactions
• Completed the BEA Validation Program, fully
  demonstrating the ability to inter-operate with
  BEA's Weblogic 9.0 and AquaLogic Service Bus 2.1.
  
• Connects AquaLogic to CICS and IMS-based
  mainframe environments

28
Feature Summary (Partial)

• Payload Format Support
• SOAP (with attachments)
• CORBA
• XML
• Fixed record length
• FML
• TibMsg
• Tagged

• Transport Support
• JMS and WS-RM included
• HTTP(S)
• IIOP(S)
• FTP Transport
• IBM WebSphere MQ
• TIBCO RendezvousTM
• BEA TuxedoTM

• Enterprise Capabilities
• BPEL orchestration
• Data services
• Routing
• High availability failover
• Transactions (WS-AT/C)
• WS-Addressing support

• Platform Interoperability
• BEA WebLogicTM
• IBM WebSphere
• JBoss
• Microsoft .NET (server and client)
• IONA Orbix
• BEA TuxedoTM
• IBM CICS/IMS

29
IONAs Open Source Strategy

• Change the Market Dynamics
• Drive the adoption of SOA projectsand
  Infrastructure
• Create demand for our commercial offerings
• Disrupt established competition
• Partner with Established Leaders
• Object Web the leader in open source middleware
  
• Eclipse Foundation the leader in open source
  tooling
• IONA will take a strategic role in both these
  communities

30
Open Source SOA Tools

• SOA Tools Platform Project (STP) is an open
  source tooling project, that will tool
• Artix / Celtix, the SOA System / Network
• and the next generation of SOA infrastructure
• IONA leads SOA tools platform project
• STP unifies the vendors in the SOA market making
  it possible to have an eco-system of
  interoperable SOA services
• IONA will be in the front and centre of the SOA
  System/ Network fabric

among others
31
The SOA Backplane
Life Cycle Management Tools
Development Tools
Registry
Security
Management
Adapters
Policies
Orchestration
Mediation/ Transformation
Routing/ Addressing
Extensibility Framework
QOS
Naming
Communication (SOAP, IIOP, JMS, MOM, RPC, ORB,
TPM)
Common Features
Advanced Features
Minimal Features