Understanding Configurable User Profile Synchronization

When you implement configurable user profile synchronization among databases, you can select, or configure, the fields containing data for which you want to subscribe.

All participating databases use the USER_PROFILE service operation and the USER_PROFILE.VERSION_84 message to publish user profile information.

All participating databases use the USER_PROFILE_XFR service operation and the USER_PROFILE.VERSION_XFR message to subscribe to the incoming data. You configure the USER_PROFILE_XFR inbound routing with a USER_PROFILE.VERSION_84 external alias. This alias enables the subscribing databases to receive the inbound USER_PROFILE.VERSION_84 message and transform it based on your field configuration.

The USER_PROFILE.VERSION_XFR message definition excludes only the following record.fields by default:

  • PSOPRDEFN.OPRCLASS

  • PSOPRDEFN.ROWSECCLASS

  • PSOPRDEFN.SYMBOLICID

  • PSOPRDEFN.PRCSPRFLCLS

  • PSOPRDEFN.DEFAULTNAVHP

The subscription PeopleCode for the USER_PROFILE_XFR service operation will fail if any expected records are missing or out of order. It will also fail if certain record.fields are not in the USER_PROFILE.VERSION_XFR message. The following is a list of the required record.fields for the USER_PROFILE.VERSION_XFR message to function:

  • PSOPRDEFN.OPRID

  • PSOPRALIAS.OPRALIASTYPE

  • PSROLEUSER_VW.ROLENAME

  • RTE_CNTL_USERVW.ROLENAME

  • RTE_CNTL_USERVW.RTE_CNTL_PROFILE

  • PSUSEREMAIL.EMAILTYPE

  • PSUSEREMAIL.EMAILID

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 use configurable user profile synchronization.

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