But when I ask IT professionals in the logistics industry: “how is it used in your company?...The logistics industry is document driven
And the main reason for these fears is that to do that, you must integrate with the other applications/systems/databases/etc. in the organization. Don’t get me wrong, SharePoint’s API and features make it a great system to integrate with. I am talking about the fear of integrating to other systems; these can present big challenges
Governance. It’s what content management, records management, business process management, SharePoint, and myriad other information systems have in common. It’s one of the things that complicates any move to the cloud. And it’s too often overlooked as disparate technical...
Hybrid Search Deep-dive: SharePoint Server 2013 & Office 365 Integration One of the most common configurations that is starting to emerge into today’s IT landscape is that of a hybrid cloud architecture and is something you must plan for in your organization's long-term SharePoint and/or Office 365 roadmap . SharePoint Server 2013 can integrate with cloud-based solutions such as Office 365 and/or SharePoint Online in a secure and federated manner that will allow a user with proper permission’s search to return results from both on-premises in SharePoint Server 2013 as well as in Office 365 in the cloud, as shown in image below. Hybrid Cloud (Hybrid SharePoint 2013 & Office 365) Architecture Summary Overview The following is a summary of a hybrid SharePoint Server 2013 and Office 365 search integration and the related components: The remote SharePoint Index allows for the search to be federated between the on-premises SharePoint Server 2013 environment and the cloud-based Office 365 environment for a hybrid cloud environment architecture This sample configuration provides query capability and additional configurations can be implemented to support crawl Hybrid Cloud Architecture Overview The hybrid cloud architecture requires: Configuration of an OAuth trust between your on-premises SharePoint 2013 farm and your Office 365 tenancy The creation of a result source for the remote farm An externally addressable endpoint for the on-premises farm (reverse proxy) that can be reached via the Office 365 sites This sample configuration allow you to query the result source directly or create a query rule to also allow for user queries to the cloud-based Office 365 or remote farm when needed A token is created for the user and security trimmed results are returned which requires 2-way AD synchronization between the SharePoint Server 2013 on-premises environment and Office 365 By using a query rule you can integrate the results from both farms into a single display for users and tailor the UI as desired The results of a hybrid cloud search from a user searching both SharePoint Server 2013 and Office 365 : Search Web Parts in SharePoint 2013, Office 365 and/or SharePoint Online There are several new web parts for Search in this latest release of SharePoint that allow users an entire new experience when conducting search
In my post about BPOS I focused on what I thought was the most relevant version, discussing the Dedicated licensing over the Standard (multi-tenant) licensing, because it was my opinion that this would be what most large organizations would adopt due to the fact that it was the version partners would be best able to add-value to/integrate with. Not to leave smaller companies out of the discussion, but they usually don’t have the same stringent requirements and complex custom integration requests the large enterprises have
Visual Studio 2010 is the primary tool for development in SharePoint 2010 and it comes with out of the box integration support for Team Foundation Server (TFS) 2010...Note: While TSF has better integration with Visual Studio, it does require licenses to be purchased
1 Comment - no search term matches found in comments.
SharePoint as a centralized, enterprise-level web-based collaboration platform has changed the way many businesses work and manage information, and with every iteration there are platform improvements as well as more tools and integration with fast-growing technologies and practices
Enter Information Rights Management (IRM). Integrating IRM with DMS extends the security of repositories to protect content wherever it goes, within the confines of the DMS and beyond
Last year's conference announced the integration of Yammer into the O365 family, and the promise that Microsoft would learn from the start-ups' iterative development cycle
3 Comments - no search term matches found in comments.
Over the years we have designed and/or implemented virtually everything on the SharePoint platform including: Feature rich Business Process Automation portals (link points to a case study on a SharePoint-based Accounts Payable system) with complex workflows and external system integration Global Enterprise Portals with over 100,000 planned users spanning multiple countries Public facing SharePoint 2007 and 2010 sites Commercial software built on the SharePoint platform Web-based line of business applications that leverage SharePoint but look nothing like a portal Products for visually designing, documenting and deploying SharePoint without writing code I have been very fortunate in that I’ve worked alongside several of the top experts in the SharePoint space including the seven SharePoint MVPs that have graced our halls (plus a handful more that we’ve partnered with). Working with these people has given me many insights into not only the technical aspects of SharePoint itself, but also into other considerations surrounding the implementation of SharePoint including Planning, Adoption, Governance, Information Architecture as well as Coexistence and Integration Strategies