1. Build Custom SharePoint Solutions with FrontPage 2003 & Windows SharePoint Services Deployment Strategies 최승현 대리 (shchoi@microsoft.com) 한국마이크로소프트

2. Agenda  FrontPage 2003 and SharePoint  Demo: Building custom SharePoint solutions  Partner Opportunities  Q&A

3. FrontPage 2003 More Power. Better Results. Key Benefit POWER to easily develop a sophisticated Web site. Key Feature Area Advancements Designing Design exactly the site you want Coding Code efficiently, faster Extending Buil d live XML data-driven & SharePoint solutions

4. Build Custom SharePoint Solutions with FrontPage 2003  Going beyond the FP2002 and STS v1 story  High quality page design  Working with Web Part pages  Bringing external data into SharePoint  Extending Windows SharePoint Services and SharePoint Portal Server

5. FrontPage 2003 High quality page design  Professional design tools make customized SharePoint sites look great  New layout tables and cell formatting for high quality page layout and design  New dynamic web templates for a consistent look across pages  More, professional looking themes  New integration with image editing tools

6. FrontPage 2003 Working with Web Part Pages  Doing more with Web Parts  Create custom Web Part pages  Use Web Part connections to build solutions  Add/edit/configure Web Part zones  Save to site catalog and Web Packages for reusing customized Web Parts and solutions

7. FrontPage 2003 Extending SharePoint web sites  Expand the scope of SharePoint sites  XSLT Data view Web Part for creating highly formatted views on XML data  Conditional Formatting for rich presentation of data  Connected Data Views for detailed solution pages (eg. master-details views)  Support any customer-defined schema  Data Source Catalog for accessing variety of data sources, including Office XML files, databases, and XML Web services.

8. Build Custom SharePoint Solutions Demo Enterprise Intranet Solution: Contoso Pharmaceuticals Easily build a custom SharePoint solution

9. Partner Opportunities What you can do with FrontPage 2003  Build custom solutions on WSS and SPS  Enable new scenarios with external data and SharePoint  Create pre-built, pre-configured Data View Web Parts  Build and deploy Web Packages

10. Build Custom SharePoint Solutions Questions?

11. Agenda  System overview  Single-machine deployments  Web farm deployments  Intranet deployment  ISP hosting features  Q&A

12. STS V1 Topology Web front end Rich clients Browser SQL Backend RPCs HTML Web Structure from IIS Docs stored here ACLS on files Authorization, Lists Schema, Pointers to Documents Issues: Cannot scale beyond IIS limits No transactions for updates

13. Enterprise Deployment Challenge  Flexible, scalable deployment options  Protect data and performance  No single point of failure  Ease of management

14. WSS V2 Scale-out Topology Stateless Web Server Rich clients Browser SQL Content DB Config DB Load Balancer, Hardware or software SQL stores all docs, lists, user info, site structure, config data. Add SQL servers for Content partitioning, Failover, Redundancy Low-cost blades or web servers Add servers as page hits increase SOAP HTML SQL Content DB E-MAIL Server 50,000 team sites in web farm using this architecture

15. SharePoint “ V2 ” Architecture Benefits  Flexible deployment options  Single server – small to medium orgs  Small farm – large orgs  Large farm – largest orgs  Portal server provides multiple farm integration  Highly scalable, highly available architecture  Improved management  Web based UI manages app across all servers .Net OM for extensibility  Command line scripting

16. Enterprise Scale & Reliability  Improved performance and scale up .NET Framework, SQL Server 2000  Three tier application architecture  Availability – strive for continuous uptime  Stable platform, no single points of failure  Multiple load-balanced web servers, so no single web box outage stops service  All data in SQL  Updates are transacted, and stable  SQL server & SAN technologies allow backup while live  Config data centralized, web farm update automated  Beta2 servers with 6,000 hosted sites: zero failures over 4 months, 100% uptime.

17. Deployment Modes 1 Single Box  All WSS components on a single box.  Best for work group or business unit.  For MSDE, use one-click setup  Easiest setup – accept the EULA and say OK.  Scriptable installation  Do configurations after setup completes WSS App Code IIS & ASP.Net Content DB Config DB MSDE

18. Deployment Modes 2: Corporate Intranet Scale-Out Environment DB  Web farm configuration  One or more Web servers  One or more SQL servers.  Load balancer, E-mail server  HTML transformation on separate server  Max 10,000 sites /SQL server  50,000 sites/webfarm tested  Management considerations:  Self-Service Site Creation  Use confirmation  Storage quotas start with 50mb - 100mb per site  Add anti-virus software to Web boxes Web More Webs… DB Load Balancing E-mail HTML Xforms

19. Corporate Extranet Hosting Content DB Internal VS Content DB External (internet) Access Corporate Access External VS Corporate Firewall Web Servers  Same plan as intranet, with 2 virtual servers  One VS accessible via corporate net.  One VS accessible from internet, accesses same content  Management considerations  All users must be in corporate domain – even external users  Configure IIS separately for each VS as needed  Allow corporate users to manage content, site structure, invite domain users  SSC not recommended

20. Demo: Sharing Content Between 2 V-Servers

21. ISP Provisioning Options  AD Account Creation Mode  WSS creates user accounts in AD  Setup-time option for ISPs, or extranet when IT doesn ’ t want external users in domain.  Requires separate domain controller.  Key features for managing: User quotas, invited users get emails with login & pw, WSS manages pw changes.  Command line required for site creation  Host-Header Mode  Create vanity-named sites.  Each new host-header-named site must be added to DNS.  Mainly an ISP solution.  Setup-time option, & command line required for site creation

22. Deployment Decision Points  Small orgs (hundreds of users)  Single machine  Easily set up & managed  Limited to 2gb MSDE store, single IIS server  Medium org (to 10,000 users)  Separate SQL server  Availability, data protection, and IT standards  Throughput generally not an issue  Large org (10s of thousands)  Throughput will require small farm (3-5 servers)  Availability, data protection, and IT standards may play a role  Largest orgs (100s of thousands)  Throughput will require large farm (10-20 servers), or multiple farms  Data protection, and IT standards may play a role  Custom web parts can significantly change CPU/memory requirements

23. Partner Opportunities  Single-server solutions  Rapid deployment using WSS setup  Extensible platform for single-server deployments  Full implementation, limited by MSDE, single IIS server  Web farm applications  Deployment fully automatable  Web parts extend the app  E-mail inserts, and doc library events  Web farm reporting tools needed: who, what, how many  Hosting  Same elements as web farm  Built-in quotas can be linked to billing/account management  Web parts & applications, eg: shopping cart tied to an order list for the customer, based on an inventory list.

24. Summary  Flexible architecture for variety of environments  Extensible platform for applications, with full OM & scripting support  Built-in tools: quotas, SSC, centralized web farm management  Highly available & scalable, from one server to ISP scale

25. Q&A