The aim of this article is to show how to change the UME (user management Engine) of a J2EE engine from ABAP Server to  local DB .


The User Management Engine (UME) provides a centralized user management for all Java applications and can be configured to work with user management data from multiple data sources. It is seamlessly integrated in the J2EE Engine of SAP Web Application Server Java (SAP Web AS Java) as its default user store and can be administrated using the administration tools of SAP Web AS Java. The UME runs as a service in the J2EE Engine of the SAP Web AS Java and is set up as the default user store of the J2EE Engine. By default when a JAVA server is installed, the UME is set to local DB or to USE ABAP Data source. However, depending on future needs and business requirements, this can be changed to use an R/3 server or a LDAP server which is SAP certified

Please see the note :- 718383 – NetWeaver: Supported UME Data Sources and Change Options to understand the limitations of changing the UME back to JAVA data source from ABAP data source

“When You have chose UME to  dataSourceConfiguration_abap.xml ; i.e., ABAP system as Data source No change is possible.”

This configuration supports all usages (especially SAP Exchange Infrastructure and SAP Enterprise Portal) by making ABAP users and ABAP roles available as users and groups in the UME, and supports the creation of new groups in the UME (which are then stored in the local database) as well

Ume Change from ABAP To Local Db Incase Of Standalone J2ee

Such a change is not supported due to the same reasons mentioned in the note 718383. SAP cannot guarantee that the system will operate 100% correctly after changing the datasource – it is not officially supported.

Procedure to change the UME configuration

Open the config tool and  edit the configuration .

Configuration>  cluster_config > system  >custom_global  >cfg > services  >com. sap. security. core. ume. service > Propertysheet properties

/wp-content/uploads/2015/02/1_647511.png



export the property sheet  and save the copy .

/wp-content/uploads/2015/02/2_647006.jpg

Stop the SAP system and change the configuration for Property sheet of com.sap.security.core.ume.service for the below properties

1)  Change the property ume.persistance.data_source_configuration to Default value 

/wp-content/uploads/2015/02/3_647512.jpg

2) Change the property  ume.r3.connection .master.RFCDestination  to Default Value .

/wp-content/uploads/2015/02/4_647525.png

3) Change the property ume.r3.conection.master.RFCDestinationForChanges to  Default Value .

4) Change the property ume.tpd.companies to ‘0’

5) Change the property ume.tpd.imp.class to default values

/wp-content/uploads/2015/02/5_647527.jpg

After changing the properties in the configtool ,save the changes and restart the Java cluster .

Make sure that all the applications are started in Java instance , we can restart the applications using  below telnet

telnet localhost 5<nn>08

username :- administrator

password :XXXXXXXX

>START_APP -all

Once all the applications are started logon to portal  and navigate to NWA>Configuration>Identity management >configuration > Data source  should reflect to local Java Database

/wp-content/uploads/2015/02/6_647544.jpg

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply