ConfigEngine.bat enable-managed-pages -DPortalAdminPwd=password -DWasPassword=passwordAIX® Linux™ Solaris
./ConfigEngine.sh enable-managed-pages -DPortalAdminPwd=password -DWasPassword=passwordIBM® i
ConfigEngine.sh enable-managed-pages -DPortalAdminPwd=password -DWasPassword=passwordz/OS®
./ConfigEngine.sh enable-managed-pages -DPortalAdminPwd=password -DWasPassword=password
After running 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.
For each server, 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.
ConfigEngine.bat create-virtual-portal-site-nodes -DPortalAdminPwd=password -DWasPassword=passwordAIX Linux Solaris
./ConfigEngine.sh create-virtual-portal-site-nodes -DPortalAdminPwd=password -DWasPassword=passwordIBM i
ConfigEngine.sh create-virtual-portal-site-nodes -DPortalAdminPwd=password -DWasPassword=passwordz/OS
./ConfigEngine.sh create-virtual-portal-site-nodes -DPortalAdminPwd=password -DWasPassword=password
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.
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, it is not recommended that you run the task frequently. The initial run of the task requires the most time, while subsequent runs typically require less time.
ConfigEngine.bat create-page-nodes -DPortalAdminPwd=password -DWasPassword=passwordAIX Linux Solaris
./ConfigEngine.sh create-page-nodes -DPortalAdminPwd=password -DWasPassword=passwordIBM i
ConfigEngine.sh create-page-nodes -DPortalAdminPwd=password -DWasPassword=passwordz/OS
./ConfigEngine.sh create-page-nodes -DPortalAdminPwd=password -DWasPassword=password
By default, this task is performed 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.
Specify the host name of the virtual portal. For example, vp.example.com.VirtualPortalContext
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.
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.
Indicate whether you want the task to run with multiple threads. A value of false indicates a single thread and is the default setting.Excluded
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.
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.