SAP NetWeaver Identity Management Migration Guide SAP NetWeaver Identity Management 7.2

SAP NetWeaver Identity Management Migration Guide SAP NetWeaver Identity Management 7.2
Migration Guide
SAP NetWeaver Identity Management 7.2
Document Version: Rev 18 – 2015-10-30
SAP NetWeaver Identity Management
Migration Guide
PUBLIC
Content
1
SAP NetWeaver Identity Management Migration Guide – Identity Management 7.1 to 7.2. . . . . . . .4
2
Migrating the Identity Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1
Upgrading the Identity Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Upgrading the Identity Center Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Upgrading the Identity Center Runtime Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Preparing the Identity Management Data Migration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Upgrading the Identity Center Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Upgrading Dispatcher and Event Agent Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3
Migrating the Virtual Directory Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1
Updating Connector Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4
Migrating Other Identity Management Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1
Crystal Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2
SAP NetWeaver Business Warehouse Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Updating the BI Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring the BW Connector on the Virtual Directory Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Adjusting the Configuration in the Identity Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.3
Provisioning Framework for SAP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.4
Provisioning Framework for Lotus Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5
Integration with SAP BusinessObjects Access Control (GRC Provisioning Framework). . . . . . . . . . . . . 20
4.6
Identity Provider for SAP NetWeaver Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.7
Data Import from HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5
Turning off 7.1 Compatibility Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6
Migrating a Production Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
6.1
Upgrading the Identity Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Preparing the QA system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Upgrading the Identity Center on the Production System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.2
Migrating Other Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7
Important Changes in Identity Management 7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.1
Reference Attributes Stored in mxi_link Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2
Changed Handling of Reference Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
7.3
New and Removed Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.4
No Pending Value Object for Future Values of Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.5
uApplyPending. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Content
7.6
Handling of Old Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.7
Configuration of the Password Reset Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.8
Approval Timeout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.9
Inactive Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.10
uIS_SetValue/ uIS_Create. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.11
Historic Values for Pending Value Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
SAP NetWeaver Identity Management Migration Guide
Content
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
3
1
SAP NetWeaver Identity Management
Migration Guide – Identity Management 7.1
to 7.2
This document describes the process of upgrading a solution developed with SAP NetWeaver Identity
Management 7.1 to SAP NetWeaver Identity Management 7.2.
Introduction
If you are running the provisioning framework for SAP systems in your Identity Management 7.1 environment, see
the document SAP NetWeaver Identity Management for SAP System Landscapes: Upgrading from Identity
Management 7.1 to 7.2.
Note
Before upgrading from Identity Center 7.1 to Identity Center 7.2, please see the SAP NetWeaver Identity
Management Release Notes.
The data structure of the Identity Center database has changed from Release 7.1 to Release 7.2. Before you can
start the system after an upgrade, the existing data has to be converted to the new data structure.
After an upgrade, the database is in 7.1 compatibility mode, which means that additional data is maintained in the
database to satisfy the needs of existing 7.1 implementations. This means that most existing tasks and jobs
should work as in version 7.1. You can verify that the database is in 7.1 compatibility mode by viewing the Database
tab of the Identity Center properties.
Note
Running the system in 7.1 compatibility mode decreases performance and uses more database space.
Target Audience
This document is written for people who are to upgrade from SAP NetWeaver Identity Management 7.1 to SAP
NetWeaver Identity Management 7.2.
4
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
SAP NetWeaver Identity Management Migration Guide – Identity Management 7.1 to
7.2
Prerequisites
To get the most benefit from this document, you should have thorough knowledge about SAP NetWeaver Identity
Management.
SAP NetWeaver Identity Management Migration Guide
SAP NetWeaver Identity Management Migration Guide – Identity Management 7.1 to
7.2
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
5
2
Migrating the Identity Center
This section describes how you migrate each of the components of the Identity Center.
Analyzing the configuration
Before you upgrade from Release 7.1, you should analyze your configuration to identify any potential problems
with your configuration when running Release 7.2. To do this, you use the Identity Management Configuration
Analyzer that produces a report containing a list of issues that need to be resolved before you upgrade to Release
7.2.
For an overview of important changes between SAP NetWeaver Identity Management 7.1 and 7.2, see Important
changes in Identity Management 7.2.
The report from the Configuration Analyzer contains a list of issues. For the following issues you can choose
whether you want to solve the issues manually before you run the Data Migration Tool, or whether you want the
Data Migration Tool to solve the issues:
● Entries without entry type.
● Entries without MSKEYVALUE.
● References to non-existent entries.
● Entries that are marked as inactive, but the entry type is not defined as an identity.
For more information about the Data Migration Tool, see Preparing the Identity Management Data Migration Tool.
For more information about the Configuration Analyzer see SAP NetWeaver Identity Management Using the
Configuration Analyzer.
Related Information
Important Changes in Identity Management 7.2 [page 28]
Preparing the Identity Management Data Migration Tool [page 9]
6
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating the Identity Center
2.1
Upgrading the Identity Center
To migrate an Identity Center from Release 7.1 to Release 7.2, you must upgrade all components as described
below.
Context
Note
If you are upgrading a production environment, see Migrating a Production Environment.
The process involves the following steps:
Procedure
1. Remove the access to the Identity Management User Interface to prevent changes during the upgrade
process. See Upgrading the Identity Center on the Production System.
2. Stop dispatchers and event services and wait until all jobs have stopped.
Note
It is important that there is no activity in the database during the upgrade process.
3. Back up the Identity Center database.
4. Upgrade the Management Console.
5. Upgrade the Runtime Components.
6. Upgrade the Identity Center database.
7. Upgrade dispatcher and event agent services.
8. If in use on systems without the Management Console: Update the Windows runtime engine separately.
9. Upgrade the Identity Management User Interface, see Installing and Configuring the Identity Management
User Interface in SAP NetWeaver Identity Management Installation Guide.
10. Restore access to the Identity Management User Interface.
11. Start dispatchers and event services.
Results
After this process, all components are upgraded to Release 7.2, but the system runs in 7.1 compatibility mode. To
change to 7.2 pure mode, see Turning off 7.1 Compatibility Mode.
SAP NetWeaver Identity Management Migration Guide
Migrating the Identity Center
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
7
Related Information
Migrating a Production Environment [page 24]
Upgrading the Identity Center on the Production System [page 25]
Turning off 7.1 Compatibility Mode [page 22]
2.1.1 Upgrading the Identity Center Management Console
The installation path for the Identity Center Management Console has changed from Identity Management 7.1 to
7.2.
Context
The default installation path for Release 7.1 was c:\program files\SAP\IdM\Identity Center. For Release
7.2, this is changed to c:\usr\sap\IdM\Identity Center.
To ensure a correct installation, proceed as follows:
Procedure
1. Uninstall Release 7.1 of the Identity Center Management Console.
2. Make sure to keep a copy of the file emsconfig.xml and the \key folder containing the keys.ini file that is used
for encryption.
Caution
If you loose the Keys.ini file you will not be able to decrypt any of the data in the database.
3. Install Release 7.2 of the Identity Center Management Console.
4. Copy the file emsconfig.xml and the \key folder to the new install directory.
For general information about installing the Identity Center Management Console, see Installing the
Management Console in the SAP NetWeaver Identity Management Installation Guide.
8
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating the Identity Center
2.1.2 Upgrading the Identity Center Runtime Components
The installation path for the Identity Center Runtime Components has changed from Identity Management 7.1 to
7.2.
Context
The default installation path for Release 7.1 was c:\program files\SAP\IdM\Identity Center. For Release
7.2 this is changed to c:\usr\sap\IdM\Identity Center.
To ensure a correct installation, do the following:
Procedure
1. Uninstall Release 7.1 of the Identity Center Runtime Components.
2. If the Runtime Components are installed to a different directory than the Management Console, make sure to
keep the \key folder containing the keys.ini file that is used for encryption.
3. Install Release 7.2 of the Identity Center Runtime Components.
4. If necessary, copy the \key folder to the new install directory.5.
For general information about installing the Identity Center Runtime Components, see Installing the Identity
Center Runtime Components in the SAP NetWeaver Identity Management Installation Guide.
2.1.3 Preparing the Identity Management Data Migration Tool
The Identity Management Data Migration Tool is used migrate the data from Release 7.1 to Release 7.2 data
structure when upgrading the Identity Center. It is also used to remove the reference attributes from the data
structure when changing to pure 7.2 mode.
Context
This is a command line tool that is started from a batch file. This batch file is generated from the Identity Center
Management Console.
Note
The Create Migration tool script button becomes available after the initial upgrade of the Identity Center
database schema.
SAP NetWeaver Identity Management Migration Guide
Migrating the Identity Center
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
9
Note
Make sure that you have defined the JDBC driver for your Identity Center database in Tools/Options… of the
Identity Center. Since you are upgrading from Identity Management 7.1, it should not be necessary to change
this.
To generate the batch file:
Procedure
1. View the properties of the Identity Center and select the Database.
2. Choose Create Migration tool script.
Complete the wizard to provide the necessary information to connect to the Identity Center database. Use the
<prefix>_oper (default mxmc_oper) user to connect to the database.
3. Choose OK to create the script file.
Results
The script file is named MigrateDB.bat and is stored in the Identity Center installation folder, where you can start
the tool from the command prompt.
2.1.4 Upgrading the Identity Center Database
Context
Note
Before you upgrade the database schema from Release 7.1 to Release 7.2, make sure that you have run the
Identity Management Configuration Analyzer as described in Migrating the Identity Center.
Note
See SAP Note 1634988
for information about upgrading the database on Oracle if you are using SAP
NetWeaver Identity Management 7.2 SP03.
10
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating the Identity Center
To upgrade the Identity Center database:
Procedure
1. Oracle only: Run the script grant-oper-rights.cmd to grant additional authorizations to the <prefix>_oper
user. The script must be run as database administrator.
2. Upgrade the Identity Center database schema, see Installing the Identity Center Database on Microsoft SQL
Server and Installing the Identity Center Database on Oracle in SAP NetWeaver Identity Management
Installation Guide.
3. Prepare the Identity Management Data Migration Tool as described in Preparing the Identity Management
Data Migration Tool.
4. Upgrade to the 7.2 data structure with the Data Migration Tool. Open a command prompt and navigate to the
Identity Center installation folder where the generated batch file is stored. Start the batch file in the following
way:
MigrateDB BASIC
Note
The option of the batch file is case sensitive.
Note
How long this process takes, depends on the size and complexity of the Identity Center database. It is
primarily the number of identities (MX_PERSON entries) that is the determining factor.
5. The Data Migration Tool will first analyze the data to identify any potential issues. If it finds some of the issues
mentioned in Migrating the Identity Center, you are asked if you want the Data Migration Tool to solve the
problems.
If you answer No (N), the Data Migration Tool will close without migrating the data and you have to resolve the
reported issues manually before running the Migration Tool again.
If you answer Yes (Y), the Data Migration Tool will do the following:
○ Entries without entry type will be deleted. The entries are moved to mxi_old_values, but no event tasks are
executed.
○ References to non-existing entries will be deleted. The reference attributes are moved to mxi_old_values,
but no event tasks are executed.
○ For entries without MSKEYVALUE the Data Migration Tool will generate and add an MSKEYVALUE in the
following format MX_<MSKEY>_MT.
If the Data Migration Tool encounters errors while processing data, it will either log an error message and exit
and you must run the Data Migration Tool again or it will log the error and continue, depending on the severity
of the error.
6. A log file (MigrateDB.log) is produced where you can see the outcome of the operation.
7. Upgrade the database schema again (run mxmc-update) to complete the database upgrade.
SAP NetWeaver Identity Management Migration Guide
Migrating the Identity Center
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
11
Note
This is a crucial part of the upgrade procedure.
8. If you have upgraded from a version of SAP NetWeaver Identity Management 7.1 prior to SP5, the global
constant MX_RECONCILE is set to FALSE when upgrading to SAP NetWeaver Identity Management 7.2.
Although this is the recommended value, the constant can be set to TRUE to allow for immediate
reconciliation of changes in the role hierarchy. See About performance optimization in the Identity Center help
file for details.
Results
The Identity Center database is now upgraded and configured to run in 7.1 compatibility mode.
Related Information
Migrating the Identity Center [page 6]
Preparing the Identity Management Data Migration Tool [page 9]
2.1.5 Upgrading Dispatcher and Event Agent Services
All dispatcher and event agent services must be updated before they can be started again properly.
Context
For all dispatchers and event agent services on the system, you need to:
Procedure
1. Open the dispatcher configuration for all dispatchers and deselect Housekeeping actions on the Policy tab.
Note
It is critical that no dispatchers are running housekeeping actions during the upgrade process.
2. Uninstall the services.
3. Regenerate the dispatcher/event agent service scripts.
12
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating the Identity Center
4. Reinstall the services.
SAP NetWeaver Identity Management Migration Guide
Migrating the Identity Center
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
13
3
Migrating the Virtual Directory Server
The installation path for the Virtual Directory Server has changed from Identity Management 7.1 to 7.2.
Context
The default installation path for Release 7.1 was c:\program files\SAP\IdM\Virtual Directory Server.
For Release 7.2 this is changed to c:\usr\sap\IdM\Virtual Directory Server.
To ensure a correct installation, proceed as follows:
Procedure
1. Stop and uninstall any local services.
Note
Deployments on SAP NetWeaver AS Java are not affected unless they are using an identity store as a data
source.
2. Close the user interface.
3. Uninstall Release 7.1 of the Virtual Directory Server.
4. Make sure to keep any configuration files in the \configurations folder.
5. Install Release 7.2 of the Virtual Directory Server to the new default directory as described in Installing and
Configuring the Virtual Directory Server in the SAP NetWeaver Identity Management Installation Guide.
6. Copy the contents of the \configurations folder from the old to the new installation directory.
7. Maintain and distribute the keys.ini file as described in SAP NetWeaver Identity Management Security Guide.
8. Open the configuration files you want to upgrade to the new version. If you are using an identity store as a
data source, see Updating Connector Class.
9. Reinstall any local services and/or redeploy any deployed configurations.
Related Information
Updating Connector Class [page 15]
14
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating the Virtual Directory Server
3.1
Updating Connector Class
Context
If you have configurations where an identity store is defined as a data source, you must update the connector
class to be able to use the new data structure after the database is migrated. This must be done after you have
upgraded the Identity Center as described in Upgrading the Identity Center.
Procedure
1. View the properties of the data source and choose the Connectors tab.
2. In the list Use methods from, change the class name from MxIDStoreFlat to MxIDStoreFlat72.
3. Choose OK.
Related Information
Upgrading the Identity Center [page 7]
SAP NetWeaver Identity Management Migration Guide
Migrating the Virtual Directory Server
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
15
4
Migrating Other Identity Management
Components
This section describes how to migrate other Identity Management Components.
Related Information
Crystal Reports [page 16]
SAP NetWeaver Business Warehouse Integration [page 16]
Provisioning Framework for SAP Systems [page 20]
Provisioning Framework for Lotus Notes [page 20]
Integration with SAP BusinessObjects Access Control (GRC Provisioning Framework) [page 20]
Identity Provider for SAP NetWeaver Application [page 20]
Data Import from HCM [page 21]
4.1
Crystal Reports
The reports delivered with SAP NetWeaver Identity Management 7.1 will work when running SAP NetWeaver
Identity Management 7.2 in 7.1 compatibility mode, but they will need to be adapted to the new data structure to
work in pure 7.2 mode.
The reports delivered with SAP NetWeaver Identity Management 7.2 will work both if you run in 7.1 compatibility
mode and in pure 7.2 mode.
Any existing custom reports must be adapted to the new data structure.
For details, see the document SAP NetWeaver Identity Management Identity Center Generating Reports Using
Crystal Reports.
4.2
SAP NetWeaver Business Warehouse Integration
If you used reporting with SAP NetWeaver Business Warehouse with Release 7.1, then consider the following when
upgrading to Release 7.2:
● You must update the BI content for identity management on the BW system.
16
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating Other Identity Management Components
● If you previously set up the BW connector with SAP NetWeaver Identity Management Release 7.1 SP5 up to
patch 1, then you must set up a new connector configuration in the Virtual Directory Server.
● Adjust the configuration in the Identity Center. This includes setting up a repository based on the template
Virtual Directory Server to BW repository, if this does not yet exist, and creating a new job to use for the data
transfer.
The steps to follow are described in the sections that follow.
Prerequisites
● The BW system must have the BI content Add-On Release 7.05 SP2 or higher installed.
● The Identity Center and Virtual Directory Server have been upgraded to Release 7.2.
● Any active jobs in the Identity Center that send data to the BW system (via the Virtual Directory Server) are
deactivated in the Identity Center. This prevents data from being transferred while making the changes.
Related Information
Updating the BI Content [page 17]
Configuring the BW Connector on the Virtual Directory Server [page 18]
Adjusting the Configuration in the Identity Center [page 19]
4.2.1 Updating the BI Content
Context
To update the BI content, proceed as follows:
Procedure
1. Use transaction SA38 and execute the report RSBCT_IDM_DEL_IOBJ_MASTER_DATA to delete the master
data from all 0IDM_* InfoObjects (but not from the DataStore object 0IDM_ENAT). The deletion will take
some time to complete.
2. Afterwards, make sure the 0IDM_* InfoObjects do not contain any master data.
3. Activate the BI content for Identity Management as described in the implementation guide for Identity
Reporting Using SAP NetWeaver Business Warehouse.
SAP NetWeaver Identity Management Migration Guide
Migrating Other Identity Management Components
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
17
Note
You can skip the section for specifying the target source system if this has already been done. In this case,
you must know the name of the source system to be able to proceed.
When collecting the objects, select Match (X) or copy if you have made any changes that should not be
overwritten by the activation, but merged with the updates delivered by SAP.
There is a new field Context that causes a warning due to an incompatible change in the Web service
implementation. Confirm the regeneration of the Web service.
The activation can take some time to complete.
4. Make sure there were no errors during the content activation. Also make sure that all objects in the InfoArea
are active, in particular DTPs and transformations.
Additional Steps
Procedure
1. In the Data Warehousing Workbench (transaction RSA1), choose Modeling.
2. Expand
Identity Management
0IDM_ENAT -> 0IDM_AT
3. Choose
Execute
Attribute
Attribute (Attribute)
Data Transfer Processes
Full DTP:
and select the Data Transfer Process with a double-click.
Execute
to start the Data Transfer Process.
4. When asked whether to display the request monitor, choose Yes. Choose Refresh until the Data Transfer
Process has been completed, then select Back to return to the Data Warehousing Workbench.
5. In the Data Warehousing Workbench, choose Administration.
6. Select Process Chains in the left pane.
7. Expand the display component node without a name and select process chain Identity Management: Delta
Load with a double-click.
8. Choose Execution Execute Synchronously
execution has been finished.
to start processing immediately. Wait until the process chain
4.2.2 Configuring the BW Connector on the Virtual Directory
Server
Because there have been updates in the template used to create the connector, you must set up a new one if your
BW connector was set up for SAP NetWeaver Identity Management 7.1 SP5 up to patch 1.
Note
This is only relevant if you are upgrading from SAP NetWeaver Identity Management 7.1 SP5 up to patch 1. If
you are upgrading from Release 7.1 with a higher patch level for SP5 or with a higher SP, you can skip this step.
18
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating Other Identity Management Components
Create the connector as described in the implementation guide for Identity Reporting Using SAP NetWeaver
Business Warehouse.
Once completed, make sure the correct connector configuration is open and start the Virtual Directory Server.
4.2.3 Adjusting the Configuration in the Identity Center
Context
For more information, see the implementation guide for Identity Reporting Using SAP NetWeaver Business
Warehouse.
Procedure
1. If you have not already done so, set up a repository to use for the Virtual Directory Server based on the
template VDS to BW repository. Specify the hostname, port, user ID, and password for the VDS as they were
previously configured.
2. Create a new job to use for the data transfer based on the template IDM to BW Data Transfer. Select the
repository created above to use for the job.
Note
There were changes made in the corresponding job template for SAP NetWeaver Identity Management 7.2,
therefore, even if you have an existing job set up, create a new one to make sure that these changes are
taken into account.
3. Check whether the old job contains any variables starting with DELTA_PREV_LAST_*.
○ If yes: In this case, the new job can reuse the delta load state from the old job, so its first run will only
transfer the data that has been changed in the Identity Center after the last run of the old job. To achieve
this, copy all DELTA_PREV_LAST_* variables from the old job to the new job.
○ If not: In this case, the old job is still based on the job template delivered with release 7.1 SP5 up to patch
1. In this case, it is not possible for the new job to take over the delta load state from the old job.
Therefore, you must restore the initial state in the BW system and run a new initial load using the new job
first. For more information, see the implementation guide, section Running an Initial Load.
4. Run the new job to make sure everything works.
5. After the new job has run successfully, delete any potentially existing variables which have a value such as
This variable can be deleted.
6. Delete the old job.
7. Schedule the new job to run periodically.
SAP NetWeaver Identity Management Migration Guide
Migrating Other Identity Management Components
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
19
4.3
Provisioning Framework for SAP Systems
The existing framework (for Identity Management 7.1) can be used on Identity Management in 7.1 compatibility
mode. For information about how to upgrade a production environment running the provisioning framework for
SAP systems, see SAP NetWeaver Identity Management for SAP System Landscapes: Upgrading from Identity
Management 7.1 to 7.2.
4.4
Provisioning Framework for Lotus Notes
The existing framework runs in 7.1 compatibility mode. There will be a new Lotus Notes framework using the new
Provisioning Framework for SAP systems to be run in pure 7.2 mode. There is no upgrade path between the two
frameworks. For details, see SAP NetWeaver Identity Management Identity Center Provisioning framework for
Lotus Notes Configuration Guide.
4.5
Integration with SAP BusinessObjects Access Control
(GRC Provisioning Framework)
The existing framework runs in 7.1 compatibility mode. There will be a new framework for SAP BusinessObjects
Access Control to be run in pure 7.2 mode. There is no upgrade path between the two frameworks. For details, see
SAP NetWeaver Identity Management Compliant provisioning using SAP BusinessObjects Access Control
Configuration guide.
4.6
Identity Provider for SAP NetWeaver Application
You can upgrade to SAP NetWeaver Identity Management 7.2 without changing your identity provider software or
the AS Java release of the identity provider host. However, to use the security token service or the newest user
interface improvements in the identity provider, you must install the latest federation software component
archive (SCA) and upgrade the host AS Java to release 7.2 SPS 4 or later.
For more information, see:
● SAP NetWeaver Identity Management Identity Provider Implementation Guide
● SAP NetWeaver Identity Management Security Token Service Implementation Guide
20
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating Other Identity Management Components
4.7
Data Import from HCM
If you want to migrate the HCM LDAP export scenario you already used with SAP NetWeaver Identity
Management 7.1, then replace the 7.1 HCM staging area by importing the 7.2 HCM staging area. Afterwards,
update the identity store ID in the following places:
● The HCM template in the Virtual Directory Server
● The HR_STATING_AREA_IDS_ID global constant in the Identity Center
SAP NetWeaver Identity Management Migration Guide
Migrating Other Identity Management Components
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
21
5
Turning off 7.1 Compatibility Mode
Context
As long as the database is running in 7.1 compatibility mode, both the 7.1 and 7.2 data structures must be
maintained. This decreases performance of the solution, and also requires more disk space for the database.
Thus, it is recommended to turn off 7.1 compatibility mode as soon as the implementation is able to run in pure 7.2
mode.
Analyzing the configuration
Before you can run in pure 7.2 mode, the configuration must be compatible with Release 7.2. You use the Identity
Management Configuration Analyzer to produce a report that lists any issues that must be resolved before the
database can be updated to run in pure 7.2 mode.
For an overview of important changes, see Important Changes in Identity Management 7.2.
You may need to update jobs and/or tasks in the configuration according to the report generated from the
Configuration Analyzer.
Note
Make sure that all issues of categories 7.2 pure mode issue and Possible 7.2 pure mode issue are resolved
before you turn off the 7.1 compatibility mode.
When the configuration in 7.2 is ready, you can use the Data Migration Tool to remove the reference attributes
from the 7.1 data structure and remove the compatibility flag:
Procedure
1. Stop the system as when upgrading the Identity Center. (See Upgrading the Identity Center)
2. Back up the Identity Center database.
3. Run the Identity Management Data Migration Tool to remove 7.1 specific data and turn the compatibility flag
off. Open a command prompt and navigate to the Identity Center installation folder where the generated
batch file is stored.
Start the batch file in the following way:
MigrateDB PURE
Note
The option of the batch file is case sensitive.
22
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Turning off 7.1 Compatibility Mode
A log file is produced where you can see the outcome of the operation.
4. Upgrade the database schema again (run mxmc-update) to complete the process.
Note
After the function is completed, you must run mxmc-update. If this is not done, the dispatchers will not
start and you will get a warning from the Management Console.
5. Start the system.
6. Open the dispatcher configuration for all dispatchers and select Housekeeping actions on the Policy tab.
Related Information
Important Changes in Identity Management 7.2 [page 28]
Upgrading the Identity Center [page 7]
SAP NetWeaver Identity Management Migration Guide
Turning off 7.1 Compatibility Mode
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
23
6
Migrating a Production Environment
If the 7.1 system is a production environment based on staging from a development system to the QA and
production system, you must follow the following procedure.
This section describes how you upgrade the software components of the Identity Management in the QA and
production environments. The process starts with upgrading the development environment, which can be done
according to the same procedure.
Normally, you use the Configuration Copy Tool (export/import) to move the relevant parts of the configuration
from the development to the QA system, and Transport to move the whole configuration from the QA to the
production environment. For more information, see the document SAP NetWeaver Identity Management
Implementation guide – Transport.
For information about how to upgrade a production environment running the provisioning framework for SAP
systems, see the document SAP NetWeaver Identity Management for SAP System Landscapes: Upgrading from
Identity Management 7.1 to 7.2.
Note
A prerequisite for this procedure is that the 7.1 production system is bootstrapped and maintained according to
the document SAP NetWeaver Identity Management Identity Center Implementation guide – Staging
environment.
Note
It is not recommended to run a production system in 7.1 compatibility mode due to the impact on performance.
6.1
Upgrading the Identity Center
This section describes how you upgrade the Identity Center in a production environment.
Context
To prepare the QA system, follow the steps below.
24
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating a Production Environment
Preparing the QA system
Procedure
1. Upgrade the QA systems as described in Migrating the Identity Center.
2. Adjust the configuration to Identity Management 7.2 and change to pure 7.2 mode as described in Turning off
7.1 Compatibility Mode.
3. When the production system is upgraded, transport the configuration from the QA to the production system
as described in the document SAP NetWeaver Identity Management Implementation guide – Transport.
Related Information
Migrating the Identity Center [page 6]
Turning off 7.1 Compatibility Mode [page 22]
6.1.1 Upgrading the Identity Center on the Production System
Context
Normally, the Management Console is not installed in the production environment, but you will need that during
the upgrade process. Thus, it is installed and then removed again after you have completed the process.
To upgrade the Identity Center on the production system:
Procedure
1. Remove the access to the Identity Management User Interface to prevent changes during the upgrade
process. This can be done in several ways, depending on the version of the SAP NetWeaver AS Java. For
instance, for EHP 1 for SAP NetWeaver CE 7.1, you can stop the IDM_DataSource from the SAP NetWeaver
Administrator.
2. Stop dispatchers and event services.
Note
It is important that there is no activity in the database during the upgrade process.
3. Back up the Identity Center database.
SAP NetWeaver Identity Management Migration Guide
Migrating a Production Environment
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
25
4. Run the Configuration Analyzer, see Migrating the Identity Center. You can run the Configuration Analyzer
with the option to only show errors in data (not configuration).
5. Fix any reported issues related to the identity store data (not configuration issues, as the configuration will be
transported from the QA system).
6. Upgrade the Runtime Components, see Upgrading the Identity Center Runtime Components.
7. Install the Management Console as described in Installing the Management Console in SAP NetWeaver Identity
Management Installation Guide and create a connection to the Identity Center database as described in the
document SAP NetWeaver Identity Management Identity Center Initial Configuration.
Note
Make sure to copy the keys.ini file from one of the production servers to the server where you install the
Management Console.
Note
In case the Management Console already is installed in the production environment, upgrade according to
the procedure in Upgrading the Identity Center Management Console.
8. Upgrade the Identity Center database, see Upgrading the Identity Center Database.
9. Change to pure 7.2 mode as described in Turning off 7.1 Compatibility Mode.
10. Upgrade the Identity Management User Interface, see Installing and Configuring the Identity Management
User Interface in SAP NetWeaver Identity Management Installation Guide.
11. If in use on systems without the Management Console: Update the Windows runtime engine separately.
12. Transport the configuration from the QA to the production system as described in the document SAP
NetWeaver Identity Management Implementation guide – Transport.
13. Provide access to the Identity Management User Interface.
14. Start dispatchers and event services.
15. Uninstall the Identity Center Management Console.
Results
The production system should now be upgraded to Release 7.2 and run in pure 7.2 mode.
Related Information
Migrating the Identity Center [page 6]
Upgrading the Identity Center Runtime Components [page 9]
Upgrading the Identity Center Management Console [page 8]
Upgrading the Identity Center Database [page 10]
Turning off 7.1 Compatibility Mode [page 22]
26
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Migrating a Production Environment
6.2
Migrating Other Components
You also need to migrate any of the other components you are using as described in Migrating Other Identity
Mangement Components.
For information about how to upgrade a production environment running the provisioning framework for SAP
systems, see the document SAP NetWeaver Identity Management for SAP System Landscapes: Upgrading from
Identity Management 7.1 to 7.2.
Note
The other frameworks you are using will be part of the transport, and will only need to be updated on the
development/QA system.
Related Information
Migrating Other Identity Management Components [page 16]
SAP NetWeaver Identity Management Migration Guide
Migrating a Production Environment
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
27
7
Important Changes in Identity
Management 7.2
This section contains an overview of important changes between Identity Management 7.1 and 7.2 that affect
existing configurations.
When upgrading to Identity Management 7.2, you will need to adjust the configuration before you are able to run in
pure 7.2 mode. You can use the Identity Management Configuration Analyzer to help identify issues in the
configuration.
For more information see SAP NetWeaver Identity Management Using the Configuration Analyzer.
Related Information
Reference Attributes Stored in mxi_link Table [page 28]
Changed Handling of Reference Attributes [page 29]
New and Removed Views [page 31]
No Pending Value Object for Future Values of Reference [page 32]
uApplyPending [page 33]
Handling of Old Values [page 33]
Configuration of the Password Reset Task [page 34]
Approval Timeout [page 34]
Inactive Entries [page 34]
uIS_SetValue/ uIS_Create [page 34]
Historic Values for Pending Value Objects [page 35]
7.1
Reference Attributes Stored in mxi_link Table
Reference attributes are no longer stored in the database table mxi_values, but maintained in the database
table mxi_link. mxi_values is still used for regular (non-reference) attributes.
If there are SQL statements in the configuration that access the table mxi_values (either directly or through one
of the views) to retrieve reference attributes, these SQL statements must be rewritten to use one of the new
views. (See below.)
Note
Accessing attributes from pass definitions has not changed.
28
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Important Changes in Identity Management 7.2
Note
Accessing the mxi_values and mxi_link tables directly is discouraged, and direct access to these tables will
be removed in a future version.
Solution
Rewrite the SQL statement using one of the available views.
7.2
Changed Handling of Reference Attributes
The following attributes are not present as separate attributes for an entry after you upgrade from Identity
Management 7.1 to 7.2:
● MXMEMBER_<entry_type>
● MX_AUTOROLE
● MX_AUTOPRIVILEGE
● MX_AUTOROLE_DYNAMIC_GROUP
They are handled as synthetic attributes based on the corresponding MXREF_ attribute.
The attributes can be used as before in a pass and defined for a task in the Identity Management User Interface,
as the contents of the attributes are calculated before they are displayed or used in an operation.
In this case, no changes to the configuration are required.
If the configuration contains select statements to retrieve the above attributes, the select statement must be
modified to use the corresponding MXREF_ attribute.
The contents of the attributes are calculated in the following way:
Table 1:
Attribute
MXREF_<entry_type>
SQL Statement
Comment
MyMSKEY: MSKEY of the current entry
Sample Code
AttrId: Attribute ID
SELECT mcOtherMSKEY
FROM idmv_link_basic
WHERE mcThisMSKEY =
<MyMSKEY> AND
mcAttrId = <AttrId of
MXREF_<entry_type>> AND
mcAssignedDirect = 1
AND
mcLinkState = 0
SAP NetWeaver Identity Management Migration Guide
Important Changes in Identity Management 7.2
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
29
Attribute
MXMEMBER_<entry_type>
SQL Statement
Sample Code
Comment
MyMSKEY: MSKEY of the current entry
AttrId: Attribute ID
SELECT mcThisMSKEY
FROM idmv_link_basic
WHERE mcOtherMSKEY =
<MyMSKEY> AND
mcAttrId = <AttrId of
MXREF_<MyEntryType>>
AND
mcThisEntryType =
<OtherEntryType> AND
mcAssignedDirect = 1
AND
mcLinkState = 0
MX_AUTOROLE
Sample Code
MyEntryType: Entry type of current en­
try
OtherEntryType: Entry type of refer­
enced entry
MyMSKEY: MSKEY of the current entry
AttrId: Attribute ID
SELECT mcOtherMSKEY
FROM idmv_link_basic
WHERE mcThisMSKEY =
<MyMSKEY> AND
mcAttrId = <AttrId of
MXREF_MX_ROLE> AND
mcLinkState = 0
MX_AUTOPRIVILEGE
Sample Code
MyMSKEY: MSKEY of the current entry
AttrId: Attribute ID
SELECT mcOtherMSKEY
FROM idmv_link_basic
WHERE mcThisMSKEY =
<MyMSKEY> AND
mcAttrId = <AttrId of
MXREF_MX_PRIVILEGE> AND
mcAssignedInheritCount
> 0 AND
mcLinkState = 0
MX_AUTOROLE_DYNAMIC_GROUP
Sample Code
MyMSKEY: MSKEY of the current entry
AttrId: Attribute ID
SELECT mcOtherMSKEY
FROM idmv_link_basic
WHERE mcThisMSKEY =
<MyMSKEY> AND
mcAttrId = <AttrId of
MXREF_MX_ROLE> AND
mcAssignedDynamicGroup
= 1 AND
mcLinkState = 0
30
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Important Changes in Identity Management 7.2
7.3
New and Removed Views
As reference attributes are not stored in the table mxi_values, existing views using this table do not contain
reference attributes. These views are available if running in 7.1 compatibility mode, as, in this case, the reference
attributes are also written to the mxi_values table. In pure 7.2 mode, the views are not available.
If your configuration uses SQL queries to retrieve information from the database, you may update them to use the
new views.
For an overview of the default views in the Identity Center database, see the topic Using views to access identity
store information in the Identity Center help file.
Substitute Views
The following table gives an overview of the views that are removed from Release 7.1 to Release 7.2 and the views
that are introduced in Release 7.2.
Note
The join to mxp_audit table, which was used in a lot of the 7.1 views are not included in any of the 7.2 views,
except where noted. The status of assignments can now be found directly in the link views.
Note
It is recommended that you only use the views starting with idmv_ from custom developed code.
Table 2:
7.1 View (Obsolete in 7.2)
Substitute 7.2 View
Comment
mxiv_simple_entries
idmv_value_basic_active
Select the 7.2 view depending on which
subset of the attributes you need to.
idmv_link_basic_active
idmv_vallink_basic_active
If you know you are looking for regular
attributes, use
idmv_value_<subset>_active.
If you know you are looking for reference
attributes, use
idmv_link_<subset>_active.
If you do not know, or you need both, use
idmv_vallink_<subset>_activ
e.
mxiv_pentries
SAP NetWeaver Identity Management Migration Guide
Important Changes in Identity Management 7.2
idmv_value_basic_active
Same as mxiv_simple_entries.
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
31
7.1 View (Obsolete in 7.2)
Substitute 7.2 View
Comment
idmv_link_basic_active
idmv_vallink_basic_active
mxiv_all_sentries
idmv_value_ext_active
Same as mxiv_simple_entries.
idmv_link_ext_active
idmv_vallink_ext_active
mxiv_sentries
idmv_value_ext_active
Same as mxiv_simple_entries.
idmv_link_ext_active
idmv_vallink_ext_active
mxiv_disabled_sentries
idmv_value_ext_inactive
mxiv_values
idmv_value_simple_all
Same as mxiv_simple_entries.
idmv_link_simple_all
idmv_vallink_simple
mxiv_oentries
idmv_ovalue_basic_all
idmv_ovalue_simple_all
mxiv_entries
n/a
idmv_ovalue_basic_all contains
attribute names.
Suggestion: Use
idmv_value_ext_active and filter
on Access_ID <> 2, or check if you can
use a "simpler" view.
mxpv_priv_addstatus
n/a
This information must be retrieved using
one of the link views.
mxuv_entries
idmv_vallink_ext2
mxuv_all_sentries
idmv_value_ext2
7.4
No Pending Value Object for Future Values of Reference
For reference attributes, no pending value object is created for future values. This means that any job or task that
retrieves information directly from the pending value object will not be able to do that with Release 7.2.
32
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Important Changes in Identity Management 7.2
Solution
Retrieve information about future assignments using the syntax described in the topic Including properties when
reading attribute values from the identity store in the Identity Center help file.
7.5
uApplyPending
For pending value objects created for reference attributes, this function will be a no-operation as the pending
value is applied automatically as the task completes.
Solution
In most cases it is not necessary to use uApplyPending, as this is done explicitly. For more information, see the
topic About pending value objects in the Identity Center help file.
7.6
Handling of Old Values
Old values of the following attributes are no longer stored in the table mxi_old_values.
Note
This also applies when running in 7.1 compatibility mode.
● MX_AUTOPRIVILEGE
● MX_AUTOROLE
● MX_AUTOROLE_DYNAMIC_GROUP
● MXMEMBER_*
Solution
Assignments are represented by only one attribute with flags for different assignment types. This attribute is
moved to mxi_old_values when the last of the flags is removed.
For the MXMEMBER_* attributes the corresponding MXREF_* attributes are moved to mxi_old_values.
SAP NetWeaver Identity Management Migration Guide
Important Changes in Identity Management 7.2
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
33
7.7
Configuration of the Password Reset Task
If your configuration contains a password reset task, the configuration of this task is no longer part of the identity
store configuration. Instead, this is a separate guided activity task that is referenced from the Password policy tab
of the identity store configuration.
For details see, the document SAP NetWeaver Identity Management Identity Center Self-Service Password Reset.
7.8
Approval Timeout
By default, the approval task will fail when a timeout occurs. In this case, the task referenced by Execute task on
failed result on the Result handling tab is executed. You can use this if want to send an e-mail or otherwise inform
of the timeout.
If you want to escalate, and go into a new approval process, a timeout must go to the decline node instead of
calling the error handling task.
For details, see the topic Creating an approval task in the help file for the Identity Center Management Console.
As of SAP NetWeaver Identity Management 7.2 SP4, the approval mechanism is enhanced, and escalations can be
configured on the approval task.
7.9
Inactive Entries
As of Identity Management 7.2, only entries with entry type MX_PERSON or a custom entry type defined as
Identity entry type can be set as inactive. If there are inactive entries with other entry types when migrating from
Identity Management 7.1, the Configuration Analyzer will report this.
7.10 uIS_SetValue/ uIS_Create
To improve performance, these functions will not start any entry event tasks or check for duplicate values. It is
strongly recommended to use a To identity store pass to update attributes in the identity store.
34
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Important Changes in Identity Management 7.2
7.11
Historic Values for Pending Value Objects
For performance reasons, pending value objects are not stored as historic values. Historic information about
approvals and assignments can be found in the view idmv_linkaudit_basic or idmv_linkaudit_simple.
SAP NetWeaver Identity Management Migration Guide
Important Changes in Identity Management 7.2
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
35
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).
36
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP NetWeaver Identity Management Migration Guide
Important Disclaimers and Legal Information
SAP NetWeaver Identity Management Migration Guide
Important Disclaimers and Legal Information
PUBLIC
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
37
www.sap.com/contactsap
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising