380 likes | 944 Vues
PeopleSoft Directory Interface for HRMS prepared for USM Regional PeopleSoft Conference June 10, 2005 Hank Kehlbeck, Sr. Product Manager, HCM Strategy. Agenda. LDAP Overview PeopleSoft Directory Interface Overview Delivered Templates Configuring Directory Interface
E N D
PeopleSoft Directory Interface for HRMS prepared for USM Regional PeopleSoft Conference June 10, 2005 Hank Kehlbeck, Sr. Product Manager, HCM Strategy
Agenda • LDAP Overview • PeopleSoft Directory Interface Overview • Delivered Templates • Configuring Directory Interface • Where to Get More Information • Lessons Learned / Your Feedback
What is LDAP? • Lightweight Directory Access Protocol • Standard protocol for reading from and writing to directories • Common language that LDAP clients and servers use to communicate with each other • Accesses directory information usually organized in a tree-like structure
What are the Benefits? • Hierarchical and specialized Database • Scalable, Flexible, Extensible • Efficient Means of Organizing/Retrieving Information • High Query (Read) Performance • Poor Update (Write) Performance • LDAP should eventually make it possible for any application running on virtually any computer platform to obtain directory information, such as email addresses and public keys.
Dn: uid=jsmith,ou=Tools,c=US,dc=oracle,dc=com LDAP Distinguished Names dc=oracle dc=com c=US c=FRA ou=HRMS ou=HRMS ou=Tools uid=jsmith
Directory Interface: Overview
PeopleSoft Database Directory What is Directory Interface? Directory Interface
Features and Benefits • Flexible • Compliant w/any LDAPv3-Compliant Directory Server • Supports flat and hierarchical schemas • Real-time or batch updates to map data • Effective-dated • Centralized Information • Eliminate managing data in multiple locations • Enable single sign-on to enterprise applications • Audit data integrity b/w HCM and Directory Server • Lower Cost, Standards-based Security • Control access to PeopleSoft using LDAP • Reduce security maintenance costs
Directory Interface Components • Mapping Data and Templates • Optional directory schema extensions • Integration Tools • Fields, Records, PeopleCode, Application Messages,Business Interlinks • Audit reports • Signon PeopleCode for Directory Server Authentication.
1. HR Transaction 2. Business Event Triggered 3. App. Msg Published to Queue (if current) App. Message Queue Application Server New Hire Data 4. App. Msg. Subscription Process Invoked HRMS to Directory Maps 5. LDAP Business Interlink writes data to Directory, using Map Defns. Process Flow of an Update <xml> http/html <xml> LDAP
dc=oracle dc=com dc=oracle dc=com c=US c=FRA c=US c=FRA ou=HRMS ou=HRMS ou=Tools ou=HRMS ou=HRMS ou=Tools uid=jsmith uid=jsmith Directory Interface feature • The PDI Features (cont’d): • A “Massive” Directory Tree Re-organization: BEFORE AFTER
Supported LDAP Servers • LDAPv3-compliant Directory Servers: • Novell NDS eDirectory using any Novell supported O/S • Sun ONE Directory Server and higher using any Sun ONE supported O/S • Microsoft Active Directory on Windows 2000 Server
Directory Interface: Delivered Templates
With 8.9, the goal was to adapt the Directory Interface to the new HCM Person Model and to consolidate HCM and Student Admin specific maps into one generic one.
Location Map Department Map Person Map Delivered HR Mappings dc=oracle dc=com c=US c=FRA ou=HRMS ou=HRMS ou=Tools uid=jsmith
5. Create Sign-on PeopleCode • Create Default User • Edit configuration.properties • Write Sign-on PeopleCode
PeopleBooks • Security > Incorporating LDAP Directory Services • PeopleSoft Enterprise Components for PeopleSoft Enterprise HRMS and Campus Solutions 8.9 PeopleBook> Using PeopleSoft Directory Interface
Q & Q U E S T I O N S A N S W E R S A
Hank Kehlbeck Senior Product Manager, HCM Strategy hank.kehlbeck@oracle.com 240.398.8528