RE: Fw: How useful is oracle internet directory server?

["Macleod, John" <john.macleod@csfb.com>]

Regarding the integration challenge from legacy directory applications, if
you have'nt already discovered Sun/NetScape's Meta-Directory product, it's
got connectors to many major proprietary systems.  I am told that it takes a
lot of heavy lifting to configure some connectors initially, but once in
place you've got cross-directory support for the duration until you can move
all your apps to LDAP.

John

-----Original Message-----
From: Giovanni Baruzzi [mailto:giovanni.baruzzi@allianz-leben.de]
Sent: Wednesday, October 13, 1999 7:11 AM
To: Mark Wilcox
Cc: Arnold Shore; Bharat Tewari; Open-LDAP General
Subject: Re: Fw: How useful is oracle internet directory server?


Hallo Mark

we have here basically two distinct ideas:

1. the first idea is to have an  Lightweight SQL Access Protocol; JDBC and
DBI
are good steps in the right direction, but as far not so mature or global as
LDAP. (JDBC is limited to Java, for example, DBI to Perl; what about other
languages?)
That is in itself a good goal.

2. the second idea is one that many of us must face in everyday Practice.
We have old legacy applications that stored "directory information" in SQL
tables. We cannot bring all this data AT ONCE in a LDAP server option,
because
we have so many applications hanging from it. We need integration.
Up to now we had been building horrendous gimmicks to update the information
in
LDAP AND in the old Database (often an Oracle, for us).
The simple fact that the LDAP server uses as Back-End your old Oracle, even
is
separata table spaces, with a completely different model, is just ONE MORE
CHANCE to perform a better integration and to enable a future full
migration.


Bets regards
Giovanni





Mark Wilcox wrote:

> This would kind of be the wrong way to go. A directory is not an RDBMS so
it
> shouldn't support the same functionality.
>
> What you're asking for (and it's a good idea) is a an open standard for
> communicating with a RDBMS. Most people think that's SQL, but SQL is only
> useful after you've connected to the database. There still is not a true
> open standard to a RDBMS. The closest things we have are ODBC (which is
just
> because MS shipped with every copy of Windows and is still primarily a
> Windows only protocol), Java's JDBC and Perl's DBI.
>
> If you had a true open RDBMS database protocol, then you could talk more
> sensibly about which to use (e.g. LDAP or RDBMS protocol) for an
application
> instead of trying to fit an RDBMS into LDAP.
>
> Mark
> -----Original Message-----
> From: Arnold Shore <ashore@stginc.com>
> To: giovanni.baruzzi@allianz-leben.de <giovanni.baruzzi@allianz-leben.de>;
> Bharat Tewari <tewari@wipinfo.soft.net>
> Cc: Open-LDAP General <openldap-general@OpenLDAP.org>
> Date: Tuesday, October 12, 1999 6:39 AM
> Subject: RE: Fw: How useful is oracle internet directory server?
>
> >I would add that as LDAP usage grows into an enterprise infrastructure
> >element, then its widening use will be facilitated by making available
the
> >SQL functions that are inherent to rdbms's.  My view is that it's a sign
of
> >maturation.
> >
> >Or, as my grandmother might have said, "Paradigm, schmaradigm - it works
> >OK!"
> >
> >Arnold Shore
> >Annapolis, MD
> >
> >-----Original Message-----
> >From: owner-openldap-general@OpenLDAP.org
> >[mailto:owner-openldap-general@OpenLDAP.org]On Behalf Of Giovanni
> >Baruzzi
> >Sent: Tuesday, October 12, 1999 7:11 AM
> >To: Bharat Tewari
> >Cc: Open-LDAP General
> >Subject: Re: Fw: How useful is oracle internet directory server?
> >
> >
> >
> >
> >Bharat Tewari wrote:
> >
> >>  >>>>
> >> <?fontfamily><?param Arial><?smaller>Hi
> >> I just read somewhere that oracle has come out with Internet directory
> >> server where basically its the open ldap server code and the backend
> >> database is oracle. Now as per my understanding, the RDBMS and
> >> directory service are two different paradigms so what exactly is the
> >> advantage oracle is going to get with this move?
> >
> >Sure RDBMS and LDAP are very distant.
> >But wer have so many RDBMS applications that we want to use and we don't
> >have neither time or money to rewrite them completely, that every chance
> >in integration is welcomed.
> >The fact that the data repository of LDAP lies in the same Database as
> >my application greatly enhances the possiblities of intergration. One
> >can think of stored procedures to maintain application tables while
> >updating LDAP or retrieving "Legacy Data" while accessing LDAP.
> >
> >>
> >> Secondly how ldap and e-commerce are related?
> >
> >LDAP is infrastrucutre that you need to collect the data about your
> >customers, their authentication, their rights, their settings.
> >
> >
> >
> >> Can somebody give me a good pointer on various e-commerce products
> >> that use ldap and how does the relational database as a backend
> >> advantageous(if it is!!).
> >
> >I have no pointers.
> >About RDBMS: they are a very good way to organize data in tables. Is a
> >mature technology and today very effective.
> >We need data in tables; LDAP would not be the ideal solution here.
> >
> >
> >> If anyone of you is planning on this direction and can throw some
> >> light without violating patents, copyrights or confidentiality it
> >> would be really helpful to me.
> >> Thx
> >> bharat
> >> <?/smaller><?/fontfamily>
> >> <<<<
> >>
> >>
> >
> >My 0.5 cents
> >
> >Giovanni Baruzzi
> >
> >
> >

This message is for the named person's use only.  It may contain confidential, proprietary or legally privileged information.  No confidentiality or privilege is waived or lost by any mistransmission.  If you receive this message in error, please immediately delete it and all  copies of it from your system, destroy any hard copies of it and notify the sender.  You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE GROUP, CREDIT SUISSE FIRST BOSTON, and each legal entity in CREDIT SUISSE FIRST BOSTON  reserve the right to monitor all e-mail communications through its networks.  Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity.