The Content Server is delivered as a standard WAR archive and thus can be deployed to a servlet container like any other web application. The Server Tools are not bundled with the Content Server and have to be installed separately.
Although it is not recommended due to performance and resource issues, it is possible to deploy all Content Servers to a single servlet container, for a test scenario, for instance. If you do so, be aware of the following issues:
Context Path
Each Content Server web application needs a unique context path. Therefore, all clients that connect to this server must have the context path in its connection URL. That is, for example, the URL defined in
cap.client.server.ior.urlcannot have the context "coremedia" for all servers.Startup issues
You should configure the servlet container to not accept requests during startup. For Tomcat this can be set with
bindOnInit="false"in the connector element of theconf/server.xmlfile. Otherwise, it may happen that some Content Server waits for another one which appears later in the servlet container's startup sequence (for example, the Content Management Server tries to connect to the Master Live Server on startup, but Tomcat happens to start the Content Management Server first). Setting thebindOnInitflag helps to recognize the situation early, without waiting for a timeout.
 |  |  |
 |