Is your Agency ready for open source SOA?
Upcoming SlideShare
Loading in...5
×
 

Is your Agency ready for open source SOA?

on

  • 705 views

 

Statistics

Views

Total Views
705
Views on SlideShare
703
Embed Views
2

Actions

Likes
1
Downloads
19
Comments
0

1 Embed 2

http://www.slideshare.net 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • IONA was founded in 1991 in Dublin, Ireland. We have a history of providing distributed, standards-based solutions to IT organizations with complex, heterogeneous computing environments and challenging integration problems. We have a proven record of industry leadership and continuous product improvement. We make software work together so our customers can make better decisions, run their businesses more efficiently and improve their business results. Our software products enable customers to modernize and streamline their IT environments while at the same time lowering total operating costs and ultimately achieving greater return on investment (ROI) on their existing and future IT investments. Our customers span the Global 2000 and operate in a wide variety of industries: Telecommunications: AT&T, Beijing Mobile, BellSouth, Cingular Wireless, Ericsson, Marconi, Motorola, Nokia, Nortel Networks, NTT DoCoMo, O2, Sprint, Verizon, Vodafone, and Wind SpA Financial Services: Credit Suisse Group, GAD, JPMorgan Chase, Lehman Brothers, Raymond James & Associates, Reuters, Sentenial, Winterthur Insurance Government: NASA, National Geospatial-Intelligence Agency, US Department of Transportation, US Environmental Protection Agency Manufacturing: Boeing, Ford Motor Company, Mitsubishi Heavy Industries, National Semiconductor, Schlumberger
  • Common agreement
  • Since the early 1990s, IONA has built its integration products around two very significant open industry standards, initially CORBA and more recently Web services, and a unifying approach to designing and implementing large-scale systems referred to as service-oriented architecture, or SOA. An industry leader in integration and SOA, IONA has the proven expertise to design a highly flexible, distributed SOA infrastructure for the Global 2000 using standardized components. IONA customers built the first generation of SOA with its standards-based CORBA technology in the 1990s. IONA has extended that heritage with its next generation enterprise service bus (ESB), Artix, and its leadership and involvement in a broad array of open source projects that enable the adoption of SOA. IONA's commitment to open source software is part of its 15-year heritage of solving the most complex integration problems by applying open, standards-based solutions. IONA recognizes the value of open source technology and is one of the only companies in the SOA infrastructure space that both actively develops closed source solutions and contributes to a wide range of open source projects. IONA understands that developers are the foundation of open source communities and that community participation drives innovation. IONA developers lead several open source SOA projects and actively participate in many others as committers. IONA makes it easier to use open source SOA infrastructure by integrating leading open source technologies into convenient packages that are fully tested and certified to work together.
  • Successful = viable, use, market share, performance, satisfaction Others: HTML, PCI Bus, Domain Name Service, software in early days of punch cards & magnetic core memory HTML - allows source code viewing of any and every page PCI (Peripheral Component Interconnect) is a local bus standard that is included in most modern PCs and Macintosh computers. The bus serves as a channel over which information flows between two or more devices. Domain Name service allows users to easily address the millions of computers on the Internet. Open Source - model of academia
  • Services in a SOA will be created in many fashions — some in Java, some in C#, and some in C or C++. Deploying these services as web services would be well suited for interoperability, as they are by nature heterogeneous, interoperable, and loosely coupled. However, when building end-user applications or high volume processes, web services may not be the best choice. Web services are expensive in both processing and bandwidth. On average, a web service invocation is 10 times larger than the binary form of such an object interaction. Using XML and SOAP requires huge chunks of bandwidth when dealing with large numbers of transactions, as both the SOAP transport and all data are passed as XML, which is expressed as raw text. BPEL, in theory, gets us closer to SOA today and has been a good way to link and assemble some business processes, although it is not an enterprise platform for deploying high volume custom business applications. BPEL is for orchestration only: it enables the calling of processes, but does not allow for new processes to be developed. It can be an optional layer of SOA, but BPEL alone will not deliver an SOA, as it relies entirely on Web services and XML. Some of the early problems with BPEL have been difficulty in adhering to standards. Considerable customization is required to implement BPEL. Standards are often lost in the process, and many of the services end up becoming proprietary solutions, thereby losing the ability to be quickly extensible as the business requirements change.
  • Should Government mandate Open Source? Probably not a good idea Amounts to failed Industrial Policy Level the playing field Open Standards, Open data formats Correct any market failure Then let the Market decide Best value for taxpayer money Based on reliability, security, interoperability, performance, ease-of-use, TCO and support
  • OSS can have lower licensing costs Taiwan, India, Europe, Japan, China reporting expected savings either directly or from increased competitive landscape Ability to audit code for “back-doors,” “spyware” or security holes Promotes architectural diversity Lowering risks of monoculture and cyberattacks Promotes innovation by unaffiliated developers experimenting with code Reduces dependence on single software producer
  • Enterprise architecture has to take a rational view of the incorporation of open-source within the enterprise and balance it with business value, risk and culture. Many Fortune 500s have no strategy surrounding use of open-source yet it is a pervasive part of their architecture today. The vast majority of company's have open source software in use in production environments, which may include Linux, Apache, JBoss and so on. Some will think of open-source software as being free in terms of cost of acquisition while others who have vision will come to realize that the potential of using open source as a model for software development will help them build better software faster and cheaper.
  • ESBs offer a number of features such as transactionality, security, routing, and reliable messaging. To ensure maximum interoperability between implementations, ESBs base many of their features on a set of standards that include: • WS-Addressing • WS-Atomic Transactions • WS-Coordination • WS-Security • WS-Reliable Messaging
  • On Monday, December 4 th , we will announce how IONA is expanding our leadership in Distributed SOA Infrastructure with the offering of three Open Source products First, we are offering Celtix Enterprise, our Open Source ESB Also, we are offering two of the components of Celtic Enterprise as individually offered products – Celtix Advanced Service Engine or Celtix ASE for short and Celtix Advanced Messaging Where open source, webservices and SOA meet.
  • In addition to the bundled Celtix Enterprise offering, we are offering two of the component technologies - Celtix Advanced Service Engine and Celtix Advanced Messaging – that can be installed and deployed separately. The Celtix Advanced Service Engine is a Certified Open Source Product Distribution that provides the high performance and flexible capability to create and deploy services using a standards-based, pluggable services framework. This product distribution is based on the Apache Incubator’s CXF project, which is an evolution of the ObjectWeb Celtix 1.0 and Codehaus XFire 1.2 projects. The core of Celtix Enterprise the Celtix Advanced Service Engine . Based on Apache Incubator CXF, the serviceengine contains all of the front-ends, message bindings, and transports that are used to implement a service.This component provides all of the hooks required to plug in different combinations of front-ends, bindings, and transports. It also provides hook to allow service to be plugged in to the lower layers of the ESB. Celtix Advanced Messaging is a certified open source product distribution that provides a platform for enterprise messaging. Celtix Advanced Messaging is an open source message broker that implements the AMQP standard for both the broker capabilities and the wire-level format for multi-channel, negotiated, asynchronous, and efficient integration. Celtix Advanced Messaging is based on the Apache Incubator Qpid project. Based on the AMQP open specification which is being developed by the AMQP Working Group including JP Morgan Chase, IONA, Cisco, RedHat and others.Capabilities include: Queue-based messaging Publish-subscribe Header-based routing
  • So what is Celtix Enterprise? Celtix Enterprise is an open source ESB that offers enterprise support for of a Distributed SOA Infrastructure. The Celtix Enterprise distribution is comprised of several leading open source SOA infrastructure projects that have been integrated, tested and certified by IONA. This functionality includes service enablement, messaging, routing, containers for deployment, and tooling derived from the Eclipse SOA Tools Platform project.
  • — Open-source software enables businesses to be much more agile, and an open-source service-oriented architecture enables both greater adaptability and agility, said James Strachan, chief architect and co-founder of LogicBlaze. ADVERTISEMENT Indeed, Strachan, who spoke at TheServerSide Java Symposium here on March 22, said an open-source SOA stack is attainable today for users who want to implement it. "Start today using open-source software ," Strachan said. "Use open-source services … when you need them in bite-sized chunks," he said. Strachan said an open-source SOA stack is available today in the form of a bunch of Apache Software Foundation offerings. Indeed, Strachan said enterprises can use ActiveMQ for messaging, Axis 2.0 for the SOAP (Simple Object Access Protocol) stack, a new Apache project called Ode as the orchestration engine, and ServiceMix as the ESB (Enterprise Service Bus). "Message-oriented middleware is a nice, easy way to start a service-oriented architecture," Strachan said. "Apache ActiveMQ is an open-source version of a message bus." Strachan said IBM's MQ Series is a competing commercial messaging solution, but it is costly and "may not be the easiest thing to install." In the SOAP stack space, Strachan said there are four competing solutions that address what he calls mediation: Apache Axis 2; Celtix from the ObjectWeb consortium; the Java API for XML Web Services (JAX-WS) specification from Sun Microsystems; and XFire from Codehaus. "These are the big four," Strachan said. Of the group, Strachan said he thinks Axis 2 is the furthest along. Apache Ode is an open-source orchestration engine based on two code donations: one from Sybase and another from Intalio that came from FiveSight Technologies, which Intalio acquired in December, Strachan said. Meanwhile, the ServiceMix ESB is an attractive option for several reasons, Strachan said, one of which is that it supports JBI (Java Business Integration ). "The world is not going to be all Web services; it's going to be everything so JBI has something called a binding that talks to all kinds of different things," he said. Click here to read more about the convergence of SOA, open source and Web services. In addition, ServiceMix has connectivity, smart routing, transformation, orchestration, platform support and a management stack. As the developer tooling options of choice, Strachan said he prefers the Eclipse integrated development environment, the Eclipse SOA Tools Platform Project and the Eclipse BPEL (Business Process Execution Language) Designer Project offerings. "My take is to just use Eclipse—sorry Sun," he said. Strachan advised developers to "write your business logic and services as POJOs [plain old Java objects], adding some metadata with annotations." Moreover, Strachan said XML marshaling, or serializing, is very important. Guru Jakob Nielsen offers advice on designing applications for usability. Click here to watch the video. "The biggest decision for SOAs is what tool you use for XML marshaling," Strachan said. He said his two favorite XML marshaling methods are Java Architecture for XML Binding, or JAXB, and Service Data Objects, or SDO. Meanwhile, the application programming models that can be used for an open-source SOA include: JSR 181, known as JSR 181: Web Services Metadata for the Java Platform, together with JAX-WS; the SCA (Service Component Architecture) and Apache Tuscany, which is based on SCA; Enterprise JavaBeans 3.0; and Spring remoting. "SCA deserves very close scrutiny," Strachan said. However, he added, "they're all sort of related."
  • A Celtix Enterprise ESB” shows an example of how you can combine the components to create an ESB. In this example, the service being implemented using JavaScript whose clients connect to it over JMS. The command line tools to are used to generate the starting point code. The JavaScript front-end provides the interface between the implementation and the layers that provide the connectivity. The service itself creates XML messages and connects to the network using HTTP. The router provides the bridge between the service's native message formats and the JMS broker. If you decided that your service did not need to be exposed over JMS you could remove both the router and the JMS broker. If you instead wanted to implement the service using JAX-WS APIs you could use the JAX-WS front-end.
  • A Celtix Enterprise ESB” shows an example of how you can combine the components to create an ESB. In this example, the service being implemented using JavaScript whose clients connect to it over JMS. The command line tools to are used to generate the starting point code. The JavaScript front-end provides the interface between the implementation and the layers that provide the connectivity. The service itself creates XML messages and connects to the network using HTTP. The router provides the bridge between the service's native message formats and the JMS broker. If you decided that your service did not need to be exposed over JMS you could remove both the router and the JMS broker. If you instead wanted to implement the service using JAX-WS APIs you could use the JAX-WS front-end . The Celtix Enterprise Runtime The Celtix Enterprise runtime consists of three components: • a service implementation • the Celtix Advanced Service Engine • a container Together these components form a running service endpoint. The service implementation is the logic that performs the functionality defined by a service contract. The service engine provides the abstraction layer that connects the implementation to the outside world. The container manages the resources needed by the service implementation and the service engine.
  • example, you could deploy an endpoint for a bank services to exchange SOAP messages and you could deploy a second endpoint for the same service that exchanged messages using native XML without the overhead of the SOAP envelope. You could also develop your own bindings to further expand Celtix Enterprise's capabilities.
  • In conclusion, Celtix Enterprise is here! We have reached a significant milestone in IONA’s history and we are poised to lead the market for distributed SOA infrastructure solutions.

Is your Agency ready for open source SOA? Is your Agency ready for open source SOA? Presentation Transcript

  • Is your Agency ready for open source SOA ? Eric Newcomer & Michelle Davis March 1, 2007
  • Eric Newcomer Chief 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
    • Contributor to SOA initiatives:
      • Co-submitter of SOAP and founding member of the XML Protocols Working Group at W3C
      • Co-Editor of the W3C Web Services Architecture specification
      • Co-author of WS-Transactions specifications & co-chair of OASIS WS-Transactions technical committee
      • Co-chair of OSGi Enterprise Expert Group
      • Eclipse Board member
    • Co-author of Principles of Transaction Processing (1997), author of Understanding Web Services (2002), co-author of Understanding SOA with Web Services (2004)
    SOA Book Now Available!
  • IONA at a Glance
    • 75% of Global Telecom
    • 80% of Financial Services in Global 100
    • Blue Chip System Integrator Partners
    • Founded in 1991
    • Publicly traded since 1997
    • Profitable business model
    Solid business with a history of profitable growth Customers include world’s largest firms NASDAQ: IONA
    • EMEA HQ in Dublin, Ireland
    • US HQ in Massachusetts
    • APAC HQ in Tokyo, Japan
    Proven Performance, Guaranteed ROI Worldwide presence
    • Strong heritage and experienced team
    • Unique, incremental approach to SOA
    • Distributed, standards-based software
    • Commercial, open source and consulting solutions
    • Measurable customer value
    View slide
  • The Promise of SOA…
    • Reduce IT expenses
      • Reuse existing application functionality
      • Improve developer productivity
    • Increase operational efficiency
      • Share data across departments, divisions
      • Automate common business processes
    • Develop new business opportunities
      • Provide new and better customer service
      • Respond to market changes
    • It’s the “IT assembly line”
      • And 75% or more come from existing applications!
    View slide
  • SOA is going mainstream
  • What does this mean?
    • Need for enterprise quality & performance
        • Mission-critical apps going to SOA
        • Govern IT assets as reusable services
    • Platform vendors extending their tools
        • Microsoft Vista includes SOA tools, runtime
        • Java vendors countering with SCA/SDO
        • But they are not reinventing them
    • The market needs a new approach
  • SOA Adoption Timeline Maturity Level SOA Experience 2006 2007 2008 2005 SOA Adoption Mainstream: No Need to Explain SOA Industry Adoption Assured Early Adoption Stage Positive Experiences Reported Beginning market: Lot of Evangelizing
  • Why open source for SOA?
    • Low cost of entry
    • SOA is a natural evolution of IT
        • Extends application servers, databases, messaging systems, ERPs etc.- already commoditizing
        • Improves existing applications through reusability
        • i.e. it is not about new applications from the ground up
    • Open source provides transparency
    • Opportunity for community innovation
    • Mixture of open and closed source typical
  • IONA Leadership – SOA and OSS
    • Distributed computing pioneers with CORBA
    • First to market with micro kernel architecture
    • Contributing actively to open source projects:
        • Eclipse SOA Tools Platform
        • Apache CXF
        • Apache Qpid
    • Delivering enterprise-class support for open source software
        • Celtix Enterprise
    • Industry leadership activities at W3C, OASIS, OSGi
  • Future direction for SOA
    • Service-enablement
    • Orchestration
    • Store and reuse
    • Manage service performance
    ESB Service Endpoints Consumers Contracts Config Policy Business Services Administrators CORBA / J2EE Systems JAVA / J2EE Systems MOM Based Systems Mainframe Transactions IONA IONA IONA IONA
  • IONA Confidential OPEN SOURCE SOA INFRASTRUCTURE
  • Today’s Government
    • Leaders expect to be able to move quickly , using all information appropriate to make effective choices that benefit constituents.
    • Infrastructure is not well suited to responding to the demands for responsive interconnectivity
    • Working across levels and branches of government is a complex and difficult undertaking that is further complicated by the governance and infrastructure that must exist to support it.
  • Why is Open Source Important?
    • Open source products are deeply embedded in the Government
      • Apache - Over 60% of the web pages on the world wide web are presented via Apache.*
      • TCP/IP - The underlying basis of the Internet; Its creation was funded by DoD.
      • Sendmail - moves mail from one machine to another; carries nearly 90% of e-mail traffic*
      • Linux - Unix-like operating system with over 18 million users.*** Widely used to support Apache, TCP/IP, and Sendmail services.
      • MySQL - relational database.
      • Perl - An open-source-only programing language that is widely used to make web pages “smarter”
    • Open source development is widespread and international
      • SourceForge.org - 77,000 projects and 804,000 registered users
  • Forrester’s definition: SOA
      • Applications are organized into business services that are (typically) network-accessible.
      • Service interface definitions are first-class development artifacts.
      • Quality of service characteristics are explicitly specified in the design.
      • Services are cataloged and discoverable by development tools and management tools.
      • Protocols are predominantly, but not exclusively, based on Web services.
    A style of design, deployment, and management of applications and software infrastructure in which:
  • SOA and Web Services
    • SOA does not need Web Services
    • Not every Web Service is based on SOA
    • BUT
    Through 2008, SOA and Web Services will be implemented together in more than 75 percent of new SOA or Web Services projects (0.7 probability)
  • Being a Service versus a Component
  • Open Source likely to be part of today’s software infrastructure
  • SOA adopters show affinity for Open Source infrastructure
  • How Services Make Applications Open
    • An agency can quickly adapt to new methods of communication
    Message Contract
    • New implementations can be added faster and more reliably in a SOA environment
    • New customers send messages based on an agreed contract between the producer and consumer
    • The implementation is independent of the producer which enables multiple views of information without impacting legacy applications
    Secure Business Applications Business Application Service Business Logic Interface Facade Producer XML Customizable Presentation Tier Consumer ?
  • SOA infrastructure can deliver information… Service life-cycle environment Application platforms and information sources … Enterprise service bus Service command platform Service clients Service interfaces Control Change Connection Core services Service metadata Information Services Business Services
  • An ESB is a common SOA foundation
    • An ESB is an intermediary that makes a set of reusable business services widely available.
    • Service Connection :
      • Multiple protocols and data formats
      • Application adapters
    • Service Mediation :
      • Routing, interaction models, version resolution
      • Transformation and mapping, message enrichment
    • Service Change and control :
      • Transactions
      • Security and quality of service
      • Service registry and metadata management
      • Service monitoring and management
    • Service Orchestration : Business process management and monitoring
  • Celtix Enterprise Making Headlines
    • IONA is expanding leadership in Distributed SOA infrastructure with open source
    • Celtix Enterprise
        • Open Source ESB
        • Basis for distributed SOA
    • Celtix Advanced Messaging
        • AMQP reference
        • implementation
    • Celtix Advanced Service Engine
        • Based on Apache CXF
    • Enterprise-class Services
    • and Support
  • The Celtix Offering Family (Detail)
    • Celtix Advanced Messaging
        • Based on Apache Qpid, AMQP reference implementation
        • Supports fire-and-forget, publish-subscribe, reliable message queuing
        • AMQP is an open on-the-wire protocol
    • Celtix Advanced Service Engine
        • Based on Apache CXF
        • Full JAX-WS 2.0 implementation
        • Supports Java and Javascript/E4X
        • SOAP or raw XML over HTTP, JMS, AMQP
    Celtix Advanced Messaging Routing Java, Javascript/E4X Eclipse STP, code generators, JMX Enabled Celtix Advanced Service Engine Tomcat, J2EE, JBI, Spring
  • Celtix Enterprise Components
    • Messaging
        • Celtix Advanced Messaging
        • ActiveMQ JMS
        • Routing
    • Containers
        • Tomcat
        • ServiceMix JBI container
        • Lightweight Spring-based Container
        • Supports J2EE
    • Celtix Advanced Service Engine
    • Eclipse tooling from the SOA Tools Platform (STP) project
  • Celtix Enterprise Functionality Support and warranty for source code
    • Tested & Certified with:
    • Operating Systems
    • Application Servers
    • Artix & Artix plug-ins
    Messaging Pluggable Services Framework User Experience, Management Lightweight Container Routing
  • Celtix Enterprise Open Source Components Support and warranty for source code
    • Tested & Certified with:
    • Operating Systems
    • Application Servers
    • Artix & Artix plug-ins
    Celtix Advanced Messaging (Qpid) Routing * Celtix Advanced Service Engine (CXF) SOA Tools Project, JMX Console, Rhino E4X Javascript ActiveMQ JBI Container (ServiceMix) Spring-based Container Servlet Container (Tomcat)
  • Artix and Celtix in a Distributed SOA JBI Container Network Celtix Celtix Celtix Artix Tomcat Container AMQP AMQP AMQP MQ AMQP AMQP Mainframe Spring-based Container
  • Celtix Advanced Messaging – Open Source Messaging Platform
    • Based on the AMQP open specification which is being developed by the AMQP Working Group including JP Morgan Chase, IONA, Cisco, RedHat and others.
    • Based on code from the Apache Incubator Qpid
    • open source project
    • Free 30 day support available from IONA
    • Consulting, training & support offerings from IONA
    • Capabilities include:
      • Queue-based messaging
      • Publish-subscribe
      • Header-based routing
  • Architecture
  • Celtix High-level Architecture
  • Celtix Enterprise – Another View
  • Think Big, Start Small, Scale Fast
  • Pluggability / Extensibility
    • Pluggable API for building transports and bindings
      • Supports combining any transport with any binding
    • Extensibility at all levels
      • Configuration
      • Component-specific WSDL extensions
  • WSDL Centric Architecture
    • Leverage WSDL concepts heavily
      • Applications w/o WSDL also supported
    • Support all WSDL semantics
      • Extensible message exchange patterns
      • Separation of logical and physical contracts
      • Define service and tie it to a binding
      • Apply QoS
    • Initially support WSDL 1.1
      • WSDL 2.0 (next release)
  • Bindings
    • Enables integration of Celtix with any type of message and data binding.
    • Comprises of two parts,
        • Message Binding Layer, which specifically deals with message aspects of the protocol.
        • Data Binding Layer, which specifically deals with data aspects like marshalling and un-marshalling.
    • Can utilize Apache Yoko to CORBA enable an endpoint. Using a CORBA binding enables you to do the following:
        • Develop JAX-WS clients that interacts directly with CORBA back end services.
        • Develop services that interact natively with CORBA clients.
        • Incrementally migrate CORBA services and clients to a WS implementation.
  • Transports
    • Enables integration of Celtix with any transport
      • Provides flexible framework that makes minimal assumptions about type of underlying transport
    • Partial list of supported transport features
      • One-way and two-way invocations
      • Synchronous and asynchronous invocations
      • Various threading models
  • Containers
    • Celtix Enterprise provides three runtime containers:
        • the Apache Incubator ServiceMix JBI container
        • the Tomcat 5. x servlet container
        • a lightweight Spring based container
    • Also supports the deployment of runtime components into J2EE containers such as JBoss.
    • The Celtix ASE product is capable of running Web services in a standalone mode.
  • Routing
    • Celtix Enterprise provides a routing intermediary. It has the following features:
        • transport switching
        • binding switching
        • content-based routing
        • operation-based routing
        • message transformation
    • You can also add orchestration and other advanced features to Celtix Enterprise using intermediaries.
  • Tooling
    • Code generators
      • wsdl2java, java2wsdl, xsd2wsdl, wsdl2service, wsdl2soap
    • schemavalidator
      • For validating schemata
    • Other…..
      • JAXB generators from JAXB reference implementation
    • GUI Tools to be provided by STP
      • Most Notably Eclipse Development Environment Support for Standard JMX Consoles
      • endpoints instrumented with Java Management Extensions (JMX) and provides support for any SOA management console that supports JMX.
  • Environment
    • JSE 5
        • Annotations, Generics, Concurrency etc.
    • JAXB 2.0
        • Map XML schema to annotated Java classes
    • JAXWS 2.0
        • Map annotated Java classes to WSDL (and the other way around)
        • Public sync/async invocation API, handler API, etc
  • Are you Ready for OpenSource SOA? Celtix Applicability
  • Use Cases
    • Basic JAX-WS Service Creation
        • The GUI tools provide JAX-WS compliant code from WSDL contracts and help you develop applications using it. The GUI tools also provide a mechanism for generating a JAX-WS service from a Java object.
    • Reliable Messaging Delivery
        • AMQP
        • Reliable Messaging (WS-RM)
        • ActiveMQ JMS
    • Deploying Smart Endpoints
        • Has all of the functionality to send and receive messages as specified by the service's contract.
        • It does not rely on a central server and is more flexible in terms of resources and deployment options.
        • Service's built with Celtix Enterprise can be deployed as standalone processes that are completely autonomous.
  • Use Cases (Cont)
    • Web Service Enabling of Legacy Systems
        • Celtix can assist you in adding the needed JAX-WS annotations to your objects
        • It will then generate the WSDL which defines the newly created service. Once your Java code is annotated and the WSDL is generated, you can deploy the code as a service using any of the containers supported by Celtix Enterprise.
    • JAX-WS SOAP Stack in alternative containers
      • Deploying Inferno service as a web application inside Tomcat container, deploying services with Spring, deploying services on Geronimo.
    • JBI Integration
      • ServiceMix amongst others (OpenESB)
  • Use Cases (Cont)
    • Web 2.0 and JavaScript Support
        • Integration with AJAX, php, and other scripting languages.
        • Celtix Enterprise has a JavaScript front-end that allows you to write services and consumers using either JavaScript or E4X.
  • CELTIX Features Recap
    • JAX-WS 2.0
    • Bindings: SOAP 1.1, XML
    • Transports: HTTP, JMS
    • WS-Addressing, WS-Reliable Messaging
    • Instrumentation & JMX Management
    • JBI Support
    • SCA Integration with Tuscany
    • J2EE Integration with Geronimo and JOnAS
    • Routing
  • Celtix Enterprise is here!