Overview:

The SunsingSoft Content Management Suite is designed for DotNetNuke (DNN) versions 7.0.2 to Current

Understanding of the basic principles of DotNetNuke portal management is required to install and configure these components.  All modules and components can be installed into your DotNetNuke website instance independantly, without affecting any other part of your website (ie: you can still use the standard Html/Text module or any other third party modules).

The Content Server can be configured in many ways to suit your requirements, with most of the package being optional installations.  This allows for a wide variety of options.  We have simplified the installation and configuration steps into two parts, one for the Content Server, and the other for the Content Publishing Websites.  These may be installed into the same instance of DotNetNuke, or the Content Publishing Websites can be installed into a separate instance of DotNetnuke than the Content Server, on Remote or Local machines. 

Because of the wide variety of end users that utilize the websites that content is displayed on, we have provided some Use Cases to guide you through configuring your Content Publishing Websites.  In the section for each module, we will include the steps required for each Use Case:

1. Content is written by approved content authors who have permissions to self-approve and self-publish the content into their authorized website areas. This Use Case is optimized for intranets or informative websites where specific employees manage the content.
2. Content is written by users who join the website for a blogging or social networking experience.

Configuration:

1. If your Content Server and Content Publishing Websites are located in the same instance of DotNetNuke:

• Install the Content Server, Content Administration, Content Loader, Content Drag Drop, Content Manager, Content Manager List, Content Media Manager, Content Approval and Content Publishing modules into the same instance of DNN
• Leave the Content Server DataSource in all module settings to the default of "Local Database"
• For each Content Authoring Website in a different portal than Portal ID 0, login to that portal and use the Content Administration module to Handshake with the Content Publishing Website
• If the Content Publishing Website is in Portal ID 0 and is also in the same instance of DNN as the Content Server, leave all Module Settings DataSources to the default of "Local Database"

2. If your Content Publishing Website is not in the same instance of DotNetNuke as the Content Server:

• Install the Content Server module into the instance of DNN that will hold the central database as well as the web services
• Install the Content Administration and Content Loader modules into each website that will display the content then use the Content Administration module to create a Handshake with the Content Server
• Install the Content Administration, Content Drag Drop, Content Manager, Content Manager List, Content Media Manager, Content Approval and Content Publishing modules into the website that will create, approve and publish the content then use the Content Administration module to create a Handshake with each Content Publishing Website

Installation:

1. Installing the Content Server

• Install and Configure ARC component
• Install Content Server component
• Web.config changes
• Server Management module
  • Content Hosts
  • Content Authors

2. Installing into a Content Authoring Website

• Install and Configure ARC component
• Install Content Administration module
  • Handshake with the Content Server
  • Handshake with each Content Publishing Website
  • Content Authors
  • Initialize Profile settings
• Install the Content Manager module
• Install the Content Drag Drop module
• Install the Content Manager List module
• Install the Content Media Manager module
• Install the Content Publishing module
• Install the Content Approval module

3. Installing into a Content Publishing Website

• Install and Configure ARC component
• Install Content Administration module
  • Handshake with the Content Server
• Install the Content Loader module

4. Installing Additional Modules into a Content Publishing Website 

• Signup for a Content Account
• Content Account settings
• List of Content Authors
• Search for Articles
• Recent Articles
• Most Popular Articles
• Recent Videos
• Recent Images
• Random Videos
• Random Images
• Random Articles

In every installation circumstance you will need to follow the following steps, based on a new install of DNN 4.9.0:

If your Content Server, Content Authoring, and Content Publishing Websites are in the same DotNetNuke Portal:

1. Extract the contents of zipfile KHZ.ContentServer.Install.zip into the /Install/Module/ folder of your DNN Application.
2. The next time your server fires the App_Load event in DNN the modules should install automatically.  If you placed the install packages before the initial installation routine of DNN these modules should already be installed.
3. If any modules did not get installed automatically, login as host user and navigate to the Host > Module Definitions menu tab.  Scroll down and select the remaining modules from the checkbox list at the bottom of the screen, then click "Install Selected Modules".
4. Login as host user and navigate to the Host > SQL menu tab.  Open the file 04.02.02.sqldataprovider (from the install zipfile KHZ.Content.Server.zip) in notepad and Copy / Paste the contents of this file into the Script window in SQL Module.  Check the Install as script checkbox, then click the Run Script button.
5. Create a new DNN Page called something like "Content Server" and place the KHZ ARC module into it.  This creates all required web.config entries and then the module deletes itself.
6. On the same page, place the KHZ Content Server module and create a Content Host:
   1. Host name: your domain name (without the www. prefix)
   2. Host key: a shared secret key to identify this host
   3. Portal ID: the portal id of your content server (usually the current portal)
7. Create a new page called something like "Content Server Admin" selecting the Content Server page as the Parent page.  This makes it a child in the menu structure.
8. Add the Content Administration module to the new page
9. Create your Content Author account(s) and permissions to create and edit content. This will also create new users to the portal. If the user already exists (such as the admin user) then use the same Username and Password as when the user was created.
10. Navigate to the Admin > User  Accounts page and select the user, then edit the profiile for that user, setting the Content Access Key and Content Edit Key to match.
11. Create a new page called something like "Content Author" selecting the Content Server page as the Parent page. Add the Content Manager module to this page in the content pane.
12. Update the Content Manager module settings:
    1. Set the Content Server Edit Key
    2. Set the Content Server Host Key
    3. If the website is configured in IIS as a virtual directory, check the "Is Virtual Directory" checkbox
13. Add the Content Manager List module to the same page in a side pane.
14. Update the Content Manager List module settings updating the Content Server Edit Key.
15. Add the Content Drag Drop module to the same page in a side pane.
16. Update the Content Drag Drop module settings:
    1. Set the Content Server Edit Key
    2. If the website is configured in IIS as a virtual directory, check the "Is Virtual Directory" checkbox
17. Create a new page called something like "Content Test" selecting the Content Server page as the Parent page.
18. To manually add content to a page:
    1. Create a test article using the Content Manager module, save using the "Keep Private" button
    2. Add the Content Loader module to this page in the content pane.
    3. Update the Content Loader module settings:
       1. Set the Content Server Access Key
       2. Select the test article from the Content Item drop down list
    4. You should see the test article shown on the page after updating the Content Loader module settings
19. To Publish this article to a page:
    1. Create a test article using the Content Manager module, save using the "Publish" button
    2. From the options below the Save buttons, Select the Page you would like to publish to, and click Save