The JBI components that constitute Open ESB evolve separately and therefore can provide varying levels of support for systemic qualities. A goal of the Open ESB project is to ensure that all components promoted from Incubator to Released provide a consistent set of Systemic Qualities which will enable the component to be used in a production environment.

What are Systemic Qualities?

Yes - Implemented
Not Applicable
Implemented in Open ESB. To be included in next update release for Glassfish ESB

• Application Configuration: Allows configuration changes without re-build and deploy cycle
• Logging: Configure component Logging properties
• Password Handling: This initiative seeks to provide a common mechanism for components that need to handle authorization and authentication through the use of user names and passwords. All the components store and display passwords in non-cleartext way-
• Management & Monitoring: Consistent management and monitoring information across components. Monitor the state of the JBI runtime entities and to view the history as required to administer the JBI portion of the runtime
• Re-delivery: Re-delivers a message for a configured amount of times
• Throttling: Number of current ACTIVE Message Exchanges in NMR can be configured per service basis
• Serial Processing: Provide the a user configurable facility that allows control over which messages must be processed in order and which can be processed as the arrive
• Change Management of WSDLs and XSDs: It should be easy for developers to make changes to XSDs and WSDLs by making use of design-time Project and Document References
• Configuration consistency/usability: Consistent look and feel of configurations. Consistent conceptual understanding of similar configuration items
• Component upgrade: Composite applications remain deployed while the component is upgraded. Pre-upgrade component configuration and workspace are preserved. Component is aware that an upgrade has taken place and may participate in the upgrade process if required.
• Recovery: All components to recover gracefully from failure, including failure of other components internally and externally; and dealing with faults/errors in a manner that does not compromise message reliability. When components are available again the re-connect and resends should occur without explicit user actions.
• Security propagation: Provide context propagation in related Message Exchanges between JBI Components
• Transaction propagation: Provide transaction context propagation in related message exchanges between JBI Components
• Optimized payload handling (Unique message id): The user can choose what chunk of "records" to process within the context of one message exchange in JBI
• Message property propagation: Allows users to access and change Normalized Message configuration during run time
• On demand read: Allows users to access data (File content, Get a file content from remote location, etc...) from middle of business logic

This page (revision-19) was last changed on 28-Oct-09 03:07 AM, -0700 by Gopalan Suresh Raj.
This page was created on 26-Feb-09 09:31 AM, -0800 by FrankKieviet.

More info...