#### Configuring the slave servers

You can configure the slave server by using the JReport Administration page or the server.properties file.

##### Using the JReport Administration page

1. Launch JReport Enterprise Server on the slave server, and then log onto the JReport Administration page (port 8889 by default).
2. Click Configuration on the system toolbar and switch to the Cluster tab.
3. Check the Slave Server option to indicate that this server will run as the slave server in the cluster.
4. In the Admin Server's RMI Host text field, type the RMI IP address or host name of the admin server.
5. In the Admin Server's RMI Port text field, type the RMI port number of the admin server.
6. In the Server's RMI Host text field, type the RMI IP address or host name of the local server.
7. In the Server's RMI Port text field, type the RMI port number of the local server.
8. Shut down JReport Enterprise Server on the slave server.

##### Using the server.properties file

1. Launch JReport Enterprise Server once on the slave server, and then shut it down.
2. Open the server.properties file in `<install_root>\bin`.
3. Modify the properties file as follows:
   - cluster.server.backup=false
   - cluster.server.admin=false
   - cluster.admin.rmi.port=1129
   - cluster.update_concurrent_reports_immediately=(Boolean)
4. Specify the paths of the shared directories on the shared disk (mapped network drive).

   Add the following properties to the server.properties file:

   - resource.share.realm.dir=
     Specifies the directory of the realm files.
   - resource.share.properties.dir=
     Specifies the directory of the properties files.
   - resource.root=
     Specifies the directory of the JReport demo report sets.
   - resource.share.temp.dir=
     Specifies the directory for storing temporary files. It is not a must for a slave server.
   - resource.share.hist.dir=
     Specifies the directory for storing all versions of report set results in the cluster. It is not a must for a slave server.
   Make sure that these settings are consistent with those of the admin server.

After configuring each server in the cluster accordingly, the setting up process is done and you can now launch JReport Enterprise Server on each server one by one, starting with the admin server.