1.7 Subscribing from the Identity Vault

PeopleSoft is the authoritative process for ADD and DIS (delete or disable) events. Therefore, the default driver only allows updates to PeopleSoft on the Subscriber channel.

Because PeopleSoft is a relational database (instead of a hierarchical database), the Move and Rename processes generally do not apply. If these processes occur in the Identity Vault against an object that the driver is subscribed to, the driver converts them to a Modify event. The driver does this to update the eDirectory ID and eDirectory Distinguished Name in PeopleSoft, if the update process is not disabled.

The driver subscribes to Modify events that occur within the Identity Vault. PeopleSoft is designed to be the authoritative owner of data in the delivered solution. Therefore, if a User object is created in eDirectory, an employee record in PeopleSoft is not created with the default configuration.

The data elements that are being subscribed from the Identity Vault to PeopleSoft must

When the driver is notified of a modification to an attribute selected in its Subscriber filter, the driver sends the event to the Event Server. The Event Server formats the event and then updates PeopleSoft by communicating through the PeopleSoft Message Agent. Data received from the Identity Vault can be placed on a panel or page inside PeopleSoft.

Because this data is being updated and maintained outside of PeopleSoft, it should typically be set to Display Only from within PeopleSoft. It is not advisable to allow the same data element to be modified inside and outside of PeopleSoft. For this to occur, the data element would need to be defined in both the Publisher and the Subscriber channel on the driver.

You can update data in PeopleSoft to an existing PeopleSoft record. To do this, you must write appropriate PeopleCode so that data elements updated on the DIRXML_STAGE01 record definition are also copied to the desired record within the PeopleSoft environment.