Versions Compared

Key

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

...

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

...

This section outlines the sizing considerations in sizing the hardware.

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

...

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

...

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

...

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

...

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

...

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

...

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

...