Re: [Ganymede Help] Should I use Ganymede?

[Jonathan Abbey <jonabbey@arlut.utexas.edu>]

| Hi everybody.
| I have to build a batch job that syncs users in our corporate Directory
| Server (iPlanet 5.0) with our legacy "Human Resource" app; the source can be
| a CSV text file or a direct DBII view on user data table.

That is, you have data in iPlanet, and you want to periodically
extract that data from iPlanet and create data files that can then be
loaded into your legacy app, yes?

| The job should run once a day, and i'm talking about a number between 32000
| and 40000 users.

Right.

| I understand that this is a "bite" of what Ganymede can really do, but I'm
| trying to understand if could be useful to set up a Server (we can do this)
| and implement a custom GanymedeBuilderTask.

Welll.. I'm not sure.  It sounds like your master directory repository
already exists in iPlanet.  Ganymede isn't designed to act as a
synchronization conduit between two arbitrary directory
services.. instead, it is intended to be the master directory
repository, and to intelligently handle synchronization from its
internal store to external services whenever a transaction is
committed.  Ganymede's more about relatively low capacity directory
services, and extremely frequent directory synchronization, choices
which work far better for NIS than they do for something like an
enterprise-wide LDAP system.

If you wanted to use Ganymede, what you would wind up having to do
would be to store all your user information in Ganymede, then have
Ganymede synchronize to iPlanet and your legacy app whenever anything
changes.  The benefits of this would be that you'd probably get a much
more user-friendly user interface, along with the ability to write all
kinds of custom logic to guide your users through the editing process.

It really sounds like you just need to write a Java app with JNDI, or
simply use ldiffcat or the like, to pull your entire user database
from iPlanet once a day, and then reformat it and sync it to your
legacy app.  Ganymede wouldn't add anything to that process, unless
you stored your master directory data in Ganymede, and if you did
that, you'd then have to worry about doing two synchronizations, one
to iPlanet, and one to your legacy app.  Wouldn't seem to make sense,
if I understand what you're after, here.

| Any suggestion?...
| Any "GanymedeBuilderTask" sample clear enough for a novice to start with?...

You can look at the builder tasks included in the userKit package, if
you like.

| Thank you!

-------------------------------------------------------------------------------
Jonathan Abbey 				              jonabbey@arlut.utexas.edu
Applied Research Laboratories                 The University of Texas at Austin
Ganymede, a GPL'ed metadirectory for UNIX     http://www.arlut.utexas.edu/gash2

----------------------------------------------------------------------------
To make changes to your subscription to the Ganymede Help list, send
mail to majordomo@arlut.utexas.edu.

To unsubcribe, include the line

unsubscribe ganymede-help

in the body of your mail message

Visit the Ganymede web page at http://www.arlut.utexas.edu/gash2

----------------------------------------------------------------------------