21.1 Planning a Multi-Server Vibe Configuration

21.1.1 Lucene Index Server Considerations

Before you can implement a multi-server Vibe configuration, you must move your Lucene Index Server away from the initial Vibe server, as described in Section 20.0, Installing the Lucene Index Server on a Separate Server.

21.1.2 Vibe File Repository Considerations

Before you implement a multi-server Vibe configuration, you must plan the Vibe file repository for the clustered Vibe servers. Your configuration must comply with the following restrictions:

  • The Vibe file repository must be placed in a shared location that is accessible to each Tomcat instance.

  • All Tomcat instances must be configured with the same path leading to the shared storage.

For background information on the contents of the Vibe file repository, see Distributing Different Data Types to Different Locations.

21.1.3 Configuring Routing for Multicast IP on the Vibe Server

If you are planning to use ehcache as your hibernate caching provider, you might need to set up the routing for multicast IP on each server where Vibe is installed. If this is not done, then depending on your Vibe system, you might see a communication error when you start the Vibe server. For example, in the log file you might see the following:

Error starting heartbeat. Error was: No such device.

To prevent this error, or to fix the Vibe system after the error occurs:

  1. Run the following command:

    route add -net dev eth0