InetSoft Product How-To: Reporting Software - Configuring Materialized Report Views

To configure the server to use distributed materialized views, and to configure the individual nodes, follow the steps below:

1. Shut down the Style Intelligence server.
2. Add the following properties to the sree.properties file (in the SREE Home directory) on the Style Intelligence server.

comm.this.host={servername}
comm.port=6385
comm.{servername}.ips={server IP address}
fs.server={servername}


Replace {servername} with the Style Intelligence server name. Replace {server IP address} with the Style Intelligence server IP number.

For the first data node machine (node 1), configure the node by fol­lowing the steps below:

1. Create a new directory on node 1 to contain the Style Intelligence jar files (for example, “C:\node1\jar”).
2. Copy the Style Intelligence jar files into the new jar file directory: “etools.jar” and “bisuite_pro.jar” (or “visual_pro.jar”).
3. Create a new SREE Home directory on node 1 to contain the materialized view data and configuration information (for example, “C:\node1\sreehome”).
4. Open a command window on the data node machine, and navigate to the “node1” directory. Then type the following command:

java -Dsree.home=./sreehome -classpath ./jar/bisuite_pro.jar;./jar/etools.jar;. inetsoft.report.composition.mv.dgui.DistributePropertyDialog


This opens the 'Required Property' dialog box.

5. In the 'Required Property' dialog box, enter the {nodename} and {node IP address} in the 'Host Name' and 'Host IP' fields, respectively. Enter the {servername} and {server IP address} in the 'Server Name' and 'Server IP' fields, respectively. Enter the “comm.port” value (from sree.properties above) into the 'Port' field.
6. Click 'OK' to close the 'Required Property' dialog box. This populates the 'Data Node Configuration' dialog box. (Leave this dialog box open.)
7. Repeat the above steps for each data node.
8. Start up the Style Intelligence server, and open Enterprise Manager.

For the first data node machine (node 1), start the node by following the steps below:

1. Click the 'Test' button in the 'Data Node Configuration' dialog box. A 'Test successful' response indicates that the data node is able to communicate with the server.
2. If the test was successful, click 'Connect' in the 'Data Node Configuration' dialog box.
3. Click the 'Close' button (red X) to exit the 'Data Node Configuration' dialog box. This creates an sree.properties file in the data node's SREE Home directory.

The JVM heap size should be scaled according to the data that you expect the node to process.


4. In the command window, navigate to the “node1” directory. Then start node 1 by typing the following command:
java -Xmx256M -Dsree.home=./sreehome -classpath ./jar/bisuite_pro.jar;./jar/etools.jar;. inetsoft.report.composition.mv.dgui.StartDataNode
5. Repeat the above steps for each data node.
6. In Enterprise Manager on the server, open the 'Repository' > 'Dis­tributed Configuration' page under the Server tab. Verify that the nodes you have started are shown with “alive” status.

Read how InetSoft was rated #3 for implementation in G2 Crowd's user survey-based index.

If you are using a clustered environment for report generation, and wish to use a distributed materialized view for Viewsheets, follow the steps below:

1. Prepare the following reporting cluster servers:
1. A proxy server (proxy1)
2. A slave server (slave1),
2. Prepare the following distributed materialized view servers:
1. A server node (server1)
2. A data node (data1).

This allows slave1 and server1 to share the same MV definition and security settings, so that a MV query created by slave1 can be executed on server1.


3. Set proxy1, slave1, and server1 to share the same SREE Home directory.
4. In the sree.properties file in the shared SREE Home directory, make the following entries:

fs.server=server1
cluster.servers.hosts=slave1
mv.repository.servlet=http://server1/Viewer


5. Start the following servers: proxy1, slave1, and server1.

If the fs.nodes property in the sree.properties file in the shared SREE Home directory designates server1, remove that entry.


6. Start the data1server, and add it to the distributed system.

Do not use the Enterprise Manager on proxy1 or slave1 to create the materialized views manually. If you are scheduling materialized view generation, you can use Enterprise Manager on any server.


7. Create the materialized views on server1 by using Enterprise Manager on server1.

With these settings in place, Viewsheet that use materialized views will execute on server1.