 |
SageCRM Technology : Internet Architecture
|
|
 |
Related Literature: |
|
|
Unlike most CRM applications which uses client /server
technology, SageCRM solutions (SageCRM and SageCRM.com), are powered by a pure Internet architecture which is more flexible and cost efficient.
The Internet architecture of SageCRM includes
three distinct layers that communicate amongst themselves using Internet standards. The diagram below shows the functions of these layers.
SageCRM Architecture Diagram
Interface Services
SageCRM’s Internet architecture provides universal access to CRM applications for the
mobile workforce by delivering the solution within a standard Web browser, Wireless Access Protocol
(WAP) enabled device, mobile SMS device and Personal Digital Assistant (PDA).
Components within the SageCRM Presentation Layer manage the
connection between the SageCRM application and the Microsoft Internet Information Server (IIS).
The Presentation Layer detects the device type being used (browser, PDA, etc.) and outputs the user
interface in the format most appropriate for that device.
Business Logic Services
The Internet architecture of SageCRM provides a framework that enables companies to integrate
information from multiple applications into CRM solutions, making this consolidated information
available through an intranet, the Internet, and/or mobile Internet platforms.
Components within the SageCRM Business Logic Services Layer check user security, maintain user persistence (remember
what a user is doing), synchronize data with mobile users, return information from the database,
generate Web pages from data, perform transactions, process business rules and logic, and much more.
Database Access Services
All database operations in SageCRM are performed through components of the Common Database
Services Interface (CDSI) layer. To maintain data integrity, the CDSI layer validates data updates, such as
sales leads being imported to CRM from an external application, before they are written to its database.
This validation prevents any new data from corrupting the database or creating duplicate records.
Because all database access is abstracted into the CDSI layer, adaptation to a new database can be done
quickly in one place (the database driver).
|
|
|

|
|
 |
|
|
|
|
| |
|
| |
|
|
| |