Ident_SAPR3UM_Sync
Workflow for Export from Identity Store and Import to SAP ECC UM and backwards
Ident_SAPR3UM_Sync synchronizes the Identity Store and SAP ECC User Management in both directions. It processes groups before accounts on the outbound and return paths so that group structures are already present when later account updates refer to them.
Use this workflow for scheduled bidirectional synchronization when SAP ECC User Management, also known as SAP R/3 UM, remains an active source as well as a target of changes.
The workflows in this reference are delivered as factory data and are loaded into the Connectivity configuration database during the initial configuration. They are samples: use the Identity Manager to copy a workflow into your own scenario and adapt the copy. Do not change the delivered objects, because a product update can replace them.
At a Glance
Name |
|
Category |
Target Scheduled / SAPR3UM |
Technology |
Tcl-based scheduled workflow |
LDAP object class |
|
Workflow type |
|
Connected system / controller type |
- |
Configuration wizard |
|
Active in the factory data |
not set |
Factory data version |
7.0 |
Factory data path |
|
Prerequisites
-
Configure
SAP-R3-UMAgentso that it can connect to SAP ECC User Management. -
Configure
MetaCPfor the corresponding target system subtree in the Identity Store.
Workflow and Activities
| Step | Activity | Description | Agent | Runs after |
|---|---|---|---|---|
1 |
|
Export of groups |
|
start activity |
2 |
|
Import of groups |
|
|
3 |
|
Export of accounts |
|
|
4 |
|
Import of accounts |
|
|
5 |
|
export of groups |
|
|
6 |
|
import of groups to role |
|
|
7 |
|
export of accounts |
|
|
8 |
|
import of accounts to role |
|
|
Jobs and Agents
| Activity | Job | Agent | Operation | Input channel | Output channel |
|---|---|---|---|---|---|
|
|
|
Full Export |
|
|
|
|
|
Full Export |
|
|
|
|
|
Full Export |
|
|
|
|
|
Full Export |
|
|
|
|
|
Full Export |
|
|
|
|
|
Delta Import |
|
|
|
|
|
Full Export |
|
|
|
|
|
Delta Import |
|
|
Configuration Parameters
| Parameter | Default value |
|---|---|
|
0 |
|
delta-or-full |
|
1 |
|
FALSE |
|
REAL |
|
10 |
|
0 |
|
0 |
|
TRUE |
|
FALSE |
|
0 |
|
1 |
|
0 |
| Parameter | Default value |
|---|---|
|
1 |
| Parameter | Default value |
|---|---|
|
0 |
|
delta-or-full |
|
1 |
|
FALSE |
|
REAL |
|
10 |
|
0 |
|
0 |
|
TRUE |
|
FALSE |
|
0 |
|
1 |
|
0 |
| Parameter | Default value |
|---|---|
|
1 |
| Parameter | Default value |
|---|---|
|
1 |
| Parameter | Default value |
|---|---|
|
0 |
|
full |
|
0 |
|
FALSE |
|
REAL |
|
10 |
|
0 |
|
0 |
|
TRUE |
|
FALSE |
|
1 |
|
0 |
| Parameter | Default value |
|---|---|
|
1 |
| Parameter | Default value |
|---|---|
|
0 |
|
full |
|
0 |
|
FALSE |
|
REAL |
|
10 |
|
0 |
|
0 |
|
TRUE |
|
FALSE |
|
1 |
|
0 |
A Tcl-based workflow runs scheduled in the C++-based Server (IdS-C). Its activities run in the order
defined by the dxmPredecessorActivity-DN chain, and each activity starts a job that runs one agent
with one input and one output channel. Agents exchange their data through files or directly through
the meta controller, so a typical workflow consists of an export activity that writes the data of the
connected system and an import activity that maps and loads that data into the Identity Store.
You start these workflows manually from the Identity Manager or attach them to a schedule.
In this workflow, the C++-based Server runs these activities in sequence:
-
Ident2SAPR3UM_SyncGroup_MetaCPexports group changes from the Identity Store. -
Ident2SAPR3UM_SyncGroup_UMAgentimports those group changes into SAP ECC User Management. -
Ident2SAPR3UM_SyncAccount_MetaCPexports account changes from the Identity Store. -
Ident2SAPR3UM_SyncAccount_UMAgentimports those account changes into SAP ECC User Management. -
SAPR3UM2Ident_SyncGroup_UMAgentexports group changes from SAP ECC User Management. -
SAPR3UM2Ident_SyncGroup_MetaCPimports those group changes into the Identity Store. -
SAPR3UM2Ident_SyncAccount_UMAgentexports account changes from SAP ECC User Management. -
SAPR3UM2Ident_SyncAccount_MetaCPimports those account changes into the Identity Store.
If one activity fails, the workflow stops at that point and the remaining activities do not run.
Operation
-
Start
Ident_SAPR3UM_Syncmanually or on a schedule. -
The workflow begins with the Identity Store to SAP direction by exporting groups with
MetaCPand importing them withSAP-R3-UMAgent, then repeating the same pattern for accounts. -
After the outbound pass finishes, the workflow changes direction and exports groups from SAP ECC User Management with
SAP-R3-UMAgentbefore importing them into the Identity Store withMetaCP. -
It then repeats the return pass for accounts so that both object types are processed in both directions during the same run, with groups always preceding accounts.
-
When the workflow completes successfully, the scheduled run has applied outbound changes to SAP ECC User Management and has imported the latest returned group and account data into the Identity Store.