How to use SharePoint only as a content management tool from a custom web application?

We have many customizable web applications (both external and internal) written in classic ASP and ASP.NET 2.0 technologies. Internal users can upload files to these websites, which can then be viewed by external users. In some cases, external users may also upload documents. Screenshot # 1 gives a brief idea of ​​the existing architecture.

  • Internal users upload documents to custom web applications. These documents are stored in the folder structure defined in the web application.

  • Meta data and user permissions, such as users who have access to documents, are stored in a database SQL Server.

  • The same set of documents that are uploaded to custom web applications, also exists at SharePoint. However, custom web applications are not aware of SharePoint. Therefore, users must download them from SharePoint, and then upload them to custom web applications. We are currently using SharePoint 2010.

  • External users can also upload documents to custom web applications. The metadata and user permissions of the document are stored in the database based on the user who downloads the document.

Screenshot # 1 :

1

# 2 , . SharePoint. , - SharePoint , . - ASP.NET MVC. , .

β„–2:

2

:

  • , internal users SharePoint. SQL Server. SharePoint, , -. ? SQL Server SharePoint?

  • , SharePoint Web Services Business Connectivity Services (BCS) SharePoint. ?

  • - . SharePoint, - , . ?

  • - ? ? - ?

  • - , ASP.NET MVC?

  • SharePoint - (ASP.NET Web Forms/ASP.NET MVC)? , -, SharePoint -?

.

.

+3
1

1

, . , Active Directory . , , SQL Server , . , AD. , , , SQL Server SharePoint. SharePoint API , , SharePoint , . , . Microsoft MIIS ( , Forefront Identity Management ) , .


2

- SharePoint SharePoint . , SharePoint ( SharePoint ).


3

, . SharePoint Server ( SharePoint Foundation), . , , , , SharePoint .


4

, , . , , SharePoint . . . - , (, , ).


5

, . .


6

, API, .


.

+2

All Articles