This document discusses a case study of a SharePoint 2013 internet site implementation for Roadrunner Transportation Systems. It describes the business challenges of an aging ASP.NET site and outlines the solution of building 30 line of business apps and administrative tools using the SharePoint farm solutions model. Key aspects of the technical architecture including authentication and data storage are also summarized. The project was successful, increasing key metrics like page views and decreasing the exit percentage according to Google Analytics.
2. 2014
Who is Michael Blumenthal?
• Sr. Solution Architect
• CSPUG Co-Leader
• 19 years in IT Consulting
• 11 years of SharePoint
• Team member on this project
8. 2014
The Challenge:
Aging ASP.Net site
30+ Subsidiary Sites
500+ Line of business tools
Small Internal developer staff
AS400 integration
User Management
Older VB.NET code base
12. 2014
Solution: Development
What We Saw
• 30+ Subsidiary Sites
• 250+ Pages
• 100+ Forms
• 16 Login Methods
• 32 Reports
• 63 Tools
What We Built
• 30 Line of Business Apps
• 15 Admin Apps
• 8 SSRS Reports
• 7 Web Services
• 6 Service Segments Pages
• 16+ Company Sites
10/23/2014 12
21. 2014
Roadmap
The business challenge
The solution
Technical Architecture & key components
Team
Measures of success
22. SP Arch Data Arch SP Devs Tester
2014
The A-Team
Account
Exec
Practice
Lead
Project
Manager
Sr. UX
Designer
UX
Designer
• Client: 2 .Net developers, 1 Team Lead, 1 manager, 1 CIO , 1 Dir of Marketing
23. 2014
Solution: Project Management
2x Weekly status
meetings
PSC Client Extranet
Shared Team Notes
• Every Meeting
• Every App
Working Out Loud
24. 2014
Measures of success
• 700 Bills Of Lading/day
• Increased hits, decreased exits
Google Analytics 3 mo Before 3 mo After
Page Views 3,393,986 5,270,783
Unique Page Views 2,609,161 3,606,197
Average Time on Page 1m:51s 1m:21s
% Exit 27.92% 20.79%
25. 2014
Summary
The business challenge
The solution
Technical Architecture & key components
Team
Measures of success
65. Thank you for your time today.
2014
Questions
• Michael Blumenthal
SharePoint Architect
PSC Group, LLC
• MBlumenthal@psclistens.com
• psclistens.com
• www.cspug.org
• Blog.blumenthalit.com
• Twitter: @MichaelBL
• SPYam & MWC Yam
Editor's Notes
Michael Blumenthal
mblumenthal@psclistens.com
Devs?
Admins?
Using sp2013 for internet site?
Public Facing Website on SharePoint?
Truckload, Less-Than-Truckload, Intermodal
2500+ Employees, 15,000+ Contractors
30 Different Acquisitions
Website only talked about one line of business
Existing VB.NET codebase needed to be rewritten due to changes in data access – now a central db.
We wore many hats:
Gather Requirements
Business Process Consulting
Technology Consulting
Management Consulting
We helped the business understand what they needed to communicate and accomplish.
Over 500 pieces of content
Many overlaps
4 total masterpages. 1 for the main site, 1 for admin and 1 for search, (these are technically the same with some minor tweaks). Then 1 for the companies sub sites, (this one was completely different)
and page layouts...
SharePoint 2013 for Internet
Web Part Development
Solution Packages
Telerik
Twitter Bootstrap
SQL 2012 / Custom Database
No more Internet license costs vs 2010
Development of Web Parts in parallel with site structure, branding, navigation
Putting each app in its own solution package rather than one giant solution package made maintenance, upgrades easy
Use of Telerik controls ASP.NET Ajax Controls
(details later in the deck) Integrating OOTB FBA user management model with a rich user model
(details later in the deck) Use of a custom SQL database because this is highly relational Line of Business data.
SQL DB vs. Lists
Decided to go with server side development. Made decision in June 2013.
Initially wanted to go App Model
Tried of couple of process / Took 3-4 time as long
App Model is maturing / But Still Not ready Yet
Back-End is SQL instead of using Lists
- Integrate with AS/400
Pre-existing web services needed to be maintained.
Active/Passive SQL Cluster had two SQL Instances, one for SP, one for the Roadrunner LOB data.
No Fault tolerance / Disaster Recovery in the system that we replaced. New system uses a fault tolerant design.
LB
3 WFE
2 App
1 SQL Cluster
2 instances: SP, RRC DB
Stage, dev: reduced farm members