Select installation instructions for your environment

See also: Software update policy

Type of installation

Click the relevant link below to navigate to the correct section of the manual.

Local installation | Cloud/Managed

Local installation upgrades

Upgrade to 26.2: additional required steps

Version 26.2 introduces two changes that take effect regardless of your Java version and must therefore be addressed:

• JDOM1 → JDOM2 migration: All custom scripts and Java classes that import org.jdom must be updated — even under Java 11. → JDOM1-to-JDOM2 migration

• The new Application Wrapper is a Java-based tool that registers and manages your Lobster applications as system services. → Lobster Application Wrapper

Also read the Java upgrade overview before continuing.

Step 1: Determine your upgrade path

Lobster Bridge

If you use Lobster Bridge, update all bridges after the platform upgrade via the "Update Lobster Bridge" button. This ensures compatibility with version 26.1.x.

More on quarterly releases and LTS versions: Release policy: quarterly releases and LTS

Step 2: Check Java requirements

Free LTS support for JDK 11 has ended. Install OpenJDK 21 before upgrading to version 26.2 or later. Further information: Check Java version status.

Recommended OpenJDK distribution for download:

• Adoptium Eclipse Temurin^®, JDK 11 LTS — for transitional use only; free LTS support has ended across most distributions.

• Adoptium Eclipse Temurin^®, JDK 21 LTS — recommended.

NOTE

The JDK should be deployed by extracting the archive rather than via the OS installer. The path is set exclusively through the Lobster startup scripts (see below). This decouples the JVM from OS package updates and enables a fast rollback.

Java path

• Windows: Set the path to the Java working directory in ./bin/hubenv.bat and ./etc/wrapper.conf.

• Linux: Set the path to the Java working directory in ./bin/hub.sh.

Step 3: Select your setup

Windows | Linux | DMZ | High availability

26.2 — Set up the  Lobster Application Wrapper

Starting with version 26.2, the Lobster Application Wrapper manages the service uniformly across Windows and Linux. After upgrading from 26.1 to 26.2, the service must be installed once via the wrapper before it can be started. Before doing so, disable the previous startup mechanisms (the "Lobster Integration Server" Windows service or lobster.service under systemd).

java -jar ./bin/application-wrapper.jar --install-service
java -jar ./bin/application-wrapper.jar --start-service

The full setup and migration procedure is described in the Lobster Application Wrapper article. The following sections describe ongoing operations for each operating system.

Windows

Up to version 26.1:

1. Stop the Windows service "Lobster Integration Server".

2. Open the Command Prompt as administrator.

3. Run cd <install-dir>\bin.

4. Run hub.bat.

5. Wait for the update to complete. The progress is shown in the console.

6. Press Ctrl+C and wait for shutdown.

7. Restart the Windows service "Lobster Integration Server".

From version 26.2:

The service is managed through the Lobster Application Wrapper. The commands are identical on Windows and Linux.

1. Open the Command Prompt as administrator and change to the installation directory.

2. Stop the service:

   java -jar ./bin/application-wrapper.jar --stop-service

3. Wait until the service has fully shut down.

4. Start the service – the update is applied automatically on startup:

   java -jar ./bin/application-wrapper.jar --start-service

5. Check the service status:

   java -jar ./bin/application-wrapper.jar --service-status

6. You can monitor progress in ./logs/wrapper.log and ./logs/console.txt.

Linux

After downloading the patches to ./etc/update/patches (as described in the Pre-upgrade checklist), stopping and restarting the service is all that is needed. The update is applied automatically on restart.

Up to version 26.1:

1. To stop the service, enter systemctl stop lobster.service in the command line.

2. To start the service, enter systemctl start lobster.service.

3. You can monitor progress in ./logs/console.txt.

From version 26.2:

The service is managed through the Lobster Application Wrapper. The commands are identical on Windows and Linux.

1. Change to the installation directory. Make sure you have root privileges.

2. Stop the service:

   java -jar ./bin/application-wrapper.jar --stop-service

3. Wait until the service has fully shut down.

4. Start the service – the update is applied automatically on startup:

   java -jar ./bin/application-wrapper.jar --start-service

5. Check the service status:

   java -jar ./bin/application-wrapper.jar --service-status

6. You can monitor progress in ./logs/wrapper.log and ./logs/console.txt.

DMZ setup

 CAUTION 

A firewall rule may need to be added. In clustered DMZ environments, every node must be able to reach https://api.lobster-world.com/ independently.

The DMZ component can pull updates automatically only if your license permits it. Standard DMZ licenses support automatic updates.

1. Stop the inner Lobster system.

2. Stop the DMZ.

3. Update the DMZ.

4. Restart the DMZ.

5. Update the inner system.

6. Restart the inner system.

High-availability (HA) environment

 CAUTION 

A firewall rule may need to be added. In clustered HA environments, every node must be able to reach https://api.lobster-world.com/ independently.

All nodes must be stopped before updating any node.

High-availability systems are architected for continuous operation and protect against unplanned service interruptions in most scenarios. Software updates on HA systems follow a coordinated maintenance procedure across all nodes; this differs per upgrade. Check the release notes for any exceptions to the standard upgrade procedure.

Related topics

• For more information, see also: High availability architecture – Overview.

• Read Patching during load balancing operation in a new tab.

Cloud/Managed update

No action is needed from your side.

Updates, including the JDK, are managed and applied automatically. For specific concerns, contact Lobster Support. Also, refer to the section Software update policy in the Lobster Cloud documentation.