Versions Compared

Version Old Version 1 New Version 2
Changes made by

Persia Xenopoulou (Deactivated)

Persia Xenopoulou (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

Table of Contents

 

1        Introduction.. 3

2        Sizing considerations. 5

3        Hardware and System Software.. 5

3.1          Hardware Configuration.. 5

3.1.1           50K Subscribers. 6

3.1.2           200K Subscribers. 7

3.1.3           500K Subscribers. 8

3.1.4           1M Subscribers. 9

3.1.5           2M Subscribers. 10

3.1.6           3M Subscribers. 11

3.1.7           5M Subscribers. 12

3.1.8           Incremental Implementation Clause. 13

3.1.9           Other Implementations. 13

3.2          Disk Subsystem.. 13

3.3          System Software. 14

3.3.1           Operating System for the Application Server(s) and Database Server. 14

3.3.2           J2EE Application Servers for the Application Server(s). 14

3.3.3           Database Engines for the Database Server. 14

3.4          Installation topology. 15

3.5          Other optionally required components. 16

3.5.1           IVR.. 16

3.5.2           Email server. 16

4        Test Environment.. 17

 

 

 

 

 

 

 

Introduction

 

 

Overview

 

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

...

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

...

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 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:

...

  • Also 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

 

...

 

Other optionally required components

...

If you require to send emails or run email campaigns through the CRM.COM Software, then you require a TCP/IP connection to any SMPT 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.

...