Released: Jan 17, 2022

v13.19 での更新項目

機能

• New and Improved
  • Kubernetes Guidance. Now provides instructions and recommendations for PrizmDoc Viewer deployment to Kubernetes.
  • Cluster Manager for Kubernetes. A new accusoft/prizmdoc-cluster-manager container image is now available, which simplifies the deployment of PrizmDoc Viewer container images in Kubernetes.
  • New Sample for PrizmDoc Viewer deployment in Kubernetes on GitHub. Published a new sample project on GitHub. This sample provides manifest files that allow you to get a PrizmDoc Viewer cluster up and running in Kubernetes.
  • MarkupBurner performance improved. The PrizmDoc Viewer component responsible for applying markup was updated and now returns MarkupBurner results up to 30% faster for hi-load scenarios which include MarkupBurner API usage and Hi-End Server configurations.
• Fidelity Updates
  • Improved fidelity, with certain source files, when converting to PDF after updating to the new Prizm Server Docker image using Ubuntu 20.04.
• Stability Updates
  • Changed the default behavior of the accusoft/prizmdoc-application-services Docker image so that it runs a single instance of PAS, instead of running as many instances as the number of CPU cores detected on the system. This allows for using less system resources when the load is low, and scaling the PAS cluster efficiently by adding or removing prizmdoc-application-services containers. As a result of this update, instead of creating several log files named: pas-0.log, pas-1.log, etc., only one log file named: pas.log will be created by the container. If you want to preserve the legacy behavior, pass the LEGACY_RUN_MULTIPLE_INSTANCES environment variable with the value set to "YES" when starting the container.
  • Updated accusoft/prizmdoc-server Docker image to allow it to start container with overridden user.
  • Updated accusoft/prizmdoc-application-services Docker image to allow it to start container with overridden user.
  • Improved logging for the PrizmDoc Application Services to provide additional information when requesting the Viewing Session source document by URL.
  • Updated accusoft/prizmdoc-server Docker image to control time zone with TZ environment when rendering documents.
  • The ms-office-conversion-service now respects the Central Configuration cache.directory property in order to produce temporary files in the configurable directory, based on that property. Previously, the temporary files were produced in the current user's profile directory for temporary files (i.e., %TEMP%), thus making it out of the user's control.
  • The ms-office-conversion-service now cleans up the temporary files that were not deleted due to unexpected restarts or other processing failures related to Microsoft Office documents conversions, thus preventing accumulation the temporary folder with outdated temporary files.
  • Improved stability of PrizmDoc Application Services when uploading Viewing Package artifacts to S3 storage.
  • Improved stability of PrizmDoc Application Services when using the GET /SaveDocument API.
  • Docker image bases have been updated to Ubuntu 20.04 for accusoft/prizmdoc-server, accusoft/prizmdoc-application-services and accusoft/prizmdoc-viewer-eval. Accusoft recommends docker-based deployment option for deploying to Linux platforms.
• Security Updates
  • Updated PrizmDoc Load Balancer to run on node.js v16, taking advantage of recent security fixes and other changes in the node.js.
  • Replaced vulnerable version of log4j2 with the latest version in all Java components of PrizmDoc server to prevent potential vulnerability with the Log4Shell.
  • Updated PrizmDoc Application Services to run on node.js v16, taking advantage of recent security fixes and other changes in the node.js.
  • Updated PrizmDoc Public Request Service to run on node.js v16, taking advantage of recent security fixes and other changes in the node.js.

不具合の修正

• Fidelity Fixes
  • Addressed an issue in PrizmDoc Server where it incorrectly rendered specific MSG documents with UTF-7 encoded HTML body.
• Redaction Fixes
  • Addressed an issue with the PrizmDoc Server markupBurners REST API where markup definitions were not applied to PDF files created from "Muhimbi PDF Converter Services".
  • Addressed an issue with the PrizmDoc Server markupBurners REST API taking longer than expected to execute. This occurred when PDF documents had long PDF Document Custom Properties definitions.
• Stability Fixes
  • Addressed an issue in the accusoft/prizmdoc-server Docker image where the watchdog_launcher.log and config-normalizer.log were not available in the /logs folder.
  • Addressed an issue in the accusoft/prizmdoc-application-services Docker image where it was not possible to obtain the PAS console log. This log is now available as the stdout/stderr output from the container.
  • Addressed an issue in the accusoft/prizmdoc-server Docker image where it failed to start up on host systems which use the cgroup v2 process controller.
  • Addressed an issue in PrizmDoc Server where its Raster Conversion Service module might enter an incorrect state and fail to convert documents to searchable PDF, if it was restarted while doing such a conversion.
  • Addressed an issue in the PrizmDoc Server where the /v2/searchContexts API failed due to using an outdated port configuration of an internal service (this occurred after the expected internal services restarted during a high load period).
  • Addressed an issue in PrizmDoc Server when the LoadBalancer occasionally could not rotate log files and crashed on the Windows platform, making PrizmDoc Server completely unresponsive.
  • Addressed an issue in the prizmdoc-server container, when PDF and Office conversions inefficiently utilized resources allocated to the container. This improves performance and stability of the prizmdoc-server containers in cloud environments, as well as when running multiple containers on the same physical host. PDF and Office conversions in the prizmdoc-server container now respect the following CPU limiting options: Shares, Quota/Period and Affinity.