AMD.COM Monthly Stats* 15.3m unique visitors 21.7m visits 72m page views 7.3m downloads ~10k...
-
Upload
emilia-allenson -
Category
Documents
-
view
217 -
download
1
Transcript of AMD.COM Monthly Stats* 15.3m unique visitors 21.7m visits 72m page views 7.3m downloads ~10k...
AMD: 13 Million Users. 54 Million page views. AMD.com on SharePoint 2013. Done.Katie Bowman – Web Infrastructure Manager, Marketing Gil Canare – Digital Marketing ManagerMichael Mielke – IT Architecture ManagerBruce Weatherford – Sr. Member of Technical StaffAMD
SPC353
What We’ll Cover Background Features Infrastructure Scalability
Pioneers technology that frees people to push the limits of what is possible
AMD.COMMonthly Stats* 15.3m unique
visitors 21.7m visits 72m page views 7.3m downloads ~10k total pages 13 languages
19%7%
48%
12%13%
North America LATAMEMEA ChinaAPJ
* Source: Adobe Analytics as of Dec 2013
Why Migrate From SharePoint 2007SupportSharePoint 2007 no longer under mainstream support
Limitations Feature set not competitive with current systems
Publishing Content deployment not consistent and taking over an hour
CustomizationCustomizations in system causing support issues
Why SharePoint 2013Cost Significantly lower than investment required for other systems
Team Knowledge and ExperienceDeep expertise on both Marketing and IT teams
Feature List Closely matched our needs and requirements
RelationshipClose existing working relationship with Microsoft
How We Did It Build cross-functional agreement AMD Marketing and IT joint decisions and working teams
Try before you buyTwo weeks at Microsoft Technology Center to review features and capabilities and build proof of concept
Review assumptions and past decisions Examined approach to customizations and content deployment
Developed custom migration toolMigrate select content out of SharePoint 2007 and into SharePoint 2013
Features
What We Used and What We Didn’t Used Managed Navigation
Search Content By Search Web PartVariations
Unused Content Deployment Cross-Site Publishing & Catalogs Design Manager Device Channels SharePoint Apps
Used Feature: Managed Navigation Successes Challenges
Friendly URLs
Separates end-user information architecture from administrative organization
Allows for easy site restructuring
Improved SEO optimization
Does not work OOTB with breadcrumb controlCreated custom control
Displays root site in global navigation
Discovered bug with feature (Fixed by private Microsoft fix in 7 weeks, included in the October 2013 CU)
Used Feature: Search Successes Challenges
Superior search accuracy over SharePoint 2007
Site admins have more control over search configuration than previous versions
Query Rules allow site administrator configuration of promoted results
Wanted more flexibility than OOTB search center provided
Does not support friendly URLs in search navigation (Will be fixed in April 2014 CU *)
Displays draft pages in search navigation, but gives errors when clicked (Will be fixed in April 2014 CU *)
Not enough control over query suggestions
* Source: Microsoft support case
Used Feature: Content by SearchSuccesses Challenges
Replaced most Content Query Web Parts
Queries powerful and flexibleQuery other site collectionsQuery any property
More robust, functional display templates
HUGE TIME SAVER!
Display Templates not well documented at build time
Editing managed properties requires central admin rights
Thorough browser and OS testing required for Display Templates
Used Feature: Variations
SUCCESSES CHALLENGES
Faster and more stable than SharePoint 2007
Propagation settings at variation root
Simpler, selective propagation between variations
Does not support automatic and selective variation simultaneously
Selective acceptance and publishing in target variation
Successes Challenges
Faster and more stable than SharePoint 2007
Simpler, selective propagation to individual variations
Selective acceptance and publishing in target variation
Improved manageability of regional sites and their sizes
Propagation settings at variation root does not allow for different settings at the list and library level
Manual steps required when moving content databases between prod and non-prod environments
Re-usable content not displayed correctly in the Turkish (tr-tr) locale (Will be fixed in April 2014 CU *)
* Source: Microsoft support case
Used Feature: Variations
Unused Feature: Cross-Site Publishing SUCCESSES CHALLENGES
Faster and more stable than SharePoint 2007
Propagation settings at variation root
Simpler, selective propagation between variations
Does not support automatic and selective variation simultaneously
Selective acceptance and publishing in target variation
Challenges Outcome
No preview of unpublished content
Cannot connect to a catalog created in variation
Moving content database between environments requires catalog reconnection and reconfiguration
Did not fit our business processLittle to no multi-use content
Use search queries where needed
Will reevaluate as business needs change
Unused Feature: Catalogs
SUCCESSES CHALLENGES
Faster and more stable than SharePoint 2007
Propagation settings at variation root
Simpler, selective propagation between variations
Does not support automatic and selective variation simultaneously
Selective acceptance and publishing in target variation
Challenges Outcome
Requires at least one managed metadata column to connect
Limited variation support
Cannot have multiple connections to a single catalog
Requires use of cross-site publishing to realize full benefits
Use lists and search queries
Unused Feature: Design Manager
SUCCESSES CHALLENGES
Faster and more stable than SharePoint 2007
Propagation settings at variation root
Simpler, selective propagation between variations
Does not support automatic and selective variation simultaneously
Selective acceptance and publishing in target variation
Challenges Outcome
Design packages include all publishing site columns, content types, page layouts, master pagesCreates problems when uninstalling design package
Automatically applies master page from installed design package
Master page code inserted in page layouts can complicate master page updates
Needs further refinement
Used SharePoint Designer
Unused Feature: Device Channels
SUCCESSES CHALLENGES
Faster and more stable than SharePoint 2007
Propagation settings at variation root
Simpler, selective propagation between variations
Does not support automatic and selective variation simultaneously
Selective acceptance and publishing in target variation
Challenges Outcome
Large, anonymous user base and specific use case does not require custom device channel(s)
User agent strings conflict with Akamai content distribution network rendering
Did not fit our business process
Using responsive web
Infrastructure
Design Approach Referenced Product Line Architecture with
MCS Modified intranet guidance and best practices for external site
requirements Captured requirements and decisions with design documents
Service description Functional specification Build guide Functional testing plan Performance testing plan
Server Configuration SharePoint: 4 Cores, 16GB RAM, Windows Server 2012 Standard SQL: 8 Cores, 32GB RAM, Windows Server 2008 R2 Enterprise
Infrastructure Comparison 2007 2013
Content Deployment Yes No
No. of Farms 6 3
Customizations 18 2
Type of Servers Physical Virtual
Server Tiers 3 4
SharePoint Install and Configuration Manual Automatic
Network Configuration 1 DMZ 4 Transaction Zones
Authentication Internal domain controllersRead-only domain controllers (RODC) in DMZ
SQL ConfigurationSQL Clustering (Active/Passive) AlwaysOn Availability
Content DeploymentLAN DMZ Internet
SharePoint 2007Authoring Farm
SharePoint 2007Production Farm
Customer
AMDContentAuthor
Corporate Domain DMZ Domain
SharePoint 2007Duplicate LAN and DMZ farms (Dev, QA, Prod)Authoring in LAN and content deployed to DMZ
SharePoint 2013Single set of farms (Dev, QA, Prod)Authoring directly in DMZ
LAN DMZ Internet
SharePoint 2013Production Farm
CustomerAMDContentAuthor
Corporate DomainDMZ Domain
Publishing Site Configuration Implemented as 3 web applications
Used AAMs for anonymous and authoring access (ex. support.amd.com and support-auth.amd.com)
Single site collection for each web application
Limited customizations Implemented 2 farm solutions (Literal translations management and
User input form) vs. 18 previously SharePoint Apps not recommended for anonymous sites
Server Tiers and Roles
4 tiers of servers
Front end services Search Back end services Databases
Search Tier – 2 Servers- Admin- Index (one partition, two replicas)- Query Processing
Back End Services Tier – 2 Servers- Search Crawl- Search Content Processing- Analytics- Central Administration- User Profile Synchronization
- User Profile Service- Workflow Management- Distributed Cache- BDC
LAN DMZ Transaction Zones Internet
Customer
AMDContentAuthor
SharePoint Administrator
Database Tier- 3 Availability Groups- Synchronous Mirroring- Windows Server Failover Clustering
Web/Front End Services Tier – 4 Servers- MMS- Translation- Secure Store- State Service
Automated Install And Configuration Documented configuration in detail Automated almost all of our build process
using AutoSPInstaller from Codeplex Install pre-requisites and SharePoint – in parallel and remote mode Install SharePoint Create and configure farm Create and configure web applications Install and configure Services
Used AutoSPInstaller GUI from Codeplex to configure AutoSPInstaller XML file *
* Be careful with version compatibility issues
Post-Installation PowerShell ScriptsScripts
Add farm administrators group accounts
De-provision and reprovision distributed cache server
Recreate usage and health application
Add web applications policies for admin group
Delete default IIS and application pools
Disable certificate revocation list check!
Disable web applications online presence settings
Enable continuous crawl on key content sources
Reduce timing of variation timer jobs
Secure Network Configuration Multiple
Transactions Zones / VLANS
Limited open protocols and ports between zones
Leveraged Read-only Domain Controllers
LAN DMZ Transaction Zones Internet
SharePoint 2013Production Farm
(Corporate Domain)
Customers
AMDContentAuthor
AkamaiCaching and Accleration
Applications Servers
Corporate Domain
Database Servers
SQL Availability Groups(Corporate Domain)
Internet Infrastructure Transaction Zone
DNSSMTPRODC RODC
Load Balancer
Load Balancer
and Custom Redirect
RedirectServers
Configuring Read-Only Domain Controllers Identify Firewall Ports
Add firewall rules to allow connectivity between SharePoint, SQL and RODC 88 (TCP), 135 (TCP), 389 (TCP & UDP), 445 (TCP), 5722 (TCP), 49152-65535
(TCP/Dynamic Ports)
Configure Active Directory Create AD subnets for each subnet where the SharePoint and related SQL
servers reside Create AD site that contains the two DMZ RODC that serve the SharePoint and
related SQL servers Configure the password replication policy (PRP) for the RODC to cache
SharePoint service accounts SQL service account SharePoint and related SQL server machine accounts
Use nltest/dsgetdc:<domain> to confirm servers are using one of the correct RODCs
Minimal documentation on use with SharePoint http://support.microsoft.com/kb/970612 People picker is unable to resolve users in a trusted forest if the only
domain controller SharePoint can access is read-only.
Unable to let SharePoint manage service accounts
Join servers to domain before switching to RODC
May see a temporary warning message when adding users to SharePoint groups “Sorry, we’re having trouble reaching the server”
Read-Only Domain Controllers Lessons
New option for high availability and disaster recovery Recommended by MCS and supported future DR scenario Replaces disaster recovery options such as mirroring and log shipping Uses Windows Server Failover Clustering (WSFC) services and SQL
Server 2012
TechNet Articles Configure SQL Server 2012 AlwaysOn Availability Groups for SharePoint
2013 http://technet.microsoft.com/en-us/library/jj715261.aspx
Supported high availability and disaster recovery options for SharePoint databases (SharePoint 2013) http://technet.microsoft.com/en-us/library/jj841106.aspx
SQL Server AlwaysOn Availability
Database Availability GroupsGroup Databases
Configuration and Service ApplicationIncludes configuration, central administration content, and service application databases (excluding search applications)
Configuration Central
Administration Content
Secure Store Usage
State Managed
Metadata Taxonomy Machine
Translation
Search ApplicationAll search databases
Search Administration Search Analytics Search Crawl Search Link
Content All web content databases excluding Central Administration content
support.amd.com Content www.amd.com Content search.amd.com Content
Database Implementation
3 Availability Groups Across 2 Virtual Servers
Windows Server Failover Clustering (WSFC) cluster
Node 0A Node 0BSQL Sever Instance SQL Sever Instance
Config, CA and Service Apps availability group
Content Databases availability group
Search Application availability group
Secondary Replica
(RO)
Primary Replica(RW)
Secondary Replica
(RO)
Primary Replica(RW)
Secondary Replica
(RO)
Primary Replica(RW)
Listener NameListener PortListener IPSQL Client Alias
Listener NameListener PortListener IPSQL Client Alias
Listener NameListener PortListener IPSQL Client Alias
Achieving Scalability
Benefits Caches content on cache servers worldwide for optimal global
performance Absorbs majority of static page and content traffic Configurable by page type and page with cache/no-cache and
expiration rules Clear the cache when publishing new pages
Lessons learned Significantly reduces server and network load Complicates troubleshooting May cache errors May require manual cache clears to display content Significant investment based on our usage
Akamai Content Distribution Network
SharePoint caching Enabled blob caching for images, JavaScript, and CSS (visa
AutoSPInstaller) Increased object caching setting from 100 to 200 for lists, site settings,
etc. Set output cache to store page output to 5 minutes globally
IIS compression Enabled dynamic and static compression
Caching and Compression
Plan ahead Determine caching and compression strategy Pay attention to page size implications Be familiar with web developer and debugging tools and techniques
Execute load testing Engage a test professional and determine load test strategy Select load test generation tool and load test suite Create load use cases and identify % of total expected load for each
use case Determine % of load coming from each region or country Determine number of concurrent users for each test run – start small Execute load test Use tool to measure page load times from different locations worldwide
Lessons Learned
Next Steps and Lessons Learned
What Next AMD.comComplete www site migration
Shop.AMD.com Re-architect and migrate where-to-buy site
Partner Portal Set-up external secure infrastructure and migrate partner site
Digital Asset ManagementImplement asset browse, search, & upload functionality
Implement asset browse, search, & upload functionality
Lessons LearnedSimplifyAvoiding customizations significantly reduced time to deploy and issues to address
ManageLeveraging business process to manage complexity instead of system
FocusUsing only the features you need not just because they’re available
ExploreRe-examining previous decisions can result in more optimal results
Implement asset browse, search, & upload functionality
MySPCSponsored by
connect. reimagine. transform.
Evaluate sessionson MySPC using yourlaptop or mobile device:myspc.sharepointconference.com
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.