We have had SharePoint where I work for a little while now, but we've not done a lot with it. We have an intranet with hundreds of ASP/ASP.Net applications and I'm wondering what kind of things can be done to integrate with SharePoint to make a more seamless environment? We put documentation and production move requests and so on in SharePoint now, but it pretty much feels like it's own separate system rather than an integrated tool on our intranet.
我们已经在SharePoint工作了一段时间,但我们并没有做很多事情。我们有一个内部网,有数百个ASP / ASP.Net应用程序,我想知道可以做些什么来与SharePoint集成以创建更加无缝的环境?我们现在在SharePoint中放置文档和生产移动请求等,但它几乎感觉就像它自己的独立系统而不是我们内部网上的集成工具。
I've searched around to see what other people are doing with SharePoint but I've been finding a lot of useless information.
我一直在寻找其他人正在使用SharePoint做什么,但我一直在寻找很多无用的信息。
9 个解决方案
#1
2
A great idea for you would be move your most used asp.net apps to run within the SharePoint site. Each app can be added either as a control directly on a pagelayout or integrated into a webpart (use the webpart to load child controls).
对您而言,一个好主意是将最常用的asp.net应用程序移动到SharePoint网站中运行。每个应用程序既可以作为控件直接添加到pagelayout上,也可以集成到webpart中(使用webpart加载子控件)。
This would allow you to use the flexible moss interface to move the asp.net app into a unified information architecture so people can find the app easily.
这将允许您使用灵活的苔藓界面将asp.net应用程序移动到统一的信息架构中,以便人们可以轻松找到该应用程序。
SharePoint is really easy to roll out something that works, but creating a seamless intranet does require a bit of thinking outside of SharePoint itself (i.e. what should go where, which users need to see what, navigation structure...)
SharePoint很容易推出可行的东西,但是创建一个无缝的Intranet确实需要在SharePoint之外进行一些思考(即应该去哪里,哪些用户需要看什么,导航结构......)
That is really a lot of work and requires lots of input from people outside the IT area.
这确实是很多工作,需要IT领域以外的人提供大量的意见。
#2
2
A typical intranet portal segments functionality by department. Each department will probably have some custom web-based apps that you might have historically implemented in ASP.Net, and linked to from the intranet portal. With sharepoint you can start bringing the useful bits of those custom web-apps in as modular parts, so that the business owner of the portal can have more control as to how information is structured and displayed to his/her users.
典型的Intranet门户按部门划分功能。每个部门可能都有一些基于Web的自定义应用程序,这些应用程序可能在ASP.Net中历史性地实现,并从Intranet门户链接。使用sharepoint,您可以开始将这些自定义Web应用程序的有用位作为模块化部分,以便门户的业务所有者可以更好地控制信息的结构和显示给他/她的用户。
Think dashboards, populated with custom metrics that only make sense to individual departments. That's one of the most obvious places to start. HR, accounting, IT, they all have metrics they want to track and display. They all have legacy systems that they might want to correlate information from. All this can be done in reusable web-parts. Since Sharepoint gives the end-user the control over layout, display, audience control, etc, you don't end up reinventing wheels all day.
想想仪表板,填充的自定义指标只对各个部门有意义。这是最明显的起点之一。人力资源,会计,IT,他们都有他们想要跟踪和显示的指标。他们都有遗留系统,他们可能想要关联信息。所有这些都可以在可重复使用的Web部件中完成。由于Sharepoint为最终用户提供了对布局,显示,观众控制等的控制,因此您最终不会整天重新发明*。
#3
2
SharePoint was designed to be a collaboration portal and document repository. If you have other business processes wrapped up in other internal web sites, you may not get much benefit from converting these sites into SharePoint sub-sites.
SharePoint旨在成为协作门户和文档存储库。如果您在其他内部网站中包含其他业务流程,则将这些网站转换为SharePoint子网站可能无法获得太多好处。
However, if there is signifcant overlap in your applications (contact lists, inventory, specs, etc.) you may want to make the investment to combine.
但是,如果您的应用程序(联系人列表,库存,规格等)存在显着重叠,您可能希望将投资结合起来。
#4
1
If you have InfoPath, you can create online forms. You can share your docs and edit them online. You can start an approvement workflow on these docs. You can create polls. You can create work groups.
如果您有InfoPath,则可以创建在线表单。您可以在线分享您的文档并进行编辑。您可以在这些文档上启动批准工作流程。您可以创建民意调查。您可以创建工作组。
Basically SharePoint is a giant and robust document store, but you can do anything what you can do in any ASP.NET web application. You can create e.g. custom workflows to automate business processes. We've worked for several customers to create corporate intranets and sometimes internet sites, so it really works. :)
基本上,SharePoint是一个巨大而强大的文档存储,但您可以在任何ASP.NET Web应用程序中执行任何操作。你可以创建例如自定义工作流程以自动化业务流程。我们已经为几个客户创建了企业内部网,有时还创建了互联网网站,所以它确实有效。 :)
But sometimes it's very hard to implement the requested features (a lot of workarounds).
但有时很难实现所请求的功能(很多解决方法)。
#5
1
Really its an intranet in a box. We pretty much run all of our day to day development tasks off of it. We keep documentation, track defects, manage people's time off etc. You can migrate your asp.net and asp applications to run under the sharepoint site. In the adminstration section you can set up web applications to run under the same site, but outside of sharepoint's control. That would probably help with the "feel" of it being completely seperate.
真的是一个盒子里的内联网。我们几乎完成了所有日常开发任务。我们保留文档,跟踪缺陷,管理人们的休假等。您可以将您的asp.net和asp应用程序迁移到sharepoint站点下运行。在管理部分中,您可以将Web应用程序设置为在同一站点下运行,但不受sharepoint控制。这可能有助于它完全独立的“感觉”。
Sharepoint is really a shift in the way people have to think about web development and that's the key. You're no longer developing a standalone application, you're adding on to an existing framework. I would put it akin to having "silos of data" vs. a centralized database system which houses all the company's data. Once people realize that everything is connected, it will feel more like a seemless integration. My advice is to actively try and create applications in sharepoint and think about how to migrate existing apps on to it.
Sharepoint实际上是人们对Web开发思考方式的转变,这是关键。您不再开发独立应用程序,而是添加到现有框架中。我认为它具有“数据孤岛”而非集中数据库系统,其中包含公司的所有数据。一旦人们意识到一切都是连通的,就会感觉更像是一种无缝的整合。我的建议是积极尝试在sharepoint中创建应用程序,并考虑如何将现有应用程序迁移到它。
#6
1
How about BI and reporting from an ERP? When we know IE is uncapable to handle a page with 10000 table rows (without pagination) Many don't realize but the success of a reporting tool depends on the performance of the grid object used - Excel and the SpreadSheet obj from the defunct Office Web Components are still the #1 in user's (accountants, managers, ceo) choice.
如何从ERP和BI报告?当我们知道IE无法处理具有10000个表行(没有分页)的页面时许多人没有意识到,但报告工具的成功取决于所使用的网格对象的性能 - Excel和来自已解散的Office Web的SpreadSheet obj组件仍然是用户(会计师,经理,首席执行官)选择的第一名。
#7
0
I think it depends on your environment. In our environment, we setup each department with their own pages and we use it for basic information, surveys, and the employee's homepage. We've built Google/Live Search and Weather.com widgets and roll RSS feeds using Tim Huer's RSS control.
我认为这取决于你的环境。在我们的环境中,我们为每个部门设置自己的页面,并将其用于基本信息,调查和员工主页。我们使用Tim Huer的RSS控件构建了Google / Live Search和Weather.com小部件并滚动RSS源。
#8
0
One thing you can do is to create web parts to provide access to data from existing applications. Initially they could simply be read-only views, but depending on your experience they could be fleshed out to allow writes.
您可以做的一件事是创建Web部件以提供对现有应用程序数据的访问。最初它们可能只是只读视图,但根据您的经验,它们可以充实以允许写入。
Another idea is to add links between SharePoint and your applications (assuming they're web based); that will at least allow a flow between them.
另一个想法是在SharePoint和您的应用程序之间添加链接(假设它们是基于Web的);这将至少允许它们之间的流动。
I haven't done it, but you could also theoretically skin SharePoint to look like the rest of your intranet.
我还没有这样做,但理论上你也可以将SharePoint看起来像你的内部网的其余部分。
#9
-1
Create libraries
Form libraries, documents libraries, slide libraries
表单库,文档库,幻灯片库
Create standard or custom lists
创建标准或自定义列表
Standard lists - announcements, tasks, contacts
标准列表 - 公告,任务,联系人
Custom lists - suppliers, contractors, inventories, orders
自定义清单 - 供应商,承包商,库存,订单
Setup secure team discussion areas
设置安全的团队讨论区域
Build shared team calendars
构建共享团队日历
Create simple workflow processes on documents and lists
在文档和列表上创建简单的工作流程
#1
2
A great idea for you would be move your most used asp.net apps to run within the SharePoint site. Each app can be added either as a control directly on a pagelayout or integrated into a webpart (use the webpart to load child controls).
对您而言,一个好主意是将最常用的asp.net应用程序移动到SharePoint网站中运行。每个应用程序既可以作为控件直接添加到pagelayout上,也可以集成到webpart中(使用webpart加载子控件)。
This would allow you to use the flexible moss interface to move the asp.net app into a unified information architecture so people can find the app easily.
这将允许您使用灵活的苔藓界面将asp.net应用程序移动到统一的信息架构中,以便人们可以轻松找到该应用程序。
SharePoint is really easy to roll out something that works, but creating a seamless intranet does require a bit of thinking outside of SharePoint itself (i.e. what should go where, which users need to see what, navigation structure...)
SharePoint很容易推出可行的东西,但是创建一个无缝的Intranet确实需要在SharePoint之外进行一些思考(即应该去哪里,哪些用户需要看什么,导航结构......)
That is really a lot of work and requires lots of input from people outside the IT area.
这确实是很多工作,需要IT领域以外的人提供大量的意见。
#2
2
A typical intranet portal segments functionality by department. Each department will probably have some custom web-based apps that you might have historically implemented in ASP.Net, and linked to from the intranet portal. With sharepoint you can start bringing the useful bits of those custom web-apps in as modular parts, so that the business owner of the portal can have more control as to how information is structured and displayed to his/her users.
典型的Intranet门户按部门划分功能。每个部门可能都有一些基于Web的自定义应用程序,这些应用程序可能在ASP.Net中历史性地实现,并从Intranet门户链接。使用sharepoint,您可以开始将这些自定义Web应用程序的有用位作为模块化部分,以便门户的业务所有者可以更好地控制信息的结构和显示给他/她的用户。
Think dashboards, populated with custom metrics that only make sense to individual departments. That's one of the most obvious places to start. HR, accounting, IT, they all have metrics they want to track and display. They all have legacy systems that they might want to correlate information from. All this can be done in reusable web-parts. Since Sharepoint gives the end-user the control over layout, display, audience control, etc, you don't end up reinventing wheels all day.
想想仪表板,填充的自定义指标只对各个部门有意义。这是最明显的起点之一。人力资源,会计,IT,他们都有他们想要跟踪和显示的指标。他们都有遗留系统,他们可能想要关联信息。所有这些都可以在可重复使用的Web部件中完成。由于Sharepoint为最终用户提供了对布局,显示,观众控制等的控制,因此您最终不会整天重新发明*。
#3
2
SharePoint was designed to be a collaboration portal and document repository. If you have other business processes wrapped up in other internal web sites, you may not get much benefit from converting these sites into SharePoint sub-sites.
SharePoint旨在成为协作门户和文档存储库。如果您在其他内部网站中包含其他业务流程,则将这些网站转换为SharePoint子网站可能无法获得太多好处。
However, if there is signifcant overlap in your applications (contact lists, inventory, specs, etc.) you may want to make the investment to combine.
但是,如果您的应用程序(联系人列表,库存,规格等)存在显着重叠,您可能希望将投资结合起来。
#4
1
If you have InfoPath, you can create online forms. You can share your docs and edit them online. You can start an approvement workflow on these docs. You can create polls. You can create work groups.
如果您有InfoPath,则可以创建在线表单。您可以在线分享您的文档并进行编辑。您可以在这些文档上启动批准工作流程。您可以创建民意调查。您可以创建工作组。
Basically SharePoint is a giant and robust document store, but you can do anything what you can do in any ASP.NET web application. You can create e.g. custom workflows to automate business processes. We've worked for several customers to create corporate intranets and sometimes internet sites, so it really works. :)
基本上,SharePoint是一个巨大而强大的文档存储,但您可以在任何ASP.NET Web应用程序中执行任何操作。你可以创建例如自定义工作流程以自动化业务流程。我们已经为几个客户创建了企业内部网,有时还创建了互联网网站,所以它确实有效。 :)
But sometimes it's very hard to implement the requested features (a lot of workarounds).
但有时很难实现所请求的功能(很多解决方法)。
#5
1
Really its an intranet in a box. We pretty much run all of our day to day development tasks off of it. We keep documentation, track defects, manage people's time off etc. You can migrate your asp.net and asp applications to run under the sharepoint site. In the adminstration section you can set up web applications to run under the same site, but outside of sharepoint's control. That would probably help with the "feel" of it being completely seperate.
真的是一个盒子里的内联网。我们几乎完成了所有日常开发任务。我们保留文档,跟踪缺陷,管理人们的休假等。您可以将您的asp.net和asp应用程序迁移到sharepoint站点下运行。在管理部分中,您可以将Web应用程序设置为在同一站点下运行,但不受sharepoint控制。这可能有助于它完全独立的“感觉”。
Sharepoint is really a shift in the way people have to think about web development and that's the key. You're no longer developing a standalone application, you're adding on to an existing framework. I would put it akin to having "silos of data" vs. a centralized database system which houses all the company's data. Once people realize that everything is connected, it will feel more like a seemless integration. My advice is to actively try and create applications in sharepoint and think about how to migrate existing apps on to it.
Sharepoint实际上是人们对Web开发思考方式的转变,这是关键。您不再开发独立应用程序,而是添加到现有框架中。我认为它具有“数据孤岛”而非集中数据库系统,其中包含公司的所有数据。一旦人们意识到一切都是连通的,就会感觉更像是一种无缝的整合。我的建议是积极尝试在sharepoint中创建应用程序,并考虑如何将现有应用程序迁移到它。
#6
1
How about BI and reporting from an ERP? When we know IE is uncapable to handle a page with 10000 table rows (without pagination) Many don't realize but the success of a reporting tool depends on the performance of the grid object used - Excel and the SpreadSheet obj from the defunct Office Web Components are still the #1 in user's (accountants, managers, ceo) choice.
如何从ERP和BI报告?当我们知道IE无法处理具有10000个表行(没有分页)的页面时许多人没有意识到,但报告工具的成功取决于所使用的网格对象的性能 - Excel和来自已解散的Office Web的SpreadSheet obj组件仍然是用户(会计师,经理,首席执行官)选择的第一名。
#7
0
I think it depends on your environment. In our environment, we setup each department with their own pages and we use it for basic information, surveys, and the employee's homepage. We've built Google/Live Search and Weather.com widgets and roll RSS feeds using Tim Huer's RSS control.
我认为这取决于你的环境。在我们的环境中,我们为每个部门设置自己的页面,并将其用于基本信息,调查和员工主页。我们使用Tim Huer的RSS控件构建了Google / Live Search和Weather.com小部件并滚动RSS源。
#8
0
One thing you can do is to create web parts to provide access to data from existing applications. Initially they could simply be read-only views, but depending on your experience they could be fleshed out to allow writes.
您可以做的一件事是创建Web部件以提供对现有应用程序数据的访问。最初它们可能只是只读视图,但根据您的经验,它们可以充实以允许写入。
Another idea is to add links between SharePoint and your applications (assuming they're web based); that will at least allow a flow between them.
另一个想法是在SharePoint和您的应用程序之间添加链接(假设它们是基于Web的);这将至少允许它们之间的流动。
I haven't done it, but you could also theoretically skin SharePoint to look like the rest of your intranet.
我还没有这样做,但理论上你也可以将SharePoint看起来像你的内部网的其余部分。
#9
-1
Create libraries
Form libraries, documents libraries, slide libraries
表单库,文档库,幻灯片库
Create standard or custom lists
创建标准或自定义列表
Standard lists - announcements, tasks, contacts
标准列表 - 公告,任务,联系人
Custom lists - suppliers, contractors, inventories, orders
自定义清单 - 供应商,承包商,库存,订单
Setup secure team discussion areas
设置安全的团队讨论区域
Build shared team calendars
构建共享团队日历
Create simple workflow processes on documents and lists
在文档和列表上创建简单的工作流程