Changing the authschemes.xml File 

Use

You can change the authschemes.xml file using the Config Tool of SAP Web Application Server Java. When you edit the file, you should download the file to a local directory, edit it, and when uploading the edited file, create a new node in the configuration tree for it. In this way you do not loose the original version of the file.

Prerequisites

All dispatcher and server nodes in the cluster are shut down.

Procedure

...

       1.      Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee\configtool\configtool.bat.

       2.      Choose the symbol for Switch to configuration editor mode.

       3.      In the tree, navigate to cluster_data → server → persistent → com.sap.security.core.ume.service.

       4.      To switch to edit mode, choose  (Switch between view and edit mode).

       5.      In the tree, select authschemes.xml and choose  (Show the details of the selected node).

       6.      Choose Download and save the file to a local directory.

       7.      Edit the file locally.

       8.      Create a new node in the configuration tree for the edited file as follows:

                            a.      Select the node com.sap.security.core.ume.service.

                            b.      Choose the symbol for Create a node below the selected node ().

                            c.      Select the type File-entry.

                            d.      Choose Upload and select the file from your local directory.

                            e.      Enter the name for the entry, for example, authschemes_productive.xml. By default, the name of the uploaded file is used.

                              f.      Choose Create.

                            g.      Choose Close window.

The new node appears in the configuration tree.

For UME to use the new file, you have to change the value of the property login.authschemes.definition.file to the name of the new authschemes file. Change the property as described in Editing UME Properties.

       9.      Restart the nodes in the cluster for the changes to take effect.