SHAREPOINT 2013 FOUNDATION
Delivering the Plexus Customer Portal Globally
Tim Reuning – IT Customer Facing Solution Manager
AGENDA
Who is Plexus?
What problem were we trying to solve?
What were the solution requirements?
High level approach
Lessons Learned
OK, Now show me what it looks like!
2
PLEXUS GLOBAL LOCATIONS
THE PROBLEM(S)
Multiple access methods for customers to retrieve reports and collaborate with us (Not the image we want to present to our customers)
Technology platforms to support those access methods were legacy environments and a security risk to Plexus
No governance to clean up old user accounts or content
Provisioning time to deliver one or more legacy access methods was not lean – taking anywhere from 1-3 weeks
5
REQUIREMENTS
One place for our customers to run reports, access their document repository and collaborate
Must use SharePoint 2013 Foundation Kerberos authentication end to end – so we know what customer
is running what report This required us to use Citrix XenApp as our “gateway” into our SharePoint
portal Because Citrix provided external users access to our network, we needed to
secure only those resources they needed, and not allow access to things they shouldn’t
Must integrate SSRS with SP2013 and secure reports not only to the customer company, but also down to the specific user in the company
6
HIGH LEVEL APPROACH
Created a single site to store the reports, but had 4 libraries Standard report library (everyone has access to content here) Enhanced report library (only some customers need these) Custom report library (custom built reports are stored here) Admin content library
Each customer has its own individual site Created custom code to present the list of appropriate reports
based on AD credentials and library
7
LESSONS LEARNED
End product very intuitive and easy to use Security evaluation and deployment due to Citrix caused delays Multiple library model for displaying content exactly what we
needed. Works very well Legacy reports couldn’t be deleted due to data retention
requirements Access to legacy open issues list (OIL) in SP 2007 through a 2013
web part is functional but detracts from the cleaner SP2013 “look and feel”
8
SHOW US WHAT IT LOOKS LIKE, ALREADY!
9
EXAMPLES
11
12
13