The e-Logics FRAMEWORK is a component based software application configuration and development toolset that can be used to build, expand and integrate software systems. The toolset is meta driven and through the Management Console provides the technical team the ability to configure or change/maintain the business objects and interfaces and also link business logic to events. We rely on the FRAMEWORK as the platform for tailor-made software solutions and further products development. Because of its configuration ability, implementation timelines are reduced which results in less cost and quicker return on investment.
The e-Logics FRAMEWORK benefits our customers through:
Rapid Application Development
Reliability of Custom Software
Ability to alter the application behavior to support changes in business needs
The user interfaces of the e-Logics FRAMEWORK is based on Microsoft Windows standards for ease of use. The interfaces can be deployed through the following technologies:
Smart Client The Smart Client is an intelligent local PC based application that can connect to the FRAMEWORK Server Service via a LAN or Internet. The Smart Client has the ability to work off-line and Synchronise data when connected.
Mobile Client The Mobile Client is an ideal interface for field data capturing.
Web Client To deploy to “unknown” user via the Internet, the Web Client can be used as a basis.
The Server Service is the heart of the e-Logics FRAMEWORK. It ensures adherence to the business logic to all connections through the various Enablers.
Business Objects
A class defines the structure and behavior of all objects within the FRAMEWORK. A class consists of attributes (properties) and triggers (events). The attributes are used to define the content and structure of a class and the triggers are used to define the behavior of a class.
Once a class has been defined in the metadata it can be used by any of the FRAMEWORK components, for example the Data Management or Enabler Interfaces components.
Classes can be grouped together on two levels. Firstly on a user defined level known as class types and secondly on an internal or behavioral level known as functional types.
A class type is purely a user defined type and has no significant meaning internally to FRAMEWORK components; it usually defines how and where the class is displayed. A class with a specific functional type has a predefined behavior. For example, a class with a functional type of meta will be treated as a metadata class and will have a fixed set of rules that defines its behavior.
Another OO concept used in the FRAMEWORK is that of relationships. Relationships are used to define a class in relation with other classes.
The relation between classes defines their structure, restrictions and behavior.
Operations Manager
With the FRAMEWORK, you can define custom business rules on a set of predefined triggers. Triggers are events in the FRAMEWORK on which custom business rules can be ‘hooked’. For example, if there are users who need to be notified when a specific property of a class changes, an event can be set up that will send a notification when that property is changed.
Business rules can be implemented in any of the supported operation languages:
.NET Components
Stored Procedures
Database Functions
Business rules can also be linked together to form a chain of operations that will be executed in a specific order and allowed to share state. This enables modular operations to be implemented and reused.
Notifications and Events Notifications are messages that can be sent to a list of subscribers when a specific event occurs. Notifications can be as simple as an email or SMS message, or as advanced as an XML message that is posted to a specific URL.
Notifications can be triggered by business rules or a timer. The FRAMEWORK enables implementers to set up and store their own notifications.
Security Security is split into two tiers, the first being data security and the second application security. The data security is handled by the Server Service. Data security grants users the right to View/Add/Edit or Delete data according to configurable rules. Any user will always only have rights on data as defined in the system. Because this is done in the Server Service, data security is consistently implemented through the whole system built using the FRAMEWORK.
Auditing Auditing is a subsystem that when configured can audit any data changes. Auditing can be done in three levels.
Logging: This keeps track of who changed what data when.
History: This keeps track of who changed what data when, and exactly what the changes were.
Approval: This builds on the history, but allows certain users to approve or reject changes made by others.
The Server Service has various options to communicate with Client Applications. Communications protocols include TCP/IP, HTTP or HTTPS. Encryption and Compression is also optional.
Data Adaptors
The Server Service accesses data with a Data Adaptor interface. The FRAMEWORK has interfaces to all major databases or data stores as a standard, but the Data Adaptor interface enables the FRAMEWORK to easily connect to almost any data source. Remoting and Caching The FRAMEWORK can execute in a number of configurations depending on the environment, which allows implementers to optimize the performance of the application depending on the available infrastructure.
Web and Messaging Services Web Services can be built using the FRAMEWORK to implement the business logic.
Data Loader
The FRAMEWORK also contains an ETL engine. This can be configured and used as is, or it can be extended by implementing any or all of the Extract/Transform/Load components.
Synchronization
Data synchronization can be done by the FRAMEWORK. Bidirectional synchronization and replication are supported. Although most databases support synchronization the FRAMEWORK allows for synchronization between different database systems. For example, synchronize between an Oracle database to a SQL Server database or from an Oracle database to Microsoft CE.
