SAP NetWeaver Identity Management Identity Center Intial Configurtion

SAP NetWeaver Identity ManagementIdentity Center

Initial Configuration

Version 7.2 Rev 8

2014 SAP AG 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 AG. Theinformation contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould 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 AG inGermany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark informationand notices.

i Copyright 2014 SAP AG. All rights reserved.

Preface

The productSAP NetWeaver Identity Management Identity Center is a high-end identity managementsolution, capable of handling a large amount of repositories containing an unlimited amount ofinformation. The Identity Center offers a robust, flexible and scalable high-availability solutionfor workflow, provisioning, data synchronization and joining for a large number of datarepositories. The Identity Center provides a framework for a number of jobs.

The readerThis manual is written for people who are to use the Identity Center.

PrerequisitesTo get the most benefit from this manual, you should have the following knowledge:

x Generic knowledge about databases and computer systems.x Knowledge about the Java runtime environment.The following software is required:

x SAP NetWeaver Identity Management Identity Center version 7.2 SP7 or newer, correctlyinstalled and licensed.

x An Oracle, IBM DB2 or Microsoft SQL Server database with an Identity Center databaseinstalled. See the SAP NetWeaver Identity Management Identity Center databaseinstallation guides for details.

The manualThis tutorial consists of five sections describing how you add an Identity Center and perform theinitial configuration.

This tutorial is not a substitute for training.

Person names used in this tutorial are fictional.

Related documentsYou can find useful information in the following documents:

x SAP NetWeaver Identity Management Identity Center: Installation overview.x SAP NetWeaver Identity Management Identity Center: Installing the database (Microsoft

SQL Server/Oracle/IBM DB2).

x SAP NetWeaver Identity Management Identity Center: Installing the Runtime Components.x SAP NetWeaver Identity Management Identity Center: Installing the Management Console.

ii

Copyright 2014 SAP AG. All rights reserved.

iii


Table of contentsIntroduction .................................................................................................................................. 1

Section overview .................................................................................................................................. 1Section 1: Adding an Identity Center configuration .................................................................... 2

Adding the Identity Center configuration .............................................................................................. 2Creating the Identity Center connection string ....................................................................................... 3Creating the connection string for the Windows runtime engine ............................................................ 9Creating the JDBC URL for the Java runtime engine........................................................................... 13Completing the wizard ........................................................................................................................ 19Verifying the connection ..................................................................................................................... 19

Section 2: Configuring a dispatcher ........................................................................................... 21Adding the dispatcher ......................................................................................................................... 21Creating the dispatcher scripts ............................................................................................................. 22Testing the dispatcher ......................................................................................................................... 22Installing and starting the dispatcher ................................................................................................... 24

Section 3: Verifying job execution .............................................................................................. 26Creating a job for the Java runtime engine ........................................................................................... 26Running the jobs ................................................................................................................................. 28

Section 4: Configuring external event handling ......................................................................... 29Creating the file .................................................................................................................................. 29Creating the repository definition ........................................................................................................ 30Creating the event agent ...................................................................................................................... 32Creating the event agent service .......................................................................................................... 35Creating the service script files ........................................................................................................... 36Verifying job properties ...................................................................................................................... 37Installing and starting the event agent service ...................................................................................... 38

Section 5: Moving the Identity Center runtime environment to another computer................. 40Microsoft Windows ............................................................................................................................ 40Unix ................................................................................................................................................... 42

iv


1IntroductionSAP NetWeaver Identity Management Identity Center Initial Configuration


IntroductionThis manual leads you through the process of adding an Identity Center and performing theinitial configuration. The tutorial shows some of the basic functionality of the Identity Center.

This tutorial requires that the prerequisite software is installed as described in the SAPNetWeaver Identity Management Identity Center: Installation overview.

Section overviewThe tutorial consists of the following sections:

Section 1: Adding an Identity Centerconfiguration

This section describes the necessary steps for addingan Identity Center configuration.

Section 2: Configuring a dispatcher In this section you will learn how to add, configure andstart a dispatcher.

Section 3: Verifying job execution This section shows how to create and run jobs.

Section 4: Configuring external event handling In this section, we configure external event handling.

Section 5: Moving the Identity Center runtimeenvironment to another computer

This section describes how you move theIdentity Center runtime environment to a secondcomputer. Procedures for both Microsoft Windows andUnix are described.

2Section 1: Adding an Identity Center configuration

SAP NetWeaver Identity Management Identity Center Initial Configuration


Section 1: Adding an Identity Center configurationNote:The Management Console and the Identity Center database (either Microsoft SQL Server,Oracle or IBM DB2) must be installed. See the installation guides for details.

All other prerequisites mentioned in the installation guides are also necessary to complete thetutorial.

In this section, we will add an Identity Center configuration to the console tree and create thenecessary connection strings that are used to access the Identity Center database.

Three different connection strings are required:

x An ADO connection string which is used from the Management Console, connecting asadministrator (_admin, e.g. mxmc_admin or IC_admin).

x An ADO connection string which is used from the Windows runtime engine, connecting asthe RT (RunTime) user.

x A JDBC URL which is used from the Java runtime engine as well as from the dispatcher,connecting as the RT (RunTime) user.

All these connection strings are defined using the Identity Center database connection wizard.

Adding the Identity Center configuration1. Start the Identity Center by choosing All Programs/SAP NetWeaver Identity

Management/Identity Center from the "Start" menu.

2. Start the wizard by selecting the "SAP NetWeaver Identity Management" entry in theconsole tree and choosing New/Identity Center configuration from the context menu.

3. Choose "Next >".

Enter a name and description for the Identity Center. This name is used to identify theIdentity Center in the console tree. The description is optional.

4. Choose "Next >".

3Section 1: Adding an Identity Center configurationSAP NetWeaver Identity Management Identity Center Initial Configuration


Creating the Identity Center connection stringHow this connection string is created depends on the database system you are using.

Microsoft SQL Server1. Continue the wizard to create the connection string used by the Management Console.

2. Choose "" to the right of the "Connection string" field to start the "Data Link Properties"wizard.

Choose "Microsoft OLE DB Provider for SQL Server" in the list of providers.




3. Choose "Next >>".

Server nameSelect or enter the server where the Identity Center database is installed (server name or IPaddress of the server).

Note:You may also specify a named instance on the server in the following way \.

User nameSpecify a user name to access the database. The user name is mxmc_admin (unless theprefix was changed when installing the Identity Center database).

PasswordSpecify the password for the user name you specified.

You can choose to "Allow saving password" or not. If the password is not saved, you willbe prompted for the password every time you start the Management Console.

DatabaseSelect the Identity Center database.

Note:The default database name is MXMC_DB. If you have changed the prefix before installingthe database, this could be something else.

Choose "Test connection" to verify that the parameters are correct.

4. Choose "OK".

The resulting connection string may look something like this:Provider=SQLOLEDB.1;Password=*****;Persist Security Info=True;UserID=mxmc_admin;Initial Catalog=MXMC_db;Data Source=ORION

5. Choose "Next >".



Oracle1. Continue the wizard to create the connection string used by the Management Console.


Choose "Oracle Provider for OLE DB" in the list of providers.





Data sourceEnter the database SID of the Identity Center database.

User nameSpecify a user name to access the database. The user name is mxmc_admin (unless theprefix was changed when installing the Identity Center database).


You can choose to "Allow saving password" or not. If the password is not saved, you willbe prompted for the password every time start the Management Console.


4. Choose "OK".

The resulting connection string may look something like this:Provider=OraOLEDB.Oracle.1;Password=*****;Persist Security Info=True;UserID=mxmc_admin;Data Source=Oracle

5. Choose "Next >".



IBM DB21. Continue the wizard to create the connection string used by the Management Console.


Choose "IBM OLE DB Provider for DB2" in the list of providers.





Existing data sourceSelect this option to access the database (data source) on the local host. Enabling this optionalso enables "Data source" field that needs to be specified.

Data sourceSelect or enter the database to be the Identity Center database.

Direct server connectionSelect this option as an alternative to the "Existing data source" option, to connect to anyDB2 database (i.e. on any server). Enabling this option also enables fields "Select or enter aserver name" and "Select the database on the server".

Select or enter a server nameSelect or enter the name of the server where the database is installed.

Note:If you are using the default port 52222 as defined in the Identity Center, then the portnumber should be a part of the server name, e.g. db2server:52222. It will be necessary toenter a port number as a part of the server name every time the IBM default port 50000 isnot used.

Select the database on the serverSelect the database to be the Identity Center database, from the server defined in theprevious field.

User nameSpecify a user name to access the database. The user name is IC_admin (unless the prefixwas changed when installing the Identity Center database).


You can choose to "Allow saving password" or not. If the password is not saved, you willbe prompted for the password every time start the Management Console.




4. Choose "OK".

The resulting connection string may look something like this:Provider=IBMDADB2.DB2COPY1;Password=*****;Persist Security Info=True;UserID=IC_admin;Data Source=IC_DB;Location="";Extended Properties=""

5. Choose "Next >".

Creating the connection string for the Windowsruntime engineHow this connection string is defined depends on the database system you are using.

Microsoft SQL Server1. Continue the wizard to create the ADO connection string for the Windows runtime engine:




2. Choose "" to the right of the "Connection string" field to start the "Data Link Properties"wizard and fill in the information.

Some of the fields are filled in using information about the database.

Enter mxmc_rt as the user name (unless the prefix was changed when installing the IdentityCenter database) and the password that was provided for this user when the database wascreated.

Select "Allow saving password". This must be set, since the runtime engine will be runningin the background.


3. Choose "OK".

The connection string may look something like this:Provider=SQLOLEDB.1;Password=*****;Persist Security Info=True;UserID=mxmc_rt;Initial Catalog=MXMC_db;Data Source=ORION

4. Choose "Next >".



Oracle1. Continue the wizard to create the ADO connection string for the Windows runtime engine:









3. Choose "OK".

The connection string may look something like this:Provider=OraOLEDB.Oracle.1;Password=*****;Persist Security Info=True;UserID=mxmc_rt;Data Source=Oracle

4. Choose "Next >".

IBM DB21. Continue the wizard to create the ADO connection string for the Windows runtime engine:





Enter IC_rt as the user name (unless the prefix was changed when installing the IdentityCenter database) and the password that was provided for this user when the database wascreated.



3. Choose "OK".

The connection string may look something like this:Provider=IBMDADB2.DB2COPY1;Password=*****;Persist Security Info=True;UserID=IC_rt;Data Source=IC_DB;Location="";Extended Properties=""

4. Choose "Next >".

Creating the JDBC URL for the Java runtime engineHow this URL is defined depends on the database system you are using.

Microsoft SQL Server1. Continue the wizard to create the JDBC URL for the Java runtime engine:




2. Choose "" to the right of the "JDBC URL" field to start the "JDBC connection wizard".Choose "Next >".

Select the driver corresponding to your version of Microsoft SQL Server from the list.

3. Choose "Next >".

Fill in information about how to access the database.

Note:If you are connecting to a named instance on the server, do not define the port number, i.e.make sure that the "Port" field is empty.


4. Choose "Next >" and then "Finish".

The JDBC URL may look something like this:jdbc:sqlserver://ORION:1433;databasename=MXMC_db;user=mxmc_rt;password=*****

5. Choose "Next >".



Oracle1. Continue the wizard to create the JDBC URL used by the Java runtime engine:


Select the "Oracle thin driver" driver from the list.




3. Choose "Next >".

Fill in information about how to access the database.



The JDBC URL may look something like this:jdbc:oracle:thin:mxmc_rt/******@Sirius:1521:Oracle

5. Choose "Next >".



IBM DB21. Continue the wizard to create the JDBC URL used by the Java runtime engine:


Select the "DB2" as the JDBC driver from the list.




3. Choose "Next >".

Fill in the following information:

ServerEnter the name of the server, i.e. .

PortEnter the port number, or leave the default value 52222.

DatabaseEnter _DB (default IC_DB).

UserEnter the user _RT (IC_RT by default).

PasswordEnter the password for the _RT user.

SchemaEnter _OPER (default IC_OPER).

Note:The value must be entered in upper case.

FunctionPathEnter _OPER (default IC_OPER).

Note:The value must be entered in upper case.

Stmt. cacheMake sure that the value is set to "100".


The JDBC URL may look something like this:jdbc:db2://server1:52222/IC_DB:user=IC_rt;password=******;currentSchema=IC_OPER;currentFunctionPath=IC_OPER;maxStatements=100;retrieveMessagesFromServerOnGetMessage=true;

5. Choose "Next >".



Completing the wizardNow all necessary connection strings are defined.

Choose "Finish" to complete the wizard.

Verifying the connectionWhen the wizard is completed, the Identity Center configuration is added to the console tree:




If there is a database schema mismatch, you will see an error message, which may look like this:This version of Identity Center requires that database update 1050 is installed.The latest update installed is number 1049. Make sure all applicable databaseupdates are installed.

In this case you should follow the instructions for upgrading the database schema found in thedocument:

x SAP NetWeaver Identity Management Identity Center: Installing the database (MicrosoftSQL Server)

x SAP NetWeaver Identity Management Identity Center: Installing the database (Oracle)x SAP NetWeaver Identity Management Identity Center: Installing the database (IBM DB2)

21Section 2: Configuring a dispatcherSAP NetWeaver Identity Management Identity Center Initial Configuration


Section 2: Configuring a dispatcherIn this section, you configure a dispatcher. The dispatcher is responsible for starting the runtimeengines that execute the jobs. This is a Java application, which must be running permanently inthe background on every computer where the runtime engine is installed.

Note:Keep in mind that, when installing the Identity Management dispatcher, the correspondingWindows Service will be started with default recovery actions Take no action. This will preventservices to recover automatically in case the database connection got temporarily lost. Basedon your configuration requirements, you can change the action to Restart the Service with anappropriate restart interval or choose any other available recovery actions.

Adding the dispatcherThere must be at least one dispatcher defined in each Identity Center.

To define a dispatcher:

1. Select the Identity Center's "Dispatchers" entry in the console tree and chooseNew/Dispatcher from the context menu.

2. A dispatcher named "idmdispatcher" is inserted in the console tree. Rename the dispatcherto reflect the name of the computer.

Enter the name in the "Name" field in the "Options" tab of dispatcher's details pane.

3. Choose "Apply".

22Section 2: Configuring a dispatcher



Creating the dispatcher scriptsBefore the dispatcher can be started, we must create the script files that the dispatcher uses.

Choose "Create dispatcher scripts":

Specify where you want to save the scripts. The default value is the "Service-Scripts" folder.The following files will be generated:

Dispatcher_Service_.batDispatcher_Service_.sh

where is the name of the dispatcher as defined in the Management Console. In addition,a property file for Unix and Windows is created, i.e. Dispatcher_Service_.prop.Note:If you change the parameters in the Management Console, for example when running theconnection wizard, you must re-create the dispatcher scripts.

Testing the dispatcherTo verify the dispatcher configuration, choose "Test" in the properties pane. This will verify thatthe dispatcher is able to start.

You should see the following output from the dispatcher script:



Verify that no error messages are displayed during the process. If error messages occur, consultthe Help file for details. The topic "Creating scripts for a dispatcher" contains usefulinformation.

Abort the execution by pressing CTRL+C.

View the dispatcher properties:

The "Version" and "Last check" fields have been filled in.

Note:You may need to refresh the properties before these fields are filled in.

24Section 2: Configuring a dispatcher



Installing and starting the dispatcherNote:Make sure that the dispatcher is not running before you continue.

The dispatcher can be installed as a service:

1. Choose "Install" in the properties pane.

2. You can now choose "Start" to start the service.



The "Service state" is updated to "Running".

By default, the dispatcher is started automatically each time the system is started. If you deselect"Automatic startup" option, you manually have to start the dispatcher after a reboot.

26Section 3: Verifying job execution



Section 3: Verifying job executionThis section describes how you verify that the Java runtime engine is able to run jobs. You willcreate a dummy job that does not perform any operations, but is used to verify that the IdentityCenter is properly configured.

Creating a job for the Java runtime engineTo create a job for the Java runtime engine, do the following:

1. Select the "Job folder" and choose New/Empty job from the context menu.

Fill in the following values:

Change the name of the job in the console tree.

Make sure that "Enabled" is selected.

Choose "Every minute" as the "Schedule rule".

Select the dispatcher in the list "Run by dispatchers".

Verify that "Java" is selected in the "Runtime engine" field.

2. Choose "Apply".

27Section 3: Verifying job executionSAP NetWeaver Identity Management Identity Center Initial Configuration


The job is ready for execution, and will be started by the dispatcher every minute. This can beverified by looking at the job log:

After a couple of minutes, the job log should look something like this. Note that there are noentries processed, which is correct, since the job does not do anything.

Also, looking at the dispatcher status (the "Status" tab in the details pane of the "Dispatchers"node in the console tree), you should find the dispatcher you created:

28Section 3: Verifying job execution



Running the jobsThere are two ways to run a job: either directly from the management console or by using thedispatcher. How the job is run is determined by the "Test job" check box.

If "Test job" is selected, the job can only be run from the management console. In this case, theschedule rule is not used.

Run the job by clicking the ("Run") button in the toolbar.

Note:If you do not want the jobs to be executed continuously, change the schedule rule to "Ondemand".

29Section 4: Configuring external event handlingSAP NetWeaver Identity Management Identity Center Initial Configuration


Section 4: Configuring external event handlingThere are cases where you want to monitor a repository, and schedule a job when a changeoccurs in the repository. For this purpose, you can use an event agent.

The event agent constantly monitors a repository for changes. When a change occurs, the eventagent will schedule a specified job, which in turn is responsible for acting upon the change.

Defining external event handling involves the following steps:

x Define the data source as a repository definition in the Identity Center.x Define an event agent to monitor this repository definition.x Define a service that is responsible for running the event agent.

Creating the fileIn the following example, we will monitor the change date of a file, and use this to schedule oneof the previously created jobs.

Create a file in the file system. It does not matter what the file contains, as we will not actuallyprocess the file, but just detect that it changes. For example, use Notepad to create a text file. Inthis tutorial, the following file name will be used:

c:\tutorial\myfile.txt

30Section 4: Configuring external event handling



Creating the repository definitionCreate a repository definition for the file:

1. Start the repository wizard by selecting the Identity Center's "Repositories" entry andchoosing New/Repository from the context menu.

2. Choose "Next >".

Locate the template "File" in the "Repositories" directory.



3. Choose "Next >".

Enter "TUTORIALMYFILE" as name for this repository.

4. Choose "Next >".

Fill in the file name, including path. You can use the "" button to the right of the field tolocate the file. When holding the mouse over the field, you can see the name of therepository constant holding the value.

5. Choose "Next >" and then "Finish" to complete the wizard.




The repository is added to the console tree:

Creating the event agentThe next step is to create an event agent for this repository definition:

1. Start the event agent wizard by selecting "Event agents" in the console tree under "Externalevent handlers" and choosing New/Event agent from the context menu.

2. Choose "Next >".

Select the repository you created.



3. Choose "Next >".

Select "File Change" as the agent type for this event agent.

4. Choose "Next >".

Enter "Tutorial MyFile" as name of the event agent.




5. Choose "Next >".

Select the job that is to be scheduled when the event agent detects a change in the repositorydefinition.

6. Choose "Next >" and then "Finish" to complete the wizard.

The event agent is included in the console tree:



Creating the event agent serviceWe need a service that is responsible for running the event agent we just created:

1. Select the entry "Services" under "External event handlers" and choose New/Event agentservice from the context menu.

2. An event agent service named "new agent service" is inserted in the console tree. Renamethe service to reflect the name of the computer.

Select the "Tutorial MyFile" agent in the list.

3. Choose "Apply".




Creating the service script filesCreate the script files and test the service in the same way as you did with the dispatcher.

1. Choose "Create service scripts" to generate the scripts needed for the event agent.

2. Choose "OK".

3. Test the event agent service by choosing "Test".

The output should start something like this:

4. Verify that the command does not produce any error messages. Typical problems includeloading the JDBC drivers.

5. Abort the execution by pressing CTRL+C.



Verifying job propertiesWhen we created the event agent, we chose one of the jobs that should be scheduled each timethe event agent detects that the file has changed.

1. View the properties of the job:

2. Verify that the job is enabled and that the schedule rule is set to "On demand".

3. Choose "Apply" if you have made any changes to the configuration.

The job should now be ready to be scheduled by the event agent when a change is detected.




Installing and starting the event agent serviceNow, we are ready to install and start the event agent service.

Choose "Install" to install the service and then "Start".

This will start monitoring the file.



Make a change to the file and save it. The event agent will detect the change within one minuteand schedule the job to be executed. Check the job log for the "Dummy Java" job to verify thatit has been run.

Note:The dispatcher must be running for the job to be executed.

40Section 5: Moving the Identity Center runtime environment to another computer



Section 5: Moving the Identity Center runtime environment toanother computer

In some cases it would be necessary to move the runtime environment to another computer thanthe one where the Identity Center is installed.

This section will describe the process, for both the Microsoft Windows and Unix platforms.

Microsoft WindowsThe process involves the following steps:

x Preparing the runtime environment on the second computer.x Creating a dispatcher for the second computer.x Moving and adapting the necessary files.x Configuring and testing the dispatcher.x Running jobs.

Preparing the environmentInstall the Runtime Components including the necessary prerequisites as described in thedocuments SAP NetWeaver Identity Management Identity Center Installation Overview and SAPNetWeaver Identity Management Identity Center: Installing the Runtime Components.

Creating the dispatcher and the necessary script filesTo add the dispatcher:

1. Select "Dispatchers" in the Identity Center console tree and choose New/Dispatcher fromthe context menu.

2. Fill in information about the dispatcher. Choose "Apply".

3. Generate script files for the dispatcher and note where the files are stored.

Moving and adapting the filesTo move the files:

1. Locate the dispatcher files you just created.

2. Copy the files Dispatcher_Service_.bat andDispatcher_Service_.prop to the second computer. You can put the filesin the installation directory. If you do a default installation, this will beC:\usr\sap\IdM\Identity Center.

You may need to adapt the following settings in Dispatcher_Service_.bat:

x DSE_HOMEIf the runtime engine is installed in a different location than on the computer where the fileis generated, this must be changed.

x MXDISPATCHERJARVerify that the files and locations are correct.

41Section 5: Moving the Identity Center runtime environment to another computerSAP NetWeaver Identity Management Identity Center Initial Configuration


x MXDISPATCHERPROPModify the path to the Dispatcher_Service_.prop file.

It should not be necessary to modify any of the settings in the .prop file, unless you use adifferent JDBC driver to connect to the Identity Center database.

Testing the dispatcherTest the dispatcher by entering the command at the command prompt:

Dispatcher_Service_ test checkconfig

Verify that the dispatcher is able to start and read its configuration. The most probable problemis that the dispatcher is not able to find the required JDBC drivers. Verify that the information inthe .bat and .prop files matches the configuration on the computer.

Then start the dispatcher by entering the following command at the command prompt:Dispatcher_Service_ test

View the properties of the dispatcher in the Identity Center to verify that "Version" and "Lastcheck" is filled in.

You can also install the dispatcher as a service, if you want to do that.

Running jobsThere are still no jobs assigned to the dispatcher. To do this:

1. View the properties of the dispatcher and select the "Jobs" tab.

2. Select the jobs that this dispatcher should be responsible for executing.

3. Choose "Apply".

To schedule the job(s):

1. View the properties of the job.

2. Select a suitable schedule rule for the job. You can select "On demand" and choose "Runnow" to test the job execution immediately.

3. Choose "Apply".

View the job log, the job status overview and the system log to see that everything works asexpected.




UnixCreating a runtime environment on a Unix system involves the following steps:

x Preparing the runtime environment on the Unix system.x Creating a user.x Creating a dispatcher for the Unix system.x Moving and adapting the necessary files.x Testing the dispatcher.x Running jobs.

Preparing the environmentInstall the Runtime Components including the necessary prerequisites as described in thedocuments SAP NetWeaver Identity Management Identity Center Installation Overview and SAPNetWeaver Identity Management Identity Center: Installing the Runtime Components.

Creating a userIf you want to run the dispatcher with another user than was used to install the RuntimeComponents, create a user for this purpose in the operating system and name it for instanceidmadm.

Creating the dispatcher and the necessary script filesTo add the dispatcher:

1. Select "Dispatchers" in the Identity Center console tree and choose New/Dispatcher fromthe context menu.

2. Rename the dispatcher. It is recommended to give it a name that identifies the server onwhich it is running.

3. Fill in information about the dispatcher. Choose "Apply".

4. Generate script files for the dispatcher and note where the files are stored.

5. Create separate dispatchers for each Unix server.

Moving and adapting the filesTo move the files:

1. Locate the dispatcher files you just created.

2. Log in as idmadm (the user you created to run the dispatcher).

3. Copy the files Dispatcher_Service_.sh andDispatcher_Service_.prop to the Unix system. The files must be copiedto the same folder (or a sub-folder) where you installed the Identity Center RuntimeComponents.

Note:Make sure to transfer the files as ASCII.

43Section 5: Moving the Identity Center runtime environment to another computerSAP NetWeaver Identity Management Identity Center Initial Configuration


Note:Make sure to make the following changes as idmadm (the user you created to run thedispatcher).

Adapt the following settings in Dispatcher_Service_.sh:

x MXDRIVERJARModify the parameters to contain the correct path for the JDBC driver to the Identity Centerdatabase.

x MXDISPATCHERPROPIf necessary, modify the path to the Dispatcher_Service_.prop file.

Adapt the following settings in the Dispatcher_Service_.prop:

x DSECLASSPATHModify the CLASSPATH to reflect the paths on the Unix system.

Note:To be able to execute the .sh file, make the file executable.

Testing the dispatcherTest the dispatcher by entering the command at the command prompt:

Dispatcher_Service_ test checkconfig

Verify that the dispatcher is able to start and read its configuration. The most probable problemis that the dispatcher is not able to find the required JDBC drivers. Verify that the information inthe .sh and .prop files matches the configuration on the computer.

Then start the dispatcher by entering the following command at the command prompt:Dispatcher_Service_

View the properties of the dispatcher in the Identity Center to verify that "Version" and "Lastcheck" is filled in.

For testing purposes it can be sufficient to start the dispatcher manually, but in a productionsystem you would want to start the dispatcher as a service started using an init script. See thedocumentation for your Unix system how to do this.

Running jobsThere are still no jobs assigned to the dispatcher. To do this:

1. View the properties of the dispatcher and select the "Jobs" tab.

2. Select the jobs that this dispatcher should be responsible for executing.

3. Choose "Apply".

To schedule the job(s):

1. View the properties of the job.

2. Select a suitable schedule rule for the job. You can select "On demand" and choose "Runnow" to test the job execution immediately.

3. Choose "Apply".

View the job log, the job status overview, the system log and the dispatcher status to see thateverything works as expected.




SAP NetWeaver Identity Management Identity Center Initial ConfigurationPrefaceTable of contentsIntroductionSection overview

Section 1: Adding an IdentityCenter configurationAdding the IdentityCenter configurationCreating the Identity Center connection stringMicrosoft SQL ServerOracleIBM DB2

Creating the connection string for the Windows runtime engineMicrosoft SQL ServerOracleIBM DB2

Creating the JDBC URL for the Java runtime engineMicrosoft SQL ServerOracleIBM DB2

Completing the wizardVerifying the connection

Section 2: Configuring a dispatcherAdding the dispatcherCreating the dispatcher scriptsTesting the dispatcherInstalling and starting the dispatcher

Section 3: Verifying job executionCreating a job for the Java runtime engineRunning the jobs

Section 4: Configuring external event handlingCreating the fileCreating the repository definitionCreating the event agentCreating the event agent serviceCreating the service script filesVerifying job propertiesInstalling and starting the event agent service

Section 5: Moving the Identity Center runtime environment to another computerMicrosoft WindowsPreparing the environmentCreating the dispatcher and the necessary script filesMoving and adapting the filesTesting the dispatcherRunning jobs

UnixPreparing the environmentCreating a userCreating the dispatcher and the necessary script filesMoving and adapting the filesTesting the dispatcherRunning jobs

SAP NetWeaver Identity Management Identity Center Intial Configurtion

Text of SAP NetWeaver Identity Management Identity Center Intial Configurtion

SAP NetWeaver Identity Management Identity Center Installing and Configuring the Identity

Sci261- Sap Netweaver Identity Management - Workflow Configuration

SAP NetWeaver Identity Management Identity Center

SAP NetWeaver Identity Management Identity Center Tutorial - Context-Based Assignments

SAP NetWeaver Identity Management Identity Services ...a248.g.akamai.net/n/248/420835/32ae37ca1751ec381f62c27b8084a724465966... · SAP NetWeaver® Identity Management Identity Services

Intial Planning Paper

SAP NetWeaver Identity Management Password Hook ...a248.g.akamai.net/n/248/420835/20a8b8e19d8fcd5b112a7cdd...SAP NetWeaver Identity Management Password Hook Configuration Guide ©

Everyone's intial design

fine art intial

SAP NetWeaver Identity Management Compliant provisioning ... · SAP NetWeaver® Identity Management Compliant provisioning using SAP BusinessObjects Access Control Configuration guide

SAP NetWeaver Identity Management Virtual Directory Server ......The SAP NetWeaver Identity Management Virtual Directory Server can logically represent information from a number of

intial public offering

Identity Management With SAP NetWeaver IdM

SAP NetWeaver Identity Management Technical Overview ...nicx.co.uk/uploaded_files/identitiy management.pdf · SAP NetWeaver Identity Management Technical Overview Presentation

SAP NetWeaver Identity Management Identity Provider

SAP NetWeaver Identity Management- IDM Connector Overview

SAP NetWeaver Identity Management Identity Center Tutorial - Working ...a248.g.akamai.net/n/248/420835/4bdb0b983c840542e10b526ca8fcd16… · SAP NetWeaver® Identity Management Identity

SAP NetWeaver Identity Management Implementation Guide - Transport

INTIAL IDEAS

Intial Report

SAP NetWeaver Identity Management Identity Center Tutorial ... · SAP NetWeaver Identity Management Identity Center is the primary component for identity management. The Identity

Our intial Digipak

SAP NetWeaver Identity Management Identity Providersanty.wdfiles.com/local--files/singlesignon/SAP_SSO_IdentityGuide.pdf · Implementation Guide SAP NetWeaver Identity Management

Intial Msn Plan

Solution Details SAP NetWeaver® Identity Management rapid- deployment solution

SAP NetWeaver Identity Management Virtual Directory Server Using SSL for LDAP ...a248.g.akamai.net/n/248/420835/07aff44b36ce74efc56ea9e52... · 2016-01-22 · SAP NetWeaver® Identity

SAP NetWeaver Identity Management Identity Services Configuration Guide · 2019. 11. 12. · Configuration guide. xSAP NetWeaver Identity Management Compliant provisioning using SAP

Intial Ideas Pitch Final

SAP NetWeaver Identity Management Virtual …...SAP NetWeaver Identity Management Virtual Directory Server Tutorial - Joining data sources Section 1: Viewing the data sources and opening

BGR Intial Coverage

Documents

SAP NetWeaver Identity Management Identity Center Intial Configurtion

Text of SAP NetWeaver Identity Management Identity Center Intial Configurtion