Overview of EE
The Template Designer is a powerful graphical interface. Using the Template Designer, a user can create reusable EE components for connectivity to either source or destination data. Templates store metadata (data about data) information based upon their graphical configuration. The internal data layout is represented by Blocks, which is analogous to a relational table. Each block will contain the actual data columns associated with the data source. When deployed to the server, each template configuration describes the type of data, the data location, access instructions and the selection criteria needed to retrieve the data.
Using the Active Integration Interface (Aii) Designer, a user can create rules and methods to control data transformation between source and destination templates. Mapping source data to destination data is achieved by simple drag-and-drop. This allows disparate types of data (i.e. relational data, plain text, etc.) to be used together as a single “data source” for processing. In addition to data mapping, the Aii Designer provides a simple interface to create any combination of logical conditions and formulas.
Each process design is represented by a flow-sheet. A process contains Trigger Nodes, Process Nodes, Transition Nodes and Process Variables. The user can drag-and-drop these nodes to create a custom executable process. When deployed, the executable process can be triggered by an event or a by ad-hoc request. One of the most common nodes is the Strongly Named Transformation Node which uses an Aii to perform data transformation. Upon execution of this node, the chosen Aii will execute the Aii’s designated source and destination templates.
Our Enterprise Master Service (EMS) Designer creates virtual data definitions. This allows data to be consumable by applications, databases or devices. EMS definitions support secure write-back to any back-end system. This provides out of the box data federated live from multiple sources packaged for virtual consumption as a web service (SOAP, JSON, REST, OData) and also as ADO.NET, JDBC, ODBC, and as an External List for SharePoint BCS, all done without staging or programming and without limitations to XML and Web Services.