This document discusses using shadow databases to enhance security and scalability for PeopleSoft deployments. It provides examples of federal government and commercial organizations using shadow databases for employee onboarding solutions. Shadow databases allow for logical and physical separation from the main PeopleSoft database, enabling features like independent authentication schemes, application security, and smaller footprints. Benefits include enhanced security, scalability, user experience and independence from the core PeopleSoft system. Integration between shadow and main databases can be achieved through database links, messaging or web services.

2. #OHUG2016
Secure and Scalable PeopleSoft--
Sensitive and High Volume
Deployment Case Studies
Session: 16383
Kirk Chan, VP Business Development, Smart ERP Solutions, Inc.

3. #OHUG2016
Agenda
• Introductions
• Alternate Architectures for Security &
Scalability
• Use Cases:
– Federal Government
– Staffing Industry
• Other Use Cases
• Questions & Answers

4. #OHUG2016
Introduction:
Alternate Architectures
SHADOW DATABASES
A logically and physically
separate PeopleSoft
database can be very
effective to:
• ENHANCE SECURITY
• IMPROVE SCALABILITY

5. #OHUG2016
Benefits of shadow databases
• Independence from PeopleSoft application database
system (HCM/Financials/Campus Solutions)
• Authentication Scheme
• LDAP
• Multi-factor Authentication
• CAPTCHA
• Application PUM independence
• Data Security
• Enhanced User Experience
• Smaller footprint

6. #OHUG2016
Use Cases for Alternate
Architectures
Shadow Databases in LIVE Production Use
• Federal Government Examples
• Commercial Example

7. #OHUG2016
Use Case 1: Federal Government
Organization
SHADOW DATABASE
• Front-end database
houses Automated
Employee Onboarding
Solution (SmartERP)
• Logical and Physical
separation ENHANCES
SECURITY
+50 new-hire forms
Highly sensitive HR info

8. #OHUG2016
Use Case 1: Federal Government Organization
Deployment Architecture
DB
DB
HCM HCM
Internal Network

9. #OHUG2016
Use Case 2: Federal Government
Organization
SHADOW DATABASE
• Front-end database
houses Automated
Employee Onboarding
Solution (SmartERP)
• Logical and Physical
separation ENHANCES
SECURITY &
SCALABILITY
+5,000,000 job
applications
+1,000,000 in one year
E-Verify for all new-hires

10. #OHUG2016
Use Case 2: Federal Government Organization Authentication
Architecture
Welcome Page

11. #OHUG2016
Use Case 3: Commercial
Organization: Staffing Industry
SHADOW DATABASE
• Front-end database
houses Automated
Employee Onboarding
Solution (SmartERP)
• Logical and Physical
separation ENHANCES
SCALABILITY
Shared Service (PeopleSoft & Non-
PeopleSoft)
+10,000
onboards/month
+300,000 onboards/year
+25,000 E-Verify

12. #OHUG2016
Shared
Services
ATS
Front
OfficeHR
Use Case 3: Commercial
Organization in Staffing Industry

13. #OHUG2016
Other Use Cases for Alternate
Architectures
Shadow Databases to address other
requirements
• Version Compatibility, Cloud, etc.

14. #OHUG2016
Other Use Cases for Alternate
Architectures: VERSION
COMPATIBILITY
SHADOW DATABASE
• Front-end database
houses different version
of PeopleTools
• Logical separation
alleviates PeopleSoft
incompatibilities with
organization’s
enterprise environment
(IDM)
PeopleTools 8.54 FLUID
UI features desired
without upgrading to
8.54

15. #OHUG2016
Other Use Cases for Alternate
Architectures: CLOUD enablement
SHADOW DATABASE
• Front-end database
houses separate Cloud-
based/Hosted public
facing interface
• Logical/Physical
separation cloud-
enables on-premise
PeopleSoft application
in a controlled/secure
manner
Provides for Cloud/On-
Premise Onboarding
even for non-PeopleSoft
HR

16. #OHUG2016

17. #OHUG2016

18. #OHUG2016

19. #OHUG2016
Data Integration with Shadow
Database
• Database Links
• Messaging (Integration Broker)
• Web Services

20. #OHUG2016
Summary
• Concept though simple is very powerful
• Shadow databases provide opportunities to
efficiently enhance security/scalability/user
experience/etc.
• Benefits:
• Independence from PeopleSoft application database
• Facilitate authentication schemes (only where needed)
• Application PUM independence
• Data Security
• Enhanced User Experience
• Smaller footprint

21. Questions & Answers
Kirk Chan, kirk.c@smarterp.com