Scaling Jedox


Standard system layout

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; see Jedox Web Services and Configurations for more information. Both power users (application designers) and application consumers use the same instance to develop and use the application:

Alternative system layouts

The standard layout may not be sufficient in some scenarios, depending on the number of users/concurrent sessions, data volume. Network throughput, latency, and system availability may be unable to be handled by the hardware initially used. In that case, alternative system layouts may be implemented.

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.:

See also:

Scaling Jedox in Windows (clustering)
Scaling Jedox in Linux (clustering)

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

Configuring services to run in a multiple-host scenario

Provided you will be splitting the load between two or more hosts, one of which is running the OLAP component and the other is running the Web, Spreadsheet, and Integrator 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).