Overview

This document outlines the hardware and system requirements for CRM.COM software for billing solutions.

CRM.COM software is a web based, 0-client, n-tiered application. It is developed entirely on Java and fully conforms to the Java Enterprise Edition (JEE) standard.

The Client tier can be any PC running any browser. The Middle tier can be one or more servers running a J2EE compliant application server (Application Server). And the EIS tier can be one or more servers running a Database such as Oracle, DB2, PostgreSL or MS SQL (Database Server).

The suggested network bandwidth per logged on user for the client tier is between 50-100 Kbits/ sec.

The following table outlines the execution platforms.

Sizing considerations

This section outlines the sizing considerations in sizing the hardware.

Hardware and System Software

Hardware Configuration

Users mentioned below represent logged on users

50K Subscribers

200K Subscribers

500K Subscribers

1M Subscribers

2M Subscribers

3M Subscribers

5M Subscribers

Incremental Implementation Clause

For implementations of 500K subscribers and over (1M, 5M and so on), we suggest incremental scaling of the HW sizing. The reason for suggesting this is because our sizing represents typically the maximum possible sizing requirement, whilst your particular usage pattern might require considerably less hardware requirements. We therefore advice our customers to expand incrementally the number of CPUs and Memory.

Other Implementations

For larger implementations or for implementations with special requirements like numerous interfaces or batch jobs, please contact CRM.COM for a detailed sizing

Disk Subsystem

All above configuration require a highly available external disk subsystem:

• No single point of failure
• RAID data redundancy
• In terms of sizing assume 300 KB per subscriber (excluding images and scanned documents), i.e 300GB for 1M subscribers when migrating subscribers to CRM.COM
• For startup projects and existing CRM.COM customers we advise a disk size growth of 2KB per active subscriber per month
• For 1M subscribers and over we suggest where possible solid state disks

System Software

Operating System for the Application Server(s) and Database Server

The following are supported:

• MS Windows Server
• Red Hat Enterprise Linux
• Preference on RHEL 7
• CentOS Linux
  • Preference on CentOS 7

J2EE Application Servers for the Application Server(s)

The following are supported:

• IBM WebSphere

• Wildfly

Database Engines for the Database Server

The following are supported:

• IBM DB2
  • Including DB2 Express

• Oracle
• MS SQL
• PostgreSQL

Installation topology

The CRM.COM install topology is as follows:

• The CRM.COM Software is installed as an EAR under the J2EE Application server. Each Application server runs an independent copy of the J2EE Application server and CRM.COM
• The database server runs as a pure database server with no CRM.COM components installed on it. High availability (a cluster) can optionally be setup and is transparent to the application layer
• A load balancer / router that supports JSession is required in order to balance the http and https requests on the Application servers
• Disaster Recovery options can be optionally discussed and setup

Other optionally required components

IVR

To integrate an IVR system to the CRM.COM Software, it is advisable to select an IVR system that is able to integrate on line to our software via web service calls through http over port 80.

Email server

If you require to send emails or run email campaigns through the CRM.COM Software, then you require a TCP/IP connection to any SMTP compliant email server.

Test Environment

A test server is advisable to be setup, to run both the Application Server and the Database server. Sizing wise we suggest a similar server to one of the App servers of the corresponding configuration.

The test server should be loaded with the same versions of the customer selected system software.