Support Policy Knowledge Base
- Audience Targeting for Digital Experience Platform 7.2
 - AWS Cloud Services Support Policy
 - Bookmarks Module for Digital Experience Platform
 - Cobertura de suporte na transição para Quarterly Releases
 - Critical Incident Contact role
 - Digital Experience Platform 7.0 Deprecated and Archived Items
 - Digital Experience Platform 7.1 Deprecated and Archived Items
 - Digital Experience Platform 7.2 Deprecated and Archived Items
 - Digital Experience Platform 7.3 Deprecated and Archived Items
 - Document Conversion Support Policy
 - Document Repository Support Policy
 - Document Thumbnails and Previews Support Policy
 - Glassfish Support Policy
 - Google Authorization Removal in Liferay DXP 7.2
 - IBM DB2 Database Support Policy
 - IBM JDK Support Policy
 - Installing Archived Modules From Liferay's Public Repository
 - Internet Explorer Support Policy
 - Java TCK Certified OpenJDK Binaries
 - JBoss Support Policy
 - JDK7 Concerns
 - JDK Certification, Java TCK Compliance, and Liferay
 - LDAP Support Policy
 - Liferay and Amazon S3 SigV2 Deprecation
 - Liferay Docker Image Security Policy
 - Liferay Documentum Connector for Digital Experience Platform 7.1
 - Liferay DXP 2023.Q3 and DXP 2023.Q4 Transitional Support Coverage
 - Liferay DXP 7.0 Fix Pack Releases
 - Liferay DXP Compatibility with Elasticsearch Service on Elastic Cloud
 - Liferay Security Practices
 - Liferay Social Networking for Digital Experience Platform 7.1
 - Liferay Web Proxy Module for Digital Experience Platform 7.1
 - Linux (general) Operating System Support Policy
 - Microsoft Azure Cloud Services Support Policy
 - Microsoft Edge Compatibility
 - Microsoft SQL Server Database Support Policy
 - Mobile Device Support Policy
 - MySQL Database Support Policy
 - NTLM Module in Digital Experience Platform 7.2
 - OpenID Removal in Liferay DXP 7.2
 - Oracle Database Support Policy
 - Oracle JDK Support Policy
 - Oracle JRockit JDK Support Policy
 - PostgreSQL Database Support Policy
 - Red Hat Enterprise Operating System Support Policy
 - Resources Importer
 - Rolling Restart - Breaking Changes
 - SAML Support Policy
 - Search Portlet in Liferay DXP 7.2
 - Solaris Operating System Support Policy
 - SSO (general) Policy
 - Third-Party Paid Apps Activation Support Policy
 - Tomcat Support Policy
 - WebDAV Support Policy
 - WebLogic Support Policy
 - WebSphere Support Policy
 - Wildfly Support Policy
 - Xuggler Support Policy
 
Third-Party Paid Apps Activation Support Policy
This article specifies the Liferay Support Policy for activating 3rd-party paid apps from the Liferay Marketplace. Currently, app licenses are not fully compatible with virtualized environments due to specific license requirements. The customer is responsible for fulfilling these requirements through system configuration.
Policy Details
Activating a 3rd-party Marketplace app can be done either through a *.xml license file or through an online connection, by using an Order ID. Both methods rely on the following server information:
- hostname
 - IP address
 - MAC address
 
The screenshot below shows where 3rd-party app customers can register their server to obtain a *.xml license file.
The app will deactivate if the information listed above changes. This is common in virtualized environments, where the system is not running on the same physical server(s).
In order to keep the paid app active in a virtualized environment, a customer can configure their system to have a static IP address. If the IP address is the only field that does not change, the customer will need to register with a *.xml license file where the hostname and MAC address fields are empty.