This is an archive related to a previous version of Esri Maps for SharePoint. If you need the current version go to http://doc.arcgis.com/en/maps-for-sharepoint/.
Business data often resides in more than just one place. Esri Maps for SharePoint leverages SharePoint's Business Connectivity Services (BCS) to retrieve data that resides in Microsoft SQL Server (including SQL Server Express) and pull it in to SharePoint. BCS creates an external content type in SharePoint that allows for read and write access to the connected table. This means that not only can SQL Server external content be added to a connected list in SharePoint, changes made to the list by the Esri Maps Connect workflow, including location information and enriched attributes, can be written back to the original table.
The Esri Maps Connect workflow walks you through the process of connecting to your SQL Server database, selecting the applicable table, creating the connected list, spatially enabling the list, and enriching the list with demographic and other contextual data, all with no custom code or programming. Once the connected list has been created, the list data can be added to the ArcGIS Map Web Part and the Esri Maps Web Part.
The Esri Maps Connect workflow creates a SharePoint list that maintains a connection to the underlying SQL server database. The SharePoint Business Connectivity Service (BCS) uses SharePoint timer jobs to maintain and update the connection between the SQL Server database and the connected SharePoint list. By default, the timer job runs once every hour, but this setting can be changed in the SharePoint Central Administration.
When the Esri Maps Connect workflow completes, the result is a regular SharePoint list, not an external list. That said, the fields created from the SQL Server database are of an external type, and edits made to these fields in SharePoint cannot be passed back to the database. SharePoint can only pass back the fields it has created, such as for the Esri Maps Locate workflow and GeoEnrichment.
The Esri Maps Connect workflow supports external content from Microsoft SQL Server 2008 R2, 2012, and 2014, including the SQL Server Express editions. The external content must contain data that can be spatially enabled (geocoded), such as an address, U.S. city, U.S. state, ZIP code, or world city. Alternatively, the table can contain an existing SQL server spatial data type (geography or geometry) column that is then converted by the Esri Maps Connect workflow for use in Esri Maps for SharePoint. If the external table has an existing spatial column that contains no data, the Esri Maps Connect workflow populates the column based on other location information in the table (for example, address). If no spatial column exists, the Esri Maps Connect workflow creates a geography spatial type column named EsriShape with a Spatial Reference Identifier (SRID) of 4326 (WGS 84). The EsriShape field supports all geometries including points, lines, and polygons. In all scenarios, the external content can be geoenriched with additional geographic data variables from ArcGIS.
The Esri Maps Connect workflow requires the following prerequisites:
The following steps describe the first part of the Esri Maps Connect workflow and cover signing in to ArcGIS and creating a connection to your external content. You must complete these steps before you can spatially enable (geocode) and geoenrich your list items.
The Esri Maps Connect workflow appears.
When the workflow completes successfully, the external content type is saved to the site collection, allowing you to reuse the external content type, if necessary.
External content types are a key feature of SharePoint's Business Connectivity Services that store descriptions of connectivity information and data definitions. For detailed information, see External content types in SharePoint 2013.
For the database server, enter <server name>\<instance>. For the database name, enter the name of the applicable database. You will select a table from the database in the next step.
The next set of steps describe the second part of the Esri Maps Connect workflow and cover spatially enabling (geocoding) and optionally enriching your data with additional geographic variables. This part of the Esri Maps Connect workflow is identical to the Esri Maps Locate workflow used to spatially enable existing SharePoint lists.