SharePoint CMIS bridge
The CMIS bridge is a connection bridge allowing you to retrieve files from a CMIS enabled SharePoint repository. These files will be imported into Matrix as system assets (such as images, text files, and more) under the CMIS bridge. These assets can be edited, linked, and moved around the system just like any other asset.
| The CMIS bridge currently only supports connections to Microsoft SharePoint 2010 document repositories with basic authentication enabled. |
Once created, you can configure the settings of the CMIS bridge on its associated asset screens. These screens are often the same or similar to those for a standard page and are described in the Asset screens documentation. This documentation will describe the Details screen, which is different for a CMIS bridge.
Details screen
The Details screen of a CMIS bridge allows you to configure the asset.
Read the Asset screens documentation for more information about the Status, Future status, and Thumbnail sections
Connection setup
The Connection setup section allows you to configure the connection to the CMIS compatible SharePoint repository. The Connection setup section is shown in the figure.
The following fields are available:
- WSDL URLs
-
Enter the WSDL URLs of the services of the CMIS server. The following WSDL URLs must be configured:
- ObjectService
-
Enter the WSDL URL of the object service of the CMIS server. This service controls the functionality of individual objects on the repository, for example, uploading document objects to Matrix.
- NavigationService
-
Enter the WSDL URL of the navigation service of the CMIS server. This service navigates the object hierarchy of the repository, displaying its documents and folders.
- RepositoryService
-
Enter the WSDL URL of the repository service of the CMIS server. This service controls the functionality of the repository, such as creating the connection to the repository.
To connect to SharePoint subsite document libraries, include the subsite path in the WebURL component of the WSDL URLs. For example, http://www.example.com/site1/_vti_bin/cmis/soap/ObjectService.svc?wsdl - Username
-
Enter the username to use to connect to the SharePoint server.
- Password
-
Enter the password to use to connect to the SharePoint server. This password must be entered twice for validation purposes.
- WS-Security header
-
Select whether a web services security header will be sent on SOAP requests to the repository. This field may be required if basic HTTP authentication is not sufficient.
Synchronise options
This section allows you to manage the results of the CMIS bridge. The Synchronize options section of the Details screen is shown in the figure.
The following fields are available:
- Synchronize now?
-
Selecting this button and selecting Save will synchronize Matrix with the connected CMIS enabled SharePoint repository. This synchronization process will trash any old files under the CMIS bridge (and their links), update any existing files that have been modified on the repository and create new files. Updating files under the CMIS bridge that are live will place them under construction.
Assets under the CMIS bridge are updated and created automatically by the sync CMIS bridges scheduled job, set to run on a nightly basis. You can change the frequency and time this job runs on its Details screen. Read the Scheduled jobs manager documentation for more information. - Repository name
-
Enter the name of the repository to connect with on the CMIS bridge. Any files to be imported on the CMIS bridge should be direct children of this repository (that is, not under sub-folders). The repository name is case-sensitive.
When a valid repository name is supplied to a connected CMIS bridge, the Metadata field options will appear, as shown in the figure.
The Metadata field options allow you to specify metadata fields to map the CMIS properties of returned documents. These metadata fields must belong to a metadata schema applied to the CMIS bridge, with cascading enabled.
The CMIS properties available for metadata mapping will depend on the document repository specified in the repository name field. Additional custom fields created for the document library will dynamically appear in this section and be made available for metadata mapping.
The following CMIS properties require metadata mapping for synchronization:
- Modified
-
Select a metadata date field with the default display format (d/m/Y H:i:s) to store the last modified date of returned documents.
- cmis:objectid
-
Select a metadata text field to store the CMIS ID of returned documents.
Example: Adding a CMIS bridge
To create and configure a CMIS bridge, follow the steps outlined below.
-
Create a CMIS bridge asset.
-
On the Details screen, enter the ObjectService, NavigationService, and RepositoryService WSDL URLs of the SharePoint server to which you want to connect.
-
Enter the username and password of your SharePoint server.
-
In the Repository name field, enter the name of the document library to be bridged. This field is case-sensitive.
-
Select Save. the Metadata fields set up section will be displayed, as shown in the figure.
You need to specify metadata fields to map the modified and cmis:objectid properties of returned documents. These are required on the CMIS bridge before it can be synchronized.
-
In the Modified field, select a metadata DateTime field of a metadata schema applied to the CMIS bridge. This field will be used to store the last modified date of returned documents.
-
In the cmis:objectid field, select a metadata text field of a metadata schema applied to the CMIS bridge. This field will be used to store the CMIS ID of returned documents.
You can select additional metadata fields to map the remaining property fields of the document repository.
-
Select the Synchronise now button and select Save. The files of the specified repository will be imported into Matrix as fully functional system assets, as shown.
Now that the CMIS bridge has been created and synchronized with a CMIS compatible SharePoint repository, you can use the repository documents within your system.