The Standard Configurations

In a standard Content Engine installation, both solr and the indexer application are deployed alongside the Content Engine in the same Tomcat instance. The solr instance is used to provide search functionality for Content Studio. Template developers can optionally use the same solr instance to provide search functionality for their publication web applications. The following illustration shows a single-host installation of the Content Engine set up in this way:

In a multiple-host installation, the hosts on which the Content Engine runs are typically specialized: some are editorial hosts, supporting a network of Content Studio clients, while others are presentation hosts supporting public access to the organization's publications. The default configuration of the search components (as described in the Escenic Content Engine Installation Guide) is, however, almost the same:

The only difference between the two configurations is that in the multiple-host configuration, only one instance of the indexer web service is used, for reasons of efficiency. Using the web service in every Content Engine can result in a lot of unnecessary database accesses. The web service used by each indexer web application is specified by means of an Environment element in the Tomcat context.xml file, as described in Install Application Server.