Bostech Corporation has announced the release of the alpha version of ChainBuilder ESB, a new Java Business Integration (JBI) compliant solution for use in Service Oriented Architecture (SOA) environments. The final version is due in January 2007. An Enterprise Service Bus (ESB) is considered to be the least complex, lowest cost approach to implementing a Service Oriented Architecture. ChainBuilder ESB is a product that includes an Enterprise Service Bus and additional integration functionality to enable an enterprise’s disparate software systems to plug into the ESB. The alpha version is available for immediate free download from their website. ChainBuilder ESB offers a graphical (rather than a programmatic) user interface. What this means for developers is a premier Visual Enterprise Integration solution where individual ESB services and other integrated application components can be shown in a high-level graphical integration flow. This visual depiction of the entire integration environment allows developers to step back and consider the flow of their application integration and then drill down on each component to define specifics. ChainBuilder ESB components are written in Java and easily configured via a graphical user interface plugged into the popular Eclipse development platform. The alpha release of ChainBuilder ESB shows feature depth with several editors, including component flow, mapping, custom format and EDI X12 editors. Bostech Corporation is deploying a dual-license distribution model for ChainBuilder ESB. Developers can download the open source software under the common GPL license. Additionally, these open source developers can purchase a subscription that provides ChainBuilder ESB training, support and intellectual property indemnification. A commercial license is also available. Message was edited by: email@example.com
- Posted by: Eric Lu
- Posted on: November 06 2006 08:59 EST
- Re: Bostech’s ChainBuilder ESB Released in Alpha by Roland Altenhoven on November 07 2006 03:13 EST
- Re: Bostech’s ChainBuilder ESB Released in Alpha by Eric Lu on November 09 2006 07:09 EST
All Solutions with a strategic Concept for JBI (Java Business Integration) are everytime welcome. What are the advances of ChainBuilder ESB - comparing with some existing ESB-Solutions which has extended JBI-Strategies ? In my personally opinion is the Apache License a more extensible solution for enterprises ... -- BTW: A interested Article with association to JBI from here:
Is JBI Dead?. The Autor of this Article is Dain Hansen - Senior Product Manager for AquaLogic Service Bus at BEA Provides AquaLogic Service Bus ESB extended Support for JBI ? James Strachan and ServiceMix are mentioned in this Article - long time nothing to hear on TSS from James ... -- Roland SOA Kompetenznetzwerk Information & Collaboration-Portal At 20. November we are starting with a new Look & Feel and advanced Information- & Collaboration-Concept ... For the moment only in German Language - soon also in English and Spanish ...
While many of the JBI-compliant ESB solutions have focused primarily on the bus or container, we concentrate on ease of deployment using a graphical IDE and increasing functionality with more robust binding components and service engines. The main benefit of using an open standard like JBI is the ability to mix and match containers and components, possibly from different sources, to come up with the best possible solution. We provide an Eclipse-based IDE that allows you to create JBI Service Assemblies without getting bogged down in the details of the JBI specification. This allows the end user to concentrate on solving their business problem and not on learning the JBI specification. We also provide additional graphical editors to configure the service engines we provide. It seems that a lot of other JBI solutions provide a set of binding components and service engines with some basic functionality, but not full featured enough to address most real situations. The components that we introduce include functionality that we have found necessary in our previous years of integration experience. This includes more advanced file processing, the ability to handle non-XML data just as easily as XML data. We also include more advanced error handling capability that message can be saved into an error data base in case there is an error or exception instead of just disappeared in standard JBI container. This allows you to do further processing if needed. We also provide complete X12 EDI support to allow you to use ChainBuilder ESB to parse and transform complex EDI document. In addition to a typical XSLT component to transform XML document, we also provide a graphical map editor to directly generate Java code based on a map. Many complaints we hear from developers are XSLT is slow and hard to program. Our map editor takes care that problem.
While many of the JBI-compliant ESB solutions have focused primarily on the bus or container, we concentrate on ease of deployment using a graphical IDE and increasing functionality with more robust binding components and service engines. The main benefit of using an open standard like JBI is the ability to mix and match containers and components, possibly from different sources, to come up with the best possible solution.Exactly - but the object of the definition of a standard is, that it's later provided in many solutions from business and open source areas, otherwise ... Looking to the Member List of the Standard JBI ( Java Business Integration ) shows many interested providers of integration solutions which has participated. http://jcp.org/en/participation/members/ Paradoxically, when we make a List with all integration solutions, which supports today the Standard JBI - such would be a little bit smaller ... --- So, finally gives this information from Eric a closer look to the possibilities of ChainBuilder ESB and I personally think that's very interested, to take a more detailled look into this solution when the final version is available. The availability of more business-associated JBI-Components (how the mentioned EDI support with parsing of EDI Documents , ..., or some Banking Protocols, how e.g. Swift, ...) can be a way, to make the JBI-Standard still more interested for the Business Scene ... -- For the moment we are busy with the last steps of the changes of our Information- and Collaboration-Portal. But in the first weeks of the next year, we will provide an extended article over the real possibilities of some JBI-Solutions in Business Operations - maybe that's a theme which will be interested also for some guys here on TSS ... Cheers, Roland
I read the interesting article "Is JBI Dead?" by Dain Hansen. A title like that makes people pay more attention to JBI itself which is a good thing. I tend to agree that JBI standard is mostly for ESB or Integration software vendors. However, with the right technologies, corporate application developers can greatly benefit from it too. The ChainBuilder ESB alpha version has enough functionality to do a proof of concept SOA or Integration project. We focus on improving usability and reliability and adding additional binding components and service engines for our 1.0 production release. Please check out our alpha release when you have a chance. We don’t rush to add a long list of features just to compare with other products. With our long history playing in integration space, we believe that a feature is useful only if it adds business values. In future releases, we plan to add financial protocols such as SWIFT and Accord, healthcare protocols such as HL7 and HIPAA, and e-commerce protocols such as AS1 and AS2. Regards, Eric Lu www.chainforge.net