several integration levels of a custom .NET application to SharePoint
- Integration Level 0 (No Integration)
Advantages
Simplest solution as there is no need to integrate with MOSS 2007 or deploy.
More reliable as there is no reliance on MOSS 2007 services.
Server requirements are reduced as SharePoint services are not running/not required.
Simpler development and deployment model and debugging.
Regular workstations can be used for development and Visual Studio 2008 is good for development and no add-ons or extensions required.
Can take advantage of third party tools such as DevExpress and Log4net with little or no setup changes.
Service account can be used for database access, no need to worry about Single Sign On.
Disadvantages
Limited integration with existing MOSS 2007 portals.
Another hosting environment to maintain.
Cannot take advantage of list data that is available in MOSS 2007.
MasterPages and Login pages with common user controls must be developed.
Cannot take advantage of SharePoint security model
Integrating to MOSS 2010 will be another complete effort.
Integration Level 1 (Using ASP.NET 3.5 hosted inside MOSS 2007 as Application Pages)
Advantages
Simpler development Model compared to higher levels of integration and debugging the Business objects and data objects is possible.
SharePoint is aware of the page – so the link is natively visible to portals (i.e. the link doesn’t need to be added to SharePoint)
Can take advantage of SharePoint master page, so the look and fell will be consistent across the organization. This will fasten the development process as there is no need for login and other user controls.
Application can be developed in regular ASP .NET fashion and integrated into MOSS 2007 as application pages, so regular ASP .NET debugging can be leveraged.
Single hosting environment and other Windows 2003 web servers can be taken off
Can take advantage of SharePoint’s security model such as User Profile.
Can take advantage of some of SharePoint’s features for future development.
Can take advantage of collaboration with some existing list data.
Don’t have to concentrate as much as for regular .NET apps regarding the AppScan vulnerabilities
Can take advantage of .Net 3.5 features such as ADO .NET entity framework and LINQ compared to higher levels of integration
Since each page is independent of other, MOSS 2010 migration will be easier compared to higher levels of integration.
Can take advantage of MOSS features in application enhancements.
Disadvantages
Dependency upon MOSS.
More powerful servers are required as there will be single hosting environment that process both regular SharePoint information and ASP .NET web application.
Initial setup of integrating ASP .NET web app into MOSS 2007 could be a night mare as there are some configuration changes, master file changes and some code changes to integrate the custom.master file.
May find some difficulties working with some third party controls such as Dev Express.
May find some challenges in using open source utilities such as Log4net and Microsoft Data Access Applications blocks as MOSS 2007 requires the signed assembly.
Changes in development and deployment process as there will be integration and that needs to be done on a web server which has SharePoint installed.
Verbose logging should be enabled in order to track down the errors in the integration part.
Double hop issue, must use local db account to access the DB or configure Single Sign On.
Cannot use proper identity impersonate with SharePoint security model.
Integration Level 2 (Using ASP.NET 3.5 and developing inside MOSS 2007)
Advantages
Single hosting environment.
Can take advantage of full SharePoint’s security model.
Can take advantage of SharePoint’s rich controls such as SPGridView, built-in web parts and Workflows.
Can integrate with existing list data if any.
Can take advantages of MOSS 2010 easy development framework such as BCS.
Disadvantages
Dependency upon MOSS 2007.
Site Pages render slower in MOSS 2007.
There is reliance on more components – so reliability of system is lower.
More powerful servers are required as there will be single hosting environment that process both regular SharePoint information and ASP .NET web application.
May find some difficulties working with some third party controls such as Dev Express.
May find some challenges in using open source utilities such as Log4net and Microsoft Data Access Applications blocks as MOSS 2007 requires the signed assembly.
Difficulty in troubleshooting. There are different log files to search for the error and it’s not clear where to look.
Development environment issues could arise as work stations do not have SharePoint libraries installed.
Reduced ability to use new .NET 3.5 features such as ADO .NET entity framework and LINQ.
Oracle client must be installed on the server in order to connect to Oracle db
More effort in migrating to MOSS 2010 compared to Integration Level 1.
Integration Level 3 (Deep Integration with MOSS 2007 using Lists , Business Data Catalog and Data Sources)
Advantages
Single hosting environment.
Can take full advantage of SharePoint’s security model.
Can take advantage of SharePoint’s rich controls such as SPGridView, built-in web parts and Workflows.
Can leverage current look and feel of SharePoint sites if they already exist.
Lists are easily customized by users.
Notifications when data changes.
Can take advantages of MOSS 2010 easy development framework such as BCS.
Disadvantages
Complete revamp of business process flow and this will require significant user education.
Dependency upon MOSS 2007.
Site Pages render slower in MOSS 2007.
There is reliance on more components – so reliability of system is lower.
More powerful web servers and SQL server required.
Difficulty in troubleshooting. There are different log files to search for the error and it’s not clear where to look.
Performance and scalability issues using Business Data Catalog to connect to external data sources.
Insane Development Requirements: You must have a Windows 2003/2008 Server as your Workstation; you really should be local Administrator on it.
More effort in migrating to MOSS 2010 compared to other Integration Levels.
No comments:
Post a Comment