1.3 Release Notes
Release Date: May 18, 2008
New Features:
Support for Java 6
This release of Chainbuilder ESB now supports the Java 6 JDK as well as Java 5.
Under Java 6, Custom Code (UPOC, Script Component, TrxId) may be implemented in Java or Groovy. Under Java 5, Custom Code must be Java.
IDE Usability Improvements
Many improvements have been made to the Map Editor and Component Flow Editor to make development easier.
- Copy & Paste functionality has been added to Map Editor and Component Flow Editor.
- Address bar has been added to Map Editor to make it easier to navigate the Source and Target Format trees.
- Additional drag and drop capability has been added to the Map Editor to improve in usability.
- Map Editor Operation view now shows more details for all operations.
- Search functionality has been improved in Map Editor.
- New ChainBuilder menu in main menu bar makes common operations more convenient.
Improved Web Service Marshalling
The default marshaller in the HTTP Component that is used in SOAP mode now supports SOAP Headers. SOAP Headers are now available as metadata in the message exchange. An additional marshaller has also been added that sets the entire SOAP Envelope as the Normalized Message content rather than just the SOAP Body.
Admin Console Audit Logging
The Admin Console now creates an audit trail of operation performed by users. This data is written to a local database that can be accessed using a command line utility called 'cbesb_audit_log' to view or export data.
Consumer Endpoint Trigger Action on Demand
The Admin Console now includes the ability to trigger consumer endpoint action on demand by clicking a button. This can be used for consumer endpoints that operate on a polling interval or advanced schedule. For example, if a File Reader endpoint is set up to run at 4:00 PM and you would like to force the endpoint to read a file immediately, than you can click the Trigger Action button to read the file rather than modifying the schedule and re-deploying the Service Assembly.
Component Configuration File
This version exposes a set of Component level configuration settings that allow the user to tune Chainbuilder for the best performance in a certain environment. Details on the available configuration settings are available
here.
A new command line tool called "project_deploy" has been added that can be used to generate the Service Assembly artifacts (Service Unit WSDL files, jbi.xml files, etc). Previously, this could only be done from within the Component Flow Editor. After running the project_deploy command, the cbesb_deploy command can be issued to build and package the Service Assembly to be deployed.
The output messages from the Transformer Component previously would generate a field with no content for all fields defined in the message, even if the particular map did not explicitly populate the field. Now, output fields are only created if a map operation explicitly sets a value in the field.
New Custom Component - InOnlySplitter
The new InOnlySplitter component can be used to receive a message exchange (normally an In-Out), make a copy of the in message and send a new In-Only exchange to a specified target endpoint. This is useful when you want to send a copy of the message to a separate sub-flow that can run asynchronously. This component can also be used to take a single message exchange that contains multiple records and create a new In-Only exchange for each record.
The Transformer component now provides the ability to validate the source and/or target message. If the message format is XSD, then the supplied schema is used for validation. If the format is a custom MDL format, the MDL is used for validation. If a message is deemed invalid according to its definition, a Fault message is returned containing the validation error.
Improved MDL Parser Error Messages
The MDL Parser used to parse custom formats as well as HL7 and X12 have been improved to give more information when a parsing error occurs. Now, errors include the element in the message where the failure occurred as well as a portion of the data that caused the issue when applicable.
The consistent metadata supports have been added to the binding components. When a message exchange is created in the consumer endpoint, it contains the metadata for the consumer configuration. When a message exchange is passed to the HTTP provider endpoint, the returned message exchange contains the metadata for the provider endpoint.
Bug Fixes
The following issues have been resolved in this release:
| Bug ID | Description |
72 | map editor should include copy, cut, and paste before/after |
256 | base mode ftp should have option to create a response message after put |
272 | display combine operation very slowly |
297 | Tag field disappearing from format editor |
298 | alphabetize target endpoint list |
301 | SEND will duplicate some lines and skip others |
302 | Schedule got exception |
332 | File Component with Write mode overwrites the message in the file |
340 | Need ability to keep track of admin changes have been made to ChainBuilder ESB |
362 | The HL7 tester reports cryptic error message |
369 | alert email notification only fires once |
390 | Unable to delete an MDL file from the UI editor |
402 | tcpip component does not reconnect |
421 | License Agreement window should be resized or changed |
433 | Cannot move translation operation above IF-ELSE operations if it is under the IF-ELSE operations. Please refer to the attached screenshot |
434 | JDBC exec mode in translation needs to return a response to tell the user if the statement is executed successfully or not. Right now, it seems that it doesn't return any response. |
437 | lookup editor should check data for errors |
458 | HTTP component has limited metadata support |
461 | The attributeFormDefault in XSD is not suported in the mapper |
463 | file writer does not handle duplicate file names |
465 | DataSourceMap file tree item deleting problem |
475 | TCP/IP component sometimes does not connect |
491 | Installer and uninstaller to start and stop CBESB services |
496 | Format Editor shows the file in modified state when there is nothing changed |
498 | Alphabetize Varaibles when they are accessed within the Operations Properties screen |
500 | TCP/IP component retry |
535 | The "deploy" fails when there is an isolated sequencer component in a flow |
537 | The latency statistics information for TCP/IP component seems to be wrong |
541 | Can not show full error message when test connection |
542 | support Java 6 |
544 | Hierachical DataSource generate wrong sql statement in DatasourceMapper Tester |
546 | Have the ability to delete a Service Assembly if it is undeployed |
547 | WSDL Import dialog locks up eclipse if an incorrect URL is provided. |
549 | JDBC Operation error does not show up in the error database |
552 | SA's java build.xml file not include the classpath of the referred java class of ESB project level |
553 | Patch installer doesn't show previous version correctly |
554 | Alert can't be activated with endpoint status RetryStarted |
555 | JMS status doesn't change after retry has completed |
556 | HTTP Client doesn't set status to error when connection can't be made |
559 | The HTTP component throws NullPointException in some case |
561 | Missing X12 IEA segment delimiter at the end of the segment |
562 | user should not be able to start endpoint if SA is stopped |
565 | User-defined CompositeSeparator is not replacing the standard one |
566 | Property changes made in AdminConsole are not used by components |
567 | Reply JMS reliable delivery is missing reply queue |
568 | TCPIP component should have metadata support |
572 | context is lost when moving in or out of structures |
576 | repeating segments in MDL only show as repeating on first instance |
578 | Patch installer does not remove old eclipse plugins |
579 | Custom component fails to start |
580 | simultaneous MDL xlates cause error |
581 | Allow the CBR component to use metadata as a TrxID type |
589 | Having a Destination Directory that cannot exist does not throw a fault |
590 | Copy/Paste inconsistency |
593 | Cycling of all log files needs to be implemented |
594 | HL7 2.5 segment references undefined datatype |
595 | uninstaller removes license file |
596 | PGP EncryptAndSign mode should Sign and Encrypt the message in one pass |
598 | Have IF operation arithmetic type default to String |
601 | WSDL Builder Page not refresh or reload the Operation Details correctly |
603 | Add File.Input.Directory metadata value |
606 | Recoverable Fault causes exception which loses message |
608 | Comment map operation behavior |
620 | Clean up the template code for custom component |
621 | FTP script mode does not return correct status |
622 | JMS consumer processor got struck |
623 | NPE in Eclipse's runtime error log when adding a new property |
624 | Refresh issue after saving the TRN file with error |
625 | JDBC operation in Map editor |
626 | Http Client non-soap mode recieves error |
630 | Misspelt "Addtional" word in ETL Exec Config editor |
635 | Audit log can not log the password info |
644 | Fail to create an ESB project |
645 | The Professional Patch Installer does not upgrade the CE installation |
646 | Deplyment failed when using some specific WSDL file in HTTP client |
647 | Fail to create an ESB project on Linux with the Prof Edition |
650 | Client mode error with SoapHeader |
651 | Archive directory is overwritten |
652 | TCP/IP component can potentially lose one message |
653 | SwA and MTOM mode should not send message with MIME if message contains no attachments |
655 | HL7 formats are inconsistent with the standard |