...
Move the File
In uPortal 2, the file was named personDirectory.xml and located in /uPortal/properties. In uPortal 3, the file is named personDirectoryContext.xml and located in /uPortal/portal-impl/src/main/resources/properties/contexts.
Rename the Package
Replace all instances of org.jasig.portal.services.persondir in the file with org.jasig.services.persondir.
CachingPersonAttributeDaoImpl
...
JdbcPersonAttributeDaoImpl
JdbcPersonAttributeDaoImpl was renamed to SingleRowJdbcPersonAttributeDao and moved into the org.jasig.services.persondir.support.jdbc package. Update the bean class attribute to org.jasig.services.persondir.support.jdbc.SingleRowJdbcPersonAttributeDao
DataSource Access
In the uPortal 2 file, access to the Portal DataSource was done via Spring's MethodInvokingFactoryBean. Although the API is still available, this will not work in uPortal 3 and will cause the portal to fail to start. The portal's DataSource is now available as a Spring bean named PortalDB which should be injected instead.
...
LdapPersonAttributeDaoImpl
LdapPersonAttributeDaoImpl was renamed to LdapPersonAttributeDao and moved into the org.jasig.services.persondir.support.ldap package. Update the bean class attribute to org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao
The ldapServer property which expected an ILdapServer has been replaced with the contextSource attribute which expects a ContextSource See the next section on getting access to the portal's ContextSource
LDAP Server Access
In the uPortal 2 file, access to the Portal LDAP server was done via Spring's MethodInvokingFactoryBean. uPortal 3 and Person Directory are now using the Spring-LDAP framework to manage LDAP access. The portal's LDAP servers are now configured in the ldapContext.xml file and the appropriately named ContextSource from that file should be used instead.
...