SharePoint 2013 Hosting :: 10 Things You should not Miss for Integrate DotNetNuke 7.2 with SharePoint 2013 Hosting

SharePoint hosting online migration is not something that can be easily achieved  rather, it engages careful planning for successful execution of the same. The reason is simple, you need to deal with a huge volume of important data and no sort of downtime is usually tolerated by an organization. Therefore, the biggest question that crops up in such situation is how to avoid the risk of losing any data ensuring an exact move of just the elements you need alongside involving minimum time possible reducing the impact upon the users along with the systems?

DotNetNuke Corporation, a premier provider of adaptive web software which keeps the online presence of a business effective and relevant, came up with the availability of an improved SharePoint integration in the year 2012. This new SharePoint Connector is capable of rendering support to SharePoint 2007 as well as the 2010 version. It offers seamless integration between outstanding document management and web content management solution of DotNetNuke. Here we bring to you certain best practices which you must consider for proper integration.

  1. Good knowledge of SharePoint and DotNetNuke – This particular approach helps in easy as well as seamless integration of both the document management system and the software making it easy for content monitoring along with modification. It is important to have good knowledge of the software as well as the application before taking up integration.
  2. Integration with SharePoint: Automatic integration of DotNetNuke is possible, which implies that if the system is operated, no additional work is needed. But, when it comes to DNN Community, it can also integrate quite comfortably through custom modules. The goal is to develop a system which enables SharePoint to go for effective communication from behind firewalls with the public-facing website. This indicates that you will be capable of pushing documents towards a portal efficiently as well as safely on your DNN website. Filter rules can also be designed in order to find out where individual documents are going.
  3. Document Management: SharePoint is the finest document management system that is applicable for all businesses irrespective of the size. Utilizing this system, which is built within the cloud in order to make room for maximum accessibility and storage, group members are able to collaborate and share an apparently unlimited quantity of data and documents. It effectively integrates with Outlook and makes use of social tools for amplifying the organized, collaborative, atmosphere. It also facilitates transformation of raw data into interactive, beautiful reports by team members.
  4. Avoid the firewall – Always make sure that the SharePoint server can enjoy an easy access to the DOTNetNuke server. This helps in smoother as well as better content management without any modification of security policies. Many companies make use of SharePoint as the document library and DNN as the public-facing website. In most cases this implies that the SharePoint server resides within the trusted zone while the DNN is made available to the public. All communications that take place between the two servers begin from the SharePoint server. This feature can be used without making any kind of modifications to the security policy.
  5. Allow filtering of documents to be transferred– This particular approach helps the users to filter the documents easily through the integrated SharePoint filtering views. This helps the users to make use of the Create View UI and need not rely upon two different sets of filters.
  6. Extended web application: When there is already a SharePoint web application making use of Active Directory for authentication, the same can be extended to support users from DotNetNuke hosting. For this a DNS or hosts file entry needs to be created for the upcoming SharePoint site.
  7. Modification of web.config files: A number of changes need to be considered within the web.config file in the SharePoint application. Before making any kind of modifications, it is advisable to create a backup.
  8. Taking care of file size: With respect to the file size, DotNetNuke possesses an option beneath the host settings which limits the file size on the website. The files are compared against that number by the Connector. Files bigger than the stipulated limits of the website are not published.
  9. Synchronize the deletes – Taking up this particular approaching during the process of integration also helps avoiding the errors of “file not found” during the successful execution of removal of files. This particular approach of cleaning also ensures reduction of unimportant database clogging, duplication, overall risk, and human errors.
  10. Handling permissions: Remember that permissions from a SharePoint to a DNN site are managed by DNN’s security model. It is not possible to manage permissions across SharePoint and DNN. This in because, in a number of cases, users and roles are different when it comes to the intranet and the public website.

Following the above-mentioned tips is sure to help you achieve a successful integration of DotNetNuke with SharePoint and ensure defining the success metrics for your organization in terms of less error, reduced publishing time, etc.