Customizing a UME Data Source Configuration 

Purpose

UME provides data source configuration files that define a configuration for standard scenarios. If none of these files cover the scenario that you require, you can modify the existing configuration files according to your requirements.

This option is not recommended. Normally you should only need to change the data source configuration files if you are using an LDAP directory as data source and need to adapt the attribute mappings.

Before changing a configuration file, make absolutely sure that none of the preconfigured files meet your requirements. If at all possible, use one of the preconfigured files rather than creating your own.

If you have to create a customized configuration file, you should set up a dedicated project with experienced project members for creating the customized file.

Upgrades may include changes to the shipped data source configuration files. When you perform an upgrade to your SAP Web AS Java installation, these changes will not be reflected in your modified configuration files. You will have to add these changes to your modified files manually.

The following section outlines how to define your own data source configuration.

In Data Source Types, Home Data Source, Data Partitioning Scenarios, and Namespaces, concepts are explained that will help you when you define your configuration.

The section on Structure of a Data Source Configuration File explains the logic behind the different sections of the configuration file.

The examples show you how to implement different types of data partitioning scenarios.

The remaining topics outline additional scenarios that you can optionally configure. These include:

·        Configuration of More Than One LDAP Data Source – for scenarios where user data is distributed across more than one LDAP directory server.

·        LDAP only: Multiple Object Classes for a Principal Type – allows you to specify more than one object class for a principal type

·        LDAP Only: Negative User Filter – allows you to define that certain users and accounts are not displayed on the user interface and are not taken into account by the UME.

Prerequisites

·        You have clearly defined where you want user management data to be read, searched, and written to.

·        You have installed SAP Web AS Java with the option to use a database for user management.

Procedure

...

       1.      Download the data source configuration file that most closely meets your requirements. See Editing UME Configuration Files.

       2.      Adapt the file as required.

       3.      Verify the correctness of your data source configuration file using the document type definition (DTD) file, which you can find at the same location as the data source configuration files.

       4.      Upload the data source configuration file under a different name. See Editing UME Configuration Files.

Result

You have created a new data source configuration file.

To configure UME to use it, set the UME property ume.persistence.data_source_configuration to the name of the new configuration file.

ume.persistence.data_source_configuration=dataSourceConfiguration_new.xml

For an example of how to activate a new data source configuration after installation, see Configuring UME to Use an LDAP Server as Data Source.