Install the authoring portlet
Pages that include the Web Content Management authoring portlet and the local rendering portlet are created when you first install WebSphere Portal. You only run the authoring portlet configuration task if you have previously uninstalled your authoring or local rendering portlets. The authoring portlet configuration task will automatically create Web Content Management pages and install the authoring portlet and local rendering portlets.
- Run the configuration task...
profile_root/ConfigEngine
./ConfigEngine.sh configure-wcm-authoring -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password- Log out of the portal and log back in.
- Select Web Content from the product banner to access the authoring portlet.
For a clustered environment, if the authoring portlet does not display after installation, you may need to activate the portlet.
See managing portlets for more information.
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 WebSphere Portal functions, such as date selection fields. These will be displayed using the locale of the WebSphere Portal server. For this reason, the language and locales of the site being created, the client and server should be consistent.
If your site contains content in different languages, then a separate Web Content Management authoring applications should be setup for each language on different 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 Management dialogs will be closed. A user will also have to start a new session before it is displayed using the new locale. It is best practice to have the client's correct locale set prior to using Web Content Management.
Parent topic:
Configure a Web content authoring environment