Open Source OSGi ESB - FUSE ESB 4 (ServiceMix 4)

Download

Download FUSE ESB v4.1 (based on Apache ServiceMix 4) for your platform

• UNIX (33 MB, BIN.SH)
• Windows (33 MB, EXE)
• Source (4.5 MB, ZIP)

Waiting for your download to complete? Why not check out how FUSE support, services, training and consulting for Apache ServiceMix can help you be as successful as possible making FUSE a part of your enterprise?

Downloading the product is just the beginning!

Documentation

FUSE ESB 4 Release

What’s new in FUSE ESB 4 (ServiceMix 4) documentation:

• Added Camel JBI to OSGi migration documentation
• Revamped library guide

Searching the Library

The best way to search the library is using Google directly and narrowing the search scope using site:fusesource.com/docs/esb.

This method will limit the search to the FUSE ESB (ServiceMix 4) documentation. You can limit the scope further by adding a version number to the site: string.

For example to search the documentation for references to polling the file system you could enter site:fusesource.com/docs/esb/4.0/ polling into the Google search field. Only results from the FUSE ESB version 4.0 library will be returned.

Getting Started

Book	PDF
Getting Started with the FUSE Product Family
Logistix Tutorial Guide
Using the FUSE ESB (ServiceMix 4) Library
Getting Started with FUSE ESB (ServiceMix 4) Documentation
FUSE Glossary

Installing

Book	PDF
FUSE ESB (ServiceMix 4) Release Notes	—
Installing FUSE ESB (ServiceMix 4) Documentation
Migrating to FUSE ESB 4.1 (ServiceMix 4) Documentation

Configuring and Running the Container

Book	PDF
Managing the FUSE ESB (ServiceMix 4) Runtime
Using JBI in FUSE ESB 4 (ServiceMix 4) Documentation

Developing Services

Book	PDF
JAX-WS Applications with FUSE ESB (ServiceMix 4) Documentation

Integration

Book	PDF
Enterprise Integration Patterns
Using the FUSE Services Framework Binding Component
Using the JMS Binding Component
Using the File Binding Component

Reference

Book	PDF
Console Reference Guide
API Reference Guide	—
XML Configuration Reference Guide	—
Apache ServiceMix User’s Guide	—

ZIP File

Download the documentation: .zip

Previous Releases

4.0

Demo Videos

To run the demos yourself, first review the slide presentation then download the code:

• Getting Started With FUSE Webinar (pdf) – Slide Presentation
• fuse-tutorial-payments-demo.tar.gz – zipped tar ball containing code

These videos are .mov files which require QuickTime to view.

• Building, installing and running FUSE ESB 4 (screencast): In this session, Ade shows how to build, install and run FUSE ESB 4. He also shows how to “prune” the installation so that FUSE ESB only loads up the modules you need for your work.
• Deploying a POJO into FUSE ESB 4 (screencast): In this session, Ade gives an overview of his development environment, and shows how to deploy and share your Java POJOs into FUSE ESB 4. He shows how to integrate your logging with the FUSE ESB 4 logging system, and, how to read your own custom configuration data using properties files and the OSGi configuration service.
• Deploying a Web Service into FUSE ESB 4 (screencast): In this session, Ade shows how to create a SOAP/HTTP web service using JAX-WS and deploy it into the FUSE ESB 4 runtime. He also shows how to tie this new component in with the shared POJO developed previously.
• Deploying an Enterprise Integration Pattern into FUSE ESB 4 (screencast): In this session, Ade shows how to create and deploy enterprise integration patterns. Using the Apache Camel DSL, he creates a file- and FTP-poller to read in plain-text CSV files, saves them to a persistent queue using JMS, and then splits the batch data line-by-line for individual processing.
• Deploying a JBI component into FUSE ESB 4 (screencast): In this session, Ade shows how to take JBI solutions developed and deployed in FUSE ESB 3 and deploy them in the FUSE ESB 4 container.

License

for FUSE ESB (based on Apache ServiceMix)

[Based on the Apache License Version 2.0, January 2004]

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

READ THE TERMS OF THIS LICENSE AGREEMENT (“AGREEMENT”) CAREFULLY BEFORE INSTALLING THIS WORK. BY INSTALLING THE WORK OR USING THE DOCUMENTATION PROVIDED WITH THE WORK, YOU ARE ACCEPTING AND AGREEING TO THE TERMS OF THIS AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY THE TERMS OF THIS AGREEMENT, YOU SHOULD CLICK ON THE “DECLINE” BUTTON BELOW.

This FUSE ESB v. 4.1 License Agreement is made by and between YOU and Progress Software Corporation and consists of the Apache License version 2.0 modified to be specific to FUSE ESB v. 4.1, with the Additional Terms in Section 10. The original Apache License version 2.0 can be found at http://www.apache.org/licenses/.

1. Definitions.

“License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 10 of this document.

“Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

“Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

“You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License.

“Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

“Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

“Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

“Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

“Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”

“Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

a. You must give any other recipients of the Work or Derivative Works a copy of this License; and

b. You must cause any modified files to carry prominent notices stating that You changed the files; and

c. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

d. If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

10. Additional Terms and Conditions. The terms and conditions of this License Agreement shall apply to FUSE ESB version 4.1 only. The Work may contain or be accompanied by third party software or components created and separately licensed to You by said third parties. Some of these third-party software components are identified in, and subject to, special license notices, terms and/or conditions set for in a “notice.txt” file (http://fusesource.com/downloads/license-agreements/notices/fuseesb4-1) accompanying the Work. In the event of a conflict between such additional terms and conditions and Agreement, such additional terms and conditions will take precedence (but solely with respect to the third party component(s) to which the additional terms and conditions relates). This is a License Agreement, not a transfer of copyright ownership. All copyrights remain with their respective owners.

Why OSGi

FUSE ESB 4 (based on Apache ServiceMix 4) Supports OSGi

The primary difference between FUSE ESB 3 and FUSE ESB 4 is support of the OSGi standard. Apache ServiceMix 4 supports OSGi but does not fully support JBI, and therefore the FUSE team recommends that developers who have been using FUSE ESB 3 or JBI continue to use FUSE ESB 3. Users of OSGi should use FUSE ESB 4. The 4.1 release of both Apache ServiceMix and FUSE ESB will fully support both JBI and OSGi.

OSGi is a Java-based service platform that can be remotely managed. The core part of the specifications is a framework that defines an application life cycle management model, a service registry, an execution environment and modules.

The primary benefit of OSGi is its dynamic component model, which allows applications to be updated without having to take them down. With OSGi dynamic deployment, components can be dynamically added to a running system, and existing running components can be stopped and updated without taking down the whole application. This is in contrast to Java EE app servers, where one has to cycle the container to change a single component. This gives server-side applications the same flexibility and dynamic behavior that is enjoyed with web applications.

A second benefit is that the OSGi Framework provides a set of built in features for security and lifecycle management, and a set of built-in services. OSGi is service oriented, and includes a service registry that’s the key for cooperation among bundles (JAR files with additional metadata describing dependencies, versions, class file requirements, etc.). Applications creating and deploying their own OSGi services can communicate service-to-service directly using OSGi, and take advantage of the built in services for logging, HTTP access, XML parsing, and various configuration, deployment, and administration functions, device management for embedded devices etc.

Thirdly, unlike JCP defined Java editions, OSGi is the same from embedded devices to the mainframe. No recoding or different APIs are required. One loads the additional modules for the enterprise features when needed, and run the embedded application in the embedded and/or enterprise space.

Resources

For FUSE ESB 4 – Apache ServiceMix 4

Quick Links

• What are the differences between Apache ServiceMix and FUSE ESB? Read why FUSE.
• Apache ServiceMix support
• Apache ServiceMix training
• Forums
• Issue Tracker
• Data sheet
• FUSE Wiki
• Supported Platforms

OSGi Resources

• Webinar: Overview of OSGi Enterprise
• Webinar: Introduction and Demo of Distributed OSGi
• Webinar: Transactions, Clustering, OSGi and ServiceMix, the Open Source ESB
• Integration Developers News: OSGi Grows in Popularity Among ESB Providers
• InfoQ: Why Do We Need Distributed OSGi?

ServiceMix 4 Resources

• Whitepaper: Large-scale deployment with ServiceMix 4
• Webinar: Large-Scale Deployments & ServiceMix 4
• Webinar: ServiceMix 4.0
• Presentation: Distributed Team building, Tooling for ServiceMix 4, ServiceMix 4 topologies
• DZone: A Look Inside FUSE ESB 4: An OSGi-Based Integration Platform