In today's blog post we will explain a few lessons around WebSphere Portal and Web Content Manager Administration:
1. How to exclude the friendly name of a page in the path:
When building the friendly URL for a page, WebSphere Portal will add the friendly names of all pages in the hierarchy to the final URL. For example in a content structure Content Root -> Home -> MyPage the URL for the page MyPage would look like /wps/portal/Home/MyPage (or /wps/myportal/Home/MyPage for an authenticated user) -
note that it is possible to configure a different context root if needed.
Now if one wants to exclude a page in the hierarchy it is possible to set the friendly name of the page to the following value: com.ibm.portal.friendly.wildcard
In our sample above by setting the friendly name com.ibm.portal.friendly.wildcard for the label Home the resulting URL for the page MyPage would be /wps/portal/MyPage (or /wps/myportal/MyPage for an authenticated user).
This is documented in more detail here:
2. How to exclude a page / hierarchy from being managed by managed pages:
If you do not want parts of your page hierarchy to be managed pages - meaning stored in WCM in the Portal Site library and syndicated if syndication is configured - it is possible to exclude pages / page hierarchies by setting a configuration flag for the page. Reasons for excluding pages from being managed could be the need to not syndicate certain pages to production since they are not needed there or a desire for moving those pages manually via XMLAccess.
Note: There is no indication in the UI if a page is managed in WCM or not. Thus excluding parts of a site may lead to a very confusing end user experience. Ideally all pages that can be edited by non admin users should be managed pages.
To exclude a page from being managed, use XMLAccess to configure the setting has-system-mapping = false as a property of the content-mapping-info tag for the page in question.
Our recommendation is to create a root page with the has-system-mapping = false setting via XMLAccess and have all the "un-managed" pages below.
3. Configuring Syndication via command line:
With Version 8 we allow to configure Syndication from the subscriber via command line. That can be particular helpful in an empty Portal that does not have a user interface.
See the following documentation for details on configuring this:
4. Is it possible to install 220.127.116.11 fix pack and the latest cumulative fix in one step?
Yes - we support installing both via the IBM Installation Manager in one step. Note that when using the command line to install the maintenance packages you will need to download both repositories.
5. Issues with maintenance installs if the basic authentication TAI is disabled
Among other things the basic authentication Trust Association Interceptor is used to authenticate requests for the theme resources stored in webdav. As part of maintenance we sometimes update the default theme
files in webdav. If the TAI has been disabled for the mycontenthandler URLs the authentication will fail and the webdav update will not take place. That can lead to issues later on.
Before installing maintenance the TAI should be re-activated.
6. How to prevent duplicated default pages after syndication
If using the Portal 8 Managed Pages feature and triggering the initial syndication of the "Portal Content" WCM library without first emptying the target system, the target system will contain some Out of the Box pages from both the Syndicator and the Subscriber. To prevent this issue, follow the documented Staging to Production approach that contains a step to first empty the default virtual Portal or creating a virtual Portal empty via the command line.
See the following article for more information on Initial Staging to Production:
7. Issue with Firefox and Managed Pages page creation
WebSphere Portal 18.104.22.168 CF6 or higher address an issue with Firefox when creating a managed page.
8. Create a javacore, heapdump, system core from the WAS Console
With WebSphere Application Server 8 and higher it is now possible to trigger the creation of a heapdump, javacore or system dump from within the Websphere Application Server Admin Console for any process in the currently managed cell or standalone server.
The feature is available under Troubleshooting -> Java dumps and cores.
9. Modifying contenthandler / mycontenthandler URLs via ConfigService setting
If you would like the contenthandler / mycontenthandler URLs to change to e.g. trigger a reload of certain theme resources from the server you can trigger that by modifying the WP ConfigService and setting a key "digest.seed" to any string, which will then be used on next portal restart to seed the digest used in the URLs.
You can find more information here: http://www-01.ibm.com/support/docview.wss?uid=swg21647572