Configuring Remote Live Staging¶
With Remote Live Staging, your Staging and Live environments are hosted on separate Liferay servers. When enabled, the Site or Asset Library used to configure Staging becomes your Staging environment, and the remote server becomes your Live environment.
Before enabling Remote Live Staging, you must configure the Liferay servers you want to use for your Staging and Live environments. You must also create a new blank Site or Asset Library on your Remote server and use its ID during Staging configuration.
Preparing Your Liferay Servers¶
If you haven’t already, follow these steps to configure your Liferay servers for Remote Live Staging:
Specify a shared authentication key for your servers by adding the following properties to a portal-ext.properties file for both Liferay servers:
Each property value depends on your chosen encryption algorithm and whether you use hexadecimal encoding (recommended) or printable ASCII characters (less secure). If you decide to not use hexadecimal encoding, the value for
tunneling.servlet.shared.secretmust be ASCII compliant.
The following key lengths are supported by the available encryption algorithms:
AES: 128, 192, and 256 bit keys
Blowfish: 32 - 448 bit keys
DESede (Triple DES): 112 or 168 bit keys. Liferay’s minimum key length does not support 56 bit keys.
Add each server to the other’s list of allowed servers by adding the following property to each server’s
If the server has multiple IP addresses, each IP address must be added.
If you’re validating IPv6 addresses, you must configure the app server’s JVM to not force the usage of IPv4 addresses. For example, if you’re using Tomcat, add the
-Djava.net.preferIPv4Stack=falseattribute in the
Update the remote instance’s Tunnel Authentication Verifier Configuration.
To do this, go to the Control Panel → Configuration → System Settings → API Authentication → Tunnel Authentication.
Click /api/liferay/do and insert the additional IP addresses you’re using in the Hosts Allowed field. When finished, click on Update.
While it is enabled by default, ensure each Liferay server’s tunneling servlet authentication verifier is enabled.
Alternatively, you can write this configuration into an OSGi file in your Liferay instance (e.g.,
enabled=true hostsAllowed=127.0.0.1,SERVER_IP,[Local server IP address] serviceAccessPolicyName=SYSTEM_User_PASSWORD urlsIncludes=/api/liferay/do
Restart both Liferay servers to implement your changes.
Once restarted, both servers are ready for Staging configuration.
When applying patches to a remote Staging environment, you must apply them to all your servers. Having servers on different patch levels is not a good practice and can lead to import failures and data corruption. It is essential that all servers are updated to the same patch level to ensure remote Staging works correctly.
Setting Up Remote Live Staging¶
Once you’ve prepared your Liferay servers, follow these steps to set up Remote Live Staging for a Site or Asset Library:
Open the Staging application in your Site or Asset Library.
For Sites, go to Site Menu () → Publishing → Staging.
For Asset Libraries, go to Global Menu () → Applications tab → Asset Libraries. Then open the desired Asset Library and click on Staging under Publishing.
Select Remote Live. This reveals additional configuration fields.
Enter the following Remote Live Connection details:
Remote Host/IP: Enter your Remote server’s IP address into the Remote Host/IP field. This should match the
tunnel.servlet.hosts.allowedproperty specified in your
Remote Port: Enter the port for your remote DXP instance into the Remote Port field.
Remote Path Context: Enter the Remote Path Context. This is only required if a non-root portal servlet context path is used on the remote Liferay server. Access to this context must not be blocked by a proxy or firewall.
Remote Site ID/Remote Asset Library ID: Enter the Site ID/Asset Library ID for the desired target.
If you’re configuring an IPv6 address, it must contain brackets when entered into the Remote Host/IP field (e.g., [0:0:0:0:0:0:0:1]).
If the Remote server is a cluster, you can set the Remote Host/IP to the cluster’s load balanced IP address to increase the availability of the publishing process. See the Configuring Remote Staging in a Clustered Environment for details.
Determine whether to use a secure network connection (i.e., HTTPS) for publishing Pages from Staging to Live.
Determine whether to define manually the remote URL used for the Site or Asset Library.
(For Sites only) Select whether you want Page Versioning enabled on Public and/or Private Pages.
Select the data and content types you want to stage.
Asset Libraries only support staging data for the Documents and Media and Web Content applications.
With Sites, you can stage data for any of the following applications.
When applications are checked, their data is copied, and it may not be possible to edit them directly on the live Site. When unchecking an application, first make sure that any changes in Staging are published, since they may be lost. See Managing Data and Content Types in Staging for more information.
Click Save to initiate the Staging process. The duration of this process depends on the size of your Site or Asset Library.
If your attempt to enable Remote Live Staging fails, please verify that you’ve properly prepared your servers.
Once the process is complete, you are ready to use Remote Live Staging. See Site Staging UI Reference for information about navigating the Staging environment’s publishing features.
Never clone your Liferay DXP database. Doing this can duplicate important data used by Staging (e.g., UUID), causing the remote publishing process to fail.
Remote Live Staging Permissions¶
When a User attempts to publish changes from Staging to Live, Liferay passes the User’s email address, screen name, or User ID to the remote server to perform a permission check. To succeed, the publishing User must have identical credentials and permissions on both servers.
To give a local User permission to publish changes from staging to production/live, create an identical User account with identical permissions for the User on the remote server.
To simplify this process, you can use LDAP to copy selected User accounts from your local server to your remote server. See Connecting to an LDAP Directory for more information.
Configuring Remote Staging’s Buffer Size¶
When you’re using Remote Live staging and you are publishing a large amount of content, this process can be slow and cause a large amount of network traffic. To help with this, Liferay DXP transfers data piecemeal, instead of one large data dump. You can control the size of data transactions by setting the following portal property in your
This property sets the file block sizes for remote staging. If a LAR file used for remote staging exceeds this size, the file is split into multiple files prior to transmission and then reassembled on the remote server. The default buffer size is 10 megabytes.
Disabling Remote Live Staging¶
Disabling Remote Live Staging disables the connection between your environments without deleting any data. Since no data is erased and no processes are started, disabling Remote Live Staging is almost instantaneous.
When you disable remote Staging, you must ensure the Live Site or Asset Library is still accessible so both sides can communicate. Do not shut down your Live environment. If the network connection is ever lost between environments, an error message appears and instructs you to forcibly disable Staging.
Forcibly disabling Staging erases your Staging information from your staging server, not the content. The Live environment remains in a locked state. A possible workaround is to create a new Live Site or Asset Library and import content to it, if necessary.
Follow these steps to disable Remote Live Staging:
Open the Staging application in your Site or Asset Library.
Click the Actions button ( ) located in the Application bar and select Staging Configuration.
Select None for your Staging configuration and click Save.