The Standard Configurations
In a standard
Content Engine
installation, the indexer
application is deployed
alongside the
Content Engine
in the same Tomcat instance. A separate 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 (although you should never do this for production
purposes). The following illustration shows a single-host installation
of the
Content Engine
set up in this way:
This kind of configuration is not recommended for production purposes since the indexing requirements for publication web applications are very different from Content Studio's requirements (see Modifying The Standard Configuration).
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 differences between the two configurations are:
-
The indexer web applications on the editorial hosts are set up to use the internal indexer web service (
index
), while the indexer web applications on the presentation hosts are set up to use the external indexer web service (presentation-index
). -
Only one instance of each indexer web service is used, for reasons of efficiency. Using the indexer web services 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.