Infrastructure for mySAP installation, or import the file using the 

ldapmodify

command. 

The following example shows the LDIF file used in this scenario. It also shows 

the user ID and group membership relationships used in this scenario.

Example 1   LDAP group definitions for IBM Dynamic Infrastructure for mySAP

dn: cn=OfferingProviderAdministrator,dc=ibm,dc=com

cn: OfferingProviderAdministrator 

objectClass: groupOfUniqueNames 

description: Offering Provider Administrator 

uniquemember: cn=dexteradmin,dc=ibm,dc=com 

dn: cn=OfferingServiceManager,dc=ibm,dc=com 

cn: OfferingServiceManager 

objectClass: groupOfUniqueNames 

description: Offering Service Manager 

uniquemember: cn=dexterservicemanager,dc=ibm,dc=com 

dn: cn=ODSProviderAdministrator,dc=ibm,dc=com

cn: ODSProviderAdministrator 

objectClass: groupOfUniqueNames 

description: e Utility Provider Administrator 

uniquemember: cn=dexterodsadmin,dc=ibm,dc=com 

dn: cn=OfferingSubscriber,dc=ibm,dc=com 

cn: OfferingSubscriber 

objectClass: groupOfUniqueNames 

description: Offering Subscriber 

uniquemember: cn=dexteremea,dc=ibm,dc=com

uniquemember: cn=dexterap,dc=ibm,dc=com

uniquemember: cn=dexteramericas,dc=ibm,dc=com

The following example shows the definitions of the above groups using the 

ldapmodify

 command.

Example 2   Output of ldapmodify command

ldapmodify  i your_config_file.ldif  h db2srv  w tdsuser  D "cn=root"

modifying entry cn=OfferingProviderAdministrator,dc=ibm,dc=com

modifying entry cn=OfferingServiceManager,dc=ibm,dc=com

modifying entry cn=ODSProviderAdministrator,dc=ibm,dc=com

modifying entry cn=OfferingSubscriber,dc=ibm,dc=com

Dynamic Provisioning of SAP Environments using IBM DI for mySAP and Tivoli Provisioning Manager

15