Show TOC

Procedure documentationChanging the Texts of Notification E-Mails Locate this document in the navigation structure


The user management engine (UME) ships with default texts for notification e-mails. These texts are stored in a Java archive (JAR) file on the SAP NetWeaver Application Server (AS) Java. You can modify the default texts and store them in the configuration store of the AS Java. The modified texts stored in the configuration store have priority over the texts in the JAR file and are not overwritten during an upgrade.

The notification texts are defined in packaged files. There are a number of files delivered with the UME. Each file includes the e-mail notification texts for a single Java locale. User management also provides a range of placeholder variables that you can use in the text.


This procedure requires you to stop the AS Java, so you should plan for the required downtime while the AS Java restarts.


  1. Create a file for the language you require, and enter the texts that you want to use for notification e-mails.

    Recommendation Recommendation

    We recommend that you copy an existing file and modify it as required.

    To modify an existing file, proceed as follows:

    1. On the file server, navigate to the following location:


    2. From the file, extract the file

    3. From the file, extract the file notificationTexts_<Java_locale>.properties.

      The Java locales consist of the ISO 639-1 language code and an optional ISO 3166 country code separated by an underscore (_).

      Example Example

      There is a separate file for each language. German texts are defined in Texts for Hong Kong Chinese are defined in To modify the e-mail message in several languages, you must modify all the corresponding files.

      End of the example.
    4. Create a copy of the file and modify the copy as required.

      For line breaks, use \n control sequence.

      The following placeholders are defined and can be used to pull relevant variables from the user data.

      Placeholder Variables for User Data




      Display name of the sender.


      Salutation of the sender.


      First name of the sender.


      Last name of the sender.


      Display name of the receiver.


      Salutation of the receiver.


      First name of the receiver.


      Last name of the receiver.


      Password of the receiver.

      Note Note

      The system replaces the placeholder with the password:

      • When users register themselves and the system generates the user passwords automatically

      • When users reset their own passwords with the logon help

      • When the user administrator changes or resets the user’s password

      • When the user administrator creates a new user

      End of the note.

      Caution Caution

      The system sends the password in plain text. Users must change their passwords at the first opportunity.

      End of the caution.


      Free text. This is the text that the administrator or user can add in the text box, for example when locking a user. Do not remove the free text placeholder.

    5. Save the file with the name<Java_locale>.properties.

      Note Note

      When determining which file to use for the notification texts, the UME uses the following criteria:

      • If the Java locale of the user is specified, the UME tries to match the Java locale in the user profile with the Java locale in the filename. The UME checks for that exact Java locale, then checks for the less specific versions of the locale until it finds a match.

        Example Example

        Donna Moore has specified a Java locale en_US_Bronx in her user profile during self-registration. The UME first checks for a file with en_US_Bronx. If it cannot find one, it checks for a file with en_US. If it cannot find one, it checks for a file with en. If it still cannot find one it uses the default notification texts.

        End of the example.
      • If the Java locale of the user is not specified, the user receives the text from the default e-mail notification text file.

      End of the note.
    End of the recommendation.
  2. Upload the file to the AS Java as follows:

    1. Shut down all cluster elements.

    2. Start the config tool.

    3. Choose the Switch to configuration editor mode (Switch to configuration editor mode) pushbutton.

    4. In the Display Configuration tab, choose   cluster_config   system   custom_global   cfg   services   persistent  .

    5. Choose the Switch between view and edit mode (Switch between view and edit mode) pushbutton.

    6. Select the persistent node and choose the Create sub-node (Create sub-node) pushbutton.

      A dialog box appears.

    7. Choose File entry.

    8. Upload the file you created.

      The text of your file appears in the text field.

    9. Create the file and then close the window.

      A new entry appears under persistent with the name<Java_locale>.properties.

    10. Restart all cluster elements.


The modified texts appear in the notification e-mails.