Dot netnuke

2,266 views

Published on

Dotnetnuke content management system

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,266
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
55
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • [ Note to presenter: As you go through these presentations and demos, be sure to call out the key features below] Key Features: Overall Design Easy to install and to host. Built on up-to-date Microsoft ASP.NET technology, and runs on various database platforms. Fully extensible and scalable. Suitable for a variety of projects -- from the smallest Web site to the largest corporate deployment. Internet or intranet sites can be developed entirely with built-in DotNetNuke features, or can be augmented through third-party private assembly tools. Clearly licensed under a BSD-style license. Software can be completely incorporated, modified, and adapted to personal/business use without having to worry about legalities. Constantly evolving through real world trial. Open source nature of DotNetNuke allows programmers and webmasters to read, redistribute, and modify the source code, essentially evolving the software at a rapid pace. End-user suggestions result in quick improvements and enhancements to the software. Simply efficient and manageable. DotNetNuke can support multiple portals off of one installation. Divides administrative options between host level and individual portal level. Allows administrators to manage any number of sites, each with their own look and identity, all off of one hosting account. Priority on security. Emphasis placed on validation, encryption, “bug” tracking, and potential threats. Fully customizable. Changes can be made to portals at all levels – from basic stylesheet elements like font type, color, and bullet points, to overall site appearance. New skins and module containers can be easily applied to the site with no repercussion on content. Fully localized. Built-in multi-language localization features allow administrators worldwide to easily use and adapt DotNetNuke software for their own use. User-friendly interface. Well-researched interface makes it easy for users to manage all aspects of their projects. Site wizards, help icons, and an intuitive user interface allow universal ease-of-operation. Easy to access community support. With a dedicated core programming team, over 125,000 registered users, and a growing legion of third-party DotNetNuke developers, hosters, and resellers, community support is always close-at-hand.
  • © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 04/29/10 09:29 Note: If you want to support e-mail you need to point to an SMTP server. SMTP can be on the machine or not. MSDE management tools? Use SQL Server Developer Edition on non-server operating system No Access Data Provider in the box: Blackjacket software, mySQL, Oracle Will run with firefox.
  • Unzip the code to a directory Give Network Service account modify permissions to folder Create a virtual directory pointing to the content Create an empty SQL database and user account Assign the user account permissions for the roles: db_securityadmin, db_ddladmin, db_datareader, and db_datawriter Edit the Web.config file for the SQL Connection string Browse to the Web site http://www.domain.com/virtualdirectory
  • Parent Portals Parent Portals are sites which have a unique URL (for example, www.contoso.com) associated to them. This generally involves purchasing a domain name from an Internet registrar, setting the Primary/Secondary DNS entries to point to the hosting provider’s DNS server, and having your hosting provider map the Domain Name to the IP address of your account. An example of a valid Parent Portal name is “Error! Hyperlink reference not valid.” You can also use the IP address of your site without a Domain Name (for example, 65.174.86.217). If you need to have multiple Domain Names pointing to the same portal, you can add multiple aliases in the portal edit interface. Do not create a Parent Portal until all of the DNS mappings are in place or else you will not be able to access your portal. Child Portals Child Portals are complete DNN portals that are located in a subdirectory of the main site (for example, www.contoso.com/mysite). Child Portals are accessed by entering the URL address which includes a Parent domain name followed by the portal’s name (for example, www.byte.com.au/directory). An example of a valid Child Portal name is “www.byte.com.au/portalname”. A Child Portal can be converted into a Parent Portal at any time by adding a Portal Alias entry.
  • DotNetNuke has a rich ecosystem: for example, modules, skins, and language Packs. Web hosters can use these (or even create custom modules and skins) to differentiate their offerings. For more resources search for DotNetNuke… Because it's an open source project with a lot of momentum, there is a ton of interest from developers and others to build modules that plug into it. Modules: Online store Chat Support desk Contact manager Job board Classifieds Reports Form creator … and more Skins: Many available for free and paid www.snowcovered.com/snowcovered2 dnn.com.au www.dotnetnuke.de www.dnnskins.com www.nsurvey.org Additionally, in June the DotNetNuke team will release a book about building portal sites with DotNetNuke (from Wiley/Wrox press).
  • This is a screen shot of the DotNetNuke Forums page to give a sense of the excitement and activity in the DNN community.
  • To help users learn how to build DotNetNuke sites, the DotNetNuke team has published the DotNetNuke guided tour. This is a free, online step-by-step guide which covers common tasks like creating pages, configuring modules and so on. You can access the guided tour at www.dotnetnuke.com/guidedtour.
  • Note: You need to include the ‘default.aspx’ at the end of the URL. Remember, DotNetNuke is not a Microsoft application to the resources and I’m going to point out here are actually run by the DNN community project. To get started with your DotNetNuke deployment, visit www.dotnetnuke.com/hosting/default.aspx. On this site you’ll find technical guidance, online forums, and links to additional resources that you can use to customize your offer (like modules, skins, and so on). The site also contains screen shots and other marketing materials that you can use to promote your DNN offering. DotNetNuke is available for use free of charge (under a free BSD style open source license (this is a non-GPL license)). If you’d like, you can download the source code and make your own modifications. However remember that it’s an open source project that’s constantly evolving, so you will have to merge your changes with updated versions. The DotNetNuke open source project is run by Perpetual Motion – the project lead is Shaun Walker. If you’re interested in custom development for DNN, or paid support (that is, support with an SLA) you can contact Perpetual Motion.
  • IT is all open source, you can open it up in visual studio and see it all
  • Key Features: Overall Design Easy to install and to host . Built on up-to-date Microsoft ASP.NET technology, and runs on various database platforms. Fully extensible and scalable . Suitable for a variety of projects -- from the smallest website to the largest corporate deployment. Internet or Intranet sites can be developed entirely with built-in DotNetNuke features, or can be augmented through third-party private assembly tools. Clearly licensed under a BSD-style license . Software can be completely incorporated, modified, and adapted to personal/business use without having to worry about legalities. Simply efficient and manageable . DotNetNuke can support multiple portals off of one install. Divides administrative options between host level and individual portal level. Allows administrators to manage any number of sites, each with their own look and identity, all off of one hosting account. Priority on security . Emphasis placed on validation, encryption, “bug” tracking and potential threats. Fully customizable . Changes can be made to portals at all levels – from basic stylesheet elements like font type, color, and bullet points, to overall site appearance. New skins and module containers can be easily applied to the site with no repercussion on content. Fully localized . Built-in multi-language localization features allow administrators worldwide to easily use and adapt DotNetNuke software for their own use. User-friendly interface . Well-researched interface makes it easy for users to manage all aspects of their projects. Site wizards, help icons, and an intuitive user interface allow universal ease-of-operation. Easy to access community support . With a dedicated core programming team, over 125,000 registered users, and a growing legion of third-party DotNetNuke developers, hosters, and resellers, community support is always close-at-hand.
  • © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 04/29/10 09:29 SQL EM used for config. What to use for MSDE? SQL Scripting process Upgrade process assumes you haven’t changed the core code To upgrade, I often create a new directory, copy in previous contents, unzip new over it, change vdir & visit it.
  • Website Starters for Windows applications are a set of 3rd party applications optimized to run in a Windows-based hosted environment. Applications in Website Starters for Windows drive end-customer interest and up-sell by providing a full set of compelling applications built by Microsoft partners and the community. DotNetNuke Portal Builder : The easy to use DotNetNuke Portal Builder helps end-users quickly build and manage rich web-sites. With more than two hundred integrated modules available today, the portal builder provides an easy way for service providers to add new features and applications in Web hosting offers. Opportunity to customize and differentiate offers Part of the real power of the DotNetNuke Portal Builder lies in the opportunity for service providers to build on it to add further value to customers. In addition to the hundreds of modules that ship today, service providers can easily build new modules
  • DotNetNuke is best targeted at hobbyist users – it’s not an application for complete beginners. DotNetNuke’s Wizard helps less technical hobbyist users get started. Several templates are provided, and hosters can easily build more templates and add them to the list. In this series of photos we show a site based on the ‘Club/Organization’ template being built. First the user selects the ‘Club/Organization’ template, then selects the design (aka ‘skin’), then adds details (like the site title, description, and keywords). The resulting site is populated with pages for Events, Photo Gallery, and Discussions, since these are common pages in many Club/Organization sites.
  • One of the key features of DotNetNuke is the ease with which users can add advanced functionality to their sites. This functionality is added via modules. In this example the user adds an Events module: first the user selects the ‘Events’ module from the admin bar, then presses ‘Add’ and the Events module appears on the site. The user can now start using the module (adding events, move it around the page etc.)
  • Dot netnuke

    1. 1. DotNetNuke Technical Overview
    2. 2. Section Overview <ul><li>Installing DotNetNuke </li></ul><ul><ul><li>Demo: “DotNetNuke Manual Installation” </li></ul></ul><ul><li>Enabling a Shared Hosting Offer </li></ul><ul><ul><li>Demo: “Exploring the Host Account” </li></ul></ul><ul><ul><li>Demo: “Provisioning DotNetNuke” </li></ul></ul><ul><li>Enabling the Reseller Scenario </li></ul><ul><ul><li>Demo: “Creating Multiple Portals” </li></ul></ul><ul><li>Best Practices and Resources </li></ul>
    3. 3. Installation Requirements <ul><li>Current: DotNetNuke v3.0.13 or later </li></ul><ul><li>Requires: </li></ul><ul><ul><ul><li>Microsoft Windows 2000 Server or Microsoft Windows Server ™ 2003 </li></ul></ul></ul><ul><ul><ul><li>Internet Information Services (IIS) installed </li></ul></ul></ul><ul><ul><ul><li>.NET Framework V1.1 </li></ul></ul></ul><ul><ul><ul><li>Microsoft SQL Server ™ 2000 </li></ul></ul></ul>
    4. 4. Install DotNetNuke <ul><li>Installation Process </li></ul><ul><ul><li>Unzip the code to a directory </li></ul></ul><ul><ul><li>Give Network Service account permissions </li></ul></ul><ul><ul><li>Create a virtual directory pointing to the content </li></ul></ul><ul><ul><li>Create an empty SQL database and user account </li></ul></ul><ul><ul><ul><li>Assign permissions to db_securityadmin, db_ddladmin, db_datareader, and db_datawriter </li></ul></ul></ul><ul><ul><li>Edit Web.config for SQL connection string </li></ul></ul><ul><ul><li>Browse to http://www. domain .com/ vdir </li></ul></ul>
    5. 5. Portals Defined <ul><li>DotNetNuke supports multiple portals within a single instance </li></ul><ul><ul><li>Additional portals are contained within the same site and the associated database </li></ul></ul><ul><li>What is a Parent Portal? </li></ul><ul><ul><li>Complete portal accessed by a unique domain </li></ul></ul><ul><ul><li>URL: www.contoso.com </li></ul></ul><ul><li>What is a Child Portal? </li></ul><ul><ul><li>Complete portal located in a subdir of the main site </li></ul></ul><ul><ul><li>URL: www.fabrikam.com/vdir </li></ul></ul>
    6. 6. Best Practices <ul><li>Use page preview as Admin </li></ul><ul><li>Make modules that are visible only to Admin show red box </li></ul><ul><ul><li>Pages visible only to Admin don’t show any flag </li></ul></ul><ul><li>Add functionality with custom modules </li></ul><ul><ul><li>Versus making core changes </li></ul></ul><ul><li>Use providers for plug-in flexibility </li></ul><ul><ul><li>Data access, membership, HTML edit, search, scheduling, logging, friendly URLs </li></ul></ul><ul><li>Watch DNN forums and bug tracker for fixes </li></ul><ul><li>See the documentation directory – many details explained </li></ul><ul><li>Visit the many resource sites for skins, containers, tutorials, other tips and tricks, and so on </li></ul>
    7. 7. DotNetNuke Ecosystem <ul><li>More DotNetNuke resources: </li></ul><ul><li>Online forums for help </li></ul><ul><li>Context sensitive help </li></ul><ul><li>Wrox DotNetNuke Book </li></ul><ul><li>Quickstart tutorial – http://www.dotnetnuke.com/guidedtour/ </li></ul>
    8. 8. DotNetNuke Community http://forums.asp.net/90/ShowForum.aspx
    9. 9. DotNetNuke Guided Tour www.dotnetnuke.com/guidedtour
    10. 10. Next Steps <ul><li>Get up-and-running with DotNetNuke </li></ul><ul><ul><li>www.dotnetnuke.com/hosting/default.aspx </li></ul></ul><ul><ul><li>Free of charge (BSD-style open source license) </li></ul></ul><ul><li>Custom development and service-level agreement (SLA) support </li></ul><ul><ul><li>[email_address] (Shaun Walker) </li></ul></ul>
    11. 11. APPENDIX
    12. 12. DNN Architecture Core Services (VB.NET) Business Logic Layer Data Providers Common Classes Logic and Security SQL Server Data Provider Profile and Localization Web Gateway Web Presentation Layer User Controls Rendering Logic HTML Rendering Skinning SQL Server Stored Procedures Tables Functions
    13. 13. DotNetNuke Baseline Performance <ul><li>Overview </li></ul><ul><ul><li>Scenario: 2,000 websites on 1 front-end web server with databases on 1 back-end SQL server, both running Windows Server 2003 SP1. 400 websites were configured per application pool, with a total of 5 app pools. </li></ul></ul><ul><ul><li>ASP.NET v1.1 ran in Medium Trust and we removed browserCaps and mobile support. IIS 6.0 had memory-based recycling enabled for app pools to ensure the system never reached unhealthy limits (private bytes=700MB, virtual bytes=1300MB) and an increased kernel request queue (5,000). </li></ul></ul><ul><ul><li>Each test ran for 12-hours. </li></ul></ul>
    14. 14. DotNetNuke Baseline Performance Results <ul><li>DotNetNuke Results </li></ul><ul><ul><li>Traffic Distribution: 95% traffic > 100 sites, 5% traffic > 2,000 sites </li></ul></ul><ul><ul><li>Pages requested: 8 </li></ul></ul><ul><ul><li>Requests-per-second: 611 </li></ul></ul><ul><ul><li>Pages-per-second: 20 </li></ul></ul><ul><ul><li>Total HTTP requests: 26,526,776 </li></ul></ul><ul><ul><li>Average working set: 12MB </li></ul></ul><ul><ul><li>Average response time: 42msec </li></ul></ul><ul><ul><li>Hardware: Each server had (2) 3.6Ghz HT processors and 4GB RAM </li></ul></ul>
    15. 15. Key Features of DotNetNuke Overall Design <ul><li>Easy to install and to host. </li></ul><ul><li>Fully extensible and scalable. </li></ul><ul><li>Clearly licensed under a BSD-style license. </li></ul><ul><li>Constantly evolving through real world trial. </li></ul><ul><li>Simply efficient and manageable. . </li></ul><ul><li>Priority on security. </li></ul><ul><li>Fully customizable. . </li></ul><ul><li>Fully localized. . </li></ul><ul><li>Easy to access community support.  </li></ul>
    16. 16. Designed for Hosting <ul><li>Partitioned Data Model </li></ul><ul><ul><li>Enable multiple installs in a single DB </li></ul></ul><ul><ul><li>User base can be shared or isolated across sites </li></ul></ul><ul><ul><li>Shared admin tool constrained for current site </li></ul></ul><ul><li>Other features </li></ul><ul><ul><li>Easily add-value with customized skins </li></ul></ul><ul><ul><li>Easily add-value with new language packs </li></ul></ul><ul><ul><li>Skins / languages are additive </li></ul></ul>
    17. 17. DNN Installation Walkthrough <ul><li>Installation Process (staging machine): </li></ul><ul><ul><li>Unzip the code to a directory </li></ul></ul><ul><ul><li>Give ASPNET/Network Service account permissions </li></ul></ul><ul><ul><li>Create a virtual directory pointing to the code </li></ul></ul><ul><ul><li>Create an empty SQL database, set up account as dbowner </li></ul></ul><ul><ul><li>Edit Web.config for SQL connection string </li></ul></ul><ul><ul><li>Browse to http://localhost/vdir </li></ul></ul><ul><ul><li>Change Host and Admin passwords! </li></ul></ul><ul><li>Upgrade Process (simple): </li></ul><ul><ul><li>Back up your current configuration </li></ul></ul><ul><ul><li>Unzip the new code into the directory structure </li></ul></ul><ul><ul><li>Browse to the vdir </li></ul></ul>
    18. 18. Installation Details <ul><li>Initial setup – build a local staging site before trying to install in a hosted environment </li></ul><ul><li>Database = SQL (Access in v3 via 3rd party) </li></ul><ul><li>Web.config tags (in <data defaultprovider>): </li></ul><ul><ul><li>objectQualifier, databaseOwner </li></ul></ul><ul><li>Installation failures: try delete & re-create DB </li></ul><ul><li>Web.config overview… </li></ul><ul><li>Site Builder Wizard – rehydrate from template </li></ul>
    19. 19. For More Information <ul><li>www.dotnetnuke.com – project download (register) and info </li></ul><ul><li>support.dotnetnuke.com – Gemini bug tracker </li></ul><ul><li>www.asp.net/forums – DNN forums </li></ul><ul><li>www.gotdotnet.com/community/workspaces </li></ul><ul><li>http://www.cathal.co.uk/Default.aspx?tabid=28 </li></ul><ul><ul><li>Free v2 modules list (v3 coming) + resources + great skin! </li></ul></ul><ul><li>http://dnnjungle.vmasanas.net – resource portal </li></ul><ul><li>www.wwwcoder.com – resource portal </li></ul><ul><li>www.dnn.com.au – resource portal </li></ul><ul><li>www.dotnetnukehelp.com – resource portal </li></ul><ul><li>www.asp.net – Microsoft’s ASP developer site </li></ul><ul><li>http://msdn.microsoft.com/library/en-us/dnaspnet/html/asp02182004.asp - Whidbey Provider Model </li></ul><ul><li>http://spaces.msn.com/members/faithinteractive/?partqs=cat%3DDotNetNuke&_c11_blogpart_blogpart=blogview&_c=blogpart </li></ul>
    20. 20. Best Practices Continued <ul><li>Installation failures: try delete & re-create DB </li></ul><ul><li>Check SQL Database configuration </li></ul><ul><li>Verify accuracy of Web.config file </li></ul><ul><li>Visit the forums http://forums.asp.net/90/ShowForum.aspx </li></ul><ul><li>DotNetNuke Online Help Site http://www.dotnetnuke.com/default.aspx?tabid=787&helpculture=en-us&helpmodule=Portals </li></ul>
    21. 21. DotNetNuke Portal Builder <ul><li>Build fully functional site in minutes </li></ul><ul><li>Online content authoring (no HTML) </li></ul><ul><li>Wizard to help users build sites </li></ul><ul><li>Integrated forum/blog/gallery </li></ul><ul><li>Membership features </li></ul><ul><li>RSS content syndication </li></ul><ul><li>Rich 200 module ecosystem </li></ul><ul><li>Customizable (modules, skins) </li></ul>
    22. 22. DotNetNuke: Wizard Step 1: Choose a template Step 2: Choose a design Step 3: Add title and details Site pages are built
    23. 23. DotNetNuke: Adding a Module Admin Bar Select Module
    24. 24. Example: WebFusion <ul><li>http://www.webfusion.co.uk/?source=webfusion-pipexportal </li></ul>

    ×