Architecture

i-enable sd is built using several components connected to one another, each providing a specific functionality. Components that perform similar types of functions are generally grouped into layers. These layers are further organized as a stack in which components in a higher layer use the services of components in the layer below. A component in a given layer will generally use the functionality of other components in its own layer or the layers below it. The diagram below shows a popular layer structure of an i-enable sd application.

Presentation Layer:
The presentation layer is what the user actually sees. It features aspx pages, code behind classes, AJAX, Web Services, textboxes to use inputs and message boxes to give alarms to the users of the operation on their action, and by passing messages to the business layer to communicate with datastores.

Business Layer:
The business layer generated by i-enable sd consists primarily of services that are generated from classes defined in the model.  These services can be used directly as classes in application code or they can easily be wrapped in an ASMX Web service.

Data Access Layer:
The data access layer passes the business entities to the business layer which performs business logic using these entities.
 
Data Stores:
Since i-enable sd-generated applications use wrapper classes to access the data, you can use any of the databases (MySQL, Microsoft SQL Server, Oracle). Additionally, LDAP and external Web services are sources to the application for a specific function.