granjas sharepoint server para escenarios … service office web application services . ... planning...
Post on 16-Jul-2018
226 Views
Preview:
TRANSCRIPT
Granjas Sharepoint Server para Escenarios Empresariales
sp@danysoft.com
Sigue descubriendo 8º Encuentro Danysoft en Microsoft
Visual Studio | SQL Server | Sharepoint
3 salas | Madrid 24 Mayo 2011
Agenda
Planificación
Topologías Lógicas y Físicas
Escalabilidad y Rendimiento
Seguridad
Servicios Sharepoint
Gobierno
Continuidad de Servicios/Operaciones
Importance of Planning the Logical Architecture
SharePoint 2010 is designed to map against complex
business requirements and processes
It broadly maps to six business workloads: Sites
Communities or social computing
Content management
Search
Insights or business intelligence
Composites
Organizing Your Project
Structure requirements information: – Categorize functionality:
• Functional
• Nonfunctional
– Identify exceptions
Pool common requirements: – Identify commonality
– Minimize duplication
Validate information: – Ensure customer acceptance
– Test against business processes
Functional Planning
Functional planning should include: Business function
Administrative functions
Authentication and authorization
Legal or regulatory audit requirements
Data management
Reporting requirements
Planning for Nonfunctional Requirements
Nonfunctional planning should include: Performance
Capacity
Scalability
Availability
Security
Manageability
Interoperability
Business continuity
Logical Architecture
The logical architecture documents the nonphysical
structure of a solution, designed to fulfill business
requirements
It should: – Map to logical requirements rather than technologies or features
– Reflect all business functionality necessary to deliver the solution
– Be recognizable to nontechnical business users
– Map to integral solution architecture
SharePoint 2010 Logical Architecture Components
Server farms
Service applications
Application pools
Web applications
Zones
Content databases
Site collections
Sites
Lists and libraries
Items
SharePoint 2010
Managed Metadata Service Search Service
State Service User Profile Service Secure Store Service
Access Services Excel Services PerformancePoint Services
PowerPoint Service Visio Graphics Service Web Analytics
Word Automation Services Additional or third-party
services
Service Application Architecture
SharePoint Foundation 2010
Business Connectivity Services Usage and Health Data
Collection Service
Microsoft SharePoint
Foundation Subscription
Settings Service Office Web Application
Services
Server configuration offers ability to scale up
Scalability of SharePoint 2010
Farm topology offers ability to scale out
Selecting a Farm Topology
Small farm
Two or three tiers
Medium farm
Three tiers
Large farm
Three tiers
Topology for Enterprise Service Farms
Web App 1
Farm A
Web App 2 Web App 3
Farm B
Service Apps
Web App 4
Farm C
Business Group2
SharePoint Web Services
Default group
Business Group1
MMS
MMS UPS
XLS
BCS
SEARCH BCS STORE
AXS
Sharepoint Performance
Latency
The duration between the time a user initiates an action and the time the last byte is transmitted to the client
Throughput
The number of concurrent requests that a server or server farm can process
Data scale
The content size and data corpus that the system can host
Reliability
A measurement of the ability of the system to meet the targets set for the latency and throughput over time
Principles of Capacity Planning
Domain controller placement
WAN capacity
Capacity considerations for SQL Server
Performance of Web Front End Servers
• Renders Web content for client browser
• May perform application server functions in small farms
• Processor and memory are key hardware considerations
• Consider multiple load-balanced WFE servers to increase
performance
Performance of Application Servers
• Different service applications generate different load
requirements
• Typically, application servers have high CPU and RAM
• Consider dedicated servers or even multiple servers for key
service applications
• Some service applications may also have increased impact
on WFE servers
Performance of Search Servers • Two search server functions
– Crawl
– Query
• Crawl role has high processor, but moderate memory
requirements
• Query role has high processor and memory requirements
• High impact on database servers
Performance of Database Servers
• High processor and memory requirements
• High disk I/O requirements
• Consider disk storage type and profile
– DAS
– SAN
– NAS
– RAID configuration
• Consider multiple computers running SQL Server for
dedicated databases
Planning for Remote BLOB Storage for SharePoint 2010
BLOBs include:
– Images
– Audio files
– Video files
– Other binary file types
Default storage is content databases
Remote storage is available
Physical Design in a Business Context
• Existing security requirements or policies
• Existing authentication requirements
• Firewall policies
• Current network load and available bandwidth
• Database server administration and support
Additional Topology Considerations
• Network location
– Internal network
– Perimeter network
• Antivirus
• High availability
– WFE servers
– Application servers
– Database servers
• Service accounts are typically domain
accounts
• Permission levels group individual
permissions to simplify setting security
• Site collection and site permissions control user access
• Security groups can be SharePoint, Active
Directory, or local groups
• Permission policies centrally configure and manage permissions
• SSL encryption is recommended between the
client and the WFE server
Security Architecture in SharePoint 2010
Authentication Topologies for Multiple Farms
Au
then
tica
tio
n r
equ
est
Red
irec
t to
par
tner
STS
Secu
rity
to
ken
Co
oki
e
Security token request
Trust
Local STS
Partner STS
Authentication Method A
Authentication Method B
Authentication = Windows http://internal/page.apsx
Authentication = Form-based https://partner.com/page.aspx
Multi-Mode Authentication
SharePoint farm
SharePoint Web application
SharePoint sites (path)
SharePoint site collection
SharePoint Site Collection
Mapping Business Requirements to Social Computing Functionality
Tag
Business Requirements
User Profile Synchronization
Social Computing Functionality
Consuming Managed Metadata Across Farms
• Enterprise scalability
• One-way or two-way publishing
• Multiple farms publishing or consuming
Intranet farm Specialized department farm
Business Connectivity Services
• Import data from external sources
• Augment existing data
• Export not supported
Enterprise Search Architecture
Crawl database
Property database
Index server
Query server
WFE server
Index propagation
Business Reasons for FAST Search
Why choose FAST search?
• The index can increase to 500 million items
• You can sort search results by any property
• You can provide search relevancy
• It supports two-way synonyms
• It has visual enhancements
• It has grammatical enhancements
People Search is still provided by SharePoint search
Plan Excel Services architecture: – Excel Calculation Services
– Excel Web Services
– Excel Web Access
Identify the need for Excel Services: – Workbooks shared through browsers
– BI dashboards
– Reuse of business logic
– Report building
WFE
Excel Web Services
Excel Web Access
Planning for Excel Services
Application Server
Excel Calculation
Services
Database Server
Excel data
Planning Excel Services Security
Plan for access components – Trusted file locations
– Trusted data providers
– Trusted data connection libraries
Plan authentication – Integrated Windows authentication
– Secure Store Service authentication
– None (unattended service account)
Plan communication among servers
Planning for PerformancePoint Services
PerformancePoint Services components offer tools to
create monitoring, reporting, and analysis
visualization:
When to use PerformancePoint Services: – IT provisioning BI functionality
– Self-service provisioning
– Establishing company-wide objectives and responsibilities
Planning for PowerPivot
Architecture components for PowerPivot for
SharePoint
Environment planning: – Storage
– Networking
– Processor and memory
When to use PowerPivot for SharePoint: – Centralized access and management
– Analysis services
– Server-side processing
Planning PerformancePoint Services Security
Authentication – Per-user identity
– Unattended user account
– Custom data
Access components: – Trusted file locations
– Trusted data connection libraries
– Trusted lists
Roles and permissions: – Farm Administrator
– Site Collection Administrator
– Site Administrator or List and Document Library Contributor
The Importance of Planning Governance Prevent portal, team site, and content sprawl
Ensure that content quality is maintained during its life cycle
Provide a consistently high-quality user experience
Establish clear decision-making authority and escalation procedures
Ensure that the implementation strategy correctly maps to business requirements
Ensure that content is secured and stored to comply with guidelines for records retention
What Needs to Be Governed?
Content?
Profiles?
Policy?
Workflow?
Domain?
People?
Servers? Metadata?
Code?
Infrastructure?
Guiding Principles for a Governance Plan
Enterprise Sites
Business Area Sites
Department and Team Sites
Project Team, Meeting, and Document Workspace Sites
Personal My Sites
• Controlled
• Tightly governed
• Site owner accountable
• Ad hoc
• Loosely governed
• Shared accountability
• Permanent
• Knowledge management
• Applications
• Permanent
• Knowledge management
• Information sharing
• Temporary
• Collaborative
• Permanent
• Personal information
• Public/private views
One Size Does Not Fit All
Building a Governance Committee Executive stakeholders
Business division leaders
Software development leaders
Financial stakeholders
Information workers
Compliance officers
Trainers
IT leaders
Information architects or taxonomists
Governance of Sandboxed Solutions
When should a farm administrator block or unblock a sandboxed solution?
When can you transfer a sandboxed solution to the production environment as a fully trusted solution?
Who will you allow to deploy sandboxed solutions?
Will you dedicate a separate server to running sandboxed solutions?
Business Continuity Management Features in SharePoint Server 2010
User-controlled capabilities – Recycle Bin
– Versioning
– Records Center
Administrator-controlled capabilities – Availability
– Disaster recovery
– Backup and restore
Availability and Disaster Recovery
Availability – Degree to which SharePoint Server 2010 environment is available
and fully operational
– Expressed in uptime percentages—for example, 99.999 percent
Disaster recovery – Ability to recover from a situation in which a computer running
SharePoint Server 2010 becomes unavailable
– Hot standby—recover in seconds or minutes
– Warm standby—recover in minutes or hours
– Cold standby—recover in hours or days
User requests Web servers
Application servers
Database servers (clustered or mirrored)
SQL Server failover clustering SQL Server high-availability mirroring
Database Availability
Resumen
Escenarios de Granjas Sharepoint en
medianos/grandes contextos
Aproximación a las Topologías recomendadas
Revisión de Conceptos Aplicables
Continuidad de Servicios
•Te ofrecemos la gama más completa de utilidades de terceros que complementan VSTS
Utilidades
•Te asesoramos en la adquisición, renovación y consolidación de licencias software.
Licencias Software
•Editamos libros especialmente creados por y para desarrolladores.
Libros
• Formación a medida para equipos de desarrollo
Formación
• Consultorías para la puesta en marcha de tecnologías
Consultoría
• Presentaciones técnicas para ayudar a la toma de decisiones
Presentaciones
GRACIAS
Para mas información contacte en el coffee break o al finalizar el evento con el equipo Danysoft,
en el 902 123146 | info@danysoft.com
top related