Install the authoring portlet
Pages that include the WCM authoring portlet and the local rendering portlet are created when we install HCL WebSphere Portal. You run the authoring portlet configuration task only if we have previously uninstalled your authoring or local rendering portlets. The authoring portlet configuration task automatically creates Web Content Manager pages and installs the authoring portlet and local rendering portlets.
- Open a command prompt.
- Run the configure-wcm-authoring task from the WP_PROFILE/ConfigEngine.
./ConfigEngine.sh configure-wcm-authoring -DPortalAdminPwd=foo -DWasUserid=username -DWasPassword=foo
- Log out of the portal and log back in.
- Select Web Content from the product that is to access the authoring portlet.
Cluster note: If the authoring portlet does not display after we install in a cluster, we might need to activate the portlet.
Locale consistency
The language displayed in the authoring portlet is determined by the region or locale of the user. There are, however, some elements of the authoring portlet that use HCL WebSphere Portal functions, such as date selection fields. They are displayed with the locale of the HCL WebSphere Portal server. For this reason, the language and locales of the site being created, the client and server should be consistent.
If the site contains content in different languages, then a separate Web Content Manager authoring applications should be set up for each language on different HCL WebSphere Portal Servers. These can then be combined into one site using a staging server.
If a user changes their locale, any currently opened Web Content Manager dialogs will be closed. A user also must start a new session before it is displayed using the new locale. It is best practice to have the client's correct locale set before using WCM.
Parent Configure a web content authoring environmentRelated tasks:
Manage portlets in the cluster