Search Results

All Results 627
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
CNE GCP対応:Argo CDドメインと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 GCP対応:増分バックアップとリストア
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対応:セキュリティに関する推奨事項
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: 外部依存関係の設定
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: 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...
CNE GCP Ready: ブートストラップ構成リファレンス
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対応:Helm Valuesリファレンス
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: ヘルム値リファレンス
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 This glossary provides a unified vocabulary for the Cloud Native Experience (CNE). Use these terms ensure consistent communication across development, platform...
ローカルサーバーへのLiferayのインストール
Installing Liferay On A Local Server Liferay runs on an application server. There are three ways to host Liferay on a local machine: Using a Docker container Using a Liferay Tomcat bundle On a...
データベースの設定
Configuring a Database By default for demonstration purposes, Liferay DXP/Portal is configured to use an embedded HSQL database. Beyond demonstration purposes, we recommend using a full-featured,...
CNE GCP準備完了:初期環境のブートストラップ
CNE GCP Ready: Bootstrapping Your Initial Environment After completing the prerequisites, run the Cloud Native Experience (CNE) bootstrap process to provision a complete GKE environment from a...
CNE GCP対応:Elasticsearchの使用
CNE GCP Ready: Using Elasticsearch Cloud Native Experience (CNE) GCP Ready environments use Elasticsearch for search workloads. The platform deploys Elasticsearch in-cluster using Elastic Cloud on...
CNE GCP準備:はじめに
CNE GCP Ready: Getting Started The Cloud Native Experience (CNE) GCP Ready toolkit provides an opinionated framework for deploying Liferay DXP on Google Cloud Platform (GCP) with Terraform, Argo...
CNE Kubernetes Ready: アーキテクチャ、サイジング、およびサポートモデル
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 Kubernetes Ready: Argo CD による GitOps
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: Kubernetes Readyデプロイメントのためのネットワーク構築
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...
CNE GCP Ready: Liferayドメインと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 GCP準備完了:環境浄化
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準備:前提条件
CNE GCP Ready: Prerequisites Before running the bootstrap scripts for Cloud Native Experience (CNE) on Google Cloud Platform (GCP), prepare your local machine, cloud accounts, and Git repositories....
CNE GCP Ready: シークレットとライセンスの管理
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 GCP対応:移行パス
CNE GCP Ready: Migration Paths This reference helps you choose migration approaches for moving document libraries and databases into Google Cloud Platform (GCP) environments running Cloud Native...
CNE Kubernetes Ready: 可観測性とテレメトリ
CNE Kubernetes Ready: Observability and Telemetry Kubernetes Ready deployments expose Prometheus-compatible metrics, container-native logs, and optional traces. The liferay-default Helm chart...
CNE: AWS Ready - GitOpsインフラストラクチャ構成リファレンス
CNE: AWS Ready - GitOps Infrastructure Configuration Reference Cloud Native Experience (CNE) uses GitOps to manage infrastructure configuration. These configuration files define environment...
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,...
WebLogicにLiferayをインストールする
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...
Liferayを初めて実行する
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...
ホットフィックスの適用
Applying a Hotfix Subscribers A Hotfix is a fix or collection of fixes delivered between Updates (or between Fix Packs for versions before DXP 7.3 SP3) to address a customer's confirmed critical...
Configuring the Patching Tool
Configuring the Patching Tool Subscribers The Patching Tool can be adapted to any DXP installation. The tool's auto-discovery option is the easiest way to configure the Patching Tool. If you...
パッチ情報の取得
Getting Patch Information Subscribers You can see patch information at a glance, which helps maintain your installation and get help from Liferay Support. The Patching Tool's info command lists...
以前のバージョンへのパッチのインストール
Installing Patches in Earlier Versions Subscribers The Patching Tool applies Fix Packs (including Security Fix Packs and Service Packs) for versions prior to Liferay DXP 7.3 SP3. It also applies...
アップグレードの基本
Upgrading Liferay Liferay is continuously being enhanced with new features as new versions are released. To access these features in your current project, you must upgrade your Liferay instance to...
Liferayの以前のバージョンを更新する
Updating Previous Versions of Liferay Staying current with updates gives you the best security and quality. Security Updates are releases that address the latest security issues immediately. ...
JVM設定
JVM Configuration As of Liferay DXP 2024.Q3+/Portal GA125+, Liferay DXP/Portal requires a Java JDK 17 or 21 (prior versions support JDKs 8 and 11) with specific JVM option settings. There are also...
パッチのアンインストール
Uninstalling Patches Subscribers After you install a patch, you may decide to restore your installation to a previous patch level. Here you'll learn how to Uninstall Patches Revert (uninstall)...
パッチングツールのインストール
Installing the Patching Tool Subscribers The Patching Tool is easy to install and update. Installation Download the Patching Tool from the Customer Portal. For DXP 7.3+, download the latest...
Liferayのアップデート
Updating Liferay Liferay DXP 7.3 SP3+/Portal 7.4 GA1+ Update your Liferay installation with Bundle Releases. The latest features, security releases, as well as library updates are all delivered...
リファレンス
Reference When installing Liferay, you must take into consideration the specifics of your environment. These topics help you integrate Liferay into your existing environment and aid in...
Liferay DXPのアクティブ化
Activating Liferay DXP Starting with the 2026.Q1 release, all Liferay DXP installations—including trial and free-tier environments—require an XML (.xml) activation key to enable core features and...
アップグレードの準備
Preparing for an Upgrade Preparation and planning may be of little consequence for small, casual installations but is mandatory for large enterprise-level installations. There are specific...
カスタマイズの更新
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...
データベースのアップグレード
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...
Liferay Dockerイメージの使用
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...
Liferay Dockerイメージの構築
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,...
DXPをDockerでライセンスする
Licensing DXP in Docker If you're using a DXP trial license that's expiring or you have a new license (activation key) you must install, you can replace your container's existing license. Here's...
コンテナの設定
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...
Docker のメンテナンスとトラブルシューティング
Maintenance and Troubleshooting in Docker The Liferay Docker container has tools for maintenance and troubleshooting out-of-the-box. You can set various environment variables to modify settings...
コンテナへのアプリやその他のアーティファクトのインストール
Installing Apps and Other Artifacts to Containers Applications and other artifacts (such as DXP activation keys) are installed to DXP Docker containers via the container's /mnt/liferay/deploy...
Dockerイメージのバージョン
Docker Image Versions Liferay Docker image tags begin with a Liferay software version and end with an image version. [Liferay software version] [image version] For example, Liferay DXP 7.4.13...
コンテナのライフサイクルとAPI
Container Lifecycle and API At a high level, the container starts Tomcat with Liferay deployed on it. Additionally, however, the container entry point provides an API for executing these use cases:...
Dockerパッケージ
Docker Packages These are the packages Liferay installs in the Ubuntu OS to support a full Liferay DXP environment. This list includes neither the JDK nor the dependencies the packages require. ...
新しいDockerイメージへのアップグレード
Upgrading to a New Docker Image As new Liferay versions are released as Docker images, you can upgrade to them. Upgrading Liferay describes the process. Always back up your data and installation...
コンテナへのファイルの提供
Providing Files to the Container The Liferay container uses the files you provide to execute the following use cases: Configure Liferay with .properties Files and .config files Configure Tomcat...
DockerでDXPにパッチを適用する
Patching DXP in Docker Liferay patches fix DXP issues and the Patching Tool applies the patches. On Docker Hub, Liferay provides images pre-populated with each new Fix Pack, Security Fix Pack, and...
コンテナでのスクリプトの実行
Running Scripts in Containers If there's more that you want to do in the Liferay container beyond setting up Tomcat and Liferay files, deploying arifacts, and applying patches, you can use scripts....
Failed upgrade process com.liferay.asset.display.page.internal.upgrade.v2_3_2.UpgradeAssetDisplayPageEntry
Issue The following error is thrown while upgrading a DXP 7.3 instance: 2021-08-09 11:25:50.668 INFO  [main][UpgradeProcess:115] Failed upgrade process com.liferay.asset.display.page.internal.upgrade.v2_3_2.UpgradeAssetDisplayPageEntry in 49 ms...
Table 'OA2Auths_OA2ScopeGrants' already exists
Issue The following error occurs while upgrading a database to DXP 7.1 or higher Table 'OA2Auths_OA2ScopeGrants' already exists Environment Upgrading Portal 6.2 or DXP 7.0 -> DXP 7.1 or higher Resolution This error says that the table already exists, but OA2Auths_OA2ScopeGrants table...
"invalid keyLength value" error in console at the time of login post upgrade from Liferay 6.1 to DXP 7.1
Issue Post upgrade from Liferay 6.1 to DXP 7.1 user is unable to login and "invalid keyLength value" error observed in the server console. 2021-07-16 12:42:48.447 ERROR [http-nio-8080-exec-6][LoginMVCActionCommand:147] com.liferay.portal.kernel.exception.PwdEncryptorException: invalid...
'Invocation of 'addApplication' failed' after upgrading
Issue The migration was seemingly successful, but upon startup the following error is appearing in the logs: 2021-05-10 08:09:13.142 ERROR [Portal Dependency Manager Component Executor--1][AbstractJAXRSFactoryBean:102] No resource classes found 2021-05-10 08:09:13.148 ERROR [Portal...
UpgradeDDMFormDocumentLibraryFields upgrade step fails due to high number of DDM entries
Issue You might encounter a behavior where a race condition occurs due to the high number of DDM entries in your environment: 2021-03-18 09:54:44,010 INFO [Portal Dependency Manager Component Executor--1][UpgradeProcess:93] Upgrading...

該当件数: 809 件中 61 - 120