PSC Case study: SP2013 Public Facing Internet Site - Roadrunner Transportation Systems
20 de May de 2014•0 recomendaciones
1 recomendaciones
Sé el primero en que te guste
ver más
•541 vistas
vistas
Total de vistas
0
En Slideshare
0
De embebidos
0
Número de embebidos
0
Descargar para leer sin conexión
Denunciar
Internet
Tecnología
This case study gives a behind the scenes look at what it took the team at PSC Group, LLC to build the new www.rrts.com website for Roadrunner Transportation Systems.
2014
Who are these guys?
Michael Blumenthal
• Sr. Solution Architect
• CSPUG Co-Leader
• 19 years in IT Consulting
• 11 years of SharePoint
• Team member on this project
Malcolm Eaton
• Microsoft Practice Leader
• 14 years of SharePoint
• Project Leader on this project
2014
The Challenges
Aging ASP.Net site
Consolidate 30+ Subsidiary Sites
Consolidate 500+ Line of business apps
Small Internal developer staff
AS400 integration
User Management
VB.NET code base
2014
What Did We See?
• 32 Subsidiary Sites
• 251 Pages
• 49 Forms
• 16 Login Methods
• 32 Reports
• 63 Tools
• 57 Forms
5/21/2014 7
2014
What Did We Build?
• 15 Admin Apps
• 30 Line of Business Apps
• 8 SSRS Reports
• 7 Web Services
• 8 Service Segments Pages
• 16 Company Sites
5/21/2014 8
2014
The A-Team
• Client: 2 .Net developers, 1 Team Lead, 1 manager, 1 CIO , 1 Dir of Marketing
Account
Exec
Practice
Lead
Project
Manager
Sr. UX
Designer
UX
Designer
SP Arch Data Arch SP Devs Tester
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%
2014
Summary
• Plan UX Design First
• Determine Development Strategy
• Incorporate Pre-Built Tools and Frameworks
• Store Relational Data in a Database
• Test, Test, Test
2014
Come to our both for a chance to win!
• ASUS Transformer Book
T100TA-C1-GR Touchscreen
2 in 1
• Sells for $399!
• 10.1-inch HD touchscreen
• Up to 11 hours battery life
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
Thank you for your time today.
• Malcolm Eaton
Practice Lead
PSC Group, LLC
• MEaton@psclistens.com
• psclistens.com
• SPYam & MWC Yam
Notas del editor
Devs?Admins?Using sp2013 for internet site?Public Facing Website on SharePoint?
We wore many hats:Gather RequirementsBusiness Process ConsultingTechnology ConsultingManagement ConsultingWe helped the business understand what they needed to communicate and accomplish.
Over 504 pieces of content
PSC Client Portal (our SP2013 extranet) was heavily used.
No more Internet license costs vs 2010Development of Web Parts in parallel with site structure, branding, navigationPutting each app in its own solution package rather than one giant solution package made maintenance, upgrades easyUse 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 ModelTried of couple of process / Took 3-4 time as longApp Model is maturing / But Still Not ready Yet
Back-End is SQL instead of using Lists- Integrate with AS/400Pre-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.LB3 WFE2 App1 SQL Cluster2 instances: SP, RRC DBStage, dev: reduced farm members