By default, support for managed pages is enabled for the
default virtual portal. However, you can also manually enable this
support if managed pages are disabled.
About this task
Important: Do not attempt to enable managed pages
on a server where managed pages are already enabled. If you previously
disabled managed pages and want to re-enable the feature, you must
ensure that the Portal Site library is empty first. If you fail to
remove page artifacts from the previous configuration, the resulting
portal might not work properly.
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
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
Each virtual portal has its own Portal Site library.
Note: To take advantage of the features available
to managed pages in the user interface, your pages must use the Portal
8.0 theme.
Cluster consideration: In
a cluster, you need to apply this procedure only to the primary node.
In a multiple cluster configuration, apply this procedure to the primary
node of each cluster.
- Start the portal server.
- To enable support for managed pages, run the enable-managed-pages task
from the wp_profile_root/ConfigEngine directory.
- Windows
- ConfigEngine.bat enable-managed-pages -DPortalAdminPwd=password -DWasPassword=password
- Linux
- ./ConfigEngine.sh enable-managed-pages -DPortalAdminPwd=password -DWasPassword=password
- IBM i
- ConfigEngine.sh enable-managed-pages -DPortalAdminPwd=password -DWasPassword=password
After you run the enable-managed-pages task
for the first time, the property managed.pages is
created in the WP WPConfigService configuration
service. The value of the property is set to true.
- Restart the portal server.
- To populate web content libraries with information about
virtual portals in the system, run the create-virtual-portal-site-nodes task
from the wp_profile_root/ConfigEngine directory. For each virtual portal, this task creates a library and a site
area that is 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.
- Windows
- ConfigEngine.bat create-virtual-portal-site-nodes -DPortalAdminPwd=password -DWasPassword=password
- Linux
- ./ConfigEngine.sh create-virtual-portal-site-nodes
-DPortalAdminPwd=password -DWasPassword=password
- IBM i
- ConfigEngine.sh create-virtual-portal-site-nodes -DPortalAdminPwd=password -DWasPassword=password
- To populate web content libraries with information about
the portal pages in the system, run the create-page-nodes task
from the wp_profile_root/ConfigEngine directory.
This task can also be used when portal pages and managed
pages artifacts in Web Content Manager 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.
Attention: If
your virtual portals have different administrative accounts, you cannot
run the create-page-nodes task directly. You must
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 your virtual portals. When you run the create-page-nodes
task on the base virtual portal, set the VirtualPortalContext value
to __NO__VP__ID__.
- Windows
- ConfigEngine.bat create-page-nodes -DPortalAdminPwd=password -DWasPassword=password
- Linux
- ./ConfigEngine.sh create-page-nodes -DPortalAdminPwd=password -DWasPassword=password
- IBM i
- ConfigEngine.sh create-page-nodes -DPortalAdminPwd=password -DWasPassword=password
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
- 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, you must also specify
the VirtualPortalContext property. You can specify
the VirtualPortalHost property by itself only
if the host name is unique.
- VirtualPortalContext
- Specify the virtual portal context that identifies the virtual
portal. For example, vp1.
You 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 you 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 WebSphere® Integrated Solutions Console. Each thread
requires a database connection. For optimal performance, ensure that
your database connection pool supports at least as many connections
as there are threads in the pool.
- Excluded
- Specify 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.
- Optional: If you used web content pages before
you enabled managed pages, you can transfer the content for those
pages to the Portal Site library. For details on this transfer, read Transferring
content associations to the Portal Site library.
- Optional: Ensure that users have appropriate
access to the Web Content Manager REST
virtual resource so they can use Edit mode. For example, they have user access.