Ready for your Middleware Platform
EBX.Platform is a middleware-neutral MDM / Data Governance Software. Rather than reinventing the wheel on data integration, you can leverage your existing middleware infrastructure.
Deploying an Enterprise MDM / Data Governance solution requires a complex, multi-mode integration with your IT systems. Synchronization of your reference and master data with your IT systems depends on multiple criteria and technical contexts:
» Life cycle: some data such as products have very long life cycle from creation to publication, others like parties are much more volatile
» Sharing: some data are shared with all your IT systems with a low update frequency, others are shared with a limited number of systems but with near real-time integration
» Upstream/Downstream: some data are authored centrally and then pushed to your existing systems, others are updated locally, then validated centrally and re-synchronized with target systems.
Most MDM vendors propose software packages with embedded data integration / quality features. While it can be perceived as simpler solution, the reality is different: Your information systems already runs on multiple middleware solutions, from basic ETL to high-end SOA platform.
» Why reinvent the wheel on data integration?
» Do you really need another ETL/ESB just for MDM?
» Why not reusing existing integration technologies?
» Can you really rely on one integration solution?
» What if you decide to change your middleware stack or add a new one?
At Orchestra Networks, we think that your MDM / Data Governance solution must leverage your existing middleware infrastructure. With EBX.Platform, you get the reassurance of a "Middleware-neutral" software that can be connected to your current integration technologies as well as your future ones.
To achieve this, the EBX.Platform relies on a standard-based interface that has been successfully tested and deployed against leading middleware solutions.
See also: D3 - Distributed Data Delivery for distributing your reference and master data to SOA
Our customers have successfuly deployed EBX.Platform connected to:» Informatica Powercenter » IBM DataStage » Microsoft BizTalk » Tibco ESB » Software AG webMethods » Oracle Data Integrator
» IBM WebSphere ESB
» Progress DataXtend & Sonic ESB» Open source ETL solutions
.. and more ..
Please contact us for details.
How the EBX.Platform leverages your existing middleware platform?
EBX.Platform provides a set of technical interfaces that allow the connection of your central Data Governance / MDM repository to virtually any middleware solution:
» Data Services: Web Services (SOAP/WSDL) dynamically exposed based on your data model definition. Supports HTTP & WSSE authentication, WS-I compliant.
» XML: Native import/export of XML files based on XSD Data Model definition
» CSV files: Web Import/export of CSV flat files
» Java API: Full Java API for connection to any Java application. Fine integration in IDE's (Eclipse)
Combined together, these interfaces support all integration scenarios (batch, real-time) between EBX.Platform and multiple integration solutions (ETL, ESB, Data Quality, BPM...).
Secure integration using Branches
EBX.Platform has been successfully deployed on multiple integration scenarios for synchronizing data with IT systems. Thanks to the EBX.Platform branching technology, it is possible to manage "virtual staging areas" for importing data into the repository. For instance, three systems can import data in three concurrent and isolated branches. When merging branches, EBX.Platform performs automatic validation and detects potential conflicts between data. Conflicts can be resolved manually by data stewards or automatically by applied rules.
In addition, when exposing data to the information system, the EBX.Platform allows the management of versions. These versions are a snap-shot of a branch and provide a fixed reference for all systems.
» Downstream integration: Data are updated centrally and propagated in target systems
» Upstream/Downstream integration: Data are updated in both the EBX.Platform and the source system, then reconciled centrally and re-synchronized with target systems.
|
|
|
