SharePoint 2010 Blended solutions application integration


Published on

The webinar will include several demonstrations and discuss:

• Blended Applications for Public Facing Sites & Corporate Intranets
• SharePoint 2010 API's for Leveraging External Business Application Data
• Working with the Client Object Model (.NET, AJAX/JavaScript & Silverlight)(BDC)
• REST Services
• Strategic Approaches to SharePoint 2010 Integration with ASP.NET
• Best Practices for conversion of legacy ASP.NET applications
• Architectural and Performance Considerations
• Avoiding common pitfalls

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • PAUL
  • DAVE:Introduce this months agenda and outline the hour’s presentation.
  • DAVEExplain the SharePoint vs. ASP.NET Integration ApproachesWhere the existing technology investment liesDrives towards touch pointsWhat Options?
  • DAVE
  • DAVE
  • PAUL:Mention the Integration Options below:High Touch Point IntegrationMedium Touch Point IntegrationLow Touch Point Integration
  • DAVEDemo branded ASP.NET and SharePoint 2010 Solutions separate apps branded same
  • DAVE
  • DAVE
  • DAVEDemo branded ASP.NET and SharePoint 2010 Solutions separate apps branded same
  • PAULDemo branded ASP.NET and SharePoint 2010 Solutions separate apps branded same
  • PAUL
  • PAUL
  • PAUL
  • DAVE
  • PAULIf they need help, we’ve had access to SharePoint 2010 for over a year – we can guide them thru the processMention Downloads, Recording & Email invite to ECM in SharePoint 2010 WebinarExplain SharePoint GamePLAN Q & A - EVERYONE
  • SharePoint 2010 Blended solutions application integration

    1. 1. Blended SharePoint 2010 <br />and .NET Solutions<br />Webinar Series By:<br />
    2. 2. Speakers<br /> Dave Milner<br />Author: ASP.NET SharePoint 2010 Solutions<br />Sr. Architect & Lead Consultant<br />MBA, MCTS, MCSD.NET, MCT, Certified ScrumMaster<br /> Paul Papanek Stork<br />SharePoint MVP & Author <br />Chief Architect & Lead Consultant<br />MBA, MCT, MCSE, MCSD, MCDBA, MCITP, MCPD…<br />
    3. 3. Agenda<br />A sprinkling of demos throughout…<br />Introductions<br />Overview of Blended Solutions<br />Architecture and Performance Considerations<br />Best Practices for Blended Solutions Application Integration<br />Q&A<br />
    4. 4. Overview of Blended Solutions<br />July Webinar Recap: “Business Application Integration using BCS”<br />Integration Approaches<br />SharePoint Centric<br />ASP.NET Centric<br />What Strategic Approach Options Do I Have?<br />High Touch Point Integration<br />Medium Touch Point Integration<br />Low Touch Point Integration<br />How Does the Approach Impact My Choices?<br />
    5. 5. Integration – SharePoint Centric<br />Scope of SharePoint larger than your project<br />Intranet – document management, portals<br />Publishing Portal – external facing large website<br />Existing Investment in SharePoint<br />MOSS 2007 / WSS 3.0 Installs<br />Current Hardware / Software Infrastructure<br />Performance<br />Large # of Concurrent Users > 100 RPS<br />Enterprise Features<br />FAST, PerformancePoint, BI, Managed Metadata, Multi-Tenant, Variations<br />
    6. 6. Integration – ASP.NET Centric<br />Large investment in ASP.NET application<br />Complex ASP.NET applications <br />> 50 pages, Transactional Database Requirements, Many-to-many Table Joins<br />ASP.NET application features are used much more than SharePoint 2010 features<br />SharePoint Foundation Server<br />Performance<br />SharePoint load is smaller < 50 RPS<br />Overall concurrent users are smaller < 75 <br />
    7. 7. Audience Survey<br />What is your primary role as related to SharePoint?<br />Decision Maker, Influencer or Sponsor<br />Admin, Architect or Developer<br />Analyst or End User<br />Consultant<br />
    8. 8. High Touch Point<br />Layouts directory deployment<br />Modify existing application pages to use SharePoint master pages.<br />Remove authentication piece from web.config<br />Other web.config elements will be brought in through ASP.NET directory hierarchy<br />Connection Strings<br />Custom properties<br />Assemblies<br />ASP.NET application is completely contained within SharePoint<br />Built-in output caching<br />
    9. 9. High Touch Point – Pros & Cons<br />Pros<br />ASP.NET application is self contained<br />Master page changes only<br />Advanced DB interaction <br />Cons<br />Performance constraints carry over to SharePoint environment - Need to load test!<br />Deployment will not be standardized with SharePoint Solution Packages (.wsp’s) <br />Need to keep farm in sync.<br />
    10. 10. Sample High Touch Point Solution<br />
    11. 11. Medium Touch Point<br />Use Built-In SharePoint capabilities to bridge the gap between ASP.NET Applications and SharePoint 2010<br />SharePoint 2010 API’s for Integration<br />Client Object Model<br />REST Services<br />SharePoint Application Page deployment<br />Web Parts connecting to external LOB systems directly<br />
    12. 12. Medium Touch Point- Pros & Cons<br />Pros<br />Standardized SharePoint deployment management<br />Can pick and choose integration points<br />Cons<br />No standardized authentication path – may require a custom Membership Provider for both<br />
    13. 13. Sample Medium Touch Point Solution<br />
    14. 14. Low Touch Point - Cobranding<br />SharePoint 2010 is built on Master Pages<br />Starter Master Pages for SharePoint 2010 <br />Built from minimalist perspective <br />V4.Master Page Modifications<br />One approach is to copy v4.master & modify CSS<br />Fairly complex<br />Publishing Sites <br />SP2010 Standard & Enterprise, not Foundation<br />Can modify nightandday.css & nightandday.master<br />Modifies the published content facing pages only<br />
    15. 15. Low Touch Point – Pros & Cons<br />Pros<br />No additional performance strain on SharePoint farm<br />Most amount of freedom with ASP.NET application expansion<br />No pain points with integrating <br />Cons<br />Customized work with Membership Providers<br />Replacement work for SharePoint Nav<br />Branding stored in 2 places<br />
    16. 16. Sample Low Touch Point Solution<br />
    17. 17. Audience Survey<br />Where are you on the SharePoint 2010 integration curve?<br />Already done a few integrations and very satisfied with the solution<br />Attempted an integration but not satisfied with the results, architecture, etc.<br />Planning an integration with SharePoint 2010<br />Need more information<br />Not currently using SharePoint 2010<br />
    18. 18. Avoiding Integration Pitfalls<br />High Touch Point<br />Must be designed to run in VirtualDirectory<br />Medium Touch Point<br />Wrap Silverlight inside web parts<br />In-line code is prohibited<br />Low Touch Point<br />More difficult and complex than it looks<br />Co-branding is very complex<br />Two separate applications being viewed as a unified whole<br />
    19. 19. Best Practices<br />High Touch Point<br />Load test to calculate load on SharePoint<br />Consider using a Membership Provider or Claims for Authentication<br />Medium Touch Point<br />Leverage SharePoint for logging, error handling, authentication, and caching<br />Be conservative when re-factoring web parts<br />Low Touch Point<br />Minimize Navigation contact points<br />Leverage common CSS, images, and JavaScript<br />
    20. 20. Audience Survey<br />What do you see as next steps?<br />Assess current integration opportunities and environment<br />Learn more about integrating solutions with SharePoint 2010 and ASP.NET<br />Plan for an integration between SharePoint 2010 and an ASP.NET application<br />
    21. 21. Downloadable Brochures<br />Several handouts are available for download from LiveMeeting.<br />SharePoint 2010 GamePlan<br />Enterprise Content Management GamePlan<br />Blended Application Case Study<br />SharePoint Composer/Maestro<br />
    22. 22. Resources and Q & A<br />Assessment & Planning<br />SharePoint GamePLAN<br />Contact us for demos & guidance<br />Learn<br />Next Webinar: No-code SharePoint 2010 SolutionsInstall to Implementation without writing ANY code<br />Resources<br />Dave’s Book:<br />SharePoint 2010 SDK -<br />SharePoint P & P Guidance -<br />Contact<br /><br />800-445-1279 x300<br />