Skip to Content

In this blog, I will explain how to set the iView (application) language in the portal, and how the language (locale) is determined by the portal mechanism.

The blog is based on the official SAP documentation: Lookup of Resource Bundle.

The iView language (locale) is determined in the following order (sorted by priority):

 

 

    1. Forced Request Language

 

             A parameter that can be configured in the iView properties. The locale is configured from a

             provided list of locales.

             This parameter forces the iView to be displayed in the selected locale.

             This parameter affects only the locale of the iView itself.

 

A user can also modify the Forced Request Language parameter, provided they have the right permissions, by using the portal iView  personalization.  If the user has made changes to this parameter and has launched the iView, the iView locale will be determined by the user’s  configuration of the Forced Request Language parameter and not by the value of the parameter in the iView properties.

For more information, see:

     SAP NW 7.0x Personalizing iViews

     SAP NW 7.1 and upPersonalizing iViews

The following block is relevant only for AI (Application Integration) iViews:

In the event that the required locale is not on the Java Runtime Environment-supported list of locales, to add additional locales, see Start iViews with  a Dynamically Computed Language.

A known issue is that an iView is displayed in the wrong locale just for a specific user. For this issue, the following SAPnote may help:

1590901 – Enterprise Portal – Unexpected Behaviour Affecting One User Only

 

 

     2. Portal mandatory locale

 

The locale is determined by the following portal runtime configuration properties:

      • request.mandatorylanguage
      • request.mandatorycountry

These properties do not exist by default!

They should be added and configured in the Portal Runtime Properties.

These settings affect the whole portal framework locale.

To configure the Portal Runtime properties:

     SAP NW 7.0x –   Setting Mandatory Language For Portal

     (this should be done for all server nodes of the cluster)

 

     SAP NW 7.1 and upConfiguring the Portal Runtime Properties

     (this should be done for all server nodes of the cluster)

 

 

      3. User locale

 

This locale is defined in the profile of the current user. The user locale can be modified from the Identity Management application.

This setting affects the whole portal framework locale.

       To access Identity Management:

            SAP NW 7.0x Identity Management

 

     SAP NW 7.1 and upIdentity Management

 

When in the Identity Management application, search and select the desired user,

Then, under the General Information Tab, modify the “Language” property to the desired locale according to the list of available languages.

 

General Information language - user locale.png

A user can also modify the portal language ,if they have the right permissions, using the portal personalization.

For more information see Personalizing Your Portal.

If the desired locale is not available from the locale selection list, the following SAPnote will help with configuring additional locales that are supported by the Java Runtime Environment:

1013521 – Configuration of supported languages within the portal

 

 

    4. Request locale

 

The request locale is defined by the browser language settings.

This setting affects the whole portal framework locale.

For example, in IE:

 

             Navigate to Tools –> Internet options –> General –> Languages

Select “Add…” and specify the desired locale.

 

IE set language example - Reqeust locale.png

 

 

Since, in most cases, the browser does send a locale, the next two sections are considered to be a code fallback if the locale is not configured and sent from the browser:

 

   5. Portal default locale

 

The locale is determined by the following portal runtime configuration properties:

      • request.defaultlanguage
      • request.defaultcountry

These settings should be configured in the Portal Runtime Properties and affect the whole portal framework locale.

To configure the Portal Runtime properties:

SAP NW 7.0x

             Example for en_us locale that will display the portal content in English:

               1. Log on to the Portal Server

               2. Navigate to the following path in the SAP installation directory:

                    \\usr\sap\<SID>\JC<InstanceNumber>\j2ee\cluster\server0\apps\sap.com\irj\

                         servlet_jsp\irj\root\WEB-INF\portal\system\properties

               3. Open the file ‘prtDefault.properties’

               4. Modify the parameters to the desired locale:

 

        • request.defaultlanguage=en
        • request.defaultcountry=us

               5. Save the file and restart the server for changes to take effect.

 

SAP NW 7.1 and upConfiguring the Portal Runtime Properties

 

 

    6. System default locale

 

             This is the Java default locale defined by the system, either by the operating system or by

             the JVM. This setting affects the whole portal framework locale.


You want to influence the product roadmap of SAP Enterprise Portal? You plan to implement your Portal in the cloud? Seize the opportunity and make a difference by providing your feedback: https://blogs.sap.com/2016/10/11/2016-elections-vote-now/.

 

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Noël Hendrikx

    Hi Etay,

    Thanks for the information. In the past it gave me headaches 🙂

    Here are some best practices as well:

    Portal mandatory language and forced request languages are used when your application does not support other languages. Storing the language in the UME (User Locale) is a good option if you want to control the number of languages – also for supporting your applications.

    Request locale can give you languages you don’t support. If you are using standard SAP apps, they should support every language. If you want to use Request locale then, make sure the User Locale in the UME is empty 🙂

    Cheers,

    Noël

    (0) 
  2. Rama P

    Nice Blog.

    Just need to understand few more points related to browser language setting for BEx iViews.

    In Portal 7.0, the browser language forces the back-end language(set to some other locale) when the language in UME is not set.

    But, in 7.4 the back-end(BW system) language is only considered for BEx iViews even though  the browser language is set to something else.

    In our case, we use FPN and producer(BW) portal uses ABAP data source and consumer portal is configured to LDAP data source.

    Any inputs are highly appreciated. Thank you.

    (0) 

Leave a Reply