Liferay DXP 2026.Q4    |    Release Webinar: 18 November 2026    |    Replay coming soon! 

Blogs

Liferay Objects Beyond the Default Database

Exploring External Storage in Liferay DXP 2026.Q4

Himanshu Chauhan
Himanshu Chauhan
4 minutes de lecture



Liferay Objects make it easier to build applications around business data. By default, Object entries use Liferay's portal database. But what happens when the data belongs in Salesforce, SugarCRM or another external system?

Liferay DXP 2026.Q4 includes a Storage Type option for Object definitions. Depending on the available integrations and configuration, it can connect an Object to an external storage manager instead of using default storage.

While exploring this capability, I also found a potential enhancement: letting administrators select an external Liferay supported database directly as an Object's storage destination.

Why Another Storage Option?

Not every application stores its data in one place. A customer-facing application may use Salesforce, while an internal business application has data in a separate database managed by another team.

Liferay's external Object storage framework addresses the first part of this challenge: it lets supported Object entry operations be delegated to another system. The Q4 bundle I inspected includes Salesforce and SugarCRM managers, as well as a function-based manager for a custom external service.

The gap I wanted to explore is a direct, administrator-approved database option. Adding JDBC properties alone does not make an arbitrary database appear as an Object storage type in the inspected Q4 bundle.

What Liferay's Storage Types Do

  • Default storage. Liferay's Object persistence manages entries in the portal database.
  • Salesforce. The Salesforce entry manager sends supported Object entry operations to Salesforce through its API.
  • SugarCRM. A separate manager integrates Object entry operations with SugarCRM.
  • Function-based manager. Liferay delegates supported entry operations to a configured external service. That service can work with an API or a database, but the service must be built and operated separately.

These are different backends behind the same idea: select a storage type for an Object, then let the registered manager handle the operations it supports. Available options depend on the instance's configuration and active services.

Enable the Proxy Object Feature

In the Q4 instance shown below, the Storage Type selector is controlled by the Proxy Object feature flag, LPS-135430. An administrator can enable it for the virtual instance:

  1. Open Instance Settings > Feature Flags.
  2. Under Virtual Instance Scope, select Release.
  3. Search for 135430 or Proxy Object.
  4. Enable Proxy Object (LPS-135430) if it is not already enabled.

The screenshot shows Proxy Object enabled for the virtual instance.

Feature-flag availability and support can vary by release and environment. Review the applicable Liferay guidance before changing a flag, and make the change in an appropriate test environment first.

Choose a Storage Type

After enabling the feature, open Control Panel > Objects and create a new custom Object. Enter its label, plural label and Object name, then open the Storage Type selector.

The example shows Default, Salesforce and SugarCRM. Default is selected initially.

Choose Default to use Liferay's normal Object storage. To use Salesforce or SugarCRM, first configure the corresponding integration and its credentials. A function-based choice requires a registered and configured Object Entry Manager client extension and an external service. The choices shown and whether they can be used depend on the active managers, feature flags and instance configuration.

How It Works

The storage choice is associated with the Object definition. When an entry request is made through a supported Liferay UI or Headless API operation:

  1. Liferay identifies the Object definition and its selected storage type.
  2. It looks up the registered ObjectEntryManager for that storage type.
  3. The manager handles the supported operation: the default manager uses Liferay persistence, while an external manager delegates to its configured system or service.
  4. The manager returns the result to Liferay, which returns it to the caller.

The manager interface includes create, list, read, update and delete operations. Filtering, sorting, pagination, permissions and other behavior depend on the selected manager and must be checked for the use case.

 

Liferay Object | v Selected Object entry manager | +-- Default -> Liferay portal database +-- Salesforce -> Salesforce API +-- SugarCRM -> SugarCRM API +-- Function -> Custom external service

For example, the portal database can remain on an internal DB while a Salesforce-backed Object reads and writes supported entry data through Salesforce. Liferay's Salesforce manager sends supported requests to the Salesforce API using the configured connection and Object/field mappings. The Object definition and Liferay platform metadata remain in the portal database.

This is a proxy Object, not a complete move of Liferay data. Liferay also creates its own Object tables during publication, and related data or copies may exist in other systems such as search indexes, logs or backups.

See It in Action

Consider a customer service application where customer records already exist in Salesforce:

  1. Prepare the Salesforce Object, fields and integration credentials.
  2. Configure Liferay's Salesforce connection in the applicable configuration scope.
  3. Create a custom Object in Liferay and select Salesforce as its storage type, when available.
  4. Configure the Object and field external reference codes to match the Salesforce API names expected by the connector.
  5. Publish the Object and verify supported entry operations with a controlled test record.

The inspected Q4 Salesforce configuration includes a login URL, consumer key, consumer secret, username and password. Use a restricted integration account and store credentials securely.

A Feature Request for External Liferay Supported Databases

The Q4 bundle I inspected does not provide a built-in generic JDBC storage type that lists administrator-configured databases for individual Objects. A custom service can use an external database through the function-based manager, but that service must be built and operated separately.

The proposed enhancement is to let administrators configure approved database aliases and let Object creators choose one, while keeping the portal database as the default. Object metadata, proxy limitations, security and database lifecycle behavior would need careful consideration.

Discuss this idea in the Liferay Community ->

Get Started

To explore existing external storage in Q4, configure the integration you need, check that its storage type is available, and create a proxy Object with the appropriate external Object and field mappings.

For Salesforce, the inspected Q4 configuration includes a login URL, consumer key, consumer secret, username and password. For SugarCRM, it includes an access-token URL, base URL, client ID, grant type, username and password. Configure the relevant Third Party settings in the applicable scope, use a restricted integration account, and protect the credentials.

For a custom service, use the function-based Object Entry Manager extension pattern. Register the client extension and its OAuth application, then implement and configure the external service and its storage behavior. Enabling the feature flag alone does not provide that service.

Before You Try It

External storage also has limitations in Q4:

  • Categorization, comments, friendly-URL customization, entry history and Liferay's Encrypted Object field type are restricted to default storage.
  • Several native entry endpoints, including numeric-ID CRUD and certain version, subscription and action operations, require the default manager.
  • Relationships, workflow, search, attachments and other platform features need individual compatibility checks.
  • External entry storage does not remove Liferay metadata or its managed Object tables from the portal database.

Any future external DB storage feature would need to define its own database support, data-isolation boundaries and recovery behavior. It should not be assumed to provide native Object feature parity.

Learn More

Version note: External Object storage is available in the Q4 bundle inspected for this post; parts of the framework also existed in earlier releases. The post does not claim that the feature first appeared in Q4.

Commentaires sur la page

Related Assets...

Aucun résultat trouvé

More Blog Entries...

Himanshu Chauhan
novembre 20, 2026
Tony Lim
novembre 19, 2026