One-click migration from older systems

Access to the Update center

• Older 4.6 systems may require activation to access updates. Contact your Lobster representative if the update does not appear in the Update center.

• The legacy portal.lobster.de was shut down on December 31, 2025, and completely replaced by the Update center. There, you can select and download the required Lobster version with the current updates for all supported versions.

Before migration

• Confirm you are running 4.6.14 or later before you can migrate to 25.1.x.

• Begin by testing every new version in a test environment before migrating your production environment.

• Complete the Pre-upgrade checklist, including SAP library backup.

• Merge the _data and _pro installations if you have both. The pro installation cannot be merged into the platform after you have migrated your _data  installation.

• Following the migration to the Lobster Data Platform, _data HA customers will need to share an additional folder in the shared file system: ./PRO/config/files 

• Review whether you have received a renewed dedicated DMZ license, if you have a DMZ.

After migrating to 25.1.x

Clear browser cache

Clear your browser cache before logging in. The initial login after the migration to Lobster Data 25.1 may take a moment.

Database re-encoding

MySQL tables are automatically re-encoded to utf8mb4 during migration. Log messages about tables that can’t be migrated due to mixed collations are expected and can be disregarded.

Verify start scripts

The updater automatically adjusts the references to classes in the startup scripts. Check if this change has been made:

Previously

• com.ebd.hub.update.UpdateInstaller

Now

• de.lobster.updater.LobsterInstaller

hub.bat (Windows)

If the file looks exactly like this, proceed.

set UPDATE="%JAVA_HOME%\bin\java" -cp bin/updater.jar -Djava.io.tmpdir="%HUB_HOME%\tmpIO" de.lobster.updater.LobsterInstaller

execute.sh (Linux)

If the file looks exactly like this, proceed.

$JAVA -cp bin/updater.jar -Djava.io.tmpdir=$HUB_HOME/tmpIO de.lobster.updater.LobsterInstaller $HUB_HOME

If you see different content in these files and are uncertain about how to fix the file, contact  support for clarification.

Cross-platform migration

If you want to migrate your installation across platforms, please contact support.

Platform GUI configuration

The 25.1.x platform GUI requires a reference to the HTTP server to serve the web application. Legacy 4.x _data installations with a PRO installation do not contain this setting. Without it, the platform GUI is inaccessible after the migration.

In PRO/config/etc/systemManagers/de.lobster.scm.rest.WebAppManager.xml , verify that the httpServerName property is present: <Set name="httpServerName">Main Server</Set> .

If this line is missing, add it and restart the service.

Moving HA systems to the Lobster Data Platform

The transition from 4.6.x to the Lobster Data Platform requires a full cluster shutdown. This one-click migration automatically migrates the database to support new platform capabilities; however, the entire cluster must remain offline during this process.

Wait until the node controller has fully started and completed its migrations before beginning a migration of the worker nodes and DMZs. Once the move is complete, the standard rolling update process will apply for future maintenance.

Migration order:

1. Stop all systems.

2. Migrate and restart NodeController and Primary DMZ.

3. Migrate and restart working nodes and Secondary DMZ systems.

Validate

After the migration, perform the following validation checks:

• The platform must start without errors. Check the service logs for errors or stack traces.

  • Windows: ./logs/wrapper.log

  • Linux: ./logs/console.txt

• Test connectivity: Partner channels and communication protocols in use (SFTP, OFTP, AS2, SMB, databases, etc.).

• Test profiles: Run existing test case profiles that cover key functions. Consider using the Profile test manager for a structured validation.

• Review the latest error.log files for anomalies compared to the pre-migration state.

Next step

Don't proceed to 26.x until 25.1.x is running and has been fully tested.

SAP libraries

SAP libraries are no longer distributed with new releases due to licensing restrictions. If your system uses SAP connectivity, manually back up the following files before migration and restore them afterward.

Legacy layouts (existing installations before migration)

For older hubs, both JCo 3 and (optionally) the old RFC library might be present. Use this table for legacy 4.x systems that already have SAP configured in the classic locations:

Troubleshooting a migration from 4.x to 25.1.x

Rollback