2.1 Beta1 Release Notes
Release Date: February 23, 2009
New Features:
Upgrade of Third Party Libraries
More third party libraries have been updated to the latest stable release including Apache Derby, Apache Axis2, Jetty and iBATIS.
BLOB and CLOB support in ETL
The ETL Component now provides support for fields defined as BLOB and CLOB. The data in large object fields can be handled in ChainbuilderESB as an attachment in a NormalizedMessage or as part of the XML message. The Data Source Map Editor provides the setting for this on any field defined as BLOB, CLOB, LARGEVARBINARY or LARGEVARCHAR.
JMS Component Improvements
The JMS component has been improved to include support for JTA transactions in both consumer and provider modes. It now also has performance and scalability improvements which allow better processing under heavy loads. This includes the ability to configure a JMS consumer endpoint to have multiple concurrent consumers. This allows multiple messages to be read from a queue and processed simultaneously.
Parser and Serializer Scalability Improvements
The message parser and serializer that handles all non-XML messages, including X12 and HL7 has been improved to provide better performance, especially under heavy loads.
Runtime Database Support for Additional Databases
The Runtime Database, which by default uses Derby, can now be configured to use an alternate database server. The databases that are currently supported are: Oracle, MySQL and Microsoft SQL Server. The runtime database is used for the Admin Console settings, error database, user database and SMAT.
Improved DATE and TIME Macro Support
The {DATE} and {TIME} macros are used in the File or FTP component to generate the file name based on the current timestamp. They are extended into the {DATE("pattern")} and {TIME("pattern")} formats where the "pattern" is any string value that is described in Java's
SimpleDateFormat class
.
Alias Support in Data Source Map for Table Join
In the Data Source Map editor, when you drag a source table into a target table that has the name, the editor will prompt to define an alias for the source table. This functionality allows you to model the SQL join with same table.
New OnSuccess and OnError Settings in ETL Consumer wizard
You can now define two different post-select actions in ETL consumer:
- OnSuccess: the type of post-select action that will be executed when a message exchange returns without any fault.
- OnError: the type of post-select action that will be executed when a message exchange returns with a non-recoverable fault.
Miscellaneous ETL Runtime Improvement
- The Etl_response message in the OUT normalized message returned from ETL provider endpoint contains detailed information about which tables and how many rows affected by the operation defined in the message exchange.
- The ETL provider endpoint can support multiple records in the IN normalized message.
Bug Fixes
The following issues have been resolved in this release:
| Bug ID | Description |
476 | The "Build Clean" in Flow editor fails when CB ESB sever is running |
837 | Move of multi-selected items does not work |
907 | empty translate file prevents other translates from building |
923 | Script component UPoC does not work |
939 | Merge the code changes from 2.0 branch into trunk |
941 | Out of memory error occurs in HTTP wizard |