You have been lied to about integration.
You’ve heard all the hype and spin about business integration platforms. You were told - "No problem... The ERP platform you just bought will integrate "seamlessly" with your existing line-of-business solutions." Only after you spent three years and hundreds of thousands if not millions of dollars can the truth be told - you were lied to!
That's why we built Enterprise Enabler®. It’s easy for us to use words like revolutionary, innovative and groundbreaking when we talk about Enterprise Enabler (EE). We prefer that you take a look at all the unique features of EE and come up with your own description.
Why are we different and why isn't this just another lie about integration?
To start with, we were tired of perpetuating the lies when we were at other companies. We didn't want to be part of the problem and knew there had to be a better way to solve the technology debt crisis.
We don't use adapters.
Agile Integration - Revolutionary, Innovative and Groundbreaking
How did we come up with the answer?
If you are working on business integration platforms, you know that an adapter is a full integration in itself with predetermined source, destination, and mapping. Enterprise Enabler doesn’t use adapters. To put it bluntly - we saw the light!
AppComms
Enterprise Enabler utilizes AppComm technology. AppComms are the connectivity mechanism used by EE to communicate with applications (point-to-point, multi-point and enterprise) and data sources.
Interesting isn't it? It gets better -
Compare the characteristics of an adapter and an AppComm and some things will become clearer:
I’ve heard enough I want to test drive Enterprise Enabler
Bi-directional, Real-time Data Flow
The unique architecture of Enterprise Enabler enables real-time, bi-directional flow of data. The intelligence and adaptability of the AppComm is a key part of this capability but the use of shared, native metadata end-to-end is another key capability.
Metadata drives all aspects of Enterprise Enabler. Metadata about applications and connectivity is captured. Metadata about how data transformation should occur and about business process workflows is captured. The intelligence built into each AppComm discovers and captures external metadata while internal metadata is captured during integration development. The existence of metadata describing processes and integration allows for the computerized monitoring and management of change and its impact across the environment.
Imagine what you could achieve with that kind of flexibility and adaptability.
Keep going…
Enterprise Enabler AppComms Technology Advantage
AppComms automate the discovery of data schema for any application or data store. Once discovered, it will save the data schema as metadata. This provides the ability to have a virtual connection with real-time and on-demand access to the data and to start the aggregation of data. Since the schema information is stored as metadata, it never necessary to compile and deploy assemblies when creating or modifying a dynamic data model.
AppComms are part of an architecture that decouples the knowledge of how to connect to a particular type of application or data source from the assumptions about the specific instance. An AppComm is completely metadata driven and is reusable in its "off-the shelf" form without any modification. Furthermore, the AppComm architecture is always streaming, and offers high speed native connectivity.
Powerful? Easy? Time-saving? There’s much more…
No More Transformation Mapping or Data Caching
Enterprise Enabler does not require data caching and essentially does not transform the data, unlike other business integration software. EE creates virtual data relationships by the use of native metadata and direct relationships of information. Data relationships and mapping are resolved at run time, when the data is transferred thus avoiding the need for the conventional transformation engine, mapping or staging.
This unique approach permits easy integration of many-to-many in mixed relational and hierarchical formats and connectivity to proprietary formats.
EE's run-time engine make use of multiple application domains to isolate each process instance, and within each domain, multi-threading further supports parallel processing. The result is high performance and scalability combined with robustness enhanced by isolation that greatly reduces the potential for severe failure.
What will you do with all the time you’re going to save? We’re far from being finished…
No More Coding
That’s right – zero coding. Can it be any plainer than that? We could talk about the intuitive, highly graphical process development EE provides.
Transactions and compensating activities, process flows (using decision nodes) and the data mapping of complex mixed relational and hierarchical input and output are developed visually. Relationship building between heterogeneous data sources is done visually. Metadata building for processes, mapping, and endpoint schemas is also a graphical process.
Easy…simple…and, straightforward. Any question about that?
Okay. We said revolutionary, innovative and groundbreaking. What do you say?
We know what developers look for in business integration software: easy process development, the flexibility and adaptability to handle data no matter the source, format or transport protocol, etc. …and, most of all minimizing the time and tedium it takes to create, troubleshoot and validate a project.
We hear you. That’s why we created Enterprise Enabler.
We have only covered some of the highlights here. There is so much more to EE. To see true power that EE can put in your hands check out all of capabilities and features of this cutting-edge integration software…
I’ve heard enough I want to test drive Enterprise Enabler
Also, read about what means to deploy Agile Enterprise Integration Software (AIS).
Read our other White Papers and Case Studies…