Content Engine Set-up

To set up your Content Engine instances to use the RMI hub, you need to edit four configuration layer .properties files. For general information about configuration layers and how to edit them, see Configuration Layers. The files you need to edit are:

configuration-layer-root/neo/io/managers/HubConnectionManager.properties

The following properties must be set for this component:

hub=rmi://hub-address:1099/hub/Hub: The location of the hub. Replace hub-address with either the host name or the IP address of the host machine on which your RMI hub is installed. This property is common for all Content Engine instances in the cluster, so it can be set in the common configuration layer.
hostname=address: The host name or IP address of the host machine on which this Content Engine instance is installed. This property is host-specific, so it must be set in a host configuration layer.

In a standard installation, default values should work for this component's other properties.

configuration-layer-root/Initial.properties

Make sure the following properties are set for all servers (that is, set them in the common layer):

service.1.1-remote-expire=/neo/io/services/RemoteExpireServiceBootstrap
service.1.2.5-api=/io/api/RMIBootstrap

Add the following property to this component (in the common layer):

service.1.6-rmi-hub-manager=/neo/io/managers/HubConnectionManager

The addition of this property ensures that the hub connection manager is started.

configuration-layer-root/io/api/EventManager.properties

The following properties must be set for this component (in the common layer):

clientConfiguration=/neo/io/services/HubConnection: This tells the event manager to poll the HubConnection service for events.
pingTime=10000: This tells the event manager to poll for events every 10 seconds.

configuration-layer-root/neo/io/services/RemoteExpireService.properties

For change-generating servers only, add the following property to this component:

clientConfiguration=/neo/io/services/HubConnection

This tells the RemoteExpireService to send invalidation events to the HubConnection service. Since this setting is only required on change-generating servers, you should add the property to the appropriate host configuration layers (or possibly to a family configuration layer).