2.90:CMIS+ (Concept): Difference between revisions

Revision as of 12:57, 27 December 2019

All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints. CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms by using CMIS Bindings. These bindings include:

CMIS connections
FTP directories
Microsoft SharePoint sites
Email servers
NTFS file system.

The settings and logic used to connect Grooper to an individual storage platform is contained in its corresponding CMIS Binding. For example, the AppXtender Binding contains all the information Grooper uses to connect to the ApplicationXtender content management system. Which binding you use (and therefore which platform you connect to) is set by creating a CMIS Connection and choosing the appropriate binding as the "Connection Type".

Using this architecture, Grooper is able to create a more standardized import and export workflow. You now use CMIS Import and CMIS Export providers regardless of the storage platform. They connect to a CMIS Repository imported from a CMIS Connection and use that as Grooper's import or export path.

Only how you create a CMIS Connection differs from CMIS Binding to CMIS Binding, as each binding has a different way of connecting to it (You don't connect to an Outlook inbox the same way you connect to a Windows file folder, for example).

@@ Line 1: / Line 1: @@
-All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were CMIS endpoints.  CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms including:
+All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints.  CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms by using [[CMIS Bindings]]. These bindings include:
 * CMIS connections
@@ Line 7: / Line 7: @@
 * NTFS file system.
-The settings and programming used to connect Grooper to a storage platform is contained in a CMIS Binding.  For example, the [[AppXtender (CMIS Binding)|AppXtender Binding]] contains all the information Grooper uses to connect to the ApplicationXtender content management system.
+The settings and logic used to connect Grooper to an individual storage platform is contained in its corresponding [[CMIS Binding]].  For example, the [[AppXtender (CMIS Binding)|AppXtender Binding]] contains all the information Grooper uses to connect to the ApplicationXtender content management system.  Which binding you use (and therefore which platform you connect to) is set by creating a [[CMIS Connection]] and choosing the appropriate binding as the "Connection Type".
-Using this architecture, Grooper is able to create a more standardized import and export workflow.  The CMIS Import and CMIS Export providers are configured the same, regardless of the storage platform used.  They connect to a [[CMIS Repository]] imported from a previously created [[CMIS Connection]] and use that as Grooper's import or export path.
+Using this architecture, Grooper is able to create a more standardized import and export workflow.  You now use [[CMIS Import]] and [[CMIS Export]] providers regardless of the storage platform.  They connect to a [[CMIS Repository]] imported from a [[CMIS Connection]] and use that as Grooper's import or export path.
-Only how you create a [[CMIS Connection]] differs from [[CMIS Binding]] to CMIS Binding.
+Only how you create a [[CMIS Connection]] differs from [[CMIS Binding]] to CMIS Binding, as each binding has a different way of connecting to it (You don't connect to an Outlook inbox the same way you connect to a Windows file folder, for example).