Introduction

This document outlines the ServiceMobility hardware requirements, sizing and IT knowledge prerequisites for customers deciding to host ServiceMobility in their data center.

The requirements listed in this document are sufficient enough for a 5000 mobile user installation. However, there are many factors that can affect the final size including; actual number of mobile technicians, number of jobs per day, frequency at which the technician communicates with the server, amount of history retained, photo capture requirements, and video chat, to name a few. 

ServicePower consultants work with the customer during the blueprint phase to determine the final production server sizing requirements. After the blueprint phase and for smaller installations, it may be possible to combine servers and functionality. 

Notes:

• ServicePower does not recommend any specific high availability (HA) related hardware
• ServicePower strongly recommends customers configure separate development and QA instances
• The CPU configurations in this proposal are specified as a Virtual CPUs (vCPU). One vCPU provides the equivalent CPU capacity of a 2.0 GHz Opteron or Xeon processor (circa 2007)

Disclaimer of Warranty

IT Knowledge Prerequisites

ServicePower assumes that any customer deciding to host the ServiceMobility solution have the required IT staff and required knowledge to support such a complex system. Specifically, the IT staff must be knowledgeable in the following areas:

• Windows Server 2008 R2 setup, configuration and monitoring
• Java VM monitoring
• Network firewall configuration
• Network routing
• Network load balancing
• SSL certificates and configuration in a Java environment
• High Availability (HA)
• Network Attached Storage (NAS)
• Storage Area Network (SAN)
• RAID
• Server / database clustering
• Master / slave failover configuration
• Server and network monitoring
• Server backup and restoring 

NodeJS Server Requirements

The NodeJS services provide the following:

• Hosting of all web applications
• ServiceMobility application deployment
• JWT Authentication and authorization services
• Entry point for all REST APIs

Hardware Requirements

• 2 vCPU
• 8 GB RAM
• 50 GB System Partition
• 20 GB Application Partition

Software Requirements

• Operating System Options
  • RedHat Enterprise Linux 7.0+ (Preferred)
  • Windows Server 2008 R2+
• Java 8+
• Node.JS 4.2.1+

High Availability

• Requires a minimum of two servers
• Simple load balancer - either hardware or software

RedHat JBoss A-MQ

JBoss A-MQ provides a persistent message store for transactions destined to mobile devices, transactions received from the mobile devices, and acts as a message bus for the FUSE ESB Servers. While JBoss A-MQ is based on the open source Apache ActiveMQ project, ServicePower has selected the RedHat distribution for production release in order to gain 24x7 support and hot fixes of critical bugs. 

Hardware Requirements

• 4 vCPU
• 12 GB RAM
• 50 GB System Partition
• 20 GB Application Partition

Software Requirements

• Operating System Options
  • RedHat Enterprise Linux 7.0+ (Preferred)
  • Windows Server 2008 R2
• Java 8
• RedHat JBoss A-MQ 7.2

NAS / SAN Requirements

• 200 GB Data Partition
  • RAID 1 or 6
  • Actual data partition size may be adjusted up or down based on the results of the system blueprint phase

High Availability

• High availability requires a minimum of two servers
• Configure JBoss A-MQ in a shared file system master / slave topology
• Requires Network Attached Storage (NAS) or Storage Area Network (SAN)
  • NFSv4+
    
• For more information refer to the following RedHat document
  • https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_A-MQ/6.2/html/Fault_Tolerant_Messaging/FMQFaultTolMasterSlave.html#FMQMasterSlaveShared
    

RedHat FUSE ESB

RedHat FUSE ESB processes all inbound transactions from the mobile devices, provides a collection of REST APIs used by the Planner web application, and exposes a collection of REST APIs for integration to backend systems. 
While FUSE ESB is based on the open source Apache ServiceMix ESB project, ServicePower has selected the RedHat distribution for production release in order to gain 24x7 support and hot fixes of critical bugs. 

Hardware

• 4 vCPU
• 16 GB RAM
• 50 GB System Partition
• 20 GB Application Partition

Software

• Operating System Options
  • RedHat Enterprise Linux 7.0+ (Preferred)
  • Windows Server 2008 R2+
• Java 8
• RedHat FUSE ESB version 7.2

High Availability

• Requires a minimum of two servers
• Configure FUSE ESB in a shared file system master / slave topology 
• For more information refer to the following RedHat document
  • https://access.redhat.com/documentation/en-US/Fuse_ESB/4.4.1/html/Clustering_Guide/files/Failover-MasterSlave-Shared.html

Microsoft SQL Server 

 Hardware Requirements

• 4 vCPU
• 24 GB RAM
• 50 GB System Partition
• 20 GB Application Partition
• 200 GB Data Partition
  • RAID 1 or 6
  • Actual data partition size may be adjusted up or down based on the results of the system blueprint phase

Software Requirements

• Operating System Options
  • Windows Server 2008 R2+
  • Windows Server 2012 R2+
• Microsoft SQL Server 2008 R2+ Enterprise Edition
• Microsoft SQL Server 2012+ Enterprise Edition

High Availability

• High availability requires a minimum of two servers
• ServicePower recommends using SQL Server Enterprise edition with database mirroring

ElasticSearch Server

ElasticSearch is used by ServiceMobility to provide advanced searching capabilities within the ServiceCenter web application. ServiceMobility also leverages ElasticSearch to store all system log information providing advanced analytics capabilities. 

Hardware Requirements

• 4 vCPU
• 16 GB RAM
• 50 GB System Partition
• 20 GB Application Partition
• 200 GB Data Partition
  • Actual data partition size may be adjusted up or down based on the results of the system blueprint phase

Software Requirements

• Operating System Options
  • RedHat Enterprise Linux version 7.0+ (Preferred)
  • Windows Server 2008 R2+
• ElasticSearch 1.5.2+
• Java 8

High Availability

• Cluster (recommended)
  • Cluster of 3 or more nodes
  • In this configuration RAID is not required
• Single Server (not recommended)
  • RAID 1 or 6 is highly recommended for single server installations

Related Links