Scaling Jedox


Standard setup (both for Linux and Windows) installs all Jedox components on a single machine. Several software components are represented by different service daemons that listen on different network interfaces/ports. This standard layout is most widely used and acceptable for most situations.

 In the standard setup, both power users (application designers) and application consumers use the same instance to develop and use the application:

For more information on standard setup, see Jedox Web Services and Configurations.

Scaling by clustering

The standard layout may not be sufficient in some scenarios, depending on the number of users/concurrent sessions and data volume. The initial hardware system may be unable to handle network throughput, latency, and system availability. In that case, clustered system layouts may provide improved performance.

Jedox can be configured to split the load between two hosts, one of which is running the OLAP and Integrator components and the other running the Web and Spreadsheet components. You can use a standard setup (both Windows and Linux) to install all components on both systems and then make adjustments to both (remove unused components/services and/or adjust config files). You could also configure Jedox across multiple hosts, each of them running a separate Jedox component.

One option could be to add additional web instances (in addition to the main instance) that handle separate user groups, e.g. one user group always uses instance number 1, etc.:

Adding a load balancer adds even more flexibility to the system: