Enable managed pages

After migration, manually enable support for managed pages. Without managed pages support, some features like the project menu are not available on the migrated server.

After migration, managed pages are initially disabled on the migrated server. In this case, there is a single workspace for storing WCM 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 the content environment, these dependencies can make it difficult for an administrator to determine which libraries to select for syndication to a syndicator.

When we enable managed pages, a workspace is created for each virtual portal. This separation ensures 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 used only by a specific virtual portal

Syndicate the libraries from the default virtual portal to the specific virtual portal.

Libraries shared by multiple virtual portals

Syndicate the shared libraries from the default virtual portal to each specific virtual portal.

After syndicating the libraries unique to specific virtual portals, we can delete the libraries from the default virtual portal.

When support for managed pages is enabled for a virtual portal, all pages in the virtual portal are copied into the Portal Site library in WCM. 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

Each virtual portal has its own Portal Site library.

To take advantage of the features available to managed pages in the user interface, the pages must use the Portal 8.5 theme.

Enable managed pages

1. Start the portal server.

2. Enable support for managed pages...
   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh enable-managed-pages -DPortalAdminPwd=foo -DWasPassword=foo<

   After running the enable-managed-pages task for the first time, the property managed.pages is created in the WP ConfigService configuration service. The value of the property is set to true.

3. Restart the portal server.

4. To populate web content libraries with information about virtual portals in the system, run the create-virtual-portal-site-nodes task. For each virtual portal, this task creates a library and a site area called lost-found for resources that cannot be properly located. If the library or site area exist, the task exits. By default, the task runs on all virtual portals in the system.
   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh create-virtual-portal-site-nodes -DPortalAdminPwd=foo -DWasPassword=foo

5. To populate web content libraries with information about the portal pages in the system, run the create-page-nodes task.

   This task can also be used when portal pages and managed pages artifacts in WCM are not synchronized. In this case, the task attempts to resynchronize the portal artifacts and web content artifacts, giving precedence to the portal artifacts.

   Performance note: Depending on the amount of information in the system, the create-page-nodes task can take a long time to run. Because of the database load of the task, do not run the task frequently. The initial run of the task requires the most time, while subsequent runs typically require less time.

   If the virtual portals have different administrative accounts, we cannot run the create-page-nodes task directly. Run the task for every virtual portal, including the base virtual portal. Use the VirtualPortalHost or VirtualPortalContext parameter with the create-page-nodes task. Run the list-all-virtual-portals task to get a list of all the virtual portals. When we run the create-page-nodes task on the base virtual portal, set the VirtualPortalContext value to __NO__VP__ID__.

   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh create-page-nodes -DPortalAdminPwd=foo -DWasPassword=foo

   By default, this task is run on all pages in all virtual portals. To limit this task to a specific virtual portal, identify the virtual portal by adding one of the following parameters to the command line. Each parameter requires the prefix -D on the command line.

   VirtualPortalHost

   Host name of the virtual portal. For example, vp.example.com.

   If the host name of the virtual portal is the same as the host name of the default virtual portal, we must also specify the VirtualPortalContext property. We can specify the VirtualPortalHost property by itself only if the host name is unique.

   VirtualPortalContext

   Virtual portal context that identifies the virtual portal. For example, vp1.

   We can customize the task with the following optional parameters on the command line. Each parameter requires the prefix -D on the command line.

   RunParallel

   Indicate whether we want the task to run with multiple threads. A value of false indicates a single thread and is the default setting.

   A value of true indicates multiple threads, as specified by the work manager wpsJcrSyncWorkManager in the WAS console. Each thread requires a database connection. For optimal performance, ensure that the database connection pool supports at least as many connections as there are threads in the pool.

   Excluded

   Set a list of unique names of page nodes to exclude from the creation process. Excluding a page also excludes its child pages. By default, the portal administration pages (ibm.portal.Administration) are excluded.

6. If we used web content pages before we enabled managed pages, we can transfer the content for those pages to the Portal Site library. For more information, read Transferring content associations to the Portal Site library.

7. Optional: Ensure that users have appropriate access to the WCM REST virtual resource so they can use Edit mode. For example, they have user access.

Parent Enable new functionality in a migrated portal

Related tasks:

Transfer content associations to the Portal Site library
Enable vanity URL support
Synchronize the vanity URL database