Skip to main content

How to update the Web2Publish Application to a newer version

Introduction​

This guide describes how to update an existing Web2Publish installation on Linux and Windows.

It applies to environments where:

  • PubServer is already installed and running
  • Web2Publish is already installed and in use
  • You want to upgrade to a newer compatible version (for example, within the 4.7.x release line)

This document focuses on:

  • What needs to be updated
  • What can be reused
  • What must be verified after the update

Supported Update Scenarios​

You can use this guide if you are updating one or more of the following components:

  • Web2Publish Spring Boot application
  • Web2Publish Service (PubServer plugin)
  • ISON configuration (if required by the new version)

⚠️ Cross–major-version upgrades may require additional migration steps. Always review the release notes before updating.

Prerequisites​

  • PubServer: Version 4.7.0.x (already installed)

  • Java SDK: Must match the target Web2Publish version (e.g. Java 21 for 4.7.0)

  • Existing configuration files backed up:

    • application.properties / application.yml
    • ISON configuration
    • AuthService configuration (config.xml)

  • Access to Priint WebFTP

Update Overview​

ComponentUpdate Method
Web2Publish Spring Boot AppReplace JAR file and restart application
Web2Publish Service (Plugin)Redeploy WAR file
PubServer AuthServiceVerify configuration (usually unchanged)
ISON ConfigurationUpdate only if required by release notes
Reverse ProxyNo change unless URLs or paths change

1. Download the Updated Package​

Download the Web2Publish package that matches your target PubServer version.

Example for 4.7.0:

https://webftp.priint.com/#/priint_suite_4.7.0/publishing%20server%20add-on%20zips/latest/

Unzip the package locally.

2. Update the Web2Publish Application (Spring Boot)​

2.1 Stop the Running Application​

Linux (systemd):

sudo systemctl stop w2p

Windows:

  • If running as a Windows Service: Stop it via Services Manager
  • If running manually: Stop the Java process

2.2 Replace the JAR File​

Locate the updated JAR file, for example:

Web2Publish-4.7.x.jar

Replace the existing JAR file.

Example paths:

  • Linux

    /opt/pubserver/w2p/w2p.jar

  • Windows

    C:\priint\pubserver\w2p\w2p.jar

2.3 Reuse Existing Configuration​

  • Keep your existing:

    • application.properties or
    • application.yml

  • Review the release notes for:

    • New configuration properties
    • Deprecated or removed settings

Add or adjust configuration values only if required.

2.4 Start the Application​

Linux (systemd):

sudo systemctl start w2p
sudo systemctl status w2p

Windows:

  • Start the Windows service, or start manually:

    java -jar w2p.jar --spring.config.location=file:application.properties

3. Update the Web2Publish Service (PubServer Plugin)​

Locate the updated WAR file, for example:

Web2PublishService-4.7.0.x.war

Redeploy it using one of the following methods:

  • Payara Admin Console, or
  • Copy it to the PubServer autodeploy directory

4. Verify PubServer AuthService Configuration​

In most cases, no changes are required.

Verify that the Web2Publish app entry still exists:

[path_to_domain]/config/AuthService/config.xml

Example:

<app name="priint:w2p" id="web2publish" visible="true">
    <uri>[W2P_HOME_PAGE]/auth/callback?sessionId={sessionId}</uri>
    <sessionCookieName>w2pSessionId</sessionCookieName>
</app>

Restart PubServer if the configuration was modified.

5. Update ISON Configuration (If Required)​

  • Existing ISON configuration is reused by default
  • Update it only if:
    • New features are introduced
    • Existing configuration options change

6. Post-Update Validation Checklist​

  • Web2Publish UI loads correctly
  • Login via PubServer AuthService works
  • Web2Publish Service API is reachable
  • ISON-based features behave as expected
  • No errors in:
    • Web2Publish logs
    • PubServer logs

Summary​

  • Updating Web2Publish mainly involves replacing the Spring Boot JAR
  • Existing configuration files are reused
  • Web2Publish Service is updated by redeploying the WAR
  • AuthService configuration usually remains unchanged
  • The update process is identical on Linux and Windows, except for service management