4.3.2 Installing Node 1 for Repository and Admin Servlets
Node 1 will run both a Repository servlet and an Administration servlet. Follow the steps below to configure this node:
1. Install the Style Intelligence server onto Node 1.
Use the appropriate installation procedure for your platform. For example, on a Windows computer, run the installer executable, and select the 'Standard Server' option on the 'Installation Type' screen.

This will install the entire server framework, including the Repository and Administration servlets.
2. Launch the Style Intelligence Server on Node 1, and log into Enterprise Manager.
3. Under the Server tab, open the 'Server' > 'Security' page. Configure your security provider as desired. (See Specifying a Security Provider for full details.)
4. Open the 'Server' > 'Status' page. If required, change the 'Repository Servlet URL' to “/sree/Reports” and click 'Apply'. (Ignore any warning messages. See Viewing Server Status for full details.)
See Configuring the Scheduler for full details about the Scheduler application. Only one Scheduler application may run within a cluster.
5. Open the 'Server' > 'Scheduler' > 'General' page. Deselect the 'Auto Start' and 'Auto Stop' options. (See Using a Clustered Environment to manually run the Scheduler on a cluster node.)

6. Open the 'Configuration' > 'Server' page. Select 'Servlet with server clustering'.

The 'Server' > 'Cluster' page is only displayed if the selected server type supports clustering. See Changing the Server Type.
7. Open the 'Server' > 'Cluster' page. Make the following settings:
a. Set the 'Node Servlet URI' to “/sree/Reports”.
b. Set the 'Enterprise Manager URL' to the URL of Enterprise Manager on Node 1 (i.e., the URL you are currently using to access Enterprise Manager.) For example:
http://node1:8080/sree/EnterpriseManager
c. Select the 'Cluster Load Balance Algorithm'. Round Robin assigns requests to the registered nodes in sequence, while Load-based assigns requests based on node's load.
d. Under the 'Cluster Servers' panel, click the 'Add' button.
You will add the other cluster nodes here at a later stage.
e. Add Node 1 as a cluster node: Enter the host name and port (e.g, “node1:8080”), and a valid license key.

f. Select 'Use this server for scheduled reports' if you want scheduled reports to be processed this machine (in addition to on-demand reports).
8. Click the 'Apply' button.
9. Log out of Enterprise Manager.
10. Stop the Node 1 application server. Open the sree.properties file (located in the WEB-INF/classes directory), and make the following changes:
a. For the properties scheduler.classpath and log.output.file, replace any occurrence of the variable $(sree.home) with a hard-coded absolute path to the WEB-INF/classes directory (SREE Home). For example:
C\:/Program Files/Style Intelligence/server/webapps/sree/WEB-INF/classes/
b. Add the following new property:
replet.cache.directory={Path to SREE Home}/temp
For example:
replet.cache.directory=C\:/Program Files/Style Intelligence/server/webapps/sree/WEB-INF/classes/temp
c. Save your changes to the sree.properties file.
You may use the existing location on Node 1 if this will be accessible to all nodes (via sharing).
11. Copy the entire WEB-INF/classes directory to a shared location that will be accessible to all cluster nodes.
Alternatively, you can also store configuration files and report templates in a database that can be accessed by cluster nodes. See Configuring the Data Space.
12. Add the following entry to the web.xml file of the SREE webapp (in sree/WEB-INF) on Node 1.
<context-param>
<param-name>sree.home</param-name>
<param-value>{Path to shared location}</param-value>
</context-param>
For {Path to shared location} above, substitute the full path of the WEB-INF/classes directory that you copied in the previous step.
Any changes that you make in the Enterprise Manager (e.g., enabling/disabling security) after the cluster is set up and started will only be reflected when the nodes are restarted.
| << 4.3.1 Server Clustering Procedure | © 1996-2013 InetSoft Technology Corporation (v11.5) | 4.3.3 Installing Additional Nodes for Repository Servlets >> |