Product architecture
ProgressCRM is a .NET application, running on SQL Server 2005. ProgressCRM offers a range of interfaces:
The diagram shows the architecture of a ProgressCRM solution.
For office-based users, ProgressCRM's Windows interface is underpinned by the database's business logic, or ‘object framework' written by Fisk Brett. This in turn runs on Microsoft's .Net framework, on a SQL Server platform.
Other business systems, or websites, do not need the Windows interface. These systems access the Object framework using XML messages via a ProgressCRM XML web service. Customer websites can also link to ProgressCMS- Content Management System-, which in turn accesses data from the Object framework via XML web services. ProgressCMS runs on Microsoft Internet Information Server (IIS), underpinned by SQL Server Reporting Services running on the .Net framework on the SQL Server platform.
To access data remotely, users would use the ProgressCRM browser interface. This links to the database object framework via IIS, and mobile devices connect to data in the same way.
System requirements
'Fat' client PC specification for Windows interface
Pentium 4 2Ghz or better, 256MB RAM or greater, screen resolution 1024x768 or greater, 16bit colours or greater. Microsoft Windows 2000 Professional or XP Professional, mouse, keyboard, 20MB or more available hard disk space. For links to Microsoft Office you will need Office 2000 or later.
'Thin' client PC specification for Windows interface
PC or Apple Mac running remote desktop protocol (RDP) - application served on a Windows Terminal Services server. See Microsoft website for more information.
Database server specifications
The server specification is dependent upon the number of ProgressCRM users and the size of your database. These specifications are based upon dedicated use of the server for the database:
Dual Pentium 4 or later or Dual Xeon, each 2Ghz or faster, 2Gb RAM or greater, screen resolution 1024x768 or greater. Microsoft Windows Server 2003, mouse, keyboard, 50Gb or more available hard disk space, SCSI RAID 5 (or higher) disks and disk controller, Microsoft SQL Server 2005 Enterprise edition.
Local Area Network bandwidth
In order to deal with medium data volumes you should run ProgressCRM over a 100mbit network. For larger data volumes it is also recommended that you have a 1gbit link between the hub and server.
Notes:
- There are many factors beyond our control which can affect the perceived performance of ProgressCRM - speed and volume of network traffic, virus checking software, servers being used for more than one purpose and so on - therefore, these specifications are not a guarantee of performance in any environment.
- ProgressCRM may run on a lesser specification computer but performance will be compromised.
- ProgressCRM will not work on 800x600 resolution, or less.
- Servers running both Exchange Server and SQL Server may experience performance problems, both are resource-hungry systems and therefore you should be prepared for the need for a dedicated database server,
- Please ensure your server is equipped with a tape backup system, or at least that the data is backed up by a tape system from another server. ProgressCRM databases do not make their own data backups. Most popular tape backup systems will back up SQL Server databases. Backing up data is your responsibility and should be part of your organisation's backup policy.
- Fault tolerance - it is your choice as to whether you wish to add fault tolerant features to the server, such as RAID, fail-over power supplies and network interface cards
- If we are not supplying you with Microsoft SQL Server you will need to supply it. ProgressCRM Standard edition needs Microsoft SQL Server 2005 Enterprise edition, with sufficient Client Access Licenses for the total ProgressCRM Windows users.
