Editing SAMBA CLUSTER PUNJAB GOVT IFMS-IWDMS PROJECT (section)

== Requirements  ==
• openldap-servers (contains migration utilities used in this document) 

• 389-DS (the directory server should already be installed) 

• samba, samba-client, samba-common (samba server, also provides schema needed for storing samba information) 

• schema to ldif migration script (can be downloaded from here:

[http://directory.fedoraproject.org/download/ol-schema-migrate.pl http://directory.fedoraproject.org/download/ol-schema-migrate.pl])


First off we need to provide 389-DS with a samba schema that it understands. Now lets break down how 389-DS implements extending schemas : 


• All schema files are in ldif format and loaded during server start .


• <nowiki>All schema's are located in /opt/389-DS/slapd-<server>/config/schema, where <server> is 'ldap1' or 'ldap2', as the case may be.</nowiki>


• Filenames are sequential and loaded in order and 99user.ldif is always the last schema to be loaded. 


For this document we are going to name our schema file 61samba.ldif. As stated above we need to provide 389-DS with a schema it understands which involves converting the provided /usr/share/doc/samba/LDAP/samba.schema to ldif format. Luckily, there is a utility provided 3rd party that will assist in doing this which can be found at [http://directory.fedoraproject.org/download/ol-schema-migrate.pl http://directory.fedoraproject.org/download/ol-schema-migrate.pl]


We do this on the 389-DS server. 


Use of this script is straight forward : 


<nowiki># perl ol-schema-migrate.pl -b \</nowiki>

/usr/share/doc/samba-*/LDAP/samba.schema \

<nowiki>> /etc/dirsrv/slapd-<server>/schema/61samba.ldif </nowiki>


Once the ldif is in place restart the slapd service : 


<nowiki># service dirsrv restart </nowiki>