CRM.COM News
LTV successfully upgrades CRM.COM Software and goes live with Triple Play. Read more
CRM.COM Signs Agreement with AVG JSC for Provision of SMS & Billing Software
AVG selects CRM.COM to provide an SMS & Billing platform for their DTT and DTH operation in Vietnam. Read more
CRM.COM is Hosting Two Loyalty Events in June
CRM.COM is hosting two events in June 2011: Loyalty for Card Issuers and Loyalty for Retailers. Read more
SMC become Authorised CRM.COM Agents in Africa for Pay TV
SMC partners with CRM.COM to promote and sell the CRM.COM Pay TV SMS and Billing solutions in Africa. Read more
CRM.COM Articles
Work on-line with your subsidiaries, affiliates and dealers to serve customers, cross-sell products and services, and outsource work. Read More
Web or MS Outlook access channels
Access CRM.COM Software functionality from a variety of web-based desktops or MS Outlook. Read More
Training & Events
Brochures
Increase the efficiency of all your CRM processes with CRM.COM software extensive coverage of ALL sales, service, marketing and operations functions. Download brochure
Business on-demandIntroducing the CRM.COM Software solution that automates all business processes. Download brochure
Logical Architecture
The following diagram shows the logical software architecture of CRM.COM Software.
As shown in the diagram, CRM.COM Software is divided into 3 Tiers, namely: Client Tier, Middle Tier and EIS Tier. The Middle Tier consists of the Web and EJB containers. As depicted on the diagram above the functionality can be described in terms of steps:
| STEP 1 |
The client operates in a Zero Client Mode sending only HTTP requests through the browser. |
| STEP 2 |
The Controller layer handles all client requests. The controller components are responsible for detecting user input and possibly calling the domain model, which is done through a Controller Session bean. |
| STEP 3 |
The Controller Session Bean attempts to locate the JNDI name of the requested Session EJB and calls it using Reflection since the method name and EJB name are String representations. |
| STEP 4 |
The requested EJB in turn interacts with Hibernate using HQL |
| STEP 5 |
Hibernate then translates the HQL to native SQL (SELECT, INSERT, UPDATE, DELETE) and executes it against the RDBMS using the JDBC driver of the appropriate RDBMS. |
| STEP 6 |
Hibernate receives a Result Set back from the database (in case of a SELECT statement), maps the flat data into the appropriate entity BOs (DTO) |
| STEP 7 |
The DTOs are returned back to the EJB for further processing |
| STEP 8 |
The DTOs are returned to the Controller Layer of the application as the result of the method invocation on the EJB |
| STEP 9 |
The Controller adds the DTO(s) in the Struts form, which in turn resides in the HTTP session and selects the next view for the client. |
| STEP 10 |
The View components are the ones that generate the HTTP response. The HTML components are fed with DTO data (e.g. Contact). The generated HTML is then returned back to the client (browser) |
Session Beans can connect to more than one database server. Master Partner (this is the Company concept in CRM.COM Software) host their data in separate logical databases isolated from each other. Usually Master Partner databases reside in different database server boxes. Alternatively, one database box could host more than one Master Partner database.
Apart from the Master Partner databases there is another database called eCentre database. This database keeps system information about all Master Partners that exist in the system (the eCentre). eCentre information includes CRM.COM Software content and user information.
The web components residing in the web container dynamically control the way the user interface will be presented. JavaScript is used to enhance the user interaction with the browser.