Global Application Settings
Overview
The following Global settings can be set for a Web Content Management solution:
DefaultEncoding This setting is used to set the default encoding for your Site. It is pre-configured as UTF-8. The following languages are supported:
- UTF-8
- Arabic, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian, Italian, Norwegian Polish, Portuguese, Portuguese (Brazilian), Russian, Spanish, Swedish, and Turkish.
- Shift_JIS
- Japanese
- EUC-KR
- Korean
- GB2312
- Simplified-Chinese
- Big5
- Traditional-Chinese
DefaultHost Defines the default host for Web Content Management. Used with "Connect" tags and URL requests that do not include a full host specifier. This is case-sensitive. DefaultURL The URL to retrieve if no tag attributes at all are specified in the request URL. This is case-sensitive. LogRequestParameters Enables or disables printing of query parameters and post parameters in the log MaxConcurrentTasks The maximum number of concurrent tasks the scheduler can execute. This is equivalent to the size of the schedulers thread pool. Proxy Details of Proxy Server. SchedulerSleepPeriod Number of milliseconds that the scheduler will sleep between checking the pending queue for tasks to execute.
Change the Default Encoding of a Site
It is recommended that once the Default Encoding of a Web Content Management server is set, that it should not be changed. This is because any content that already exists in a Site may be corrupted when the default encoding is changed. For this reason, it is very important to determine which default encoding is to be used with your Site when first deploying a Web Content Management solution.
Locale Consistency
The language displayed in the Web Content Management Authoring and Rendering Portlets is determined by the region or locale of the User. There are, however, some elements of the Authoring and Rendering Portlets 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.
Multiple Remote Rendering Portlets on separate servers may need to be created to display sites in different languages to enable features such as Portal Search.
Parent topic: The connect.cfg file.
IBM Workplace Web Content Management - V5.1.0.1 -
Workplace Web Content Management is a trademark of the IBM Corporation in the United States, other countries, or both.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.