Example 1: Setting Up a Simple Logi Report Server Cluster

This topic describes how you can configure a simple Logi Report Server Cluster by modifying the configuration options in the server console of each Logi Report Server, as an administrator.

Example description:

Set up a simple Logi Report Server Cluster via the server console. Assume that Logi Report Server Monitor has been installed on your computer.
The cluster consists of two copies of Logi Report Server on one computer.
The cluster uses one server DBMS.
The cluster uses shared directories for resources, so no resource copies are required.

Take the following steps to set up the cluster:

Install the two Logi Report Servers respectively to C:\LogiReport\Server1 and C:\LogiReport\Server2 using the cluster enabled license key.
Launch the Logi Report Server installed to C:\LogiReport\Server2.
Access the server console of Server2 using port 8888 as an administrator, point to Administration on the system toolbar, select Configuration > Service from the drop-down menu, then set Port to 8883 to make it different from that of Server1. You may use any port number which is available on your system.
Point to Administration on the system toolbar, select Configuration > Cluster > Configuration from the drop-down menu to display the Configuration page.
Specify a cluster name and select the Enable Cluster option, then select Save to enable the cluster.
Restart the Logi Report Server installed to C:\LogiReport\Server2.
Log onto the server console of Server2 using the port 8883 specified in step 3 (http://localhost:8883) as an administrator.
Go to the Administration > Configuration > Cluster > Configuration page, leave the Load Balancer Type as Round Robin.
Select the Cluster Scheduler Lease option to enable lease for the cluster, then set the active count, valid time and check interval for the cluster scheduler lease.
Change the Cluster Storage History, Realm and CRD Result Number of Copies to 1. We will just use one resource directory.
Keep the default value 2 for Cluster Memory Storage Number of Copies, thus 2 memory copies will be shared in the cluster.
Select the Notify via E-mail When a Server Is Down option, and in the E-mail Address text box, type the e-mail addresses of the people to whom you want to send a notification e-mail.
Keep the default values for Properties Directory, Realm Directory, Resource Root, History Directory and Temporary Files Directory.
Type the IP address or host name of Server2 in the Server's RMI Host text box and type the port number in the Server's RMI Port text box.
The port is the RMI port of the clustered server. The default port number is 1129. If there are two or more Logi Report Servers started on one machine, the RMI port number of each clustered server must be changed to a unique one, in order to avoid port conflicts.
In this example, the port number is changed to 1130, since the other server will use the default port number 1129.
Select Save to accept all the changes, then shut down the server.
Edit C:\LogiReport\Server2\bin\dbconfig.xml and remove the lines with auto-start-derbyservice. We only want Server1 to start the server DBMS since we will always use the Server1 database.
Launch the Logi Report Server installed to C:\LogiReport\Server1, log onto its server console (http://localhost:8888) as an administrator, then point to Administration on the system toolbar, select Configuration > Cluster > Configuration from the drop-down menu.
Use the same cluster name as Server2, thus making Server1 join the existing cluster. Select the Enable Cluster option, then select Save to enable the cluster.
Restart the Logi Report Server installed to C:\LogiReport\Server1, and log onto the server console again.
Go to the Administration > Configuration > Cluster > Configuration page, configure Server's RMI Host and Server's RMI Port. Remember to keep Server's RMI Port to its default value 1129.
Upon finish, select Save to accept all settings and shut down Server1.
Copy rmi.auth in C:\LogiReport\Server1\bin to C:\LogiReport\Server2\bin. This allows RMI to be authorized between the two systems.
Edit server.properties in C:\LogiReport\Server2\bin and remove cluster.member.id. It will be recreated when you restart Server2 with a unique number.
Start the server Derby DBMS service by double-clicking the startNetworkServer.bat file in C:\LogiReport\Server1\derby\bin.
Restart Server1 and Server2. It does not matter which one you started first.
Access the server console of the first server using port 8888 as an administrator, and then submit a scheduled task. In the Scheduled tab, you will see the newly scheduled task.
Log onto the server console of the second server as an administrator and create a new user Tom in the Administration > Security > User page.
Access the server console of the second server using port 8883 as Tom, and then submit another scheduled task.

Notes:

When you schedule to publish a report on a clustered server to disk, you should first specify a disk in your file system and make sure that every node in the cluster has the same disk name mapping to the same physical location. Then the publishing result will be directly saved to the disk you specify.
You can only view scheduled tasks that you have submitted.
From the server console of the clustered Logi Report Servers, you can only view completed tasks that you have submitted.
If there are more than two clustered servers in the cluster, then after you shut down one server, all the scheduled tasks running on this server will be run on other servers.

Previous Topic Next Topic