Novell Doc: Identity Manager 3.6.1 Fan-Out Driver for SAP User Managment Implementation Guide

2.1 Association Format

The association format has changed in the SAP User Management Fan-Out driver. Table 2-1 shows the changes in the association format. The new driver is backwards compatible. The older drivers do not support the newer format.

Table 2-1 Association Format

Old Association Format	New Association Format
USd<USERNAME> US: The class. d: A delimiter. <USERNAME>: The unique identifier and username in the SAP system. For example: USdBERG	<LSNAME>USd<USERNAME> <LSNAME>: The logical system name where events are sent. US: The class d: A delimiter. <USERNAME>: It is the unique identifier and username in the SAP system. For example: \S71CLNT800\USdABERG

Old Association Format

New Association Format

USd<USERNAME>

US: The class.
d: A delimiter.
<USERNAME>: The unique identifier and username in the SAP system.

For example: USdBERG

<LSNAME>: The logical system name where events are sent.
US: The class
d: A delimiter.
<USERNAME>: It is the unique identifier and username in the SAP system.

For example: \S71CLNT800\USdABERG

The two main points to remember the association format are:

The association is very close to a DN format.
The first part of the association contains an identifier that tells the shim which logical system receives the event.

The following is an example of the association format in a trace:

<nds dtdversion="3.5" ndsversion="8.x"> 
  <source>
    <product version="3.6.0.4294">DirXML</product> 
    <contact>Novell, Inc.</contact>
  </source>
 <input>
   <modify class-name="US" event-id="metaserver1#20090513130202#1#2#0" from-merge="true" src-dn="\META\data\company\users\aberg" src-entry-id="40801">
      <association>\S7ICLNT800\USdABERG</association>
      <modify-attr attr-name="ADDRESS:FULLNAME">
        <add-value>
          <value timestamp="1234481823#65" type="string">Berg Andrea</value>
        </add-value>
      </modify-attr>
   </modify>
 </input>
</nds>

If the driver is running in fan-out mode, there are multiple associations added to the user object. They are required for fan-out to work correctly. The format of the association is:

fanout1-xTFRgkLOmElpuMUxUYJCzg==
fanout2-xTFRgkLOmElpuMUxUYJCzg==

The xTFRgkLOmElpuMUxUYJCzg== value is the GUID of the User object in the Identity Vault.