Transfer content associations to the Portal Site library
When you enable manage pages, any web content pages that you have are converted to managed pages and added to the Portal Site library. However, the content associated with the web content pages remains in the original libraries. We can transfer this associated content to the Portal Site library with the internalize-content-mappings task.
Administration pages are not intended to be managed pages and so are not included when you enable managed pages.
When you transfer the content association for a page to the Portal Site library, several things happen:
- The content referenced by the default content association for the page is copied to the portal page site area for the page. Only the default content association is affected; other content associations for the page are ignored.
Nested pages are not copied. Nested site areas are not copied in the following cases:
- The nested site area is referenced by the default association of another page.
- The nested site area has the same name as an existing site area for the same page.
- Template mappings and content elements that exist in the associated site area are copied over into the portal page. If the template mapping or element already exists for the page, the copy is not performed.
- The default content setting for the portal page is modified to reference the copied content.
- The configuration of any web content viewers on the page is updated to reference the content stored in the portal page site area. However, viewer configurations that use content paths are not affected.
To transfer content associations, run the internalize-content-mappings task from the WP_PROFILE/ConfigEngine.
ConfigEngine.bat internalize-content-mappings -DPortalPage=target_page -DIncludeDescendants=true_or_false -DSynchronous=true_or_false -DPortalAdminPwd=foo -DWasPassword=foo
The following properties must be specified either on the command line or in the wkplc.properties file.
- PortalPage
- The object ID or the unique page name of the page for which to transfer content. If the target page is contained in a virtual portal, identify the virtual portal by specifying either the VirtualPortalContext parameter or VirtualPortalHost parameter.
- IncludeDescendants
- Specify true to transfer content for the target page and any child pages. To transfer content only for the target page, specify false. If not specified, the default value is true.
- Synchronous
- Specify true to perform the transfer synchronously. To perform the transfer asynchronously, specify false. If not specified, the default value is true.
- Verbose
- Specify true to output additional information to the log. To generate basic log information, specify false. If not specified, the default value is false.
- VirtualPortalContext
- Specify the virtual portal context that identifies the virtual portal. For example, vp1.
- VirtualPortalHost
- Specify the host name of the virtual portal. For example, vp.example.com.
Important: If the host name of the virtual portal is the same as the host name of the default virtual portal, also specify the VirtualPortalContext property. We can specify the VirtualPortalHost property by itself only if the host name is unique.
- PortalAdminPwd
- The administrator password for WebSphere Portal.
- WasPassword
- The administrator password for WebSphere Application Server.
Example commands:
ConfigEngine.bat internalize-content-mappings -DPortalPage=example.page -DIncludeDescendants=true -DSynchronous=true -DPortalAdminPwd=foo -DWasPassword=foo
Parent: Configure managed pages