Deployment Options

There are 2 deployment options available for SysforeHRMS :
  • On-premise, cloud hosted deployment (Amazon EC2 / Windows Azure)
  • On-premise server within the network deployment

Cloud hosted deployment

You can have a production ready system setup on public cloud environments like Amazon's EC2 or Windows Azure. Sysfore will help set this up for you on a custom basis, depending on your specific requirements.

There are pros and cons when deciding between a cloud hosted deployment and an on-premise deployment environment. You will have to choose your mode, depending on the specifics applicable to your situation.

Few advantages of a cloud deployment are:
  • Reduced Cost– When your application is running on the cloud, your IT Staff costs are lesser as they don't have to perform the tasks of maintaining the servers, networking, OS and overall computing infrastructure for this. These are taken care of by the cloud services provider
  • Easier mobile computing- The strict security protocols applicable to a corporate network, make it difficult for mobile devices to have proper access to enterprise business applications, but on the cloud hosted model, access authorizations are more effortlessly taken care of
  • Financial benefits– Instead of investing in capital expenditure in buying servers, software, bandwidth etc, you incur only operating expenses in a cloud hosted environment, freeing up cash flow
  • More robust and reliable environment – Public cloud service providers build their infrastructure to support high-speed, load-balanced environments to support the demanding needs of their customers Hence they have quick and easy ability to scale quickly without having to incur capital expenditure and time for sourcing equipment
  • Increased Application Availability/Performance– Large public cloud service providers have multiple, geographically dispersed data centers, and have provisions to deploy customer applications closer to the end user delivering better response times and decreased outage
  • Quick time to production– You can get started with a product and live application much sooner when it is deployed on the public cloud service, than getting it all deployed together and ready for production in your own environment

Few reservations regarding a public cloud deployment are:

  1. Data control risks – If sensitive data is being hosted on the public cloud, then it is important to screen the service providers for strong security controls, data backup and Disaster Recovery Strategies implemented by them to prevent System downtime/ Data loss etc, that would arise from any lax on the part of the public cloud service provider in terms of security controls and other external data loss risks.

On-premise deployment

System Requirements

Client Server Architecture

Client: Hardware
To use web interface of SysforeHRMS, any modern office Workstation/Laptop would work. Since SysforeHRMS is a web application it can be used on any device that is capable of running current web browser (see browser´s system requirements for a bare minimum). As with most web based applications, a faster CPU and more RAM makes the GUI snappier and more pleasant to use. Larger displays also make users more productive using wide grids, forms and multiple tabs. To give an example: a computer with an i3 processor with 4GB RAM and display with a 1680x1050 resolution is a comfortable setup for the SysforeHRMS web client.

Client: Web Browsers
It is strongly recommended to use at least the recommended versions of the mentioned browsers to ensure a better user experience as SysforeHRMS does benefit greatly from the improved performance in those versions.

Web browserMinimum Version requiredRecommended version
Chrome 8 9 or higher
Firefox 3.6 4 or higher
Internet Explorer 7 9 or higher
Safari 5 5 or higher

Client : Network Connectivity
Here there are example configurations, depending on the number of concurrent users to be supported. These assume the server is hosted with a fast connection so its network is not a limiting factor.

Downstream BandwidthConcurrent Users
3Mbit/s <=10
10MBit/s <=20
100Mbit/s <=100

Note: As every usage scenario is different and there is no standard, the real bandwidth usage in practice may differ from those given above.

Server [Host] : Java based = multiplatform

SysforeHRMS runs wherever the Java JDK works. This currently means:
  • Operating systems: Windows, any Linux distribution, FreeBSD, Mac OSX, Solaris and more
  • Architectures: x86, x86_64, IA64, Sparc, PowerPC, AIX

Either PostgreSQL or Oracle should also be supported by your target system

Server: Software Stack

Stack ComponentMinimum RequiredRecommended VersionNotes
Java 2 SE 1.6.0 Latest 1.6.x Sun JDK, OpenJDK and IBM JDK supported
PostgreSQL >=8.3.5, 8.4.x, 9.0.x Latest 8.4.x With UUID support enabled (contrib)
Oracle 10gR2, 11g 11gR2 Oracle XE not supported
Apache Tomcat 6.0.x Latest 6.0.x Tomcat 7 not supported
Apache Ant 1.7.1, 1.8.x 1.7.1 -
Apache HTTP Server 2.2.x Latest 2.2.x Optional but recommended
Apache mod_jk connector 1.2.x Latest 1.2.x Optional but recommended
Apache Tomcat Native 1.1.x Latest 1.1.x Optional but recommended

Note: If a new major version is not listed here it means it is not yet tested and it is not officially supported.

Server: Hardware Sizing

Optimal concurrent usersDatabaseArchitectureBandwidthHardware equivalence (single server)
3 PostgreSQL 32-bit (x86) 2Mbps Dual Core 2GHz, 2 GB RAM, disk 10000 rpm
15 PostgreSQL 32-bit (x86) 4Mbps Core 2 Duo 2GHz, 3 GB RAM, disk 10000 rpm
25 PostgreSQL/Oracle 64-bit (x86_64) 4Mbps Core 2 Duo 2GHz, 8GB RAM, disk 10000 rpm
65 PostgreSQL/Oracle 64-bit (x86_64) 4Mbps Quad Core 2.6GHz, 8GB RAM, disk 10000rpm
100 Oracle 64-bit (x86_64) 10Mbps App Server: Quad Core 2.6GHz, 8GB RAM, disk 10000rpm
DB Server:
Quad Core 2.6GHz, 8GB RAM, disk 10000rpm


  • The above table is an averaged estimation of the hardware resources required to support implementation of the Sysfore HRMS Application instance in terms of the CPU, physical RAM and hard disk speed. Even if the hard drive capacity is not specified, it should always be higher than 100GB. However, Sysfore strongly recommends to test customer installations before going live
  • For "on premise" installations it is recommended to be more conservative and apply a security factor (looking at the next level hardware configurations or more CPU speed, more RAM and the faster disk) so that we all can be more confident that the hardware will be able to cope with the requirements