|
Architecture

Enterprise Enabler Server is a Microsoft based technology that integrates processes, applications, and data sources residing
on Microsoft and non-Microsoft platforms.
.net Framework
Enterprise Enabler is built on the .net 2.0 Framework and leverages all the features and enhancements of the Framework. All
of the features are also passed on to the end users of EE, allowing them to easily build plug-ins, reusable code snippets , business
rules, process nodes and AppComms (see below). In addition, EE supports the reuse of any libraries written in .net/com outside
of EE, so that they become reusable components accessible through the standard EE development environment.
AppComms
AppComm technology can be thought of as the next-generation of Adapters. It is the connectivity mechanism used by EE to communicate
with various applications and data sources, regardless of the platform on which they reside 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 Adapter is a full integration in itself, with predetermined source, destination, and mapping. An AppComm, on the other hand
is completely metadata driven and reusable in its "off-the shelf" form without any modification. The AppComm architecture is
always streaming, and offers high speed native connectivity.
Metadata
All aspects of EE are metadata driven, so metadata is captured about applications and connectivity, about how data transformation
should occur, and about business process workflow. External metadata is discovered and captured through intelligence built into each
AppComm, and iInternal 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. All metadata is stored, encrypted
and compressed, in SQL Server 2005.
Runtime Engine
EE's runtime engine is architected to take advantage of multiple application domains to isolate each process instance, and within
each domain multithreading is utilized to further support parallel processing. The result is high performance and scalability, with
robustness enhanced by isolation which greatly reduces potential for severe failure.
|