Previous Topic  Next Topic

Managing a Logi JReport Server Cluster

In the Logi JReport Server console, if you are an administrator you can administer the servers in a cluster. For example, you could configure the performance weight for the clustered servers, balance the server load to make the servers work more effectively, and if there is a Logi JReport Server Monitor installed, use it to monitor the status of each clustered server.

Below is a list of the sections covered in this topic:

• Configuring Performance Weight
• Balancing the Server Load
• Monitoring Clustered Servers

Configuring Performance Weight

If you have chosen the Weighted Min-load (loadbalance.type=2) algorithm for load balancing when creating a cluster, you will have to configure a performance weight for each clustered server in the cluster. The higher performance weight you set to a clustered server, the higher chance it may get selected by the server that has the active scheduler during load balancing.

To configure performance weight:

1. Start a clustered server in the cluster and log onto the server console.
2. Point to Administration on the system toolbar, select Configuration > Cluster > Weight from the drop-down menu to display the Weight page.

   

3. In the weight table, specify a weight value for each clustered server manually. Performance weight is a positive float number.
4. Select OK to save the weight values.
5. If you want to test each clustered server's performance weight value at current time, specify a catalog and a report that will be used for the testing in the Catalog and Report text boxes and then select the Test button.

The following are two examples for how Least Weighted Current Reports algorithm works:

Example 1 - when there are free servers:

Example 2 - when there are no free servers:

Balancing the Server Load

In a cluster environment, Logi JReport Server provides a load balancing mechanism which enables the server to work more effectively.

Load balancing process

1. When the time of a scheduled task arrives, active schedulers compete and the winner gets to trigger the schedule.
2. The server that has the active scheduler selects a server in the cluster according to the load balancing algorithm specified which can either be a built-in one or a customized one, and then sends the task to the selected server.

You can also write your own load balancing algorithm based on the API included in Logi JReport Server. For details, see Writing Customized Load Balancing Algorithm via API.

Monitoring Clustered Servers

If you have Logi JReport Server Monitor installed, you can use it to monitor the status of each clustered server.

Before you can use Logi JReport Server Monitor to monitor servers in a cluster, the following steps must be taken:

1. Modify the server.properties file in <monitor_install_root>\bin to configure the IP address and port information of one clustered server.
2. Copy rmi.auth from <server_install_root>\bin of the clustered server whose IP address and port information you modified in the last step to <monitor_install_root>\bin, or remove rmi.auth from <server_install_root>\bin of this clustered server.
3. Start Logi JReport Server.
4. Launch MonitorServer.bat in <monitor_install_root>\bin to start Logi JReport Server Monitor.
5. Access Logi JReport Server Monitor using http://monitorhost:monitorport (default 8848), or by selecting Monitor on the Administration > Other drop-down menu in the Logi JReport Server console.

   Note: Monitor is not displayed on the Administration > Other drop-down menu in the server console when the web.monitor.link.enable property in the server.properties file in <server_install_root>\bin is set to false. You can specify the monitor port by setting monitor.jmx.htmladaptor.port in server.properties.

Previous Topic  Next Topic