Migration: Enabling managed pages
After migration, you must manually enable support for managed pages. Without managed pages support, some features like the project menu are not available on the migrated server.
About this task
When you enable managed
pages after migration, several considerations apply:
- After migration, managed pages are initially disabled on the migrated server. In this case, there is a single workspace for storing IBM® Web Content Manager content. All virtual portals on the server share this workspace. Although this single workspace simplifies the sharing of content between virtual portals, it can also lead to dependencies between content libraries and different virtual portals. Depending on your content environment, these dependencies can make it difficult for an administrator to determine which libraries to select for syndication to a syndicator.
- When you enable managed pages, a workspace is created for each
virtual portal. This separation ensures that there are no cross-references
between content items in different virtual portals. In addition, by
selecting all libraries that are visible in a workspace, references
are guaranteed to be resolved during syndication.Because of this separation of workspaces, extra syndication steps might be required on the migrated server for web content libraries:
- Libraries that are used only by a specific virtual portal
- You must syndicate the libraries from the default virtual portal to the specific virtual portal.
- Libraries that are shared by multiple virtual portals
- You must syndicate the shared libraries from the default virtual portal to each specific virtual portal.
- When supported, managed pages is enabled for a virtual portal, all pages in the virtual portal are copied into the Portal Site library in IBM Web Content Manager. However, the following pages are not treated as managed pages and are not copied:
- Administration pages, as identified by the label ibm.portal.Administration and its child pages
- Private pages
- In scenarios where the configured user realm does not contain the domain administrator, an alternative user must be provided. If you have a multi-realm configuration, see Defining alternative administrators for multi-realm configurations.
Note: To take advantage of the features available
to managed pages in the user interface, your pages must use the Portal
8.5 theme.