Multiple Instances of Live Access

Live Access, with Birst Connect, communicates with Birst to execute queries for reports in a space. The following instructions and diagrams show how this communication and processing occurs.

Tip: Live Access is configured using Birst Connect, and requires Birst Connect in order to extract data and execute reports. For a related diagram showing the Birst Connect topology, see Birst Connect.

Setting Up Multiple Instances of Live Access

For better load balancing and performance you can set up two or more instances of Birst Connect running the same Live Access configuration for one space.

For best results, set up and run Birst Connect as a Windows service. See Running Birst Connect as a Windows Service.

Create the Live Access configuration. See Creating a Live Access Connection.

Implementation Notes

• Load balancing works on a first-come, first-serve model and the load may not be equally distributed.
• The instances must use the same configurations.
• It is a best practice to set up the instances on different machines, however you can set them up on one machine. For best results the Birst Team suggests a maximum of 6 instances overall. For optimal use of machine resource allocation put no more than 3 instances on a single machine.
• The queries run in parallel, without any additional configuration.

One Live Access Instance and One Server

Live Access polls Birst every one minute, and executes any returned request on its own thread.

Live Access can handle multiple requests from Birst concurrently.

Multiple Live Access Instances and One Server

The process flow is the same if you have multiple instances of Live Access.