PeopleSoft and ou's

Hi,

I have some questions about the PeopleSoft driver 5.1.1 and IDM 3.51.
We want to synchronize organizational information. The synchronization
of users is already implemented and works well.
We need organizational attributes from PeopleSoft to eDirectory.
I think for the IDM access we need a new schema ci for mapping to class
"organizational unit" and a new transaction table.
Additional, we need definitions for fields, records and sql code. Is
that correct?
Is it possible to use such definitions from the PSA sample project or
we have to create new definitions?
But I'm not sure if we need a second driver for the ou's, because the
classes user and "organizational unit" uses different data record id
fields.

Regards,
hafu


-- 
hafu
------------------------------------------------------------------------
hafu's Profile: http://forums.novell.com/member.php?userid=10757
View this thread: http://forums.novell.com/showthread.php?t=327483

On Mon, 12 May 2008 08:06:02 GMT, hafu <hafu@no-mx.forums.novell.com>
wrote:

>We need organizational attributes from PeopleSoft to eDirectory.
>I think for the IDM access we need a new schema ci for mapping to class
>"organizational unit" and a new transaction table.

That should work, yes. I'm not a CI expert, but it seems to me that you
should be able to do this in one CI / PeopleSoft driver, just with
different information coming through for different classes of object. It
might be simpler to impliment as a second driver, though.

>Additional, we need definitions for fields, records and sql code. Is
>that correct?
>Is it possible to use such definitions from the PSA sample project or
>we have to create new definitions?

I suspect you'll have to replicate what the project does to set up a
second set of everything if you're going to do this via a second driver.


---------------------------------------------------------------------------
 David Gersic                                            dgersic_@_niu.edu
 Novell Support Forums Volunteer SysOp            http://forums.novell.com

Hi,

If you use a separate Transaction component, you will need a separate driver. 
Each driver can consume from only 1 transaction table.  It is possible to place
the transactions from multiple data components into the same Transaction table
if desired so you can use 1 driver.  As for the record ID fields, since the
driver deals with a Component Interface, it is possible to change the default CI
field names without changing the names of the underlying Component or Record
field names.  This is incredibly easy to do.  As you noted, it is required to
have the same CI key field name if you wish to use 1 driver.

Regards,
Mark

>>> hafu<hafu@no-mx.forums.novell.com> 5/12/2008 2:06 AM
>>>
Hi,

I have some questions about the PeopleSoft driver 5.1.1 and IDM 3.51.
We want to synchronize organizational information. The synchronizationof users
is already implemented and works well.
We need organizational attributes from PeopleSoft to eDirectory.
I think for the IDM access we need a new schema ci for mapping to
class"organizational unit" and a new transaction table.
Additional, we need definitions for fields, records and sql code. Isthat
correct?
Is it possible to use such definitions from the PSA sample project orwe have to
create new definitions?
But I'm not sure if we need a second driver for the ou's, because theclasses
user and "organizational unit" uses different data record idfields.

Regards,
hafu--
hafu------------------------------------------------------------------------hafu
's Profile: http://forums.novell.com/member.php?userid=10757View this thread:
http://forums.novell.com/showthread.php?t=327483

Hi Mark and David,

thanks for your responses. I'll try it.

Regards,
hafu


mworwetz;1557551 Wrote: 
> Hi,
> 
> If you use a separate Transaction component, you will need a separate
> driver.  Each driver can consume from only 1 transaction table.  It is
> possible to place the transactions from multiple data components into
> the same Transaction table if desired so you can use 1 driver.  As for
> the record ID fields, since the driver deals with a Component
> Interface, it is possible to change the default CI field names without
> changing the names of the underlying Component or Record field names. 
> This is incredibly easy to do.  As you noted, it is required to have
> the same CI key field name if you wish to use 1 driver.
> 
> Regards,
> Mark
> 
> 
> >>> hafu<hafu@no-mx.forums.novell.com> 5/12/2008 2:06 AM
>>>
> 
> Hi,
> 
> I have some questions about the PeopleSoft driver 5.1.1 and IDM 3.51.
> We want to synchronize organizational information. The
> synchronizationof users is already implemented and works well.
> We need organizational attributes from PeopleSoft to eDirectory.
> I think for the IDM access we need a new schema ci for mapping to
> class"organizational unit" and a new transaction table.
> Additional, we need definitions for fields, records and sql code.
> Isthat correct?
> Is it possible to use such definitions from the PSA sample project orwe
> have to create new definitions?
> But I'm not sure if we need a second driver for the ou's, because
> theclasses user and "organizational unit" uses different data
record
> idfields.
> 
> Regards,
> hafu--
>
hafu------------------------------------------------------------------------hafu
's
> Profile: 'NOVELL FORUMS - View Profile: a0210491'
> (http://forums.novell.com/member.php?userid=10757View) this thread:
> 'PeopleSoft and ou's - NOVELL FORUMS'
> (http://forums.novell.com/showthread.php?t=327483)


-- 
hafu
------------------------------------------------------------------------
hafu's Profile: http://forums.novell.com/member.php?userid=10757
View this thread: http://forums.novell.com/showthread.php?t=327483