Server 4

Recommended Live Configuration

Contains the most important settings for servers and deliveries to take into account when running Sophora in productive environments.

The configuration parameters given here must be seen as a guideline. This list is not necessarily complete and should be revised for every installation. The best configuration for your enviroment may differ from those depicted here. In case of doubts about certain configuration parameters, contact Subshell.

Java Version

Since version 4 Sophora requires Java 11. We recommand to use the latest version of Open JDK 11.

Java Garbage Collection

The exact parameters for the Java Garbage Collection highly depend on the environment (CPU, memory), Java version and the use case (how many concurrent user, how many imports). We recommend using the G1GC.

Sophora Server

An overview of all configuration parameters is provided here.
The Java VM arguments should be maintained in the file under the configuration key vmargs=...

Maximum number of open files

The maximum number of open files must be increased on unix system. Add the following lines to the file /etc/security/limits.conf.

*               soft    nofile            4096
*               hard    nofile            4096

Check the result with the command ulimit -a.

Sophora Primary Server and Sophora Replica Servers

Persistence Technology

We recommend using Oracle or MySQL as database technology.

Sophora Primary Server, Sophora Replica Servers and Sophora Staging Servers

Jackrabbit Configuration

The following jackrabbit related configuration should be adopted in the following files:

  • ./repository/repository.xml
  • ./repository/workspaces/default/workspace.xml
  • ./repository/workspaces/live/workspace.xml
  • ./repository_archive/repository.xml
  • ./repository_archive/workspaces/default/workspace.xml

		<param name="bundleCacheSize" value="1024" />

Search Index

ResultFetchSize and MaxMergeDocs

The parameters resultFetchSize and maxMergeDocs should be removed. Please note, that the first start of the Sophora server after removing the parameter maxMergeDocs will take very long. The Lucene indexes are grouped into larger segments. This may take 60 minutes or longer depending on the size of the indexes.

<SearchIndex  class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
	<param name="initializeHierarchyCache" value="false" />

Important Security Parameters to set

  • sophora.solr.username
  • sophora.solr.password
  • sophora.replication.userName
  • sophora.replication.password
  • sophora.jmx.username
  • sophora.jmx.password

Sophora Staging Servers

Persistence Technology

For staging servers we recommend using Derby as database technology.


An overview of all configuration parameters is provided here.

Tomcat Configuration

Tomcat tag pooling should be disabled.

Document Cache

The delivery holds a cache for document requests to its Staging Server. This cache is crucial for the performance of the delivery. Its size must be adjusted considering the available heap space for the java process. Take the following configuration as guidance:

Configuration of the Delivery Cache

Java VM Arguments

-Djava.rmi.server.hostname=<external hostname> 

Last modified on 5/20/22

The content of this page is licensed under the CC BY 4.0 License. Code samples are licensed under the MIT License.