Setting the preferred language for the whole application is a two-step process:
For the server component, you have to set the context parameter
called locale
in its web.xml
:
<context-param>
<param-name>locale</param-name>
<param-value>en</param-value>
</context-param>
This setting will affect mostly the labels on the chart images, as these are the only resources generated by the server component that are language-dependent.
For the portlets, you have to set the context parameter
which configures the JSTL library in the portlet module
web.xml
:
<context-param>
<param-name>javax.servlet.jsp.jstl.fmt.locale</param-name>
<param-value>en</param-value>
</context-param>
This setting will specify the language for the whole web-based user interface.
Both these parameters accept the standard Java locale signs as value, but please make sure that the property file of the selected language is available in your distribution. Please see the project site for localized versions available.
For advanced users: as you see, one server supports only one language set, which is absolutely sufficient in most of the cases. A multi-language server would require a more complicated caching mechanism (some parts of the content are language-independent thus could be shared between client requests with different locale settings, while others are not), which is necessary only in some infrequent environments. As workaround, for two languages you can launch two separate Kosmos servers with different language settings.