Understanding Default User Profile Synchronization

When you implement default user profile synchronization among databases, other than the default user profile synchronization exceptions mentioned below, the subscribing databases have no control over the data that they receive and process.

All participating databases use the USER_PROFILE service operation and the USER_PROFILE.VERSION_84 message during the publish and the subscribe processes.

This diagram shows the service operations and messages, and the way in which user profile data is published by and subscribed to by three PeopleSoft systems that are using default user profile synchronization.

Diagram of the flow of user profile information as it uses standard synchronization among three PeopleSoft databases

Default User Profile Synchronization Designed Exclusions

Adding and deleting user profiles on the publishing node cause corresponding changes on the subscribing nodes. Modifying user profiles on the publishing node causes corresponding changes on the subscribing nodes with these exceptions:

  • Changes to the primary email account are ignored if a primary email exists in the subscribing node.

  • Changes to a user ID type are ignored if the user ID type is not valid on the subscribing node. Instead, the subscribing node inserts an ID type of None if the subscribing node does not have a row for None already.

  • In general, changes that produce invalid field values in the subscribing node are ignored by the subscribing node.