Search Results

All Results 6970
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
シャード化された環境のアップグレード
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...
データベースアップグレードツールの使用
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...
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...
クラスタ環境とシャード環境のアップグレード
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 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...
構成とプロパティの移行
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 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...
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,...
ジョブスケジューラフレームワーク
Job Scheduler Framework Liferay Self-Hosted Liferay PaaS Job Scheduler is a flexible framework built on Liferay's scheduler engine for running and scheduling business logic. This framework uses...
依存性注入
Dependency Injection
ジョブスケジューラディスパッチフレームワークリファレンス
Job Scheduler Dispatch Framework Reference Liferay Self-Hosted Liferay PaaS Liferay Job Scheduler is a flexible framework built on top of Liferay's Scheduler Engine. You can use it to add,...
メッセージバス
Message Bus The Message Bus provides a loosely coupled way to exchange messages. A class sending a message invokes the Message Bus to send the message to a destination, while other classes...
構成の分類
Categorizing a Configuration When you register a configuration interface, the UI for your application is generated in System Settings → Platform → Third Party. If you prefer a different section and...
ノードのバージョン情報
Node Version Information Liferay DXP uses Node (and NPM) for many different frontend components. Specifically, the Liferay Theme Generator and Liferay's JavaScript application tools require the use...
ジョブスケジューラテンプレートの作成
Creating Job Scheduler Templates Liferay Self-Hosted Liferay PaaS Job Scheduler Tasks are created by implementing the DispatchTaskExecutor interface. Liferay DXP provides multiple out-of-the-box...
スコープ構成
Scoping Configurations In Liferay DXP, you can set an application's configuration to different levels of scope: System, Instance, Site, or Portlet. For example, if you create an application to have...
フィールドオプションプロバイダー
Field Options Provider You can populate a drop-down list manually in the @Meta.AD annotation of the configuration interface. But you can also populate the option labels and values automatically...
スケジュールされたジョブを手動でプログラミングする
Manually Programming Scheduled Jobs Implementing the SchedulerJobConfiguration interface provides greater flexibility and improved performance as it is closer to the core of the job scheduler...
Poshiのリソースの使用
Using Poshi Resources Once the Poshi resources jar file is loaded onto your Poshi project, you are now able to use Liferay's commonly used functions, paths, and macros. To distinguish between files...
Poshiのリソース
Poshi Resources To give Poshi test writers easy access to commonly used functions or other files, Poshi resources were created to store existing Poshi files as dependencies that can be loaded apart...