Select installation instructions for your environment

Prev Next

Type of Installation

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

Local installation | Cloud/Managed

Local installation upgrades

Step 1: Determine your upgrade path

Current version

Target version

Path

4.6.14 or later

25.1.x

Direct upgrade (see Upgrading from 4.x to 25.1.x)

25.1.x (latest patch)

26.x

Direct upgrade

4.x (below 4.6.14)

25.1.x

Upgrade to 4.6.14 first, then one-click migration to latest 25.1.x

Step 2: Check Java requirements

Platform version

Java required

4.6.x, 25.x, 26.1

JDK 11

Recommended OpenJDK distribution: Adoptium (Eclipse Temurin).

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

Windows

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

  2. Open a Command Prompt as Administrator.

  3. Run cd <install-dir>\bin

    • Execute hub.bat.

  4. Wait for the update to complete.
    The progress will be shown in the console.

  5. Press CTRL+C and wait for shutdown.

  6. Restart Windows Service "Lobster Integration Server".

Linux

After downloading 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.

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

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

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

DMZ setup

Note

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 DMZ.

  3. Update DMZ.

  4. Restart DMZ.

  5. Update the inner system.

  6. Restart the inner system.

High availability (HA) environment

Note

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

Cloud/Managed update

No action is needed from your side.

Updates are automatically managed and handled. For specific concerns, contact Lobster support. Also refer to the section Software Update Policy in the Lobster Cloud documentation.

Related articles