Syndication and staging | HCL Digital Experience
You can use syndication to update content that was originally created by deploying portal solution releases with either the XML configuration interface or through a Portal Application Archive (PAA) file. You can also set up syndication between virtual portals or primary portals on the same system or between virtual portals on different systems.
- Syndication can be set up only between systems that use the same user repository.
- Syndication for managed pages between multiple servers requires that you run an initial staging to all the servers.
- The syndication process runs a prerequisite check on the subscriber to ensure that any required themes, skins, portlets, or iWidgets on a page are present on the target system. If any required objects are missing on the subscriber, syndication is not run for the page. This behavior can result in missing pages and syndication errors for affected pages. Use the XML configuration interface to transfer the missing resources.
- iWidgets and portlets can store data in the WebDAV file store. The syndication process does not verify or transfer WebDAV data. If a portlet on a managed page requires data from the WebDAV file store, you must manually copy the required objects to the target system.
For information about using syndication, see Syndication.
Managed pages and syndication
- In addition to web content, syndication includes artifacts like pages and wires.
- When you populate the production server for the first time, you must run a full export with either the XML configuration interface or through a Portal Application Archive (PAA) file. This full export can include pages and wires.
- When you update the production server after the initial staging, do not continue to export pages and wires, but instead use syndication to transfer the updates. If you export pages and wires after the initial staging, you might inadvertently overwrite changes that are already published through syndication.
The ExportManagedPagesRelease.xml file or a Portal Application Archive (PAA) file is available for exporting all artifacts except pages and wires. For details on using this file, see Staging artifacts that are not transferred by syndication or Creating a differential release.