Web

• Web browser. Sage CRM has a thin client configuration, therefore users can access and work with Sage CRM by using just a web browser. This can be any web browser supported by Sage CRM.
• Application server. The Sage CRM application server includes a number of components, which work together to coordinate the delivery of information and functionality to Sage CRM users. These components are used to implement user security, maintain user persistence, read and write information in the Sage CRM database, generate web pages from data, and process business rules and logic. The application server also runs the eWare.dll file, which is the Sage CRM dynamic link library. Web Server (IIS) communicates with Sage CRM via eWare.dll and Internet Server Application Programming Interface (ISAPI) technologies. eWare.dll and Web Server (IIS) must be on the same server.
• Microsoft SQL Server. This server hosts the Sage CRM database that stores corporate data and metadata, which define the Sage CRM screen configurations, system customization, security, and business rules.
• Mail server. You can connect the application server to this optional component to automate the sending of emails and SMS messages as part of the Sage CRM implementation. To customize the email functionality, you can use the CRMEmail object, and the CRMMsgHandler object and its child objects. You can also use the CRMMessageBlock object to send messages in SMS and email format.
• Apache Tomcat Redirector. The redirector in Sage CRM is an ASP.NET Reverse Proxy, which is a 32-bit/64-bit ASP.NET web application configured in standard Apache format. This ASP.NET rewriter uses the HTTP protocol instead of binary socket and can be accessed directly in a browser, so you can easily check if Tomcat is working. For more information, see the Installation and Upgrade Help on the Sage CRM Help Center and articles on the Sage CRM Community.