ENTELLIFLOW

Introduction

Advantages

Product Description

Technical Description

ROI

 

EntelliFlow TECHNICAL DESCRIPTION

EntelliFlow is based on the Microsoft .Net framework.  Data is saved throughout the system in  XML format, a W3C consortium standard, which provides automatic compatibility with a wide variety of programs and access from systems located anywhere in the world.

EntelliFlow provides a Simple Object Access Protocol (SOAP) API.  SOAP provides a standard object invocation protocol built on Internet standards, using HTTP as the transport and XML for data encoding.  Dynamic HTML is used to ensure screen formatting is consistent between clients.  This standard is also supported by the W3C consortium.

Architecture - The architecture of EntelliFlow makes use of the .NET framework version 1.1 architectural model.  EntelliFlow utilizes flexible architectural elements, the most important of which are its web services.  The software employs message-based interfaces suitable for being accessed across the Internet, intranets or extranets.  By utilizing this architecture, EntelliFlow offers flexible deployments such as deployment on several networked computers.  EntelliFlow is designed and built based on best practices in design for distributed enterprise applications.

The services provided by EntelliFlow Web Services use a layered design which can be broken into four logical layers.

XML Format

EntelliFlow data and controls are exchanged in XML format optimizing system portability, flexibility and compatibility.  The string-type, XML-based data format employed by EntelliFlow ensures that the Web services can be used regardless of platform.

Database Connections

EntelliFlow's Web services rely on the database connection pooling provided by the System.Data.SqlClient.SqlConnection object. The connection pool contains connections for all concurrent Internet users. The Web services use connections from the pool and release them whenever they are not required, making the connections available to other users. The more quickly the connections are released after use, the more concurrent users the Web service is able to handle.