Approach_to_SOA

Document Sample
Approach_to_SOA Powered By Docstoc
					1

The IONA Approach to SOA
Distributed SOA Infrastructure
IONA Technologies, July 2007

2

Executive Summary
Global 2000 companies are increasingly taking advantage of new technologies to develop a service-oriented architecture (SOA) in an effort to create an agile IT infrastructure to more quickly respond to changing business needs. As with most new technologies or computing models, confusion abounds around how to best design and deploy an SOA, and in what order to adopt key technologies needed for SOA enablement. Many vendors package and price their SOA-related offerings to promote SOA design and deployment as a linear adoption process requiring a substantial upfront investment coupled with expensive pieces of technology deployed in a successive fashion. In reality, building an SOA is an iterative process where core SOA infrastructure components are deployed in many combinations, to many degrees. IONA’s heritage and experience working with companies to build SOAs - including the world’s largest and earliest SOA deployment at Credit Suisse - has given IONA a unique perspective on the realities of SOA design and deployment. Our experience has led us to offer a more flexible approach, driven by key product attributes found in IONA Artix, our advanced suite of SOA infrastructure products. IONA Artix enables the creation of a technology-neutral, distributed, dynamic and adaptable computing environment that creates unparalleled business agility. These attributes are unique to IONA, and drive IONA’s flexible approach to SOA deployment. With IONA’s approach to SOA, organizations can: Mix and match infrastructure components, using as much or as little as they need. Choose products that not only work together, but also interoperate with other technologies in which an organization has previously invested, or plans to utilize in the future. Leverage IONA’s pay-as-you-go pricing model so they can think big, incorporating pieces of several products early in the process, with the ability to layer additional capabilities over time. Pay only for what they use, allowing for an incremental approach to SOA adoption. This document describes the benefits of IONA’s unique approach, the key product attributes that make this approach possible, and the core products organizations can leverage for SOA success. With flexible deployment options, pricing and the ability for incremental adoption, organizations can progress at their own pace, reducing the risks often associated with software implementation. They can avoid vendor lock-in, and make it easier to adapt to new technologies and changing business requirements in the future.

3

A New Approach to SOA
SOA Flexibility
Many SOA vendors today require that customers purchase an entire stack of solutions for SOA enablement. Implementation of all technology products are required to power the SOA, and sometimes the purchase of the stack is required up front. While there may be some advantages to doing this such as the simplicity of dealing with one vendor for all your technology needs, the negatives far outweigh the positives. The speed of technological innovation over the last decade has been astounding, and it shows no signs of slowing down. No single vendor can possibly keep up with the pace of technological development and many companies are haunted by the time and cost associated with “ripping and replacing” technologies that have run their course. There are many vendors trying to offer all the solutions needed for SOA enablement. With time, this approach creates vendor lock-in, and companies choosing this route will pay the price when their investments restrict their ability to adapt to new technologies in the future.

There is another way.
New technologies provide companies with a way to not only future-proof their new SOA, but to leverage past technology investments. These lightweight, distributed technologies allow disparate software to work together and enable companies to achieve superior performance and flexibility. These technologies reduce the risks associated with technology investments, and allow organizations to take advantage of new, innovative technologies down the road. IONA offers a comprehensive suite of SOA enablement products, available as commercial offerings or from carefully chosen partners. These products exhibit the key characteristics an organization can utilize to design and deploy a flexible SOA. Because IONA believes in the utmost flexibility in SOA deployment, these products can be used together, separately, or with other existing software products within your organization. IONA offers organizations options for SOA deployment - they can purchase what they need, when they need it, creating the greatest flexibility in SOA deployment. In short, IONA enables companies to take a true best-of-breed approach to SOA.

SOA at Your Own Pace: Incremental Adoption
Many vendors force organizations to make big up-front investments in their SOA infrastructure solutions, and often require one product to be deployed before another product will function correctly. These large projects take time, destabilize the IT environment, affect time-to-market and don’t align with the realities of SOA design and deployment. SOA requirements for most organizations are unique. In some cases, an organization is already using a registry to keep track of its services, but struggling with service-enablement to populate that registry. Another organization might have service–enabled multiple systems but lacks the ability to organize, search for and reuse those services. Most organizations evaluating or actively involved in SOA design and deployment today would prefer to mix and match components that fit their unique requirements. These same

4

organizations would also prefer to adopt each component incrementally, rather than shut down their IT environment to install a stack of software across the enterprise. Even for solutions an organization can adopt in phases, vendors require the full capital expenditure, regardless of how much that component is used early in the project.

IONA’s approach meets your needs.
With IONA, organizations can service-enable existing systems on demand, incorporating everything from back-end mainframes to existing .NET infrastructure components into a network of services. IONA products service-enable existing systems and support any transport, protocol, and payload format so IT architects can migrate gradually to SOA with minimal disruption. IONA allows organizations to deploy only what they need, when they need it. IONA doesn’t require multiple SOA products for your architecture to operate effectively. For example, if technical orchestration is not required, or performance monitoring is not necessary at a certain stage of SOA deployment, there is no requirement to purchase and use these components, from IONA or any other technology vendor. IONA’s pay-as-you-go pricing model facilitates this incremental adoption. Customers pay only for what they use and no more. Instead of paying in full for an enterprise service bus (ESB), they pay only for the systems they service-enable. This pricing model extends to the costs for a registry/repository; instead of a large upfront investment, the cost of a registry/repository is based on the number of services stored therein. Organizations can start with small projects, testing and measuring success before they evolve their SOA. This enables companies to purchase pieces of core infrastructure components, to realize the true value of the solution before they roll it out across the enterprise. With the IONA approach, organizations can adopt an SOA on a schedule that works for them, both technically and economically.

5

Key Product Attributes
The IONA approach is powered by three key product attributes either exhibited by, or enabled by IONA’s family of SOA solutions. This not only includes internally developed products, but carefully chosen solutions from IONA partners. These attributes are the cornerstones of the IONA product development principles and enable flexible deployment and incremental adoption.

Technology-Neutral
For true flexibility in SOA design and deployment, products need to be standards-based and technology-neutral. This significantly cuts down on the costs of SOA design and deployment and ensures an SOA is compatible with emerging technologies. With IONA Artix, “plug-ins” make any existing service compatible with any existing platform, protocol, or transport. IT architects do not have to force development teams to standardize on a single set of technologies or to deploy common middleware at every endpoint. IONA’s plug-in architecture is open at every level and supports: Any transport system – Most enterprises have a transport system currently deployed, and unilateral replacement destabilizes operations. IONA Artix supports any transport system – from TIBCO to HTTP to MQ to JMS among others – so organizations can leverage IONA solutions within their existing infrastructures, and project teams are free to deploy the transport system of their choice for new projects. Any transaction – Most SOA transactions are “fire and forget” in nature, but many enterprise transactions require the ACID reliability of 2-phase commit. Still others require the performance of a point-to-point connection. Through transaction management plug-ins, IONA supports any type of transaction, so corporations do not have to choose between good architecture and application requirements. Any payload format – XML has many useful attributes, but forcing applications to convert data into XML slows performance and can introduce errors. IONA products allow data to be sent in any format, including binary, simply by adding a plug-in to any endpoint that receives the payload. Any security, management, or platform tool – to further preserve the autonomy of backend systems, any security standard, system management suite, or development platform is supported at individual endpoints rather than forcing all applications to adhere to the same configuration. IONA’s technology-neutral approach gives companies the ability to leverage existing product investments, and removes the requirement for developers to learn proprietary software that many other SOA infrastructure vendors have. This can save an organization tremendous time and expense, and help them achieve their business goals more quickly.

Fully Distributed
IONA Technologies has been a leader in delivering standards-based, distributed solutions since distributed computing was invented. IONA developed a reputation as an innovator in distributed computing – the infrastructure now referred to as an SOA - by being the largest and most proven

6

provider of CORBA, the first standard for distributed computing. The corporation widely recognized as having the earliest and largest SOA deployment, Credit Suisse, built their architecture with IONA’s technology. With the distributed architecture of IONA Artix, SOA becomes practical for the large and complex IT environments found in the Global 2000. This mature and patented plug-in architecture is why IONA was chosen to provide solutions for 80% of the world’s telecommunications firms and 70% of the financial services in the Global 100 – industries that are typically fraught with the most demanding technical requirements. This distributed computing model is enabled by IONA’s Enterprise Service Bus, Artix ESB. At the core, Artix ESB is different from traditional integration solutions in that it creates a network of services using smart endpoints, instead of relying on a centralized server. While most SOA deployments distribute some features, only Artix ESB is able to distribute all features, eliminating the complications that occur in large-scale integration. Artix ESB connects all systems, including packaged and proprietary applications, existing EAI systems, and application server installations, using distributed technology. Even enterprises that have traditional integration solutions installed can continue to use and leverage them while using Artix ESB for broader integration projects. Artix ESB is fully distributed because of its patented plug-in architecture. Endpoints are extended to include just the integration services that are needed, and can be easily reconfigured because of Artix ESB’s unique plug-in architecture. Plug-ins extend endpoints without requiring code changes to that system to add support for any transport, any transaction, any payload format, any development platform, or any quality of service. Plug-ins can be easily created, reconfigured, or modified without vendor assistance or special training, and without taking systems offline.

Dynamic and Adaptable
The only certainty is that there will always be change, and creating an IT infrastructure that cannot adapt to meet unexpected requirements limits future growth. Business agility is a must in today’s competitive world. A dynamic infrastructure provides a tremendous advantage to a growing, changing organization. As business needs change, technology must adapt to those changes. In many organizations, this requires an operational shutdown so that changes to IT systems can be implemented, resulting in lost productivity. With IONA Artix, updates are made at individual endpoints instead of on a centralized server, allowing departments to make changes without disrupting the rest of the corporate infrastructure simply by reconfiguring endpoints. Artix ESB features are determined at runtime and loaded as plug-ins as needed. This makes Artix ESB extremely lightweight and right-sized for an organization’s particular integration needs. Unlike heavyweight centralized servers, Artix ESB can provide just the features you need using minimal resources. As your needs grow, IONA Artix’ plug-in architecture allows you to add functionality that meets or exceeds the capabilities of centralized solutions, always allowing you to leverage what you already have. Plug-ins can be reconfigured without code changes and changes to one endpoint do not require changes throughout an enterprise.

7

Development teams can use plug-ins to address: New qualities of service (QoS) and enterprise policies – New policies, including security and management measures, are handled by plug-ins at the endpoint, eliminating the need to create yet another server or technology stack. New applications – As additional applications come online, they often introduce new interfaces and unique requirements that stress inflexible infrastructure. Plug-ins provide compatibility locally so as not to disturb other applications development teams. New standards and technology – As new data models, protocols, and infrastructure products evolve, IONA Artix plug-ins allow the infrastructure to efficiently support new requirements negating the need for a new layer of adaptors.

8

Tools for the Job
IONA delivers the key infrastructure components needed for SOA enablement through its advanced SOA infrastructure suite – IONA Artix.

While there are other SOA-related products and technologies that provide benefits to many organizations, IONA Artix delivers the core components are the most necessary for deploying an SOA. IONA Artix and partner products, with their technology-neutral, distributed and dynamic nature, work with any other product an organization has in-house or plans to invest in down the road. This is crucial to IONA’s flexible approach to SOA. At a high level, services should be exposed with an ESB, and those services can be linked together to form Business Process Execution Language (BPEL) orchestrations more appropriate for consumption at the business level. Services can then be transformed to a specific data format for consumption by other systems. Those services and associated policies should be stored and managed with a registry/repository, and the performance of the services can be monitored with an SOA management solution. Once services are exposed and managed effectively, they can be used in a wide variety of enterprise systems like Business Process Management (BPM) or Customer Relationship Management (CRM) applications. While IONA sees this as the natural progression for SOA design and deployment, we understand that organizations have complex IT systems and equally complex IT needs. There may certainly be situations when an organization does not require one of these components for their SOA, or

9

when it makes more sense to deploy these solutions in a different order. With IONA’s flexible and incremental approach to SOA, any order or combination of SOA components can be used to successfully power your SOA.

Service Enablement - Enterprise Service Bus
An ESB is Web services-capable middleware infrastructure that supports intelligent program-toprogram communication and mediates the relationships among loosely coupled and uncoupled business components. An ESB enables the passing of messages between enterprise systems in an SOA. An ESB service enables systems to participate in the SOA. An ESB should do this without a centralized intermediary server, leveraging existing messaging infrastructure like WebSphere MQ or TIBCO, and providing QoS such as security, management, high availability, and transactions. Using Web Services Description Language (WSDL), users can expose aggregate functionality of underlying systems that can be useful throughout a large organization in different applications. Endpoints configured using WSDL provide an abstraction layer between systems, and allow services to be independently implemented and maintained using the technologies and languages most familiar and appropriate for a particular business function. Tying these services together is the role of an ESB. To be effective in this service-enablement and integration role, an ESB must support the widest array of disparate technologies: operating systems, device types, languages, and network messaging protocols. It must be extensible to add capabilities as needs change and as new technologies need to be supported.

Artix ESB
The ESB is an architectural step forward, but some of today's ESB products lack the capabilities that large enterprises require. The vast majority of these products depend on a single protocol (e.g., SOAP), programming language (e.g., Java), messaging transport (e.g., JMS), or deployment architecture (e.g., JEE application server) that limits their ability to bridge multiple platforms. In addition, many ESBs are marketed by small startups with no experience in complex enterprise integration projects. IONA offers Artix ESB, which dramatically reduces operating costs for organizations with complex and heterogeneous IT systems by deploying, managing and securing an SOA without requiring a centralized hub. Artix uses distributed computing technology to leverage and modernize existing middleware investments to help the Global 2000 deliver products and services to their customers faster and more efficiently. The fully distributed Artix ESB is: For incremental SOA adoption – Artix ESB creates a network of smart, standards-based endpoints using existing infrastructure so enterprises can begin with low-risk, highvalue SOA projects and gradually add services as needed. Dynamic and adaptable – Artix ESB endpoints are independently configurable so services can be extended, modified and hot deployed without disrupting the rest of the enterprise.

10

Technology-neutral – Artix ESB is a multi-platform and multi-protocol solution that connects diverse and lightweight endpoints without an expensive and cumbersome centralized server, and without promoting vendor lock-in. With the technology-neutral, distributed and dynamic Artix ESB, organizations can integrate complex, heterogeneous IT environments, exposing Web services to be leveraged within the SOA. This service-enablement is the crucial first step in designing and deploying an SOA.

Service Readiness - Technical Orchestration
In order to deploy a dynamic SOA, organizations must have the ability to reuse services from new or existing applications across the enterprise. The ability to leverage these services demands that they be orchestrated into service compositions that can be consumed at the business level. As an example, a developer may want to expose functionality for reuse by a business analyst who needs customer information in the context of a long-running business process. To expose a “GetCustomerInfo” service, multiple steps may be required to aggregate and reconcile relevant customer information from one or more enterprise systems. The customer information may require acquiring a user ID from one system to obtain account information from a different system. These individual steps are probably not generally useful across the SOA as independent services, but creating an orchestrated service makes it possible to expose multi step services for easier reuse.

Artix Orchestration
IONA provides Artix Orchestration to facilitate the composition of fine-grained functionality into reusable coarse-grained services. Artix Orchestration allows developers to create, deploy and manage these types of service orchestrations using BPEL. Orchestrations can include services exposed by Artix ESB endpoints and functionality available over any messaging system supported by Artix ESB. Artix Orchestration allows developers to orchestrate services across the enterprise using any messaging bus or middleware solution. IONA provides Eclipse-based design tools and an enterprise class BPEL execution environment. Together the Artix ESB and Artix Orchestration enable developers to expose both WSDL services and legacy systems to create service orchestrations. Once created, process analysts and application developers can use Artix Orchestration to test BPEL service orchestrations, and deploy those orchestrations within their BPEL execution environment.

11

BPEL orchestrations are often leveraged within BPM applications to create longer running, more complex business processes, often involving a human element. IONA solutions work with bestof-breed BPM technologies and IONA can recommend several vendors that work well within our paradigm of incremental adoption.

Data Integration – Management, Modeling and Transformation
It is crucial that organizations validate data to ensure integrity throughout an SOA deployment. In addition, large scale, performance demanding SOA deployments require that data transformation be executed quickly, at runtime. For example, a financial services provider may be required to submit data to a financial institution in an industry-specific format, such as SWIFT, FIX or FpML. The data exposed by related services constructed by the company may not be stored in that format. To enable transactions between their systems and those of the institution, the provider would have to write custom code to map their data to the industry-specific data format. If the data format changes (for example, SWIFT changes annually), the provider is often given 60 – 90 days to implement code changes to comply. Hand-coding to comply with industry-specific formats results in significant development time and costs, and inhibits the organization’s ability to meet compliance requirements on time. With tools to easily transform to and from any data format, or to manage and deploy internal messaging meta-data, a company can dramatically reduce customer development and ongoing maintenance costs and improve performance.

Artix Data Services
Artix Data Services (C24 acquisition) is a meta-data management, data modeling, transformation and integration toolkit based on open Java technologies. Using powerful graphical development tools, Artix Data Services significantly decreases the time to develop and deploy new integration components while reducing the cost and time associated with ongoing support and maintenance. Artix Data Services is an optional add-on to Artix ESB, providing parsing, validation and transformation services, not just for XML-derived data models, but for literally any data format an organization needs to handle. Unlike centralized and costly hub-based transformation engines, Artix Data Services can be deployed at the endpoints, minimizing hardware needs and improving IT performance. Artix Data Services also includes specialized messaging libraries providing bundled sets of components and services that extend the base toolkit for highly targeted and business-specific usage scenarios. These industry standard Data Object Definition (DOD) libraries fully encapsulate the published standards for many financial services-specific message types including SWIFT, FpML, CREST, ISO 20022, TRAX and FIX.

Actively Governing a Network of Services - Registry/Repository
Service-oriented architecture is distributed by nature and enterprise SOA initiatives require a level of governance to succeed long-term. Organizations are challenged with how to manage services across the entire lifecycle, from inception through analysis, design, construction, testing, deployment and usage. Moreover, as SOAs mature and the number of exposed services grows, it is important that they have the necessary tools in place to manage SOA expansion and

12

adoption. At each stage, certain rules or policies must be implemented and enforced to ensure that the services provide value to the consumers. SOA Governance is the discipline of creating, communicating and enforcing policies for managing services. A comprehensive registry/repository helps IT managers more effectively manage a network of services by providing a catalog of services within an SOA and a place to store all metadata, policies, and implementation assets, and increases visibility and service reuse across the organization. In addition, a comprehensive tool can provide the policy and lifecycle governance features to form the foundation for delivery of software and business services.

Artix Registry/Repository
Designed for complex, heterogeneous IT environments, Artix Registry/Repository delivers the fundamental requirements for applying SOA governance and effectively addresses the challenges of deploying and managing a truly distributed SOA. Artix Registry/Repository delivers SOA business agility by providing service reuse in distributed SOA environments throughout the entire SOA service lifecycle. Artix Registry/Repository enables customers to design, build, deploy and manage a network of business services by providing a complete system of record of services in a distributed SOA environment, including the policies, contracts, implementation artifacts and dependencies that control their usage. The ability to drive, and validate, the deployment of services and policies into a distributed SOA network redefines the state of the art and starkly differentiates Artix Registry/Repository from all other available governance solutions that serve as static archives. Artix Registry/Repository gives customers a powerful command and control center to define, promote and measure the reuse of services, which is ultimately where the core value of SOA lies. The Registry provides a searchable catalog of available services. The Repository stores all metadata, policies, and implementation assets, enabling organizations to uniquely leverage this information to automatically provision and monitor a network of services, ensuring continued adherence to enterprise policies. Artix Registry/Repository is designed to meet the requirements of customers across all stages of the SOA lifecycle, which takes an organization from design and development, through deployment and management, and even revision of existing services. Because Artix Registry/Repository simplifies the process of packaging and provisioning services, organizations are better prepared to revise and refine services in the face of changing business requirements. Validating deployed services against the stored “view” of the SOA network also helps eliminate errors that can occur when updating services. As importantly, the capability of Artix Registry/Repository to encapsulate and store all relevant information about a customer’s SOA network means the entire network of services can be redeployed if necessary. As with all products in IONA Artix, Artix Registry/Repository is designed for use in performancedemanding, heterogeneous IT environments and can be deployed in an incremental manner. The product exhibits the key attributes necessary to execute the IONA approach to SOA: Technology-Neutral – Artix Registry/Repository works with standards-based Web services, allowing it to be used for discovery, governance and lifecycle management of a network of services across the enterprise.

13

Distributed – Artix Registry/Repository enables deployment and enforcement of systemwide or service specific policies, helping companies more effectively manage a distributed architecture. Dynamic and adaptable – With Artix Repository, organizations can update policy and interface information on the fly from a single user interface, increasing response time to business change. With Artix Registry/Repository, an organization can use metadata to describe the policies that they want their system to enforce, usually during runtime. For example, a policy may focus on enforcing a service level agreement that embodies predefined policies for service interactions. Artix Registry/Repository creates business agility by helping companies change IT systems in response to new customers, new requirements, or changes on the competitive landscape. All this can be accomplished without a slowdown in IT operations. For example, when a new policy is created and applied to existing services, those underlying services continue to function seamlessly. This is powerful reuse and agility. Once an organization has exposed services across the enterprise, orchestrated the services for consumption at the business level, and governed the services by applying key policies, it can enforce the re-use of services within the SOA network and maximize its return on investment.

Monitoring Service Performance - SOA Management
To govern and maintain the quality of a network of services, organizations need to head off potential problems by proactively resolving issues that arise—including issues with service levels and exceptions. To do this effectively across an evolving SOA landscape, they need a management solution that provides full coverage for disparate formats, protocols, interface, and transports.

SOA Management from AmberPoint
While IONA supports any SOA management solution, IONA has established a partnership with AmberPoint to help organizations more effectively monitor the performance of their SOA. AmberPoint is a leader in the SOA management space, and adopts the same key product attributes that IONA believes is important for flexible and incremental SOA design and deployment. SOA Management from AmberPoint provides policy-based runtime governance of services across a distributed set of endpoints. SOA Management from AmberPoint provides security, reliability, and availability to plan for growth, minimize risk, and justify additional investments in SOA. It transforms SOA systems into production-ready business assets by providing end-to-end visibility into the service network, ensuring operational health, and facilitating the roll-out of new versions. AmberPoint is:

14

Distributed - The distributed nature of SOA Management from AmberPoint improves scalability and allows the joint solution to grow with your SOA environment. There is no central bottleneck because it is neither a hosted solution, nor a monolithic platform— Artix ESB and SOA Management from AmberPoint eliminate single points of failure in the system. The distributed architecture ensures that applications and systems remain independent and loosely coupled, allowing them to communicate with multiple systems using a common interface. Dynamic and Adaptable - Unlike other products, Artix ESB and SOA Management from AmberPoint integrate seamlessly into heterogeneous, distributed environments without any additional coding to the Web services or clients. The solution service-enables existing systems without requiring changes to the systems and without denigrating qualities of service. This allows operators to makes changes to infrastructure components without slowing system performance during runtime. The solution makes it possible to meet and future-proof even the most extreme requirements quickly and efficiently. Incremental - IONA and SOA Management from AmberPoint promote an incremental, non-disruptive approach to making infrastructure and mission-critical systems interoperable. IONA solutions establish an SOA gradually without disrupting existing servers and without a large up-front investment. Existing infrastructure components can be extended and reused, and future changes are dynamically configured as needed. With services exposed, readied for use and organized, SOA Management from AmberPoint is used to ensure operational performance. Organizations ensure the success of their SOA deployments by starting with small manageable projects with an eye towards incorporating the rest of the enterprise into their SOA environment.

Designing the SOA
IONA’s tools are fully integrated with Eclipse, the most popular open-source integrated development environment (IDE). Originally introduced by IBM, Eclipse is supported by many software firms and volunteers across the Internet. Eclipse has become the de facto standard for cross-platform software development, and has been adopted by many vendors of SOA software. IONA is sponsor and principal contributor to the SOA Tools Platform (STP) project, hosted by the Eclipse Foundation. This project combines the resources of several leading SOA software vendors to produce a shared, best-of-breed development solution for customers developing and deploying SOA. For more information about the SOA Tools Project visit eclipse.org/stp .

Open Source
Many organizations are evaluating open source offerings for their SOA strategy. IONA, an open source leader, offers customers a suite of open source SOA infrastructure components combined with full enterprise-class support; designed to support all open source projects, whether they are small proof-of-concepts or large, mission-critical installations. IONA combines the confidence of working with an experienced and professional organization with the innovation and cost savings of open source software to bring the best of both worlds together in a safe and secure

15

environment. IONA’s open source strategy also aligns with the technology-neutral, distributed and dynamic product attributes described throughout this document.

FUSE: A Family of Open Source SOA Components
FUSE™ is IONA’s family of open source SOA infrastructure components that organizations with an open source strategy can use for building a flexible SOA. Like IONA’s commercial products, FUSE can be used to build an SOA leveraging existing IT investments. FUSE components include: FUSE ESB - Based on Apache ServiceMix, FUSE ESB is one of the first shipping implementations of the Java Business Integration (JBI) specification. FUSE ESB supports any JBI-compliant binding for connectivity, and enables any JBI-compliant engine to be integrated into the SOA backplane for message processing. FUSE Message Broker - The FUSE Message Broker is a high performance solution for reliable messaging based on the Apache ActiveMQ project, the leading open source JMS platform for enterprise messaging. The FUSE Message Broker provides high performance, unlimited scalability, and mission-critical reliability for distributed enterprise computing. FUSE Services Framework - Based on Apache CXF (JAX-WS), the FUSE Services Framework is a pluggable service framework that provides the easiest environment available for Java developers to create Web services. The only services framework that fully implements the JAX-WS 2.0 specification, radically simplifying the process of exposing existing Java code as a Web service or writing new Web services, the FUSE Services Framework enables developers build high performance Web services that are scalable, secure, and robust in minutes, freeing them to concentrate on the core aspects of their applications. FUSE Mediation Router - Based on Apache Camel, The FUSE Mediation Router is a powerful tool for routing and process mediation that combines the ease of basic POJO development with the clarity of the standard Enterprise Integration Patterns. Companies seeking an open source option for system integration and SOA implementation will find the capabilities that they need in one convenient package, certified, fully tested and validated for enterprise use by an SOA and integration market leader. IONA’s enterprise-class support includes various consulting packages, training curriculum and levels of support designed to give customers confidence in their open source strategies. Further, IONA validates the interoperability of the products, and gives customers the most flexible approach to enabling the “SOA backplane” required for service-oriented integration. For more information about FUSE, please visit http://open.iona.com/.

16

Transform Your Business
SOA is gaining in popularity, in large part due to the availability and stability of the standards, technologies, and products that support it. A Web services-based SOA enables integration of virtually all IT resources, including isolated data silos and previously incompatible legacy, .NET, and Java technology applications. IONA leverages its 15 years of experience, as well as best practices developed by helping companies meet their integration needs, to facilitate the move to a service-oriented enterprise, and can supply everything your enterprise needs to get started today. IONA provides an incremental path to SOA. IONA’s technology-neutral, distributed, and dynamic and adaptable SOA technologies allow organizations to take a flexible, incremental approach to SOA. IONA helps organizations service-enables infrastructure, including: Service-enabling applications Developing orchestrations of services to be more easily used within an IT environment Transforming services to meet specific data format requirements Driving a network of services and making them available for easier reuse through a registry/repository Putting in place the ability to monitor the performance of these services IONA’s full portfolio of distributed, technology-neutral SOA infrastructure components help organizations evolve existing IT assets into reusable business services that can be shared across IT environments. By commoditizing proprietary middleware stacks and allowing SOA to conform to the unique needs of enterprises, IONA delivers on the promises of SOA including business agility, increased ROI and lower operational costs.

………………………………………………………………………………………………………………………………………………………
IONA Technologies PLC The IONA Building Shelbourne Road Dublin 4 Ireland Phone +353 1 637 2000 Fax +353 1 637 2888 info@iona.com IONA Technologies Inc. 200 West Street Waltham MA 02451 USA Phone +1 781 902 8000 Fax +1 781 902 8001 IONA Technologies Japan Ltd Akasaka Sanchome Building 7/F 3-21-16 Akasaka Minato-ku Tokyo Japan Phone +813 3560 5611 Fax +813 3560 5612

Artix, Artix Mainframe, Adaptive Runtime Technology are Trademarks of IONA Technologies PLC. Orbix, Orbix 2000 Notification, and Orbix/E are Registered Trademarks of IONA Technologies PLC. COPYRIGHT NOTICE. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, photo- copying, recording or otherwise, without prior written consent of IONA Technologies PLC. Copyright © 1999-2006 IONA Technologies PLC. All rights reserved.

…………………………………………………………………………………………………………………


				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:221
posted:6/21/2008
language:English
pages:16
kristopher mensing kristopher mensing crap addictinggames.com
About