Jiwa 7 | ERP Infrastructure Guidance

Introduction

Jiwa 7 is a client server native Microsoft Windows application utilising MS SQL Server as both the database store and some business logic rules. Selecting the most appropriate infrastructure requirements will vary from organisation, dependent on such factors as:

  • Number of concurrent users
  • Existing infrastructure
  • Geographical locations
  • Software licencing costs

This document aims to provide some general guidance on the infrastructure requirements an organisation will have when deploying and growing with Jiwa Financials.


Jiwa 7 in the Cloud deployment

Jiwa 7 runs equally as well in the Cloud or on premise. There are many different hosting companies who can provide the security and up-time you require to host Jiwa 7 off your premises so that you can access your data from your offices or from anywhere in the world.

The choices you need to make are around security of your data, backup of your data, your current equipment maintenance costs and what that will be into the future. You will also need to consider your current infrastructure (current age and longevity), and your current internet upload and download speeds. Run this link at your office to see how fast your current internet connection is. www.speedtest.net.

speedtedt

This speed test above is a great result from a fibre connection to the internet.  The Download / Upload speed of around 20Mbps / 0.50 Mbps are what you usually get with ADSL2.  The 0.50 Upload will be your Branches Download speed, so hosting offsite may be a good option vs. running a server at your offices.


Small deployments (1 to 5 users)

small deployments

Figure 1 - Simple Topology for small deployments

As a general rule, small deployments of between 1 and 5 users are deployed with the Jiwa client installed on the desktop machines of each user, and each client communicating with the MS SQL Server via direct LAN connection.

For any geographically remote users, it is recommended to utilise a Remote Desktop Services server (RDS) as discussed in the medium sized deployments section below.

As the number of users rises above 5 users, the management burden of deploying patches and providing a consistence user experience increases. Whilst the infrastructure will certainly handle more concurrent users easily, the cost benefit of moving to an RDS scenario becomes apparent.


Hardware and Software requirements

MS SQL Server

Feature

Recommendation

CPU

1 x Physical Xeon

RAM

8GB ECC RAM

DISK

2x (or more) 72GB or (better) 15K SCSI

RAID

Caching RAID controller with 256MB RAM, 2 Channel

POWER

Redundant PSU

SOFTWARE

MS Windows Server x64 2008R2 or 2012
Microsoft SQL Server x64 2008R2 or 2012 (Workgroup*, Standard or Enterprise Edition)

*Note that the Workgroup edition of SQL Server will not be able to address more than 3GB of RAM.

Workstation

Feature

Recommendation

CPU

Intel Core i5 or better

RAM

4GB RAM

DISK

Single 80GB or better SATA

SOFTWARE

MS Windows 7 or 8

For ultra-small deployments of 1 or 2 users, the SQL Server can be installed on a desktop machine, and the free edition of MS SQL Express could be utilised when cost is a significant factor.  Whilst this solution will not scale well, it does eliminate the hardware and software cost of a dedicated MS SQL Server.


Medium Sized Deployments (5 to 50 users)

medium deployments

Figure 2 - Topology for medium sized deployments

Management is a primary concern with medium sized deployments. Managing software on many tens of desktops can be difficult and time consuming. For that reason, a Remote Desktop Services (RDS) server is utilised.

The RDS Server hosts a Windows desktop environment for each user on the RDS Server, and the presentation layer (screen, keyboard, mouse and audio) is relayed to and from the physical users desktop and the RDS Server. As this technology utilises the RDS Server's hardware for running the application, the hardware requirements for each desktop are reduced considerably.

As the applications installed on the RDS Server are shared amongst all users, an application needs only to be installed once on the RDS Server, saving considerable time in installation and maintenance.


Hardware and Software requirements

MS SQL Server

Feature

Recommendation

CPU

2 x Physical Xeon

RAM

16GB ECC RAM

DISK

5x (or more) 72GB or (better) 15K SCSI

RAID

Caching RAID controller with 256MB RAM, 2 Channel.  RAID 5 or 6 recommended.

POWER

Redundant PSU

SOFTWARE

MS Windows Server x64 2008R2 or 2012
Microsoft SQL Server x64 2008R2 or 2012 (Standard or Enterprise Edition)

RDS Server

Feature

Recommendation

CPU

2 x Physical Xeon*

RAM

16GB ECC RAM*

DISK

2x (or more) 72GB or (better) 15K SCSI

RAID

Caching RAID controller with 256MB RAM, 2 Channel

POWER

Redundant PSU

SOFTWARE

MS Windows Server x64 2008R2 or 2012
Microsoft SQL Server x64 2008R2 or 2012 (Standard or Enterprise Edition)

*The exact ram and CPU requirements will depend on the number of expected concurrent users.  Allow 512MB and 10% of a logical CPU core per concurrent user as a guide.

Workstation

Feature

Recommendation

CPU

Intel Core i3 or better

RAM

2GB RAM*

DISK

Single 80GB or better SATA

SOFTWARE

MS Windows 7 or 8


Large Deployments (50 to 200 users)

When the single RDS Server topology is unable to cope with the number of concurrent users, then the topology needs to change to introduce multiple RDS Servers.

Technology such as virtualisation or Citrix can be utilised to automatically load-balance users onto the most appropriate RDS Server, or a manual designation can be used.

The management burden is increased with each additional RDS Server, as the applications and patches will need to be installed maintained on each RDS Server.

As the organisation grows, and the number of concurrent users increased, additional RDS Servers can be added to spread the load.

As MS SQL Server cannot have its workload distributed in this fashion, the only alternative is to scale the MS SQL Server hardware up – that is, to increase the RAM, CPU and disk capabilities.

large deployments

Figure 3 - Topology for large sized deployments


Hardware and Software requirements

MS SQL Server

Feature

Recommendation

CPU

2 x Physical Xeon

RAM

16GB ECC RAM

DISK

5x (or more) 72GB or (better) 15K SCSI

RAID

Caching RAID controller with 256MB RAM, 2 Channel.  RAID 5 or 6 recommended.

POWER

Redundant PSU

SOFTWARE

MS Windows Server x64 2008R2 or 2012
Microsoft SQL Server x64 2008R2 or 2012 (Standard or Enterprise Edition)

RDS Server

Feature

Recommendation

CPU

2 x Physical Xeon*

RAM

64GB ECC RAM*

DISK

2x (or more) 72GB or (better) 15K SCSI

RAID

Caching RAID controller with 256MB RAM, 2 Channel.

POWER

Redundant PSU

SOFTWARE

MS Windows Server x64 2008R2 or 2012
Microsoft SQL Server x64 2008R2 or 2012 (Standard or Enterprise Edition)

*The exact ram and CPU requirements will depend on the number of expected concurrent users.  Allow 512MB and 10% of a logical CPU core per concurrent user as a guide.

Workstation

Feature

Recommendation

CPU

Intel Core i3 or better

RAM

2GB RAM3

DISK

Single 80GB or better SATA

SOFTWARE

MS Windows 7 or 8


Other Related Recommendations


  • Laser Printers, JIWA’s reports and forms are set up for A4 paper by default.
  • Microsoft Terminal Services and / or Citrix Metaframe to significantly enhance JIWA’s speed over a Wide Area Network;
  • Microsoft Exchange Server should not be on the same server as JIWA unless on a “small” network 100Mb Network Cards in the Server & Workstations.
  • 100Mb Hub or switch;
  • 100Mb Network Cabling;
  • An appropriate backup system should be part of the network;
  • Dedicated Server (preferred) – especially if Microsoft Exchange Server is also on the same local area network.