Documentation Center

Configuring the Reach Web application

Optimize Reach Web application performance by setting Java's initial and maximum heap size and by overriding session timeouts.

Procedure

  1. Based on the amount of RAM available on your target machine, check and set the initial and maximum memory pool (heap size) used by Java in your Web application server. For example:
    • If your Web application server is Apache Tomcat running on a Windows machine, run the tomcatVERSIONw.exe tool, where VERSION is the Tomcat version (say 7), select the Java tab and set Initial memory pool and Maximum memory pool to your preferred size (Thread stack size can be null).
    • If your Web application server is Apache Tomcat running on a Linux machine, access the bin/ subdirectory of your Apache Tomcat home directoy and edit the file setenv.sh. In this file, include a value for JAVA_OPTS by including a line like the following:
      export JAVA_OPTS="-XmsINITPOOL -XmxMAXPOOL

      where INITPOOL is your initial pool size, and MAXPOOL is your maximum pool size.

    If your Tomcat server has at least 8 GB of RAM, your initial pool size can be set to 2048, and your maximum pool size to 6144.

  2. Specify the Tomcat session timeout override for SDL LiveContent Reach sessions created by SDL LiveContent Architect publish tasks.
    The Tomcat web application server has a timeout setting for each SDL LiveContent Reach session. When user inactivity is detected in SDL LiveContent Reach, a publish process may be terminated based on Tomcat's session timeout. Tomcat's session timeout can be overridden for publishing by adding the pub.session.timeout configuration item, so a long publish will not be interrupted.
    1. From the Review and Collaboration landing page, click Manage Application > Global Config.
    2. In the right pane, under Customized Config, click Add Item.
    3. In the Name field, enter pub.session.timeout
    4. In the Value field, enter a timeout value in minutes.
    5. Click Save.
  3. Specify the Tomcat session timeout override for all SDL LiveContent Reach sessions.
    Tomcat has a default session timeout of 30 minutes that is imposed on every web application that the Tomcat instance serves. In the case of the SDL LiveContent Reach application, that timeout means that you will have to log in again after 30 minutes of inactivity. You can override the Tomcat session timeout defined in the $tomcatdir\conf\web.xml file by editing the LiveContent_home\WEB-INF\LiveContentSecurity.xml file to include a session-timeout setting.
    For example, to set the timeout to 1 hour (60 minutes):
    <session-config>
         <session-timeout>60</session-timeout>
    </session-config>