In the name of god
Leila namdarian
Types of ESB&features
1.WSO2 ESB : http://wso2.org/projects/esb/java
WSO2 ESB is an ultra fast, light-weight enterprise-ready open source product based on
the Apache Synapse ESB. With WSO2 ESB, you can connect, manage and transform
service interactions between Web services, REST/POX services and legacy systems
Feature
Description
Full XML and
With built-in support for XML, Namespaces, Xpath, XSLT, XQuery,
Web Services
the WSO2 ESB is ready to support your XML processing needs. At
Support
the same time it is also capable of processing none XML content to a
great extent.
The WSO2 ESB supports major Web services standards including:

SOAP 1.1/SOAP 1.2

WSDL 1.1/WSDL 2.0

WS-Addressing (supports dual channel invocation)

WS-Security with Apache Rampart

WS-ReliableMessaging with Apache Sandesha 2

WS-Eventing with Apache Savan & WSO2 Eventing

WS-Policy (supports separate policies for incoming/outgoing
messages)
Proven
Interoperability

MTOM/SwA optimizations for binary messages

XML/HTTP (POX)

REST formats
Based on the popular Apache Synapse & Apache Axis2 projects,
WSO2 ESB has proven interoperability with major Web Services
stacks including Microsoft .NET WCF.
1
Feature
Description
Highly Performant
The WSO2 ESB has been optimized to support high-levels of
throughput at low latency, using minimal resources. It can support
thousands of concurrent connections, as well as large messages using
a constant memory footprint, using connection throttling. A
combination of non-blocking IO and a streaming XML parsing design
means that the ESB can scale as much as you need, and still perform
exceedingly well.
Minimal Custom
The WSO2 ESB has been designed to easily support the most
Development
common requirements, while it is also possible to extend its
capabilities.
There are built-in capabilities for:
Extensibility

Content based routing

Service virtualization

Load balancing

Fail-over sending

Protocol switching

Message transformation

Schema validation

Logging & monitoring

Message splitting and aggregation

Enterprise integration patterns

Request throttling

Response caching
It can be extended using simple Java extensions, POJO classes or
Spring, as well as with JavaScript, Ruby, Groovy or other Apache BSF
scripting languages.
Multi-protocol
With inbuilt support for the following protocols to integrate with your
existing network, your partners and your new projects:
2
Feature
Description

Non-blocking HTTP/S transport

Transactional JMS transport 1.0 and 1.1 with binary, text and SOAP
messages over JMS

Apache VFS file transport (e.g. S/FTP, File, zip/tar/gz, WebDAV,
CIFS, etc)
Task Scheduling

Mail transport (POP3, IMAP, SMTP) with multipart content support

AMQP via Apache QPid

Financial Information eXchange (FIX)

Hessian binary protocol for web services
Support for managing recurrent tasks via ESB allows periodic updates
and these tasks scheduled as cron daemons or as simple recuring tasks.
Event Driven
Architecture (EDA)
Event sources can be hosted in the WSO2 ESB and it can act as an
events broker making it easy to implement the integration of the
enterprise using EDA. Events going through the broker can be
mediated to perform any required changes before distributing. Event
sources can contain static subscriptions defined with the subscription
manager and the interested parties can also subscribe to the event
sources dynamically.
Subscription managers can be extended to change the behavior of the
event source and ESB ships with a built-in registry based subscription
manager.
Built-in Registry
The WSO2 ESB ships with an integrated WSO2 Registry, and can
easily connect to external/remote Registry implementations.
Advanced
The WSO2 ESB has built-in support for reading from or writing to
Mediations & EIP
Databases, as well as calling into Java/POJO classes or scripts. It also
provides the ability to do message splitting, aggregation, caching and
throttling that can be configured easily.
ESB also supports most of the Enterprise Integration Patterns (EIP),
3
Feature
Description
with the built-in mediators.
Industry Driven
Support for industry driven Financial Information eXchange (FIX)
Protocols
protocol enabling the financial sector integration and Hessian binary
web service protocol to support binary message formats. AMQP, VFS
and JMS as transports for the enterprise integration.
Internationalized
WSO2 ESB provides a set of management services and a graphical
Graphical Console
user interface to configure/manage/monitor the running ESB server.
This graphical console can be easily separable from the back-end so
that while the back-end runs on the server, you can have the graphical
console installed on your desktop which is fully internationalized and
this also can be used to manage a cluster of nodes.
Features of this new graphical console includes:
Server
Management

Sequence editor

Proxy service editor

Endpoint/Local Entry editor

Task schedular

Event source creator

Built-in registry browser

Policy editor

Predefined security scenarios

User stores

Key stores

Configure data sources

Transport management

Try-It for services

Logs, trace and statistics monitor
Ability to shutdown and re-start the ESB, gracefully and forcefully
through the management console and JMX.
4
Feature
Description
System Monitoring
The WSO2 ESB comes with comprehensive monitoring capabilities
within the management console as well as through JMX. These
monitoring capabilities includes:

System status

System statistics with graphs

Mediation statistics with graphs

Mediation tracer

SOAP tracer

Logs configuring & monitoring
Customizable
Server
With the WSO2 ESB 2.0 based on WSO2 Carbon, the Middleware a
la carte', you can customize the ESB Server to fit into your exact
requirements, by removing certain features or by adding new optional
features. These features are implemented as components acording to
the OSGi component architecture so that all the features are
seamlessly integratable.
These available optional components (features) are:

Service hosting capability (.aar, jaxws, pojo, ejb, dataservices)

Business process management

Cluster management
2. Pe tal s E S B , O p en sou rce E S B : http://petals.ow2.org/features.html
Petals ESB is an open source ESB (Enterprise Service Bus) for large SOA architectures.
Our original design, distributed across multiple servers and full compatible with all major
industry standards (such as JBI, SCA, BPEL or WSDL) enables users to :
o
Reduce maintenance
o
Easily adapt large-scale infrastructure
o
Quickly implement the architecture, thanks to free development tools
PEtALS has two main differences with other ESBs:
5
o
Works in a distributed environment, to handle large architectures.
o
Certified (SUN) for JBI, and provides framework for developing JBI components.
Feat ur es
det ai l es
o
Production efficiency
Up to 30 servers connected in
production, with 10k services, and 10
billion messages a day (ACOSS)
o
Modular architecture (Fractal) and
low-memory footprint
o
Distributed topology, adapted to large
architectures
o
Remote monitoring, administration,
and governance
o
Integration of a dynamic registry
o
Support from Petals Link (previously
EBM Websourcing), and third-party
integrators
Robustness
o
Security
o
Transaction
o
High avalability: Distributed
topology, native clustering
Design-time
o
Load Balancing
o
Persistence
o
Eclipse plugin for faster development
o
Official adapters, and third-party JBI
6
components
o
Certified JBI/JSR-208, and provides
JBI component builder
o
Modular architecture for easier
adaptation
o
Sercice composition with SCA
3.ARTIX ESB: http://www.iona.com/support/docs/artix/5.0/soa/ch02s04.html
Artix ESB is a fully distributed ESB. It is built around the concept that all of the endpoints in
your SOA are smart. Artix ESB accomplishes this by building the ESB functionality into the
runtime libraries that are loaded by deployed endpoints. Artix ESB also provides a number
of services that provide features such as location independence, security, and routing.
Artix ESB provides the following functionality:











data and transport abstraction
C++/JNI runtime
pure Java runtime
message routing
security
transactions
reliable messaging
location resolution
high availability
design time tooling
Artix ESB can be supplemented to include robust orchestration tools a ,
registry/repository solution, mainframe connectivity, and .NET interoperabilit
(IONA,2007)
The features of Artix ESB 5.1
JAX-WS 2.0 TCK Testing
New Artix Java Router
Artix Designer Enhancements
detaies
The Artix Java Runtime has been tested against the JAXWS 2.0 Technology Compatibility Kit (TCK) to ensure that
it complies with the JAX-WS 2.0specification. Our TCK
testing shows a 100-percent pass rate when running JAXWS services on Apache Tomcat.
A new Java router, based on Apache Camel, is included in
Artix ESB 5.1. Itallows you to implement a range of
enterprise application integration and message-oriented
middleware design patterns, as defined in the book
Enterprise Integration Patterns.
 Artix Data Services integration A new project type has
been added that allows you to integrate Artix ESB with
IONA Artix Data Services. You can use the Artix Data
Services Client project to create JAXB wrappers around the
7
Java classes generated by Artix Data Services, so that they
can be consumed by other Web services. The project also
generates a sample client that you can package and run
against the legacy service.
 Support for Artix Java samples You can now import
more than half of the Artix Java samples as projects into
Artix Designer and run them from within Eclipse.
Run Spring container and Tomcat from within Designer You
can now launch the Artix Spring container or an Apache
Tomcat server from the Eclipse Serversview, allowing you
to create, deploy, and run your JAX-WS services within
Artix Designer.
 Automatic migration of Artix Designer 5.0 projects to
5.1 When you open an Artix Designer 5.0 project in this
release, the project is migrated to version 5.1
automatically.
 Improved CORBA support for Artix Java runtime A
JAX-WS version of the CORBA Web Services project has
been added in this release.
 WSDL validation enabled by default In the Artix
Designer preferences panel, the Validate WSDL against
schemas option is enabled by default in this release.
UDDI Support
Support for Microsoft Visual Studio 2005
Spring Container Enhancements
You can now run Universal Description Discovery and
Integration (UDDI) 2.0 as a service within Artix ESB.
In addition, a new UDDI client-side resolver enables Artix
clients to automatically discover service contracts in UDDI
without writing UDDI-specific code. For working examples,
see the jUDDI and UDDI Client samples under the
ArtixInstallDir\java\samples\uddi directory.
The Artix ESB C++ runtime now supports Microsoft Visual
Studio 2005(VC 8.0) on Windows 2003 (32-bit). Remember
to run the artix_env script with the -compiler vc80 flag to set up
your Artix environment for this version of Visual Studio.
. The spring_container stop command now works with
multiple containers.
. Improved error messages when the container fails to start.
. Better handling of incorrect JAX-WS endpoint addresses.
. Improved formatting of spring_container -h output.
. Improved memory management when running multiple
idl2wsdl Enhancements
applications.
. The Spring container interface now returns a list of
services for a given application, not just a list of
applications.
 Support for mapping IDL modules to schema namespaces
 . Support for inheritance
WSDL Publishing Support in Tomcat
Artix Java Samples Support Spring Container
SSH FTP Support
The Artix WSDL publishing service is now supported when
deploying a service to Apache Tomcat. To enable WSDL
publishing, set the deployedinContainer variable to true in the
service.s Artix Java configuration file.
You can now deploy most Artix Java samples to a Spring
Container from the command line, where appropriate.
The Artix FTP transport has been enhanced to allow it to
talk to a Secure Shell (SSH) server. This allows Artix 5.1
endpoints to use the SSH server as a secure
intermediary persistent datastore.
8
4. MULE ESB: . (Mulesoft, 2009) http://www.mulesoft.org/display/MULE/Home
Mule ESB is a lightweight integration platform and service container that allows you to
quickly and easily connect your applications together. Mule ESB provides a robust, secure
and scalable platform to build enterprise applications offering an array of transports such as
JMS, HTTP, Email, FTP, JDBC and many more. It also offers rich set of features for web
services, message routing, mediation, transformation and transaction management. Designed
around the ESB (enterprise service bus) concept, Mule ESB is the most widely used open
source integration platform.Mule ESB™ is the world’s most widely used open source
enterprise service bus, with over 1.5 million downloads and 2,000 production deployments.
With Mule ESB’s simplified development model and lightweight architecture, developers
can be productive in minutes, easily creating and integrating application services. Mule ESB
takes the complexity out of integration, enabling developers to easily build highperformance, multi-protocol interactions between heterogeneous systems and services With
Mule ESB, there is no need to embark on a top-down transformative SO initiative with a
lengthy payback horizon. Instead, Mule ESB works with any existing infrastructure, and IT
organizations can immediately see value from the service orientation and decoupled
integration that Mule ESB provides. At the same time, the Mule ESB Enterprise suite
includes enterprise-class features and tools that enable Mule ESB to scale up and meet the
most demanding performance or reliability challenges posed by even the largest SOA
implementation.
Mule Service Registry Features
Service and artifact management
detailes





Publishing, indexing and discovery of services




Governance and lifecycle management



Dependency management



Application deployment management (Mule Netboot)




Federation capabilities


Developer productivity

Artifact and metadata storage (e.g.,
WSDLs, service metadata, Mule configs,
Spring configs, JARs, documentation etc.)
Version management and control
Collaborative comments
Query via Web interface, HTTP Supports Open
Search and Mule Service
Registry query language
Custom indexes via X Query, X Path, Groovy
View/publish/edit/subscribe to artifacts via Atom
Publishing Protocol
Policy enforcement
User-definable lifecycle and workflow
Scripting shell and event API for custom
extensions and workflows
Automatic dependency detection
Manual dependency specification
Visualization of service dependencies
Load applications remotely from
the repository
Upgrade and roll back applications and
Mule distributions from a central location
Record and manage versions
and configurations
Remote workspaces — attach remote workspaces
to a local instance for browsing and search
Replication — copy workspaces across Mule
Service Registry instances for advanced lifecycle
management
Extensible query engine for index/search of
custom artifact types
9



Deployment and runtime stability
Search support for annotations and documents in
MS Office format
Clustering for high availability and fault tolerance
Integration with ESB monitoring console for
centralized application deployment management

(Mule soft, 2009) http://www.mulesoft.org/display/MULE/Home
Technical Specifications
detailes
OS





Linux
Windows
Solaris
AIX
HP-UX


Mac OS x
Derby
Oracle


MySQL
EJB 3
Spring

Database

Containers

App Server








BPM
Standalone
Tomcat
WebLogic
WebSphere
Geronimo
JBoss
Resin
Transport












Jetty
AS400
Data Queue
Abdera
Amazon SQS
Axis
BPM
CICS CTG
CXF
Email
FTP
Hibernate
HTTP/S
Development Tools

























Ant
Eclipse
Japex
Maven
Mule IDE
Spring Security
Acegi
JAAS
ESB
Client/Server
Peer-to-Peer
Enterprise
Service Network
(ESN)
Hub and Spoke
Pipeline
Asynchronous
SEDA
Streaming
Synchronous
Transactions
Routing Patterns
Axis
Atom
CXF
Security
Flexible Deployment Topologies
Event Handling
Web Services























IMAP/S
JCR
JDBC
Jersey
Jetty/
Jetty SSL
JMS
LDAP
Multicast
POP3/S
Quartz
Restlet







RMI
SalesForce
SAP
Servlet
SMTP/S
SOAP
STDIO
TCP
UDP
VM
XMPP
WSDL
Profiler
Data Mapper
(Eclipse IDE,
Oakland)
PGP
SS4TLS
10
Languages
Data Formats
Data Transformation
Other





































.NET Web Services
REST
WS-Addressing
WS-Policy
WS-Security
WS-I BasicProfile
WS-I SecurityProfile
WSDL
Groovy
Java
Javascript
Jaxen
Jython (Python)
JRuby
JXPath
Atom
Base 64
encoded
Byte arrays
CSV
Encrypted
GZIP
Hex Strings
HTML / XHTML
Java Objects
JSON
EDI
XSLT
XQuery
Smooks
Oakland Software
BPEL
jBPM
JSR-223
(Scripting)
OGNL Filters
Quartz
5. Microsoft BizTalk ESB Toolkit 2.0 : .(Infosyse,2006 )
http://www.infosysblogs.com/microsoft/2006/09/biztalk_as_an_esb_2.htmlInfosyMicrosoft:
BizTalk as an ESB
The Microsoft BizTalk ESB Toolkit uses Microsoft BizTalk Server 2009 to support a loosely
coupled messaging architecture. BizTalk Server includes a powerful publish/subscribe
mechanism for messaging applications that works by creating and filling subscriptions, which
provides a highly efficient and scalable platform for service-oriented architecture(SOA)
applications. The BizTalk ESB Toolkit extends the functionality of BizTalk Server to provide
a range of new capabilities focused on building robust, connected, service-oriented
applications that incorporate itinerary-based service invocation for lightweight service
composition, dynamic resolution of endpoints and maps, Web service and WS-* integration,
fault management and reporting, and integration with third-party SOA governance solutions.
features
 It is not an implementation of Service Oriented Architecture --> This is more of concept
behind ESB and hence we need not map BizTalk to this.

It is usually operating system and programming language agnostic; it should enable
interoperability between Java and .Net applications, for example --> BizTalk isn't OS or
programming language agnostic by itself, but can help interoperate/integrate Java and
11
.net applications via say the SOAP adapter.

It uses XML (extensible Markup Language) as the standard communication language
--> though BizTalk can work with any document type; most of features are best used
when working with XML. In fact, a common myth is that it is necessary to convert all
input documents to XML before sending them for processing within BizTalk.

It supports Web services standards --> BizTalk has SOAP adapter that helps you
work with web services. It alohas adapter for working with Web Services
Enhancements (WSE) 2.0.

It supports messaging (synchronous, asynchronous, point-to-point, publish-subscribe)
--> BizTalk inherently works on pub-sub model. Messages are published into the
BizTalk Message box database and orchestrations and send ports subscribe to them.
BizTalk also support message routing, message translation, short and long running
transactions and various other message delivery related features. Via use of specific
adapters like MSMQ, asynchronous message delivery can be easily achieved.

It includes standards-based adapters (such as J2C/JCA) for supporting integration
with legacy systems -->BizTalk has a plethora of out-of-box and third party adapters
that can be used to integrate with various legacy and LOB systems. A list of such
adapters is available here. BizTalk also can work closely with Host Integration Server
to connect to mainframes.

It includes support for service orchestration & choreography --> Orchestration is one
of the key features of BizTalk. BizTalk conforms to Business Process Execution
Language (BPEL) standards. Not only does BizTalk provide orchestration execution
features, it also has a rich designer support well integrated with Visual Studio 2005.
Additionally, it has Orchestration Designer for Business Analysts (ODBA) that
integrates with Visio and business users can use it to designing orchestrations.

It includes intelligent, content-based routing services (itinerary routing) --> BizTalk
supports content based routing via promoted properties concept.

It includes a standardized security model to authorize, authenticate, and audit use of
the ESB --> BizTalk has mechanisms in place to provide security. It can even work
with Certificates and supports ability to resolve incoming requests via these
certificates.
It includes transformation services (often via XSLT) between the format of the sending
application and the receiving application, to facilitate the transformation of data
formats and values --> BizTalk has extensive support for data transformation via the
Mapper functionality. It provides host of funtoids out-of-box to manage the
transformations and also includes ability to custom script additionaly functionality
that isn't available via the functoids. For this transformation and schema creation
itself, BizTalk again has great tool that integrates with VS. We don't have to worry
about writing XSLT manually.


It includes validation against schemas for sending and receiving messages --> The
12
pipelines in BizTalk provide mechanisms to validate messages based on published
schemas.

It can uniformly apply business rules, enrichment of the message from other sources,
splitting and combining of multiple messages, and the handling of exceptions -->
BizTalk supports interchange handling (splitting messages) and also allows
aggregation of messages. Via pipelines and mappers we can work with the messages
and modify them. There is good business rules engine (BRE) support via which we
can define rules and policies and use them in orchestrations. The policies are
managed external to the orchestration and hence can be changed at any time without
having to touch the orchestartions. Since BizTalk supports long running transactions,
it also has mechanisms for compensating transactions.

It can conditionally route or transform messages based on a non-centralized policy meaning that no central rules engine needs to be present --> Already discussed this
above in terms of content based routing and mapping functionality.

It is monitored for various SLA (Service-Level Agreement) thresholds message latency
and other characteristics described in a Service Level Agreement --> BizTalk has
Business Activity Monitoring (BAM) features that provide a portal based approach to
track the messages and orchestration progress. Additionally, extensive performance
monitor counters are available that can be used to get additional information about
message processing speeds etc.
It (often) facilitates "service classes," responding appropriately to higher and lower
priority users --> This is managed more by appropriate deployment and configuring
specific features on specific servers.


It supports queuing, holding messages if applications are temporarily unavailable -->
BizTalk can work with adapters like MSMQ that provide such features. It also has
capabilities of setting retry count and retry intervals.

It is comprised of selectively deployed application adapters in a (geographically)
distributed environment -->BizTalk has to be deployed in full, thought post that
selective features can be enabled on the machines
6.JBOSS ESB: (TIBCO,2009)
The core of JBossESB is Rosetta, an ESB that has been in commercial deployment at a
mission critical site for over 3 years. JBoss ESB aims to provide a set of tools and a
methodology that makes it simple to isolate business logic from transport and triggering
mechanisms, to log business and processing events that flow through the framework, and to
13
allow flexible plug-ins of ad hoc business logic and data transformations. Emphasis was
placed on making it possible (and simple) for future users to replace/extend the standard base
classes that come with the framework (and are used for the toolset), and to trigger their own
“action classes” that can be unaware of transport and triggering mechanisms.
http://www.jboss.org/jbossesb/features.html
 Jboss helped accelerate our development timeline to the individual developers who
brought their expertise to the project.
 JBoss provides a fundamental building block for our SOA integration platform.
 JBoss ESB leverages other JEMS technologies, such as the JBoss Rules business rules
engine for content-based routing and JBossMQ for messaging.
 As part of its effort to enable customers and accelerate their path to SOA
 JBoss will be looking to partners to extend the ESB with connectors, B2B gateways,
SOA governance, and business services.
 JBoss Expands Open Source Platform for SOA with Enterprise Service Bus “By
offering a pluggable platform.
 One of the main tasks that the JBossESB performs is that of routing messages to the correct
services.
 support for general notification framework. Transports supported include JMS (JBossMQ,
JBoss Messaging, Oracle AQ and MQSeries), InVm, TCP/IP, email, database or file system.
JBoss Messaging 1.4.0GA is now the recommended default JMS implementation.
 JMS and SQL transaction integration.
 More seamless integration when deployed into JBossAS.
 jBPM integration.
 WS-BPEL support.
 Web Services support.
 Improved deployment and configuration, using a specific ESB server.
 Groovy support.
 trailblazer example.
 many quickstart examples to get you going.
 support for data transformations using Smooks 1.0 or XSLT.
 listeners and action model to support loose-coupling of interaction steps.
 content based routing using Drools or XPath.
 support for registries, using JAX-R and jUDDI out-of-the-box. Now supporting the SOA
Software UDDI registry too.
 gateways to allow non-ESB aware traffic to flow into the ESB.
 graphical configuration editor.
 high performance and reliability (in use by a large insurance company for 3 years).
Key features of JBoss ESB 4.0 include:
A pluggable architecture enables all JBoss ESB subsystems such as messaging and
transformation to be swapped with other alternatives, which gives customers flexibility and
choice.
Support for a variety of messaging services, including secure FTP, HTTP, email and
JMS (JBossMQ, JBoss Messaging, IBM MQSeries, and ActiveMQ).
Transformation engine that bridges data formats for seamless communication, supporting
XSLT and Smooks, a flexible alternative.
Service registry for service discovery and integration, using JAX-R and UDDI.
Persisted event repository to support governance of the ESB environment.
Notification service to allow the ESB to register events and signal subscribers.
14
Content-based routing based on XPath and JBoss Rules for a more flexible and dynamic
alternative to publish-subscribe.
Gateways that allow non-ESB aware clients to interact with services deployed within the
JBoss ESB environment.
7.FUSE ESB:( Progress Software,2009)
http://fusesource.com/docs/esb/4.1/getting_started/ESBGetStartedOverview.html
FUSE ESB is an open, standards based integration platform. It reduces the complexity of
integrating disparate applications by leveraging the service oriented architecture principles
and standardized packaging frameworks. One of the biggest challenges facing modern
enterprises is IT system integration. FUSE ESB tackles this problem using a lightweight
standards based, loosely coupled approach. By relying on standards, FUSE ESB reduces
the chances of vendor lock-in. By advocating loose coupling, FUSE ESB reduces the
complexity of integration. Based on Apache ServiceMix, FUSE ESB reduces complexity and
eliminates vendor lock in because it is standards based and built using best in breed
open source technology.
FUSE ESB features:
• The FUSE ESB kernel is lightweight and can run on most platforms.
• The FUSE ESB kernel uses the OSGi framework to simplify componentization
of applications. The OSGi framework is a newly emerging standard for managing the
dependencies between application components. It also provides a standard mechanism for
controlling the life-cycle of components.
• FUSE ESB supports the Java Business Integration(JBI) specification (JSR
208).
• Modular — The command console includes modular subshells that provide
commands for a specific set of functionality. You can also expand the
functionality by writing custom modules.See "FUSE ESB Console Root Commands and
Subshells" in Console Reference Guide for information about using the subshells.
• Artifact Management — One of the most important uses of the command
console is managing the artifacts deployed into the container. The command
console provides subshells to manage artifacts, including OSGi bundles,
collections of bundles, JBI artifacts, and OSGi bundle repositories (OBRs).
See the Console Reference Guide for information about the FUSE ESB
console subshells available for artifact management.
• Remote Management — You will likely have many instances of the FUSE
ESB runtime distributed throughout your organization. To address this
requirement, the command console includes the commands ssh and sshd,
which enable you to connect to and start a remote secure shell server.
 FUSE ESB can be coupled to other infrastructure services over a variety of transport



protocols and message formats.
FUSE ESB employs standards as much as possible to limit dependencies.
In addition, FUSE ESB supports event driven architectures.
FUSE ESB also supports events that occur outside of the bus.
8.Oracle ESB(Oracle,2005)
OracleAS Integration provides the complete web services infrastructure for building,
deploying and managing distributed applications based on open systems standards.
15
Oracle’s Enterprise Service Bus (ESB) is designed to implement your Service Oriented
Architecture (SOA) and Event Driven Architecture (EDA) providing a responsive, low cost,
high impact framework for matching technology needs to your business problems. Oracle’s
ESB is the foundation for delivering services utilizing an SOA and EDA. At its core, it is a
loosely coupled application framework that provides businesses with increased flexibility,
reusability and overall responsiveness in a distributed, heterogeneous, message-oriented
environment.
 Integrated Platform
Oracle AS Integration consists of four important solution components: (i) ESB, (ii)
BPEL PM, (iii) B2B and (iv) BAM. Oracle provides the total one-stop platform for
enterprise integration. It is fully integrated with the Oracle AS OC4J J2EE, Oracle
10g RDBMS, Oracle JDeveloper’s integrated DVE and Oracle BI. It leverages
Oracle infrastructure and GRID features such as security, high availability and
scalability.
 Reliable Multi-Transport Bus
Provides flexible real-time enterprise backbone supporting multiple protocols with
special in-memory optimization for service calls within the same virtual machine.
Features complete messaging infrastructure for managing fast, scalable, guaranteed
once and only once QOS for point-to-point and publish/subscribe patterns. Supports
Oracle OC4J JMS, Oracle JMS for Advanced Queues (AQ) on the Oracle Database
and many 3rd party JMS products.
 Complex Business Data Transformations
Utilizes standards based data mapper functionality within JDeveloper to create
transformation templates in the XSLT language for reuse across the enterprise. The
auto-mapping feature remembers and reuses common mappings from previous
transformations. Cross system referencing and domain value mappings are included
for multi system index lookups.
 Pervasive Enterprise System Connectivity
Oracle AS Adapters provide bi-directional, real-time connectivity and support open
standards such as JCA, XML, JMS, Web Services and WSIF. The Packaged
Application and technology protocol adapters provide access to over 200 data
sources with tight integration to Oracle Applications. All adapters conform to the
J2EE Connector Architecture (JCA) open standard adopted by all major integration
vendors.
 Flexible Content Based Routing
Oracle ESB exposes routing rules using design time deployment descriptor
definitions that can be modified at runtime to adjust application efficiency. It
supports a variety of rules engines including Oracle AS Java Business Rules and
external providers. Content filtering can be implemented in messaging systems such
as JMS using configurable filter based subscriptions and message selectors. CBR
services can be deployed with Oracle JDeveloper using Java, PL/SQL or Oracle
BPEL PM.
 Integrated Modeling Environment
Oracle JDeveloper provides a comprehensive, easy to use design time graphical
interface for building and deploying ESB services. The diagrammer tool enables
visually linking services and single click deployment. It includes a WSDL editor,
integrated XSLT mapper, and wizards for building messaging and adapter services.
 Comprehensive Manageability
Distributed ESB services are centrally managed with Oracle Enterprise Manager
(EM) and the ESB Monitor. The ESB Topology Viewer allows you to graph
16
dependency charts or impact analysis for proposed changes to your systems. The
viewer includes ESB wide search and browse functionality to locate specific ESB
service instances. Built-in Oracle AS BAM support enables application alerting,
reporting and organizational SLA monitoring.
 Oracle ESB – Core Features:
 Rich Set of Adapters
(technology and applications)
 Transformation
 Reliable Message Delivery
 Content-based Routing
 Publish and Subscribe
 Service URL Virtualization
 Oracle ESB – Value Added:
 Enterprise Messaging - OEMS
 Multi Transport
 Rich Monitoring Console
 Request/Response and EDA
 Native XML and Web Services
 Metadata Repository
 UDDI Repository (Systinet)
 Externalized Process Flows
 Real Time Activity Monitoring
 Integrated Design Experience
9. Apache Service mix: .( Hanson,2009)
Hanson, J. Jeffrey, (2009)" Service Mix as an enterprise service bus: Use ServiceMix
2.0 as a service-oriented message routing framework" JavaWorld.com.
Apache ServiceMix is an open source ESB (Enterprise Service Bus) that combines the
functionality of a Service Oriented Architecture (SOA) and an Event Driven Architecture
(EDA) to create an agile, enterprise ESB. Apache ServiceMix is an open source distributed
ESB built from the ground up on the Java Business Integration (JBI) specification JSR 208
and released under the Apache license. The goal of JBI is to allow components and services
to be integrated in a vendor independent way, allowing users and vendors to plug and
play.Service Mix is an ESB based on JBI. Released under the Apache license, it is an open source
ESB and SOA toolkit built on JBI's semantics and APIs. The toolkit is lightweight and easily
embeddable, has integrated Spring support, and can run inside a client or server, as a standalone ESB
provider, or as a service within another ESB. You can use Service Mix in a Java Standard Edition or
Java Enterprise Edition application server. Service Mix is completely integrated with JBoss and
Apache Geronimo and lets you deploy JBI components and services directly into Geronimo.
17
detailes
ServiceMix Features:
ServiceMix includes a complete JBI container
that supports all parts of the JBI specification
including:
ServiceMix also includes
the followingcomponents
and services:
 Service components

SOAP bindings
o
o
o
o
o
A normalized message service and router
JBI management beans (MBeans)
Ant tasks for management and installation of
components
Full support for the JBI deployment units with hotdeployment of JBI components
Rules-based routing via the Drools rule
engine
o
A client API for working with JBI
components and services
o
An implementation of Web Services
Notification
o
Business Process Execution Language
(BPEL) support for Web Services BPEL via
PXE (preboot execution environment)
o
Support for caching service invocations using
a Map cache or a JCache provider
o
Support for the Java Connector Architecture
o
Timer integration via the Quartz library
o
Scripting support, allowing any Java
Specification Request 223-compliant
scripting engine to be used to create a
component, perform a transformation, or act
as an expression language
o
Transformation using Extensible Stylesheet
Language Transformations
o
Schema validation of documents using the
Java API for XML Processing 1.3 and XML
Schema or RelaxNG
o
XSQL for working with SQL and XML via
Oracle's XSQL library
o
o
o
o
o
o

Transport bindings
o
o
o
o
Support for a SOAP stack based on the
Streaming API for XML (StAX) via
ActiveSOAP
Support for the Java API for XML-based
Web Services to make a Web services client
invocation or host a Java-based Web service
and expose it over multiple protocols
Reflection to allow plain-old Java objects
(POJOs) to be deployed in ServiceMix
SOAP with Attachments API for Java and
Apache Axis support
Integration with POJOs via the XFire SOAP
stack
Integration with the Apache Web Service
Invocation Framework (WSIF)
Email support via JavaMail
File-based components for writing messages
to files and polling directories and sending
files into the JBI
FTP support via the Jakarta Commons Net
library
HTTP support for client-side and server-side
processing
18
o
o
o
o
Bindings to the Jabber network via the
Extensible Messaging and Presence Protocol
JMS support via ActiveMQ
RSS support via the Rome library for
accessing and processing RSS feeds
VFS (virtual filesystem switch) via the
Jakarta Commons Net library, which provides
access to file systems, jar/zip/bzip2 temporary
files, World Wide Web Distributed Authoring
and Versioning, Samba (Common Internet
File System), HTTP, HTTPS, FTP, SFTP,
and others
ServiceMix is lightweight and easily embeddable, has integrated Spring support and can be run at the edge of
the network (inside a client or server), as a standalone ESB provider or as a service within another ESB. You
can use Service Mix in Java SE or a Java EE application server.
Service Mix uses ActiveMQ to provide removing, clustering, reliability and distributed failover.
Service Mix is completely integrated into Apache Geronimo, which allows you to deploy JBI components and
services directly into Geronimo. Service Mix is being JBI certified as part of the Geronimo project
10. Neuronesb2.1: http://www.neuronesb.com/
Neuron is proven to substantially reduce the amount of manually developed code
required for projects, in some cases upwards of 70%, while providing a familiar
working environment. With Neuron, projects that once took 18 months to develop and
deploy could now take 6 months. Version 2.1 of NEURON-ESB Now Released!This
newest version of Enterprise Service Bus software, Neuron-ESB 2.1, extends the
Microsoft Dynamics CRM Platform and has added design tool functionality
Neuron ESB 2.1 introduces many enhancements and new features which include:
View Neuron ESB CRM 
Adapter Video
Pipeline
Processing
o
o
o
Graphical
Designer for
Pipelines
Design time
Pipeline
Testing
Support for
Environment
Variables
Pipelines and pipeline components were
completely re-written for Neuron 2.1 and are one
of the most visible changes to the Neuron ESB
Explorer user interface. Included in Neuron ESB
2.1 are a new Pipeline Designer, new pipeline
components (steps) as well as an entirely new
user experience for testing and development. To
work with pipelines in the Neuron ESB Explorer,
select Pipelines from the navigation bar located
on the left hand side of the Neuron ESB
Explorer. This will open the Pipeline Designer
19
as well as the Pipeline Library. The Pipeline
Library appears on the left above the navigation
bar and lists configured pipelines from the
working Neuron ESB configuration. The Pipeline
Designer fills the rest of the workspace and
consists of the Design Canvas, a list of Pipeline
Steps used to create pipelines and a property grid
to specify the design time properties of the
selected component. All new Pipeline
documentation can be found in the Neuron 2.1
Pipelines.pdf located in the \Docs folder under
the Neuron installation directory.

Microsoft CRM
Adapters
o
o
While Microsoft Dynamics CRM represents a powerful,
central business application for Enterprise customers,
integration options are limited and resource intensive.
However, no real-time, non third party, non custom
coding methods exists for integrating data from or to
Microsoft Dynamics CRM. Custom data publication
from Microsoft Dynamics CRM (using Microsoft
Dynamics CRM's Plug-in model) and/or integration of
data into Microsoft Dynamics CRM (using Microsoft
Dynamics CRM's Web Service model) is timeconsuming, expensive and requires specialized
resources. Subsequent updates to customize real time
integrations can be slow and requires an experienced
developer.
Neuron ESB 2.1 offers a solution by providing real-time
event based integration to Microsoft Dynamics CRM.
The Neuron ESB 2.1 adapters require neither custom
code nor expensive development resources. By taking
the Neuron ESB approach, customers can significantly
reduce the cost of Integrating Microsoft Dynamics CRM
into their organization.
Event based
Publication
Adapter
Subscription
Adapter
Microsoft Dynamics CRM Event Based Publication
Adapter




Integrated Graphical UI in CRM
Real time Data Publication
Complex Condition(s) determine whether CRM
Event is published to Neuron
Multiple Entity/Multiple Payload Data Publication
Microsoft Dynamics CRM Subscription Adapter




Performance
o
o
Client based
publication
throttling
MSMQ
Simple Configuration in Neuron ESB 2.1 UI
Multiple CRM Web Service operations can be
handled in a single message
Accepts multi -record, multi-entity operations
Significant work was done to
increase the overall performance
and reliability of the transports that ship
with Neuron ESB.




The TCP transport has been improved for
performance and scale by a factor of 3X. There are
now settings for Reliability and Ordered Delivery.
Setting these options will decrease performance, but
guarantee that message are sent and received in the
same order and are reliable with using a
transmit/acknowledge model.
The entire software reliability layer was redesigned
to ensure reliable transmission of messages over
Neuron TCP powered Topics
The Client<T> API has been improved for
performance and scale. The Client<T> API is used
to communicate to Neuron service endpoints.
The MSMQ transport now has a recoverable
message property. This option forces MSMQ to
20


Deployment

Neuron API
o
immediately store the message to disk, thus making
the message recoverable, if MSMQ was to fail
suddenly.
Client publication throttling has been added and can
be set at the Topic. Throttling can be defined by the
following:
o Delay per message (expressed in
milliseconds)
o Messages per second
o Messages per minute
o Data per second (expressed in kilobit)
o Data per minute (expressed in kilobit)
o Max message size (expressed in
kilobit)
Neuron deployment groups contain environment
specific information including machine name and Zone.
Deployment groups can also optionally be used to
override connection settings for the Neuron Zone
database and URLs in Client Connectors and Service
Connectors.
With Neuron 2.1, Environment Variables are
introduced. Environment variables can be associated
with deployment groups and assigned unique values for
each deployment group. Once defined, environment
variables can be bound to customize the runtime
behavior of pipelines by using the Bindings Dialog.
Environment variables can be used to customize web
service URLs, connection strings, server names, and
many other properties used within a pipeline.
Deployment
Group level
Environment
Variables
The most noticeable feature change that developers will
experience is the renaming of Neuron ESB’s core
assembly, ESB.dll. The main Neuron assembly,
ESB.DLL has been renamed to Neuron.ESB.dll and refactored into multiple assemblies.




New Samples
o
All of the Neudesic.ESB.* namespaces have been
changed to Neuron.Esb.*
In Neuron 2.0, using the Neuron API in custom
applications for sending/receiving messages to/from
Topics required only a reference to ESB.dll. This
has changed in Neuron 2.1. Visual Studio projects
that once referenced ESB.dll must now reference
the following 4 assemblies: Neuron.Esb.dll,
Neuron.dll, Neuron.Pipelines.dll and
Neuron.Scripting.dll. All of these assembles can be
found in the Neuron installation directory and will
appear in the Add References dialog box with
Visual Studio.
In Neuron 2.0, using the Neuron API in custom
applications for sending/receiving messages to/from
Topics required that the Neuron “Channel”
assemblies were in the same directory as the custom
application’s executable. This is no longer a
requirement in Neuron ESB 2.1. Channel
assemblies were removed and incorporated into the
required project DLL’s to make managing runtime
deployment more predictable.
Neuron ESB ships with 7 new samples that highlight the
functionality offered by the new Pipeline and Workflow
engine. Included are samples that demonstrate the
following:
7 new
Pipeline
Samples


How a Publish Neuron Pipeline step can be used to
route a message to different topics using the Publish
step’s C# Code option. With the C# Code option,
the topic that a Publish pipeline step sends
messages on can be dynamically set at runtime
based on C# code defined by the user.
Using a Decision Neuron Pipeline step to route a
message to different topics based on the value of an
21





ESB Message property. A Decision pipeline step
contains 2 to n branches each of which can contain
any number of other pipeline steps.
Neuron Pipeline steps wrapped inside an Exception
step. An Exception step is comprised of three
execution blocks; Try, Catch and Finally.
Encapsulating pipeline steps inside an Exception
step allows for further processing in the event of
any errors.
How to use the Validate - Schema Neuron Pipeline
step to assure messages on the bus are in the form
and format expected. Schema validation is the
process of checking to assure an XML document
conforms to a defined structure.
Using the Service and Retry Neuron Pipeline steps
to call a web service. A Retry pipeline step that can
be used to wrap a Service pipeline step (or any
pipeline step) in retry logic to help overcome issues
that may occur calling the web service defined in
the Service pipeline step. The Retry step can detect
either Communication or System.Exception errors.
How a Neuron Pipeline can split a message into
parts and send those parts as separate messages on a
different topic for further processing.
Wrapping pipeline steps within a Transaction.
Transactions are used to ensure that, if a process
fails to execute, any individual step of that process
(that supports transactions or use XA resource
compliant transaction resource managers) that had
already completed prior to the error occurring is
“rolled back” to its original state.
11. Apache Synapse 1.2 ESB: http://synapse.apache.org/
Apache Synapse is designed to be a simple, lightweight and high performance Enterprise
Service Bus (ESB) from Apache. Based on a small asynchronous core, Apache Synapse has
excellent support for XML and Web services - as well as binary and text formats. The
Synapse engine is configured with a simple XML format and comes with a set of ready-touse transports and mediators. We recommend you start by reading the QuickStart and then
trying out the samples. Synapse is made available under the Apache Software License
2.0Synapse 1.2 release adds the support for the Financial Information eXchange (FIX) an
industry driven messaging standard through QuickFixJ as well as Hessian binary web service
protocol, as well as other functional, stability and performance improvements. Apache
Synapse is an ESB that has been designed to be simple to configure, very fast, and effective
at solving many integration and gatewaying problems. Synapse has support for HTTP,
SOAP, SMTP, JMS, FTP and file system transports, Financial Information eXchange (FIX)
and Hessian protocols for message exchange as well as first class support for standards such
as WS-Addressing, Web Services Security (WSS), Web Services Reliable Messaging
(WSRM), efficient binary attachments (MTOM/XOP). Synapse can transform messages
using key standards such as XSLT, XPath and XQuery, or simply using Java. Synapse
supports a number of useful functions out-of-the-box without programming, but it also can be
extended using popular programming languages such as Java, JavaScript, Ruby, Groovy, etc..
Synapse has a completely asynchronous core, and supports non-blocking HTTP and HTTPS
using the excellent Apache HttpCore NIO module. In addition, Synapse supports JMS v1.0
and higher, Apache VFS File Systems (FTP, SFTP, File (including zip/jar/tar/gz), Webdav,
CIFS), POP3/IMAP/SMTP transports. Apache Synapse can process SOAP 1.1/1.2, pure
XML/REST, Text and Binary messages with support for any-to-any conversion and
transformation.
22
Key Features
The latest release of Synapse is 1.2. Its key features are
























Proxy services - facilitating transport, interface (WSDL/Schema/Policy), message
format (SOAP 1.1/1.2, POX/REST, Text, Binary), QoS (WS-Addressing/WSSecurity/WS-RM) and optimization switching (MTOM/SwA)
Non-blocking HTTP/S transports based on Apache HttpCore for ultrafast execution
and support for thousands of connections at high concurreny with constant memory
usage
Built in Registry/Repository, facilitating dynamic updating and reloading of the
configuration and associated resources (e.g. XSLTs, XSD, JS, ..)
Easily extended via custom Java class (mediator and command)/Spring mediators, or
BSF Scripting languages (Javascript, Ruby, Groovy, etc.)
Built in support for scheduling tasks using the Quartz scheduler
Load-balancing (with or without sticky sessions) /Fail-over, and clustered Throttling
and Caching support
WS-Security, WS-Reliable Messaging & Throttling configurable via
(message/operation/service level) WS-Policies
JMS (v1.x upwards) message support for binary, plain text and XML and SOAP
payloads
Support for Hessian binary web service protocol
Industry driven Financial Information eXchange (FIX) protocol
Enhanced support for Apache VFS transports (s/ftp, file, zip/tar/gz, webdav, cifs..)
Support for message splitting & aggregation using the EIP
Database lookup & store support with DBMediators with reusable database
connection pools
Enhanced Mail transport with POP3/SMTP/IMAP protocols
GZip encoding over the HTTP/S transport
Dual-Channel message exchange with WS-Addressing
Ability to pin a proxy service or a task to server instances on a cluster
Mandatory sequence if required before mediation
Lightweight, XML and Web services centric messaging model
Configurations serialized into a file system for versioning/backup & restoration with
built-in Registry support
Support for Error handling and timeouts, recovery with http/s maintainance mode &
gracefull shutdown
JMX monitoring support
Many samples and a built-in Axis2 server to try out and experiment with samples
(Samples includes WS-Security, JMS POX/Text messages, Script mediation and
many more samples which can be run out of the box)
Enhanced documentation for samples and getting started
12. ChainbuilderESB2: http://sourceforge.net/projects/bostech-cbesb/
The Bostech Team is pleased to announce that Chain Builder 2.0 has been released. Chain
Builder ESB 2.0 is a standards-based integration framework that delivers fast and easy SOA
implementations for Enterprises and Software Vendors. With a focus on ease of use and rich
set of features, Bostech Corporation developed Chain Builder ESB to connect applications and
services to create innovative solutions. Chain Builder ESB includes an intuitive development
environment of Eclipse graphical interfaces and drag-and-drop functionality to integrate
23
strategic business operations within Service Oriented Architecture (SOA) deployments.
Installed across a diverse set of industries, including healthcare and retail, Chain Builder ESB
helps enterprises and software vendors enable niche application adapters, composite
applications and enterprise-wide infrastructures. ChainBuilder ESB is an open source
Enterprise Service Bus. ChainBuilder ESB allows IT developers with Service Oriented
Architecture (SOA) infrastructures to create standards-based ESB components through
Eclipse-based graphical user interfaces. Most organizations SOAs need to include strategic
backend systems that operate with non-XML data formats and non-WebServices
communication protocols. Bostech focus on usability ensured the initial offerings of
ChainBuilder ESB had industry standard editors to manage EDI X12, HL7, fixed and variable
formats and communication components for TCP/IP, FTP and file protocols and database
components for JMS and ETL integrations - the formats and protocols that organizations with
mature applications absolutely require. ChainBuilder ESB also has uncommon high-end open
source features, like an AJAX-based Console web interface for monitoring and controlling the
production environment, usually found only with expensive proprietary system
ChainBuilder ESB 2.0 features significant enhancements, including these areas:
http://sourceforge.net/projects/bostech-cbesb/
• New Portal Framework: Provides a plug-in API to extend the ChainBuilder ESB Admin
Console. The portal can accept GWT (Google Web Toolkit) web applications that integrate
tightly with the existing webapps, or completely independent web applications.
• Expanded Script and UPOC Framework: Enhanced to accept user arguments. The UPOC
framework now includes the ability to “stack” UPOC functions, so the output message of one
becomes the input message to the next. These enhancements greatly improve flexibility and
code re-use.
• Multiple Component Flow Files Allowed: The Service Assembly project in ChainBuilder
ESB supports multiple component flow files to handle dividing and merging complex business
flows. Also supports a connector framework for message exchange between endpoints in
different component flows or different service assembly.
• Usability and Security within the Format and Flow Editors: Incorporated copy/paste, undo,
drag and drop across the Eclipse based plugins of the Component Flow Editor, the Format
Editor, and the X12 and HL7 Editors, The password fields are now encrypted.
• Improved Map Editor Functionality: Now includes XPATH as an addressing mode or as a
filter option for an iterate operation. This addition allows fetching a value from the source
message using an XPATH expression that can be evaluated to a single value or node.
• Improved Map Editor Functionality: Introduced a new Custom Map Operation interface
which provides the developer access to the underlying Document Object Model (DOM)
structure for both source and target messages.
• Upgraded Fault Handling: All components have been upgraded to return JBI fault in event of
exception. A custom JBI component “FaultHandler” can be added in component flow for more
robust and flexible exception processing.
24
• Improved Admin Console Configuration Options: Significant improvements in configuring
endpoint settings, supporting the choice from dropdown lists, password encryption.
• More Deployment Platforms supported: Bostech expanded the supported deployment
platforms from the original Windows and Linux offerings to multiple Unix platforms including
AIX, HP-UX and Solaris.
• Runtime Upgrades: The core JBI runtime of Apache Servicemix in ChainBuilder ESB 2.0
has been upgraded to the latest 3.2.2 release.
13. Sun Glassfish Enterprise Service Bus :
http://www.sun.com/software/javaenterprisesystem/javacaps/glassfish_esb.jsp
GlassFish Enterprise Service Bus (ESB)
GlassFish Enterprise Service Bus (ESB) is a lightweight and agile ESB platform that
packages the innovation happening with Project Open ESB, the GlassFish application
server, and the NetBeans IDE into a commercially supported, enterprise-class platform.
At a Glance
Clustering, load balancing and high availability for mission critical enterprise deployments
Provides a lightweight, modular architecture that enables agile SOA-based service
development, deployment, and testing
Delivers a plug-and-play architecture where components and services can be integrated in a
vendor-independent way
Promotes greater innovation and transparency through the open-source, ESB-community
approach
Allows vertical and horizontal scalability via the asynchronous, decoupled design model of
JBI-based component architecture
Provides your choice of development language, tooling, topology, and architectural style
(MOM, SOA, EJB, BPM, EDA, and so on)
Part of the Sun GlassFish Portfolio, a cost-effective, open Web application platform that
combines the best of open-source software and support in a single package.
Clustering - Load Balancing & High Availability
A key benefit of GlassFish ESB is the ability to provide developers with a lightweight, rightsized development environment and scale to a larger solution only when project scope
expands. This approach ensures GlassFish ESB is targeted specifically to current needs,
delivering a faster deployment time. As application usage increases, there is a demand for
additional performance and high availability. GlassFish ESB meets these scalability needs
through clustering, providing increased performance and high reliability. Furthermore,
GlassFish ESB clustering provides easier maintenance and better support for decentralized
25
and distributed environments.
Complex integration requirements?
Need to integrate with packaged applications (Oracle, SAP, etc.) or legacy technologies that
include mainframe integration or other complexities? Check out the Sun ESB Suite, which
layers functionality on top of GlassFish ESB to make it well suited for the most complex
environments.
Benefits for glass fish ESB:
14. OPEN ESB
Kalali, Masoud(2008)" Introduction to integration and Open ESB, part I: Open ESB
serverside artifacts"http://java.dzone.com/articles/introduction-integration-and-o
Open ESB, an open source JBI implementation sponsored by Sun Microsystems and hosted
in Java.net, is one of major open source ESBs which integrator or SOA developers may try to
utilize in their integration or SOA. Open ESB can be deployed into Jboss, GlassFish and
Websphere Application Server along with possibility to run it as a Java SE application. Open
ESB is pre-bundled with many binding components and Service Engine which almost make
you free from looking for binding components or service engines which you may need in a
typical integration scenario. In addition to the plenty of Service Engines and Binding
26
Components, Open ESB has a very good development IDE closely integrated with Open
ESB, NetBeans IDE 6.1 has many features which ease development of composite
applications based on Open ESB's capabilities. It come with a visual designer which support
drag and drop, connectivity, configuration of binding components and required web services.
Each binding component in the Open ESB has a design time representation in the IDE which
let you easily design your integration scenario in the IDE based on the server's
facilities(Kalali,2008)
15.Celtix Open Source ESB 1.0
Features in Celtix 1.0 include:
 Advanced Java Support: Celtix 1.0 is the only ESB, either open source or
commercially available, to include a full JAX-WS 2.0 implementation. Support for
the Java API for XML-based Web services provides users the easiest way to Web
service enable existing Java applications for use in a SOA. The inclusion of
JMX?based management capabilities gives users greater visibility and control over
their Celtix-based SOA.
 Multiple Messaging Options: The multiple messaging options in Celtix 1.0 provide
users with greater flexibility to choose the messaging option that best meets their
particular SOA requirements. In addition to a JMS implementation, Celtix 1.0 also
provides WS?ReliableMessaging, offering a standards-based option for reliably
delivering SOAP messages over HTTP.
 Support for Dynamic Scripting Languages: Celtix 1.0 gives users the option to
compose Celtix applications using JavaScript or ECMAScript for XML (E4X). The
ability of Celtix to support dynamic scripting languages gives users an effective
means to get their SOA deployments rapidly up and running and the freedom to easily
adapt them as business requirements change.
 Adherence to Industry Standards: In addition to a native, lightweight SOAP stack that
does not require deployment with a Web server, Celtix 1.0 also includes a
WS?Addressing implementation and the ability to support emerging standards
including Java Business Integration (JBI) and Service Component Architecture
(SCA).
27