Skip to end of banner
Go to start of banner

Sizing and Requirements for Billing and Rewards On-Premise Solutions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Table of Contents


Overview

This document outlines the hardware and system requirements for CRM.COM software for on premise implementations.

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.

Component

Platform

Client

PC:  Intel i3 CPU or equivalent and 1GB memory

Operating system: Windows, Mac OSX or Linux

Browser: Firefox, Internet Explorer, Safari, Chrome


Application Server (App server)


Server Machine: Any machine supporting Java Runtime (JRE)

Operating System: Windows Server or Linux Server

System Software (J2EE Application Server Software): IBM WebSphere or Wildfly Application Server

Database Server (DB server)


Server Machine: Any machine supporting Oracle, MS SQL, DB2, PostgreSQL

Operating System: Any OS supporting the above databases

Database: Oracle, MS SQL Server, IBM DB2, PostgreSQL


Sizing considerations


This section outlines the sizing considerations in sizing the hardware.

Subs means subscribers and is a general term for customers that have an active billing or reward account.

Consideration

Sizing

Pre-bill Subscribers to agent users


  • 1500 subs to 1 agent seat (logged on user) up to 500K subs
  • 2000 subs to 1 agent up to 1M subs  
  • 3000 subs to 1 agent up to 2M subs
  • 4000 subs to 1 agent for 3M agents and over


Agent users to CPU

  • 30 to 50 logged on agents per core

Billing

  • 5 to 8 bts (billing transactions per second) per core

OLTP

  • 5 bts per core

Self Service / Web


  • Dedicated server (counts as App server)
  • 100K subs per core (assume 100 user sessions per 100K subs)

Database


  • Minimum Dual Core CPU
  • Up to 16 cores of app servers: 1 core of App server to 1 core of DB server
  • Above 16 cores: 0.7 core of App server to 1 core of DB server

Memory


  • App servers: 3 to 6 GB per core
  • Database: 6 to 8 GB per core

CPU

  • Indicative min CPU type: Intel E5530 Quad Core 2.40GHz


Hardware and System Software

Hardware Configuration

Users mentioned below represent logged on users

50K Subscribers

Component

Sizing considerations

Sizing

App server(s)


  • 40 users
  • 1 x App server
  • Quad Core CPU
  • 24 GB memory

DB server


  • 1 x DB server
  • 2 x Quad Core CPU
  • 48 GB memory


200K Subscribers

Component

Sizing considerations

Sizing

App server(s)


  • 160 users
  • 2 x App server
  • Quad Core CPU each
  • 24 GB memory each

DB server


  • 1 x DB server
  • 2 x Quad Core CPU
  • 64 GB memory


500K Subscribers

Component

Sizing considerations

Sizing

App server(s)


  • 350 users
  • 2 x App server
  • 2 x Quad Core CPU each
  • 48 GB memory each

DB server


  • 1 x DB server
  • 4 x Quad Core CPU
  • 128 GB memory

Billing


  • Bill run in 3.5 hours

 

  • Use same servers


1M Subscribers

Component

Sizing considerations

Sizing

App server(s)


  • 500 users
  • 3 x App server
  • 2 x Quad Core CPU each
  • 48 GB memory each

DB server


  • 1 x DB server
  • 8 x Quad Core CPU
  • 256 GB memory

Billing


  • Bill run in 3.5 hours

 

  • Use dedicated bill run server
  • 4 x Quad Core CPU
  • 96 GB memory


2M Subscribers

Component

Sizing considerations

Sizing

App server(s)


  • 750 users
  • 3 x App server
  • 4 x Quad Core CPU each
  • 128 GB memory each

DB server


  • 1 x DB server
  • 8 x Quad Core CPU
  • 256 GB memory

Billing


  • Bill run in 4 hours

 

  • Use dedicated bill run server
  • 8 x Quad Core CPU
  • 96 GB memory

 

3M Subscribers

Component

Sizing considerations

Sizing

App server(s)


  • 1000 users
  • 3 x App server
  • 4 x Quad Core CPU each
  • 128 GB memory each

DB server


  • 1 x DB server
  • 8 x Quad Core CPU
  • 256 GB memory

Billing


  • Bill run in 6 hours

 

  • Use dedicated bill run server
  • 8 x Quad Core CPU
  • 128 GB memory


5M Subscribers

Component

Sizing considerations

Sizing

App server(s)


  • 1250 users
  • 4 x App server
  • 4 x Quad Core CPU each
  • 128 GB memory each

DB server


  • DB cluster (running Oracle OPS or DB2 Enterprise)
  • 16 x Quad Core CPU
  • 256 GB memory

Billing


  • Bill run in 6 hours

 

  • Use dedicated bill run server
  • 12 x Quad Core CPU
  • 256 GB memory


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.


  • No labels