End user, you operate the JoramMQ application and directly benefit from its execution. If you maintain an internal IT service you may also take on the programming task.
The project includes all phases from realization to operation, going through test and deployment. It assumes a single operational deployment of the application, but allows as many simultaneous executions as required during the programming and debugging phases.
When you deploy a large application, you are likely to set up a validation platform to prepare for the actual deployment and future evolutions. This deployment is also included in the configurations supported by the project based support packs from
Our standard Silver pack has been designed for this reference use case where the end user takes on the whole application life cycle. The pack includes solutions for any number of execution issues raised during the development or operation project phases, and a pool of 16h development support on the first year, more dedicated to questions arising during the application programming or deployment.
When continuous operation is critical, we commit to start working on short notice, even off standard working time.
The standard offer targets simple JoramMQ configurations, i.e. limited to 4 interconnected servers. Complex (up to 16 interconnected servers) and very complex (more than 16 servers) configurations require more resources, and are supported through an additional option.
version 2.1, february 9, 2012 120209-support-en-v2-1.pdf [65.1 kb]
on standard hardware
|Debian 6.0||ext3||Sun/Oracle 6|
|Debian 7.2||ext3||Sun/Oracle 6/7|
|Centos 5.10||ext3||Sun/Oracle 6|
|Centos 6.4||ext3||Sun/Oracle 6/7|
|Windows XP||NTFS||Sun/Oracle 6|
|Windows 7 (64)||NTFS||Sun/Oracle 6/7|