Re: OpenLDAP and IBM

["OpenLDAP Sadesi" <openldap.sadesi@juntadeandalucia.es>]

Gustavo:

    i had the same problems with OID of ORACLE.

    i had to migrate data inside OID to OpenLDAP. therefore i had to writte
the OID schemas
    when i tried the ldapadd and included the files with include in
slapd.conf, all was ok

    solutions:
            - first i think that you MUST control the exact version of
OpenLDAP. i think that you MUST install
                a version, because you could control completely the
configuration of the system.
            - second: if you have made the schemas files, and you are write
the include sentences correctly, are you                     sure that
ldapadd is catching this files. you could try to down loglevel. when you
runs slapd you could
                see if the daemon parser this files correctly


    agustin.

----- Original Message -----
From: "Sánchez Bermejo, Gustavo" <gusanch@mapfre.com>
To: "'openldap-software@openldap.org'" <openldap-software@OpenLDAP.org>
Sent: Wednesday, June 04, 2003 3:03 PM
Subject: OpenLDAP and IBM


> I show you some definitions from the files I've downloaded from IBM:
>
> File IBM.V3.ibm.oc
>
> # File generated at 10:37:37 PM on 1/2/2002 from IBM LDAP schema version
1.5
> objectclass=( 1.3.6.1.4.1.1466.344 NAME 'dcObject' DESC 'Object class that
> allows domain components to be defined for an entry.' SUP 'top' AUXILIARY
> MUST ( dc ) )
> objectclass=( 1.3.18.0.2.6.28 NAME 'container' DESC 'An object that can
> contain other objects.' SUP 'top' STRUCTURAL MUST ( cn ) )
> objectclass=( 1.3.18.0.2.6.81 NAME 'eSystem' DESC 'Based on CIM_System,
this
> structural class provides the common system and subsystem aggregation
> attributes for administrative scope and contact information.  This
> object class is generally instantiated only for use as an administrative
> scoping container object.  The eSystem subclasses are instantiated to
> represent computer systems, operating systems and application systems.'
SUP
> 'cimLogicalElement' STRUCTURAL MAY ( sys $ systemRoles $
> primaryOwnerContact $ primaryOwnerName $ nameFormat ) )
> objectclass=( 1.3.18.0.2.6.83 NAME 'eComputerSystem' DESC 'Based on
> CIM_ComputerSystem, this structural class represents a computer  system.
> Use of this class in conjunction with a dcObject can help to integrate
> the CIM-based LDAP classes with commonly used domain component naming.'
SUP
> 'eSystem' STRUCTURAL MAY ( host $ location ) )
> objectclass=( 1.3.18.0.2.6.82 NAME 'eOperatingSystem' DESC 'Based on
> CIM_OperatingSystem, this structural class models the operating  system(s)
> on a computer system.' SUP 'eSystem' STRUCTURAL MAY ( osType $
> otherOSTypeDescription $ distributedOS $ version $ currentTimeZone $
> numberOfLicensedUsers $ maxNumberOfProcesses $ totalSwapSpaceSize $
> sizeStoredInPagingFiles $ applSystemHint ) )
>
> FILE IBM.V3.ibm.at
>
> attributetypes=( 1.3.18.0.2.4.328 NAME 'supportingFiles' DESC 'Attribute
for
> listing files associated with a software directory object entry.' EQUALITY
> 2.5.13.2 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 USAGE userApplications
> )
> attributetypes=( 1.3.18.0.2.4.354 NAME 'supportsFileBasedCompression' DESC
> 'see MS WBEM' SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 SINGLE-VALUE USAGE
> userApplications )
> attributetypes=( 1.3.18.0.2.4.329 NAME ( 'sys'  'systemName'  ) DESC 'A
> naming attribute that may be used to identify eSystem (and subclasses
> thereof) object entries.' EQUALITY 1.3.6.1.4.1.1466.109.114.2 ORDERING
> 2.5.13.3 SUBSTR 2.5.13.4 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE
> USAGE userApplications )
> attributetypes=( 1.3.18.0.2.4.185 NAME 'sysplex' DESC 'Identifies the name
> of an OS/390 sysplex.' EQUALITY 2.5.13.2 SYNTAX
> 1.3.6.1.4.1.1466.115.121.1.15 SINGLE- VALUE USAGE userApplications )
> attributetypes=( 1.3.18.0.2.4.804 NAME 'systemEnvironment' DESC 'protect
> environment' EQUALITY 2.5.13.5 ORDERING 2.5.13.6 SUBSTR 2.5.13.7 SYNTAX
> 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE USAGE userApplications )
>