Understanding Database Architecture
Database Administrator manages the distribution and maintenance of data in different databases. Database Administrator provides a multi-level architecture, which makes the system more robust and scalable. Databases can reside on a single computer, or can be seamlessly distributed across multiple computers.
In order to reduce the load on Main database, relevant components are replicated to other databases using Microsoft® SQL Server™ replication.
Database replication is the process of copying whole or part of a database so that two or more copies can exchange updates of data or replicated objects. This exchange is called synchronization. Each copy of the database is called a replica and contains a common set of tables, queries, forms, reports, macros and modules. A replica can also contain local objects that exist only in it.
Replication is mainly used to reduce load on the primary database server. This speeds up the system by enabling Main database to focus on Interaction management, and Media database to control the chat feature. Reports are generated from the Analytics database. The WebTrak database is used by the proactive chat feature to track visitors to the institution's website and engage them in chat sessions.
A publisher is a server that makes data available to other servers for replication. In addition to identifying the data to be replicated, the publisher detects modified data and maintains information about all publications at that site.
Tables relevant to the chat feature are replicated in Media database, and tables relevant to Analytics are replicated in Analytics database. These databases are registered as subscribers with Main database. Subscribers are servers that store replicated data and receive updates.
Main database sends updates to the subscribers on a near real-time basis. This ensures accuracy of information stored in the databases and avoids overloading the network with polling for updates.
If a computer is already configured as the distributor of a publisher, it is also configured as the distributor for all Main databases installed on the publisher.
The following diagram describes this model:
Database Architecture
The following table describes the components displayed in the above diagram.
Component |
Description |
Remote Client |
To work with the product over the Internet, the Citrix-based Remote Client can be used. This provides you with product functionality through a remote Citrix server and web-based terminal clients. |
Desktop Client |
Desktop Client is a Win32-based client that can run on Microsoft operating systems such as Windows Server 2008 and requires a TCP/IP connection to Main database. Desktop Client is the interface from which users can interact with Contacts. All Contact management tasks such as sending e-mail, running Campaigns and converting Opportunities to Orders are performed in Desktop Client. |
Web Components |
Web components comprise the web servers that are required. |
Application Server |
All clients connect to Application Server, which uses connection objects to create a temporary connection to the database and executes client requests. After the request is executed, the connection is closed and the object is sent back to the connection pool. |
Distributor database |
Distributor database is created to communicate information between Main database and the replicated databases. Main database is registered as a publisher with the distributor database, while Media, Analytics and WebTrak databases are registered as subscribers with the distributor database. |
Main database |
Main database contains all the tables used by the system. It is registered as a publisher with the distributor database. |
Archive database |
Archive database contains object records that are not being used anymore and have been archived. |
Media database |
The Media component requires both Media database as well as the chat web components that are installed on Microsoft Internet Information Services [IIS]. Web components enable users to work with the chat feature. Web components are a set of ASP pages that give users the facility to perform a web-based real-time interactive dialogue with visitors. |
Analytics database |
Analytics database contains information used to generate reports. Data is extracted from the tables and displayed in tabular form or graphically using Microsoft Excel. Analytics database is optimized for query processing, making report generation efficient and optimal. |
WebTrak database |
To utilize proactive chat, WebTrak database and WebTrak IIS components must be installed. These track visitors on specified URLs in websites that have had special Chat treatment code applied to them. WebTrak database server stores visitor details such as their IP address, visit time, current web page and so on. These details are viewed in the Chat workspace using the WebTrak IIS components. Proactive chat filters can be set up to control the visitors who qualify for proactive chat requests. |
The following table describes the main components:
Component |
Database Application Used |
Description |
CampusNexus CRMServer |
Microsoft SQL Server |
This is the server on which Main database and the other databases reside. It is optimized for transaction processing. |
Application Server |
Microsoft SQL Server |
This is the server which executes client requests and fetches data from CampusNexus CRM Server. |
Archive Server |
Microsoft SQL Server |
This is the server on which archived data is stored. |
Media Server |
Microsoft SQL Server |
This is the server on which Media database exists. This server tracks Media-related data used by features such as chat. |
Analytics Server |
Microsoft SQL Server |
This is the server on which the Analytics database exists. The Analytics engine uses this server to generate and query data needed for reports and is optimized for analytical processing. |
WebTrak Server |
Microsoft SQL Server |
This is the server on which the WebTrak database exists. This server tracks visitors on identified websites for the proactive chat feature. |
Citrix Server |
Citrix Server |
Remote access solutions provide access to CampusNexus CRM Server through the Remote Client installed on a Citrix Server. |
Database Administrator |
Microsoft Management Console |
Database Administrator is the snap-in used to administer CampusNexus CRM databases, web components, campaign dispatchers, and database-related notifications and logs. |
Business Administrator |
Microsoft IIS |
The organization's business components such as aliases, teams, users and rules are managed through Business Administrator. This module has a browser-based interface, enabling you to set configurations over the Internet. |
Media Web Server |
Microsoft IIS |
This server consists of web components required for Media. |
WebTrak Web Server |
Microsoft IIS |
This is the server that provides the web components required for proactive chat. |
Scripting |
Microsoft IIS |
Scripting is a presentation tool that ensures standardization of response and enables call centers to draw techniques from the experience of their best agents. |