[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: LDIF format question for Openldap-2.3.27
Yeah! I added the cn values to both entries, but still it didn't work
Yeah fnDbConPool is a structural objectClass.
dn: cn=jdbc,dc=production,dc=net
objectClass: top
objectClass: extensibleObject
cn: jdbc
dn: cn=testApp,cn=jdbc,dc=production,dc=net
fnDbFactoryName: OCCDataSourceFactory
fnDbCacheScheme: DYNAMIC
fnDbMaxLimit: 10
fnDbUser: testApp
objectClass: fnDbConPool
fnDbPasswd: testApp
fnDbMinLimit: 2
fnDbURL: jdbc:oracle:thin:@test.com:1521:test
cn : testApp
-----Original Message-----
From: Venkat Reddy Valluri
Sent: Thursday, April 05, 2007 3:15 PM
To: openldap-software@openldap.org
Subject: RE: LDIF format question for Openldap-2.3.27
Yeah! I added the cn values to both entries, but still it didn't work
Yeah fnDbConPool is a structural objectClass.
dn: cn=jdbc,dc=production,dc=net
objectClass: top
objectClass: extensibleObject
cn: jdbc
dn: cn=testApp,cn=jdbc,dc=production,dc=net
fnDbFactoryName: OCCDataSourceFactory
fnDbCacheScheme: DYNAMIC
fnDbMaxLimit: 10
fnDbUser: testApp
objectClass: fnDbConPool
fnDbPasswd: testApp
fnDbMinLimit: 2
fnDbURL: jdbc:oracle:thin:@test.com:1521:test
cn : workSmart
-----Original Message-----
From:
openldap-software-bounces+venkat.valluri=quinnfable.com@OpenLDAP.org
[mailto:openldap-software-bounces+venkat.valluri=quinnfable.com@OpenLDAP
.org]On Behalf Of Svend Sorensen
Sent: Thursday, April 05, 2007 2:28 PM
To: openldap-software@openldap.org
Subject: Re: LDIF format question for Openldap-2.3.27
On 4/5/07, Svend Sorensen wrote:
> On 4/5/07, Venkat Reddy Valluri wrote:
> >
> > dn: cn=testApp,cn=jdbc,dc=production,dc=net
> > fnDbFactoryName: OCCDataSourceFactory
> > fnDbCacheScheme: DYNAMIC
> > fnDbMaxLimit: 10
> > fnDbUser: testApp
> > objectClass: fnDbConPool
> > fnDbPasswd: testApp
> > fnDbMinLimit: 2
> > fnDbURL: jdbc:oracle:thin:@test.com:1521:test
>
> You are missing the objectClass
I didn't see the objectClass line. Is fnDbConPool a structural objectClass?
> and cn attributes in your entry.