Deploying Dundas BI as a server farm
Dundas BI supports multi-server deployment for load balancing purposes. In this scenario, multiple servers have Dundas BI installed but each installation points to the same Dundas BI Application Database and Warehouse Database.
From Dundas BI version 7.0 and higher, farm nodes are treated as regular instances. During deployment, each instance is installed separately and is then connected to a common application database. The application resource service feature places resources (overrides and extensions) in the application database.
2.1. For Dundas BI version 7.0 and higher
If you do not have a Dundas BI instance installed on any of your servers, follow the instructions for installing Dundas BI to install an instance. While deploying the first instance, when asked to choose the application database, you can either create a new application database or use an existing one. All the other instances must point to this common database during their deployment.
2.2. For Dundas BI version 6.0.3 and lower
The deployment process relies on a single main instance to create a farm node information file, which is then used to create additional farm nodes on the other servers. Each farm node is a replication of the main instance, but without any styles and images, and is automatically configured to use the databases and scheduler service from the main instance.
If you do not have a Dundas BI instance installed on any of your servers, follow the instructions for installing Dundas BI to install a full instance. This instance should either install or point to the application and warehouse databases to which all of the farm servers will point, and it should have a scheduler service configured.
From the Dundas BI Deployment application create a farm node information file from an instance. With the farm node information file, you can quickly create farm nodes on the other servers.
After creating the information file launch the Dundas BI Deployment application on each server, click Farm on the left and then click Create a farm node deployment.
3. Multiple scheduler services
Dundas BI allows for multiple scheduler services to be running and sharing an application database. Only one scheduler will be active at a time. The other schedulers will wait on call, and will become active if the other schedulers stop.
- Dundas BI licensing is tied to a specific Dundas BI instance which refers to everything that uses the same Dundas BI Application Database (App DB). If multiple servers are all referencing the same App DB, then additional licenses may or may not be required when you add another such server.
- The load balancer should set the following HTTP request headers: X-Forwarded-For, X-Forwarded-Proto, and X-Forwarded-Host. If the port is not already included in the X-Forwarded-Host header, an X-Forwarded-Port header should be set with the corresponding value.
- The IP address of the load balancer should be specified in the Trusted Proxy IP Addresses configuration setting in Dundas BI.
- If multiple nodes in a server farm need to override Dundas BI configuration settings with the same values, the best practice is to accomplish this using server groups. For more information, see Managing server groups.
- Custom extensions when deployed into the application database on one server are automatically copied into the local application folder and used by the other servers. For more information about Dundas BI extensions see the Understanding the Dundas BI extension format article.