Legacy _data deep link compatibility

As of Lobster Data Platform. 25.0.0, the platform includes a redirect servlet that handles legacy deep links based on the old /_data/... URL pattern. The servlet transparently redirects these requests to the current platform URL structure. No manual link updates are required.

Background

In legacy _data installations, the integration engine was accessible under paths starting with /_data/. The unified Lobster Data Platform no longer uses this path structure. Customers who reference old /_data/... URLs in internal wikis, documentation systems, or tooling do not need to update those links after migrating to the platform.

How it works

Any HTTP request arriving at a /_data/... path is intercepted by the redirect servlet. The servlet maps the incoming path to the equivalent path in the current platform URL structure. The browser or HTTP client then receives an HTTP redirect response and follows it automatically.

The redirect is transparent to end users. Existing bookmarks and shared links continue to work without any configuration.

Affected URL pattern

Configuration

No configuration is required. The redirect servlet is active by default after upgrading to Lobster Data Platform 25.0.0 or later.

Notes for admins

• This feature is relevant only for installations that have been migrated from _data 4.x to the Lobster Data Platform.

• Deep links to profiles and other integration views that were stored in customer documentation systems remain functional.

• The classic _data web application view is not available in the Lobster Data Platform. The redirect servlet provides URL compatibility only.