Cannot view large PDF files using View and Markup (retired) - SmartPlant Foundation - SmartPlant Foundation 2020 - Help - Hexagon

SmartPlant Foundation and Web Client Modified and Retired Functionality

Language
English
Product
SmartPlant Foundation
Search by Category
Help
SmartPlant Markup Plus Version
10.0 (2019)

The following applies if you are using a version of the software before Update 33 and SmartPlant Markup Plus Server 2019 SP 1 or earlier. For the latest information, see File viewing problems.

Problem

You cannot view large PDF files using the View and Markup page.

Common Cause

You might encounter this problem if the PDF file:

  • Has many images.

  • Contains thousands of pages.

There are several changes that can help alleviate these problems. For many configurations, simply modifying Brava! Server properties will help. We recommend changing those settings first, following Solution 1. If you still have problems, try modifying additional server settings, following solution 2. The file is cached once it is successfully viewed in the Web Client, making subsequent viewing faster.

Solution 1: Modify Brava! Server properties

These changes often help with viewing large PDF files.

  1. Log on to the SmartPlant Markup Plus server as an administrator.

  2. Go to Start > Administrative Tools > Services and stop the Apache Tomcat service.

  3. Open the server.properties file delivered to the [installation location]\SmartPlant\Markup\Brava! Enterprise\Brava Server folder.

  4. Comment out single.page.publishing=off by adding # at the beginning of the line.

  5. Increase the timeout value (in minutes) of publish.request.timeout. Large PDF files might require 20 or more.

  6. Go to Start > Administrative Tools > Services and restart the Apache Tomcat service.

Solution 2: Modify JobProcessor and Tomcat settings for Java

If you still cannot view large PDF files after modifying server properties, try these changes.

SHARED Tip For help with Apache Tomcat settings, refer to the documentation at tomcat.apache.org.

  1. Log on to the SmartPlant Markup Plus server as an administrator.

  2. Go to Start > Administrative Tools > Services and stop the Apache Tomcat and Blazon Job Processor services.

  3. Increase the default timeout values for the JobProcessor:

    1. Go to [installation location]\SmartPlant\Markup\Brava! Enterprise\JobProcessor.

      If you are using a version prior to SmartPlant Markup Plus 2019 Service Pack 1, the folder is: [installation location]\SmartPlant\Markup\Blazon\Blazon Enterprise\JobProcessor.

    2. In both the jpservice.config and jpconsole.exe.config files, increase the DefaultTimeoutInSeconds and DefaultStepTimeoutInSeconds values.

  4. Increase the Apache Tomcat memory allocation settings for Java:

    1. Click Start > Apache Tomcat [version] > Configure Tomcat.

    2. Select the Java tab.

    3. Increase the Initial Memory and Maximum Memory settings.

      For example, some very large PDFs might require an initial memory of at least 1000 and a maximum memory of at least 3000.

      Consider how much RAM is available. Increasing the maximum memory allocation for Apache Tomcat will decrease available memory for other processes.

  5. Increase the asyncTimeout attribute for the Tomcat <Connector> elements:

    1. Open the Apache Tomcat configuration file:

      [Apache installation folder]\Apache Software Foundation\Tomcat [version]\conf\server.xml

    2. For both the connector port and the redirect port, increase the asyncTimeout attribute on the <Connector> element to 600000 or higher. This value is measured in milliseconds.

      • Usually the connector port is 8080 and the redirect port is 8443. Your company may use different settings. If your company uses a redirect port, be sure to set the attribute for both ports.

      • Attribute names are case-sensitive.

      • The asyncTimeout attribute is added to the <Connector> elements when configuring the SmartPlant Markup Plus Server to use SSL. For more information, see Set connector attributes to personal information exchange file (PFX).

  6. Go to Start > Administrative Tools > Services and restart the Apache Tomcat service.