Search Process for Determining the Required Resource Bundle 

A resource bundle consists of a set of properties files that contain language-specific keys/value pairs. Each properties file in the resource bundle has a shared name (see Creating Language-Dependent Resources at Design Time) and the respective language key. The following naming convention is used for a Web Dynpro application: Resource+<Web Dynpro component name>_<language key>_<country>.properties.

At runtime, the relevant properties file is loaded dynamically, depending on the language ID of the current user. If the Web Dynpro application requires user authentication, the language indicator is determined through the data of the user who is logged on. If the Web Dynpro application does not require user authentication, the language key of the used browser is used for the selection of the properties file.

Search Process

Web Dynpro determines the language used for each application instance in accordance with the following rules:

...

·        With user authentication
In the case of applications that require a user logon (that is, authentication), Web Dynpro uses the language that is assigned to this user as the language indicator.

·        Without User Authentication
If no user authentication is required for the Web Dynpro application, then the language indicator of the used browser is taken for the selection of the properties file – provided the Web Dynpro application does not run in the portal. 

The search for the required properties file is done in accordance with the standard mechanisms for Java resource bundles through the suffixes of the properties files. This means that the text search is begun in the properties file using the determined language indicator; if the search is unsuccessful, the properties file with the default language indicator of the Java Virtual Machine is searched for. If this search, too, is unsuccessful, the search in the properties file will end without a language indicator – that is, the search sequence is thus:
Resource+<Web Dynpro component name>+”_”+<Language indicator>+”_“+<Land>
Resource+<Web Dynpro component name>+”_”+<Language indicator>
Resource+<Web Dynpro component name>+”_”+<Default language indicator of the Java Virtual Machine>+”_“+<Land>
Resource+<Web Dynpro component name>+”_”+<Default language indicator of Java Virtual Machine>
Resource+<Web Dynpro component name>.

Therefore, when you develop a Web Dynpro application, make sure that you use a project language that will be understood by most of the application users. The project language defines the language in which the texts are stored in the default resource bundle without a language indicator. To avoid texts appearing in several different languages simultaneously, you should ensure that the project language for all development components involved in an application is selected uniformly.

Determining the Language Indicator for JCo Links

The system variable SY-LANGU for the language in an ABAP-based SAP system is determined from the language that is linked to the JCo connection.

The language that is linked with the JCo connection is determined in different ways:

·        If the JCo connection has been set up manually through API at run time, then – as a rule – the language that was specified when the JCo client was created is used.

This procedure should only be used in exceptional cases.

·        If the JCo connection was created in the Web Dynpro Content Administrator using DefinedUser, then – as a rule - the configured language in the JCo destination is used, irrespective of the language of the user currently logged on. It is also possible to not define any language; in this case, the current language of the user or the application is determined at runtime.

·        If the JCo destination was created in the Web Dynpro Content Administrator using SSOUser, then – as a rule – the language of the current user will be used. This is specified in the User Management logon screen when the user is registered. This procedure is generally used by applications in productive operation that required authentication.