Search Results

All Results 7013
Sort By
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Database Tuning for Upgrades
Database Tuning for Upgrades Performing an upgrade impacts the database differently from daily running in production. Because of this, you should tune your database for the upgrade process before...
Example: Removing Intermediate Journal Article Versions
Example: Removing Intermediate Journal Article Versions These instructions and code samples demonstrate removing intermediate Journal Article versions. In the script console, you can remove...
Common Upgrade Issues
Common Upgrade Issues Skipping an upgrade step or creating custom references to the Liferay database, can cause upgrade issues. The following questions and answers address some common situations. ...
Troubleshooting Upgrades
Troubleshooting Upgrades Liferay has many out-of-the-box tools and features to identify and solve issues that may arise when performing an upgrade. To troubleshoot, you can upgrade modules...
Monitoring Upgrades with MBeans
Monitoring Upgrades with MBeans Liferay DXP 7.4 U76 / Liferay Portal 7.4 GA76 When upgrade upon startup is enabled, the upgrade process can be monitored with MBeans through a JVM management tool...
Upgrade Stall Detection
Upgrade Stall Detection Liferay DXP 2026.Q3+ During a database upgrade, Liferay DXP checks the database every 60 seconds and logs queries that appear stalled. You can use these messages to tell...
Updating Customizations
Updating Customizations Plugins (e.g., themes, apps, and customizations) you've developed must be adapted to the new Liferay version. This can be as simple as updating dependencies or updating code...
Upgrade Log Context
Upgrade Log Context Liferay DXP 7.4 U72 / Liferay Portal 7.4 GA72 Enable the upgrade log context to display identifiers for upgrade related processes in your console logs. The possible identifiers...
Upgrade Report
Upgrade Report Available 7.4+ When you perform upgrades, it is important to know the changes made and any issues that occurred. The upgrade status returns combined results for core upgrades,...
Upgrading Modules Using Gogo Shell
Upgrading Modules Using Gogo Shell To troubleshoot upgrade issues with particular modules, it may be necessary to test and perform upgrades on a per-module basis, instead of en-masse. Liferay has...
Migrating Configurations and Properties
Migrating Configurations and Properties Your current DXP installation's OSGi configurations (7.0+) and properties (such as portal properties and system properties) set up your DXP instance to fit...
Upgrading Clustered and Sharded Environments
Upgrading Clustered and Sharded Environments If you're upgrading a clustered installation, you must follow an upgrade approach that fits your cluster requirements. See Maintaining Clustered...
Upgrading a Sharded Environment
Upgrading a Sharded Environment Since Liferay DXP 7.0, Liferay removed its own physical partitioning implementation (also known as sharding) in favor of the capabilities provided natively by...
Upgrading the Database
Upgrading the Database Liferay's tools and instructions facilitate upgrading DXP and Portal environments safely and quickly. Non-clustered environments that have small data sets, can be upgraded...
Updating the File Store
Updating the File Store File store options and configuration values changed in Liferay DXP 7.0. If you're on 7.0 or earlier and are affected by these changes, you must update your file store before...
Database Upgrade Tool Reference
Database Upgrade Tool Reference Before Liferay 7.4 U82/GA82, the db_upgrade_client.sh file was called db_upgrade.sh. Here's an overview of Liferay's upgrade tool. Start the upgrade tool using...
Using the Database Upgrade Tool
Using the Database Upgrade Tool The Liferay Database Upgrade Tool is a client program for upgrading Liferay DXP and Liferay Portal databases offline. Always back up your data and installation...
Upgrading via Docker
Upgrading via Docker Running a Liferay Docker image with auto-upgrade enabled uses the Database Upgrade Tool to upgrade your database transparently on Liferay startup. After the upgrade completes,...
Upgrading via Auto Upgrade
Upgrading via Auto Upgrade You can upgrade your database automatically by enabling auto upgrade via the portal property before starting up your instance. Always back up your database and existing...
Using Liferay Docker Images
Using Liferay Docker Images Docker Hub hosts Liferay DXP and Liferay Portal Docker images, bundled with Tomcat on Linux. The Liferay Docker Hub pages provide image details and tags for the...
Building Liferay Docker Images
Building Liferay Docker Images Liferay is open-source and fully customizable. You can create your own Liferay Docker images using Dockerfiles to suit the needs of your installation. For example,...
Configuring Containers
Configuring Containers Everything that is configurable in a Liferay installation is configurable in a Liferay Docker container. Here are the most common things to configure: JVM Options Portal...
CNE AWS Ready: Managing Secrets and Licenses
CNE AWS Ready: Managing Secrets and Licenses Liferay Cloud Native Experience (CNE) retrieves sensitive values from an external secrets provider. This approach prevents credentials, certificates,...
CNE AWS Ready: Using Elasticsearch
CNE AWS Ready: Using Elasticsearch Cloud Native Experience environments provision OpenSearch by default for search and analytics workloads. You can configure the platform to use Elasticsearch...
Cloud Native Experience: AWS Ready - Getting Started
Cloud Native Experience: AWS Ready - Getting Started The Cloud Native Experience (CNE) AWS Ready toolkit provides an opinionated framework for deploying Liferay DXP on Amazon Web Services using...
CNE AWS Ready: Running Liferay on AWS GovCloud
CNE AWS Ready: Running Liferay on AWS GovCloud Use the Liferay Cloud Native Experience (CNE) installer to provision a Liferay environment on AWS GovCloud (US). The installer creates the required...
CNE GCP Ready: Configuring Liferay Domains and TLS
CNE GCP Ready: Configuring Liferay Domains and TLS By default, the Cloud Native Experience (CNE) environment exposes services using generated gateway endpoints. To provide a production-ready...
CNE AWS Ready: Incremental Backup and Restore
CNE AWS Ready: Incremental Backup and Restore Liferay Cloud Native Experience (CNE) AWS Ready supports automated backups and restores using AWS Backup and Argo Workflows. Backups are disabled by...
CNE: AWS Ready - Configuring Liferay Domains and TLS
CNE: AWS Ready - Configuring Liferay Domains and TLS By default, the Cloud Native Experience (CNE) environment exposes services using AWS load balancer host names. To provide a production-ready...
CNE AWS Ready: Prerequisites
CNE AWS Ready: Prerequisites Before running the bootstrap scripts to deploy the Liferay Cloud Native Experience (CNE) in your AWS environment, prepare your local machine, cloud accounts, and Git...
CNE GCP Ready: Accessing the Kubernetes Cluster
CNE GCP Ready: Accessing the Kubernetes Cluster Cloud Native Experience (CNE) GCP Ready provisions Google Kubernetes Engine (GKE) clusters as private clusters by default. Because the Kubernetes...
CNE GCP Ready: Configuring Argo CD Domain and TLS
CNE GCP Ready: Configuring Argo CD Domain and TLS Configure a custom domain and TLS certificate for Argo CD to access the GitOps interface through a secure endpoint. Prerequisites Before...
CNE Kubernetes Ready: Quickstart on k3d
CNE Kubernetes Ready: Quickstart on k3d Deploy Liferay DXP on a local k3d cluster with ephemeral PostgreSQL and Elasticsearch instances running inside the cluster. Use this environment to validate...
Cloud Native Experience Reference
Cloud Native Experience Reference Access technical specifications and detailed configuration information for the toolkit. These resources include platform-specific Helm Values References for AWS...
CNE: AWS Ready - Bootstrap Configuration Reference
CNE: AWS Ready - Bootstrap Configuration Reference The following configuration defines the cloud infrastructure, GitOps synchronization settings, and bootstrap execution options for Cloud Native...
CNE: AWS Ready - GitOps Infrastructure Configuration Reference
CNE: AWS Ready - GitOps Infrastructure Configuration Reference Cloud Native Experience (CNE) uses GitOps to manage infrastructure configuration. These configuration files define environment...
CNE GCP Ready: Bootstrap Configuration Reference
CNE GCP Ready: Bootstrap Configuration Reference The following configuration defines the Google Cloud infrastructure, GitOps synchronization settings, and bootstrap execution options for Cloud...
CNE GCP Ready: Helm Values Reference
CNE GCP Ready: Helm Values Reference Helm uses YAML for configuration. This reference describes the default values for the Liferay Helm chart when deploying on Google Cloud Platform (GCP). The...
CNE AWS Ready: Bootstrapping Your Initial Environment
CNE AWS Ready: Bootstrapping Your Initial Environment After completing the prerequisites, run the Cloud Native Experience (CNE) bootstrap process. This step provisions the AWS infrastructure,...
CNE AWS Ready: Troubleshooting
CNE AWS Ready: Troubleshooting Liferay Cloud Native Experience (CNE) deployments involve multiple components, including AWS infrastructure, Kubernetes, GitOps workflows, and Terraform...
CNE GCP Ready: Adding OSGi Modules or Client Extensions With Overlays
CNE GCP Ready: Adding OSGi Modules or Client Extensions With Overlays The Cloud Native Experience (CNE) toolkit uses overlays to customize standard Liferay deployments. Upload custom files (such...
CNE GCP Ready: Managing Secrets and Licenses
CNE GCP Ready: Managing Secrets and Licenses Liferay Cloud Native Experience (CNE) retrieves sensitive values from an external secrets provider. This approach prevents credentials, certificates,...
CNE: AWS Ready - Configuring ArgoCD Domain and TLS
CNE: AWS Ready - Configuring ArgoCD Domain and TLS Configure a custom domain and TLS certificate for ArgoCD to access the GitOps interface through a secure endpoint. Prerequisites Before...
CNE AWS Ready: Understanding EKS Auto Mode
CNE AWS Ready: Understanding EKS Auto Mode Cloud Native Experience (CNE) uses Amazon EKS Auto Mode to manage Kubernetes node scaling automatically. EKS Auto Mode scales cluster nodes when...
Cloud Native Experience GCP Ready
Cloud Native Experience GCP Ready This guide provides an automated workflow for deploying Liferay DXP on Google Cloud Platform (GCP). The Cloud Native Experience (CNE) GCP Ready toolkit uses...
CNE GCP Ready: Configuring the Cloud Native Experience
CNE GCP Ready: Configuring the Cloud Native Experience After bootstrapping the Cloud Native Experience (CNE) environment, configure the platform components required for your deployment. CNE...
CNE GCP Ready: Cleaning Up the Environment
CNE GCP Ready: Cleaning Up the Environment Remove Cloud Native Experience (CNE) resources when you no longer need an environment to avoid unnecessary Google Cloud Platform (GCP) costs. Manage...
CNE GCP Ready: Incremental Backup and Restore
CNE GCP Ready: Incremental Backup and Restore Cloud Native Experience (CNE) GCP Ready supports automated backups and restores using Argo Workflows, Cloud SQL backups, and Cloud Storage. Backups are...
CNE GCP Ready: Security Recommendations
CNE GCP Ready: Security Recommendations Cloud Native Experience (CNE) GCP Ready supports secure-by-default deployment patterns for Kubernetes, infrastructure provisioning, and platform access. Use...
CNE Kubernetes Ready: Architecture, Sizing, and Support Model
CNE Kubernetes Ready: Architecture, Sizing, and Support Model Kubernetes Ready deployments of Liferay DXP follow a consistent runtime architecture across OpenShift, EKS, GKE, AKS, on-premises...
CNE: Helm Values Reference
CNE: Helm Values Reference Helm uses YAML for configuration. This reference describes the default values for the Liferay Helm chart. This YAML shows the available values and their defaults. ...
Cloud Native Experience Glossary
Cloud Native Experience Glossary This glossary provides a unified vocabulary for the Cloud Native Experience (CNE). Use these terms ensure consistent communication across development, platform...
Installing Liferay on WebLogic
Installing Liferay on WebLogic Liferay DXP 2026.Q1 If you are using WebLogic as your application server, it is highly recommended to install DXP to a WebLogic Managed server. A managed server can...
Setting Up JNDI on Tomcat
Setting Up JNDI on Tomcat Liferay 7.4+ To set up JNDI resources, you must put the necessary JDBC drivers in the Tomcat lib folder (i.e. tomcat-9.0.56/lib). For example, if you use an Oracle...
Installing on WildFly
Installing on WildFly Liferay DXP 2025.Q3+/Portal 2026.Q1+ For pre-Jakarta Liferay versions, see Installing Earlier Versions on WildFly. Installing on WildFly requires installing the DXP WAR,...
Running Liferay for the First Time
Running Liferay for the First Time Once you've installed Liferay DXP/Portal and configured a database for it, it is ready to run. Start the Server Run the startup script bundled with your...
CNE Kubernetes Ready: Configuring External Dependencies
CNE Kubernetes Ready: Configuring External Dependencies Kubernetes Ready deployments rely on externally managed platform services for persistence, search, object storage, licensing, and secrets...
CNE Kubernetes Ready: Deploying Liferay DXP on OpenShift Developer Sandbox
CNE Kubernetes Ready: Deploying Liferay DXP on OpenShift Developer Sandbox The Red Hat Developer Sandbox provides a free OpenShift environment for validating Kubernetes Ready deployments with the...
CNE Kubernetes Ready: GitOps with Argo CD
CNE Kubernetes Ready: GitOps with Argo CD Kubernetes Ready deployments use GitOps to manage Helm values, Kubernetes manifests, and environment configurations through a Git repository. Instead of...
CNE Kubernetes Ready: Networking for Kubernetes Ready Deployments
CNE Kubernetes Ready: Networking for Kubernetes Ready Deployments Kubernetes Ready deployments expose Liferay DXP through the liferay-default Kubernetes Service created by the Helm chart. External...

Showing 8,401 to 8,460 of 8,806 entries.