Install the authoring portlet
Pages that include the Web Content Manager authoring portlet and the local rendering portlet are created when we first install WebSphere Portal. 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 Manager pages and install the authoring portlet and local rendering portlets.
Install on AIX, IBM i, Linux, Solaris, and Windows
- Open a command prompt and run...
cd 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 banner to access the authoring portlet.
- If the authoring portlet does not display after installing in a cluster, we might need to activate the portlet.
Install on z/OS
- Start the Customization Dialog.
- Navigate to the Configure Web Content Manager panel:
Configure WebSphere Portal | WebSphere Portal for z/OS | Application Configuration Tasks | Configure Web Content Management | Deploy Authoring Portlets | Define variables
- Select the option for the variables to define, and follow the panels to define the variables.
- Generate the customization jobs.
- Follow the Customization Dialog instructions for submitting the customization jobs.
- If the authoring portlet does not display after installing 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 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 the site contains content in different languages, then a separate Web Content Manager 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 Manager 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 Manager.
Parent: Configure a web content authoring environmentRelated: