Case study:
EMG at Mblox (PDF)
EMG Hardware FAQ Print
Wednesday, 05 March 2014

Enterprise Messaging Gateway (EMG) is delivered through downloading and all that is required is a valid license. Hardware must be purchased locally after which the EMG can be installed. Please see below FAQ for more information about hardware considerations.

On what platforms can EMG run?

The EMG is rather "lightweight" and can run on any Linux or Sun Solaris (Sparc or x86) server. Our experience shows that entry-level servers are normally adequate for very high throughput (hundreds, or even thousands, of messages per second). Please also see these benchmark measurements:

I plan to have a traffic throughput of a maximum of 10 messages per second at peak time. What servers can you recommend?

For example, the Dell PowerEdge R320 with Red Hat Enterprise Linux with a "Base" configuration (4 GB RAM, 2 x 500 GB hard drives mirrored using RAID-1) would be more than adequate. However, any server in a similar configuration from your prefered hardware vendor will do the job equally well.

Do you have any measurements / tests of the EMG on different servers?

Please see some EMG 5.2 benchmark results at:

Are there any hardware configurations to consider?

The exact hardware details are up to you and your current IT environment. Some customers prefer less expensive entry-level servers which can be easily replaced if they fail and some customers prefer "beefier" configurations with lots of built-in redundancy. We recommend at least some redundancy in the disk configuration (RAID 1/5/10), at least 200 GB of disk space and a minimum of 4 GB RAM internal memory. SCSI/SAS disks still tend to be more fail-safe than SATA disks.

The amount of RAM needed depends mainly on expected queue sizes and the amount of disk space how long log files need to be archived.

Can we get help from you setting up our hardware?

Unfortunately we can only support EMG issues and we cannot keep up-to-date with all hardware options. During first installation of the EMG we can be available for technical support via e-mail or phone.

Can you provide a detailed bill of material (BOM) for the EMG Server?

We only deliver software and cannot keep updated as hardware options evolve and change rapidly. You can therefore plan the new configuration to fit your IT environment and are welcome to send us any questions you might have.

Do I need a database?

No, a database is not required to run the EMG. However, depending on what applications you intend for the EMG a database might be necessary.

Is there any 3rd party software required?


I am ready to install the EMG on the server. Is it hard to install and configure?

With the EMG User's Guide, the installation and configuration is rather straightforward and most of our customers choose to install EMG themselves. We will of course be happy to answer any questions that may arise or we can perform installation remotely via SSH or similar access. This may be subject to a consultant fee.

What lead times do you have on hardware and EMG software?

The hardware you purchase locally with the lead times of your local supplier. The EMG software can be downloaded any time, including a 30-day evaluation license. A commercial license might take up to two (2) work days from receiving a correct PO. Once the hardware is in place you can be up and running after a very short period.

What about high-availability and redundancy?

Please check our technical article available.

How do I increase the speed of sending through the EMG?

Upgrading the license allows for increased speed in the following increments 10, 20, 40, 60, 80, 100, 140 and unlimited messages per second. Unlimited means that the EMG has no license restrictions and only the hardware and external connections limit the throughput.

Can I use shared storage for EMG?

EMG can use shared storage for configuration files, log files and spool directory. It is important that only one active instance of EMG access the writable files (log and spool directories) at any given point in time or data corruption will occur.

When high (100+ mps) performance is required it is common that the storage device can become the bottleneck. Enterprise-class storage is required which supports a sufficient level of iops. Low-end NAS devices will not work well for a production deployment.

As part of our benchmarks we use NFS shares on Oracle Unified Storage hardware (14 x SAS disks).