Migration to version 4.7
Introduction
This article describes the migration path to version 4.7. Please note it is advisable to create a backup before the migration. Please note that starting from version 4.6, object storage is obligatory.
New installations should always use the newest base package, which can be found on the WebFTP server: Base package for Windows or Base Package for Linux.
Migration from version 4.5 or older.
If you migrate from version 4.5 or older, please follow the steps described in the article before proceeding: Migration to version 4.6
Migration from version 4.6 to 4.7
Update Java to version 21
- Please update Payara to version 6.2025.10. Please see the following document for the details: How to update Payara in existing Pubserver. Please note, the new version of Payara runs on Java 21.
- Please add jdk 21 to the java folder of your PubServer. The directory of the JDK 21 should have the name jdk. If needed, please check the base package for version 4.7. to find JDK 21 (folder java/jdk).
- Check your
domain.xmland add the following jvm-options:
<jvm-options>[21|]--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED</jvm-options>
- Verify Java path in Payara configuration:
- Check /opt/pubserver/glassfish/payara6/glassfish/config/asenv.conf
- Ensure it points to your JDK 21
New Session SDK
In version 4.7, a new Session SDK is used. Please see the following document for the details Session SDK
priint:comet InDesignServer and InDesign Desktop Plug-Ins or priint:comet pdf renderer
The minimum required version of the priint:comet Plug-Ins resp. PDF renderer is 5.0 R37314. Connection attempts from older versions or revisions will be rejected.
We highly recommend installing 5.0 R37400, which is available in the customer FTP download area.
Migrate Documents
The new Review Stage UI is based on PDF documents. These are generated, whenever a document has been processed in a Rendering Process or has been checked out in InDesign Desktop and checked in again.
For documents already existing in the system, this PDF is missing and trying to open such documents in review stage will result in the error message "The PDF document you are trying to open does not exist.".
To fix this problem (i.e.: re-generate metadata for old documents) follow these steps:
Preparation
- check, if the rendering script
Refresh Metadataexists. This is installed with patch #1 of the PublishingServer 4.7 - if not
- connect to the PublishingServer with ISON
- open the CometExplorer and navigate to client-name > project-name > Management Planner > Document Planning
- right-click on this folder and select "New Panel Action"
- enter "Refresh Metadata" as Label
- click "Finish"
- the script is created and checked in immediately, there is no need for adaption (a more or less empty script is created from a template, which fits for our purpose)
- if yes or a similar "Do nothing" script already exists, no further preparation is necessary
Run Migration
- make sure, all services required for rendering (priint bpm, rendering service, object storage) are up and running
- make sure, appropriate rendering instances (InDesignServer or PDF Renderer, depending on the document type) are running and properly connected
- Login to Neowise
- in the Publications or Flatplan panel, find the publication you want to migrate
- Migrate single document(s)
- open the publication node
- from the 3-dot menu of the document you want to migrate, select Process > Start Process
- in the "Start Process" dialog, select Process "Run Renderer Script" and then "Refresh Metadata"
- click Execute
- Migrate all documents of a publication
- from the 3-dot menu of a publication select Process > Start Process
- in the "Start Process" dialog, select Process "Exec Script for building documents from Publication" and then "Refresh Metadata"
- click Execute
After this, the PDFs required to use the new Review Stage should be available for all documents migrated as described.