ChainBuilder ESB 1.1 with Framework for Custom JBI Components


News: ChainBuilder ESB 1.1 with Framework for Custom JBI Components

  1. Bostech Corporation has announced the general availability of ChainBuilder ESB 1.1, advancing the Service Oriented Architecture (SOA) solution in several strategic areas. The flagship feature set of this release is a custom component framework for creating, customizing and deploying service components built using the Java Business Integration (JBI) specification. The release also adds critical HL7 Healthcare message support and the capability to create solutions that leverage disparate applications which use TCP/IP, POP3, IMAP and SMTP protocols. For a free open source download of ChainBuilder ESB 1.1, visit Highlights of the enhancements in ChainBuilder ESB 1.1 are: • Custom Component Framework: This plug-in framework allows developers to create JBI-compliant components and manipulate them in the ChainBuilder ESB Component Flow Editor, significantly reducing the complexity of developing and deploying a JBI compliant solution. A new project wizard allows developers to create new JBI compliant components with most of the "JBI plumbing" automatically generated, leaving the developer to concentrate on the core logic. • HL7 (Healthcare Level 7) Message Support: HL7 is the predominant messaging standard in the Healthcare industry. ChainBuilder ESB 1.1 includes the standard library from HL7 v2.1 to 2.5 and an HL7 Editor to modify or create message definition based on the standard. ChainBuilder ESB also supports the TCP-IP based HL7 Minimum Low Level Protocol (MLLP). • TCP/IP Binding Component: A new TCP/IP Binding Component provides server or client functionality. The Binding Component includes a handler framework with the ability to implement application-level protocols, such as HL7 MLLP. • Email Binding Component: A new Email Binding Component supports POP3, IMAP and SMTP protocols. Attachments can be handled as files on the local file system, or as attachments in a JBI Normalized Message. • Scheduling Support for the File, FTP, Email and Script Components: Each of the components that operate on a polling interval can now be scheduled using a Unix Cron-like schedule. A special "Auto-Retry" type of schedule is available to trigger a job at a specific time, and to automatically retry the job until it completes successfully or the end time is reached. The schedules also support Holiday schedules where the normal process is suspended on the specified days • SSL support and a Certificate Manager : SSL configuration settings are available for Server and Client modes for the TCP/IP and HTTP Binding Components. In support of SSL configuration settings, Key Stores and Trust Stores are created in the IDE using a new Certificate Manager Wizard. The wizard guides users through the common scenarios of anonymous, self-signed, and certificate authority (CA) signed certificate. • New Eclipse Plugins: ChainBuilder ESB 1.1 includes two new editors to simplify the creation of configuration files. The Holiday Schedule Editor configures holiday schedules and the Lookup Table Editor easily configures the lookup table used in the Map Editor. In addition, new Eclipse plugins are available to support testing in the HL7 Editor, X12 Editor and Format Editor. • Endpoint Configuration via Admin Console: As the component configuration settings are exposed as a custom JMX MBean, the web-based Admin Console can change the component configuration settings on-the-fly at run-time. • Apache ServiceMix 3.1 Support: The runtime JBI container shipped with ChainBuilder ESB has been upgraded from ServiceMix 3.0 to 3.1. For a complete list of enhancements for ChainBuilder ESB, visit the ChainBuilder ESB wiki at:
  2. Congratulations Eric, this is a good news for the JBI community. Raffaele
  3. Thanks Raffaele. It is a little bit late. But congratulations on your JBI4ejb release. Regards, Eric
  4. Really like the JBI approach, brings back memory with using the Cocoon framework for "composite" solutions based on XML (sitemap) bus concept. The Cocoon framework was way to ahead of its time... Now, what ChainBuilder's position with reagrd to SUN's NetBeans 6.0 CASA (Open ESB) offerings? SUN is leveraging all of SeeBeyond's past into NetBeans SOA and JBI components. Don't work for SUN, just been working on a Healthcare project and looks like ChainBuilder's features are a sub-set of NetBeans/Open ESB stuff. Anyway, again, great news for JBI and the folks that need to break away from all those "lock-in" integrations vendors!
  5. Thanks for the comments. We collaborate with Sun's Open ESB project including sharing components. In fact, Chainbuilder's TCP/IP component is also an OpenESB JBI component project. We differ from OpenESB in several areas: - ChainBuilder ESB IDE is Eclipse plugins. We hope it will be more appealing to developers who have already used Eclipse. - ChainBuilder ESB is designed to be JBI container agnostic. We ship with Apache Servicemix and we tested with OpenESB. This give users more flexible deployment options. - We focus on easy to use. OpenESB requires you to use BPEL for any process flow. We offer simpler way to configure flow. We believe BPEL is too complex for our target users. We will offer BPEL as an option in the future for more advanced users. We hope these are enough differentiator between ChainBuilder and OpenESB. Regards, Eric