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. 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.
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. The DNN Enterprise: For those utilizing SharePoint as the document management system, and wishing to integrate the same into their website, the Nuke Enterprise edition is a good choice. With the help of this edition, custom integration is possible at a highly affordable cost. Through the connector, firewall issues can be bypassed and the content can be kept fresh, while publishing directly from the Document Library. Every document that is published is offered protection by the DNN role-oriented security network.
4. Avoidance of Firewall: 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. Leveraging filtering views: The built-in views provided by document management system for filtering facilitate the use of the Create View UI. The views that have already been created can be used without the requirement for maintenance of two distinct filter sets. More time can be spent for development of core features as the time spent on development of filtering and associated UI features is reduced to a great extent.
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. 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. Deletion from the document management system: In case “propagate deletions” is selected, the file that is deleted from the document management system also gets deleted from DNN. However, if the deleted file possesses references from a module, it will reveal broken links.
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.
Seamless integration, when effectively accomplished, empowers organizations to securely and effectively publish documents directly from SharePoint into their respective exterior-facing websites. Custom SharePoint development teams can help you build projects within allocated budgets and time schedules.