Download pdf - SAP NetWeaver Identity Management System Copy …a248.g.akamai.net/n/248/420835/93e9a0ca0c71934a80853e84f356d69cb01...SAP NetWeaver Identity Management System Copy Guide ... SAP NetWeaver

System Copy Guide PUBLIC

SAP NetWeaver Identity Management 7.2Document Version: Rev 3 – 2016-06-27

SAP NetWeaver Identity Management System Copy Guide - Copying the Identity Center Database

Content

1 SAP NetWeaver Identity Management System Copy Guide - Copying the Identity Center Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Importing the Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Creating Dispatcher for the System Copy Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Importing the Job Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Configuring the Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.3 Performing the System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Running the System Copy Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.4 Performing Post-System Copy Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

2P U B L I C© 2016 SAP SE or an SAP affiliate company. All rights reserved.

SAP NetWeaver Identity Management System Copy Guide - Copying the Identity Center DatabaseContent

1 SAP NetWeaver Identity Management System Copy Guide - Copying the Identity Center Database

This guide describes the necessary steps to perform a system copy of the SAP NetWeaver Identity Management Identity Center configuration and data from one database system to another.

To get the most benefit from this guide, you should have the following knowledge:

● General knowledge about the SAP NetWeaver Identity Management Identity Center.● General database knowledge.

The following software and configuration is required:

● SAP NetWeaver Identity Management Identity Center 7.2 SP7 or later.

You can find useful information in the documents listed in the Related Information section.

Related Information

SAP NetWeaver Identity Management Identity Center Initial ConfigurationIdentity Center Installation OverviewInstalling the Identity Center Database on MS SQL ServerInstalling the Identity Center Database on OracleInstalling the Identity Center Database on IBM DB2

1.1 Introduction

Overview

You can copy your SAP NetWeaver Identity Management Identity Center from a source database system to a target database system, where both source and target database systems may be one of the following:

● Microsoft SQL Server● Oracle● IBM DB2 (only as target database system)

This results in the following combinations/scenarios being possible for the system copy:

SAP NetWeaver Identity Management System Copy Guide - Copying the Identity Center DatabaseSAP NetWeaver Identity Management System Copy Guide - Copying the Identity Center Database

P U B L I C© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3

http://help.sap.com/saphelp_nwidmic_72/helpdata/en/82/de031fecc94c2aba078f51df128a13/frameset.htm

http://help.sap.com/saphelp_nwidmic_72/helpdata/en/5a/99e78d81b14d8c84575eb25a4c47b2/frameset.htm

http://help.sap.com/saphelp_nwidmic_72/helpdata/en/1c/f76d69020844c2986ddbe2a9db9507/frameset.htm

http://help.sap.com/saphelp_nwidmic_72/helpdata/en/a7/d063e4cc5e441089103b7ca7f40f2f/frameset.htm

http://help.sap.com/saphelp_nwidmic_72/helpdata/en/f9/0a3c919fb64a05a08ef761d231386f/frameset.htm

Table 1: System Copy Scenarios

Source Database System Target Database System

Microsoft SQL Server IBM DB2 Oracle

Microsoft SQL Server X X X

Oracle X X X

The system copy, where both the configuration and data are copied, is performed using a set of jobs (and the corresponding repository, scripts and constants) that are collected in an export file (MCC file) and imported into the Identity Center of the source database system. Each of the system copy scenarios mentioned above will have its own set of jobs in separate export files.

Prerequisites

The following prerequisites need to be fulfilled before copying the database system:

● Both the source and the target database system must have the same database schema version.● All SAP NetWeaver Identity Management components on the source and the target database system must be

on the same patch level.● All current/existing dispatchers and event services must be stopped (in both source and target database

system). A new dispatcher, running only the system copy jobs, needs to be created and configured in the source system. See Creating Dispatcher for the System Copy Jobs.

NoteThe dispatcher created and configured to run only the system copy jobs should be the only dispatcher running in the source system. No dispatchers should run in the target system.

● The source database must be IDLE, meaning that the dispatchers must be stopped and no tasks or jobs are running (that is, it is important that there is no activity in the database during the system copy process.

● Remove the access to the Identity Management User Interface to prevent changes during the copying of the database system. 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.

● SAP NetWeaver Identity Management Virtual Directory Server should be stopped.● Back up the source system's Identity Center database.● Although not necessary, it is highly recommended that the target database system is a completely new

installation (empty) before the system copy.

Related Information

Creating Dispatcher for the System Copy Jobs [page 5]




1.2 Importing the Jobs

To perform the system copy between the database systems, a set of jobs is available on the SAP Community Network (SCN) along with this guide.

The file <source database>_<target database>_SYSCOPY.mcc (for example, ORACLE_DB2_SYSCOPY.mcc) contains the necessary jobs, and each system copy scenario will have its own set of jobs in such separate export files.

A zip file will contain all export files. Download the ZIP file from the SAP Community Network and extract the export files into a suitable folder.

This section covers the following steps:

● Creating a dispatcher for system copy jobs only.● Importing the job folder (containing system copy jobs and the corresponding repository, scripts and

constants).● Configuring the imported repository.

Related Information

Creating Dispatcher for the System Copy Jobs [page 5]Importing the Job Folder [page 7]Configuring the Repository [page 11]

1.2.1 Creating Dispatcher for the System Copy Jobs

Context

A dispatcher, running only the system copy jobs, needs to be created and configured in the source system. This is the only dispatcher that should be running in the source system during the copy of the database system.

To create a dispatcher for system copy jobs, proceed as follows:

Procedure

1. In the console tree, select the Identity Center's Dispatchers entry and choose New Dispatcher from the context menu.



2. A dispatcher named idmdispatcher is inserted in the console tree. You may rename the dispatcher on the Options tab of the dispatcher properties pane.

3. On the Options tab, create the dispatcher scripts by choosing Create dispatcher scripts.4. After the scripts are created, you should test the dispatcher before installing it. Choose the Test button. If no

error messages are displayed during the test, stop the test (by pressing CTRL + C ) and choose Install to install the dispatcher.

5. Choose Start to start the service.6. Select the Policy tab and make sure that only options Run jobs for Java runtime engine and Run regular jobs

are selected before choosing Apply:

7. On the Options tab, make sure that the dispatcher status is Running threads: JOBEXECUTE. You need to choose the Refresh button to update the status. It may take at least 30 seconds (by default) before the options selected in the previous step are applied.




For more information about the dispatchers and how they are created, see SAP NetWeaver Identity Management Identity Center Initial Configuration.

Related Information

SAP NetWeaver Identity Management Identity Center Initial Configuration

1.2.2 Importing the Job Folder

Context

The file <source database>_<target database>_SYSCOPY.mcc contains a job folder with the necessary jobs.




To import the job folder, proceed as follows:

Procedure

1. Select the Identity Center (in the source system) in the console tree of the Identity Center Management Console, and choose Import from the context menu.

2. Locate the export file for your system copy scenario, select it and choose Open.3. Make sure that Import is selected.4. Select the Advanced tab and make sure that a dispatcher created in the previous section is selected for the

imported jobs.5. Choose Next >.6. Choose Import.7. Choose Finish when the import is completed. Alternatively choose View logfile before choosing Finish to view

the details about the completed import.

The imported folder with all the jobs is added to the Identity Center, here with an example of Oracle to IBM DB2 system copy scenario:




In addition, a repository named <source database>_<target database>_SYSCOPY (for example, ORACLE_DB2_SYSCOPY), that the system copy jobs belong to, is imported with the jobs:

It may be necessary to refresh the Repositories node in the Identity Center Management Console to see the imported repository. The repository constants must be defined before performing the system copy. See Configuring the Repository.

Results

The folder contains the following system copy jobs:

Table 2:

Name of the Job Description

01. Prepare source db for system copy – [<repository name>]

This job prepares the source database for copying.

02. Check prerequisites – [<repository name>]

This job checks that the prerequisites for the system copy are fulfilled. If all prerequisites are fulfilled, the job will only generate (five) warnings.

The job reports an error if any of the checks fails. The prerequisites need to be fulfilled before proceeding.

03. Prepare target db for system copy – [<repository name>]

This job prepares the target database for the system copy, which involves disabling foreign keys, triggers and computed columns.

04. Create OPER system copy job definition – [<repository name>]

This job reads the OPER schema from the target database and creates the system copy job.



Name of the Job Description

05. Create RT system copy job definition – [<repository name>]

The job reads any table owned by the RT user in the source database and creates the system copy job for these tables. The following will not be copied to the target database system:

● Column default values● Foreign keys● Triggers

06. Copy OPER tables – [<repository name>] This job is originally empty and its job definition is created by the job 04. Create OPER system copy job definition.

The job consists of two passes for each table – the first pass truncates or deletes any content in the target table (in the target database) and the second pass copies the table content from the source to the target database.

Do a refresh of the job after the job 04. Create OPER system copy job definition is run to see the created passes.

07. Copy RT tables – [<repository name>] This job is originally empty and its job definition is created by the job 05. Create RT system copy job definition.

The job consists of two passes for each table – the first pass creates the table in the target database and the second pass copies the table content from the source to the target database.

Do a refresh of the job after the job 05. Create RT system copy job definition is run to see the created passes. The following is not copied to the target database system by the job:

● Column default values● Foreign keys● Triggers

08. Enable the target db for use – [<repository name>]

This job enables the target database after the system copy – foreign keys, triggers and computed columns are re-enabled.

– [<repository name>] (for example, – [ORACLE_DB2_SYSCOPY]) is a reference to the imported repository and is automatically added by the system when the jobs are imported.

Make sure that the jobs are enabled and have a dispatcher defined.




NoteDo not rename the system copy jobs and the corresponding repository after they are imported. The system copy process depends on the used default naming.

Related Information

Configuring the Repository [page 11]

1.2.3 Configuring the Repository

Context

To configure the repository, proceed as follows:

Procedure

1. View the repository constants for the imported repository. Select and expand the repository node in the console tree and select Constants).

2. Define the following constants:



Table 3:

Repository Constants Description

SOURCE_ADMIN The repository constant SOURCE_ADMIN contains the JDBC URL for the ADMIN user of the source database system.

SOURCE_OPER This constant contains the JDBC URL for the OPER user of the source database system.

SOURCE_PREFIX The repository constant SOURCE_PREFIX contains the prefix for the source database system.

SOURCE_RT This repository constant contains the JDBC URL for the RT user of the source database system.

TARGET_OPER The repository constant TARGET_OPER contains the JDBC URL for the OPER user of the target database system.

TARGET_PREFIX The repository constant TARGET_PREFIX contains the prefix for the target database system.

TARGET_RT This repository constant contains the JDBC URL for the RT user of the target database system.

Related Information

Defining Repository Constants SOURCE_ADMIN/OPER/RT and TARGET_OPER/RT [page 13]Defining Repository Constants SOURCE_PREFIX and TARGET_PREFIX [page 14]




1.2.3.1 Defining Repository Constants SOURCE_ADMIN/OPER/RT and TARGET_OPER/RT

Context

To define the JDBC URLs for the repository constants SOURCE_ADMIN, SOURCE_OPER, SOURCE_RT and TARGET_OPER, TARGET_RT, proceed as follows:

Procedure

1. Select the constant and view its properties by choosing Properties from the context menu.2. Choose … to the right of the Value field. This will open the JDBC connection wizard dialog box.

3. Select the driver for your source/target (depending on the constant holding a source or a target JDBC URL) database system from the list of JDBC drivers, then choose Next >.

4. Fill in the requested parameters, and then choose Next >.5. Choose Finish to complete the wizard.6. The JDBC URL should now be inserted in the Value field.7. Choose OK to save the properties and close the dialog box.

For constants SOURCE_RT and TARGET_RT you may copy the value from the Identity Center properties pane (select your Identity Center in the console tree and copy the value of the Java RT JDBC URL field on the Database tab in the properties pane) and paste in the Value field of the repository constant which will take you directly to the step 6 described above. Alternatively, you may follow all the steps described to define the value manually.

See the document SAP NetWeaver Identity Management Identity Center Initial Configuration for more information on defining JDBC URLs.

Related Information





1.2.3.2 Defining Repository Constants SOURCE_PREFIX and TARGET_PREFIX

Context

To define the repository constants SOURCE_PREFIX and TARGET_PREFIX, proceed as follows:

Procedure

1. Select the constant and view its properties by choosing Properties from the context menu.2. Enter the correct prefix of your source/target database in the Value field.3. Choose OK to save the properties and close the dialog box.

1.3 Performing the System Copy

Context

To perform the copy of the database system, the following steps need to be completed:

Procedure

1. Fulfil the necessary prerequisites as described in the Introduction section.2. Run the imported system copy jobs as described in Running the System Copy Jobs.

The following is not a part of the system copy:○ The tables MC_DBINFO, MC_DBSCHEMA, HR_SAMPLE, HR_ADDRESSES.○ The global constants RT_CONN_STR and JDBC_URL in the database table MC_GLOBAL_VARIABLES,

that is, these are not changed by the system copy.○ The group holding the system copy jobs (MC_GROUP).○ The system copy jobs themselves (in database tables MC_JOBS, MC_LOGS,

MC_JOB_DISPATCHER_LINK and MC_JOBS_ONDEMAND).○ The repository used by the system copy process (in the database tables MC_REPOSITORY,

MC_REPOSITORY_TYPE and MC_REPOSITORY_VARS).




○ The definition of the dispatcher used for the system copy process (MC_DISPATCHER).○ Temporary database tables, for example, created during the copy of the RT tables.○ The way the SQL queries are built and handled may be different on the different database systems. The

system copy process will not do any changes to the SQL queries in the configuration, that is, the SQL queries will be copied to the target database system as they were written in the source database system. Any adjustments of the SQL queries to the new database system need to be performed manually as part of the post-system copy steps.

Related Information

Introduction [page 3]Running the System Copy Jobs [page 15]

1.3.1 Running the System Copy Jobs

Context

To run the system copy jobs, proceed as follows:

Procedure

1. Select the job in the console tree in the Identity Center Management Console.2. Choose Run now on the Options tab of the job properties.

The system copy jobs need to be run in sequence, in the given order (jobs 01. through 08.). Running all jobs completes the system copy.



1.3.2 Troubleshooting

Context

If you encounter any problems during running of the system copy jobs, proceed as follows:

Procedure

1. Reinstall the target database system (using the mxmc-install script and not mxmc-update).2. Correct the problem.3. Make sure that the prerequisites still are fulfilled.4. Run the system copy jobs from the start.

NoteThe above described process will apply to all jobs except for the job 02. Check prerequisites. When this job fails, it can be run again after the reported error is corrected.

1.4 Performing Post-System Copy Steps

Context

After the system copy, the following steps need to be done in the target system:

Procedure

1. If necessary, adjust the copied SQL queries to the new database system.

The way the SQL queries are built and handled may be different on the different database systems. The system copy process only copies the queries to the target database system as they were written in the source database system. You need to inspect the SQL queries and make the necessary adjustments in the target database system.

The SQL queries may typically exist in:




○ Source tab of a pass○ Access controls○ Conditional tasks○ Switch tasks○ Scripts using the uSelect function

2. Create the dispatcher scripts after the system copy. Proceed as follows:a. Select the dispatcher in the console tree in the Identity Center Management Console.b. Choose Create dispatcher scripts on the Options tab of the dispatcher properties.c. Select where you want the script files to be saved and choose OK.d. Choose OK to overwrite the existing dispatcher scripts.e. Choose OK to close the information message window.

The dispatcher can now be started. Repeat the above steps for all dispatchers you want to run in the target system.

The target database system is now ready to be used.

For more information about the dispatchers and the dispatcher scripts, see the document SAP NetWeaver Identity Management Identity Center Initial Configuration.

Related Information





Important Disclaimers and Legal Information

Coding SamplesAny 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.

AccessibilityThe 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 LanguageAs 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 HyperlinksThe 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).



Important Disclaimers and Legal Information

http://help.sap.com/disclaimer/

SAP NetWeaver Identity Management System Copy Guide - Copying the Identity Center DatabaseImportant Disclaimers and Legal Information


go.sap.com/registration/contact.html

© 2016 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.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx