2021:CMIS+ (Concept): Difference between revisions

← Older edit

Latest revision as of 11:14, 5 August 2025

This article is about an older version of Grooper.

Information may be out of date and UI elements may have changed.

CMIS+ is a conceptual term that refers to Grooper's connectivity architecture to external storage platforms. CMIS+ standardizes connections to a variety of content management system based on the CMIS standard. This provides a standardized setup to allow Grooper to interoperate with both CMIS compliant systems and non-CMIS systems. It further provides normalized access to document content and metadata for import (CMIS Import) and export (CMIS Export) operations.

All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a CMIS Connection in Grooper.

The CMIS Connection's Connection Type determines which storage platform you're connecting to.

For example, if you wanted to connect to a Windows file system, you would create a CMIS Connection configured with an NTFS connection.

Once connected to a platform, Grooper can import from and export to that platform by importing a CMIS Repository that represents a location (usually a folder) in the storage platform.

For example, if you wanted to import documents from a Windows folder named "Grooper Imports", you would first import that folder location as a CMIS Repository in Grooper. Then, you would point to that CMIS Repository when importing the documents into Grooper.

This provides Grooper the necessary infrastructure to import, access, and publish documents and their metadata to both CMIS and non-CMIS storage platforms, including on-premise and cloud based platforms.

About CMIS+

"CMIS" stands for "Content Management Interoperability Services". It is an open standard that allows different content management systems to inter-operate over the Internet. Grooper expanded on this idea in version 2.72 to create our "CMIS+" architecture. CMIS+ unifies all content platforms under a single framework as if they were traditional CMIS endpoints.

Now, Grooper connects to any external storage platform by creating and configuring a CMIS Connection (not just CMIS 1.0 or CMIS 1.1 servers).

Once a CMIS Connection is created, Grooper can "interoperate" with these platforms.
"Interoperability " means Grooper has the same access to control the system as a human being does.
Grooper has a "one-to-one" connection to the platform, allowing full and total control.

Using this architecture, Grooper is able to create a simpler and more efficient import and export workflow, using a variety of storage platforms.

You now use CMIS Import providers and CMIS Export, regardless of the storage platform.

Anatomy of a CMIS Connection

When connecting Grooper to external storage platforms, you'll start by creating a CMIS Connection. There are three important parts to understanding a CMIS Connection

The CMIS Connection itself.
It's Connection Type (and the "CMIS Binding" you select).
It's child CMIS Repositories

FYI

A "repository", in computer science, is a general term for a location where data lives. Different systems refer to "repositories" in different ways.

An email inbox could be a repository. A folder in Windows could be a repository. A folder in a Box account could be a repository. A cabinet in ApplicationXtender could be a repository.
We standardize the various terms used by various storage platforms to simply "repository".
Put simply, it's a place to put stuff.

For newer users, the difference between a CMIS Connection and a CMIS Repository can be confusing (and it doesn't help that some people use the terms interchangeably!). The key distinction is as follows:

The CMIS Connection is the object in Grooper that Grooper uses to establish a connection to some external system.
- The Connection Type determines which specific platform you're connecting to, and any settings required to connect to it.
CMIS Repositories represent a location within the connected platform.
- These are created after creating the CMIS Connection.
- Typically, these represent a folder location in the storage platform.

For example, imagine you want to use Grooper to connect to a Windows file system folder on some networked server.

First, they would create a new CMIS Connection
Then they would choose NTFS for its Connection Type
Then they would import the folder location as a CMIS Repository
- It is then this CMIS Repository Grooper will point to when importing from or exporting to this folder location.
- The CMIS Connection is just the thing that allows Grooper to connect to Windows in this case. It is the CMIS Repository that acts as the Windows file system folder in Grooper.

To reiterate, there are three basic steps involved to connect Grooper to external storage platforms:

Create a CMIS Connection
Configure its Connection Type to select which platform you want to connect to (and enter any settings to connect to that platform).
Import storage locations as one or more CMIS Repositories, which are created as children of the CMIS Connection.

FYI

Importing a CMIS Repository is not the same as importing documents to a new Batch.

"Importing" here is more like bringing the repository into a framework Grooper can use.
Upon importing the repository, Grooper has full file access to that location in the storage platform.

CMIS Bindings (AKA Connection Types)

How you configure a CMIS Connection only 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.
Thus, the property configuration for the Exchange binding is different from the NTFS binding.

A CMIS Binding provides connectivity to external storage platforms for content import and export. Each individual CMIS Binding contains the settings and logic required to exchange documents between Grooper and each distinct platform.

The Exchange Binding contains all the information Grooper uses to connect to Microsoft Exchange email servers (i.e. Outlook inboxes).
The AppXtender Binding contains all the information Grooper uses to connect to the ApplicationXtender content management system.
The NTFS Binding contains all the information Grooper uses to connect to a Windows file system.
And so on.

When creating a CMIS Connection the first step to configure the Connection Type property.

When you select a Connection Type you're selecting which platform you want to connect to (using a CMIS Binding).
- First, you select which platform you want to connect to (which CMIS Binding you want to use)
- Then, you enter connection settings unique to the platform (any values the CMIS Binding needs to connect to the platform, like login information for many platforms)

Current CMIS Connection Types

Grooper can connect to the following storage platforms using below using CMIS Bindings:

The ApplicationXtender document management platform.
The Box cloud storage platform.* The Microsoft Windows NTFS file system.
The following Microsoft content platforms
- The Microsoft Exchange mail server platform.
- The Microsoft OneDrive cloud storage platform.
- Microsoft SharePoint sites.
FTP (File Transfer Protocol) and SFTP (SSH File Transfer Protocol) servers.
IMAP mail servers
Content management systems using CMIS 1.0 or CMIS 1.1 servers.
The FileBound document management platform.
The IBM FileNet platform.

@@ Line 1: / Line 1: @@
-<onlyinclude>
+__NOINDEX__
-<blockquote style="font-size:125%">
+{{AutoVersion}}
-CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms.  All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints by using ''[[CMIS Binding]]s''.
-</blockquote>
+<blockquote>{{#lst:Glossary|CMIS+}}</blockquote>
+All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.
+The '''CMIS Connection's''' '''''Connection Type''''' determines which storage platform you're connecting to.
+* For example, if you wanted to connect to a Windows file system, you would create a '''CMIS Connection''' configured with an '''''NTFS''''' connection.
+Once connected to a platform, Grooper can import from and export to that platform by importing a '''CMIS Repository''' that represents a location (usually a folder) in the storage platform.
+* For example, if you wanted to import documents from a Windows folder named "Grooper Imports", you would first import that folder location as a '''CMIS Repository''' in Grooper.  Then, you would point to that '''CMIS Repository''' when importing the documents into Grooper.
 This provides Grooper the necessary infrastructure to import, access, and publish documents and their metadata to both CMIS and non-CMIS storage platforms, including on-premise and cloud based platforms.
-</onlyinclude>
-== About CMIS and CMIS Connections ==
+<section begin="cmisplus" />
+== About CMIS+ ==
+"CMIS" stands for "Content Management Interoperability Services".  It is an open standard that allows different content management systems to inter-operate over the Internet. Grooper expanded on this idea in version 2.72 to create our "CMIS+" architecture. CMIS+ unifies all content platforms under a single framework as if they were traditional CMIS endpoints.
+Now, Grooper connects to any external storage platform by creating and configuring a '''CMIS Connection''' (not just CMIS 1.0 or CMIS 1.1 servers).
+* Once a '''CMIS Connection''' is created, Grooper can "interoperate" with these platforms.
+* "Interoperability " means Grooper has the same access to control the system as a human being does.
+* Grooper has a "one-to-one" connection to the platform, allowing full and total control.
-[[CMIS]] stands for "Content Management Interoperability Services".  It is an open standard that allows different content management systems to inter-operate over the Internet.  This standard protocol allows Grooper to use many different platforms for importing and exporting documents and their contents.  Once a '''[[CMIS Connection]]''' is created, Grooper can exchange documents with these platforms.  "Interoperability " means Grooper has the same access to control the system as a human being does.  It is a "one-to-one" connection to the platform, allowing full and total control.
+Using this architecture, Grooper is able to create a simpler and more efficient import and export workflow, using a variety of storage platforms.
+* You now use '''''CMIS Import''''' providers and '''''CMIS Export''''', regardless of the storage platform.
-Upon connecting to an external digital storage platform, Grooper will be able to see the "repositories" associated with it.  A repository, in computer science, is a general term for a location where data lives.
+=== Anatomy of a CMIS Connection ===
-Different systems refer to "repositories" in different ways.
+When connecting Grooper to external storage platforms, you'll start by creating a '''CMIS Connection'''.  There are three important parts to understanding a '''CMIS Connection'''
-* An email inbox could be a repository.  A folder in Windows could be a repository.  A cabinet in ApplicationXtender could be a repository.
+* The '''CMIS Connection''' itself.
-* We standardize the various terms used by various storage platforms to simply "repository".  Put simply, it's a place to put things.
+* It's '''''Connection Type''''' (and the "'''''CMIS Binding'''''" you select).
+* It's child '''CMIS Repositories'''
-[[File:2021-cmis-connection-about-01.png|right]]
+{|class="fyi-box"
+|
+'''FYI'''
+|
+A "repository", in computer science, is a general term for a location where data lives.  Different systems refer to "repositories" in different ways.
+* An email inbox could be a repository.  A folder in Windows could be a repository.  A folder in a Box account could be a repository.  A cabinet in ApplicationXtender could be a repository.
+* We standardize the various terms used by various storage platforms to simply "repository".
+* Put simply, it's a place to put stuff.
+|}
-These repositories are "imported" into Grooper as a '''CMIS Repository''' object, as a child of the '''CMIS Connection''' object.  This doesn't import data into Grooper in the traditional sense of importing documents into a new '''Batch'''.  "Importing" here is more like bringing the repository into a framework Grooper can use.  Upon importing the repository, Grooper has full file access to that location in the storage platform.
+For newer users, the difference between a '''CMIS Connection''' and a '''CMIS Repository''' can be confusing (and it doesn't help that some people use the terms interchangeably!). The key distinction is as follows:
+* The '''CMIS Connection''' is the object in Grooper that Grooper uses to establish a connection to some external system.
+** The '''''Connection Type''''' determines which ''specific'' platform you're connecting to, and any settings required to connect to it.
+* '''CMIS Repositories''' represent a location ''within'' the connected platform.
+** These are created ''after'' creating the '''CMIS Connection'''.
+** Typically, these represent a folder location in the storage platform.
-For our purposes, repositories are like filing cabinets full of documents.  Once a connection is established, it's like giving Grooper a key to that cabinet.  You can open the various drawers of that cabinet.  You can pull out files and put files into.  The storage platform or content management system is like the cabinet.
+For example, imagine you want to use Grooper to connect to a Windows file system folder on some networked server.
-* The '''CMIS Connection''' object is like the key.
+* First, they would create a new '''CMIS Connection'''
-* The '''CMIS Repository''' object is like a drawer in the cabinet.
+* Then they would choose ''NTFS'' for its '''''Connection Type'''''
-* You "connect" to the cabinet by turning the key.  You "import" the repository by opening the drawer.   Now you can see there are documents in there!  You can take them out.  You can read them and put them back in.  You can put new ones in.  You can use this "open" connection to the "drawer" however you need.
+* Then they would import the folder location as a '''CMIS Repository'''
+** It is then this '''CMIS Repository''' Grooper will point to when importing from or exporting to this folder location.
+** The '''CMIS Connection''' is just the thing that allows Grooper to connect to Windows in this case.  It is the '''CMIS Repository''' that acts as the Windows file system folder in Grooper.
-== CMIS+ Architecture ==
-Grooper expanded on this idea in version 2.72 to create our CMIS+ architecture. CMIS+ unifies all content platforms under a single framework as if they were traditional CMIS endpoints.  Prior to version 2.72, there was only one type of '''CMIS Connection''', a true CMIS connection using CMIS 1.0 or CMIS 1.1 servers.  Now, connections to additional non-CMIS document storage platforms can be made via "''[[CMIS Binding]]s''".   This provides standardized access to document content and metadata across a variety of external storage platforms.
+To reiterate, there are three basic steps involved to connect Grooper to external storage platforms:
+# Create a '''CMIS Connection'''
+# Configure its '''''Connection Type''''' to select which platform you want to connect to (and enter any settings to connect to that platform).
+# Import storage locations as one or more '''CMIS Repositories''', which are created as children of the '''CMIS Connection'''.
-Using this architecture, Grooper is able to create a simpler and more efficient import and export workflow, using a variety of storage platforms.  You now use the [[CMIS Import]] '''''Import Provider''''' and the ''[[CMIS Export]]'' '''''Export Type''''', 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.
+{|class="fyi-box"
+|
+'''FYI'''
+|
+Importing a '''CMIS Repository''' is not the same as importing documents to a new '''Batch'''.
+* "Importing" here is more like bringing the repository into a framework Grooper can use.
+* Upon importing the repository, Grooper has full file access to that location in the storage platform.
+|}
-How you create a '''CMIS Connection''' only 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.  Thus, the property configuration for the ''Exchange'' binding is different from the ''NTFS'' binding.
+=== CMIS Bindings (AKA Connection Types) ===
-=== CMIS Bindings ===
+How you configure a '''CMIS Connection''' only 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.
+* Thus, the property configuration for the '''''Exchange''''' binding is different from the '''''NTFS''''' binding.
-A ''CMIS Binding'' provides connectivity to external storage platforms for content import and export.  Grooper's CMIS+ architecture expands connectivity from traditional CMIS servers to a variety of on-premise and cloud-based storage platforms by exposing connections to these platforms as ''CMIS Bindings''.
-Each individual ''CMIS Binding'' contains the settings and logic required to exchange documents between Grooper and each distinct platform.  For example, the ''AppXtender Binding'' contains all the information Grooper uses to connect to the ApplicationXtender content management system.
+A '''''CMIS Binding''''' provides connectivity to external storage platforms for content import and export.  Each individual '''''CMIS Binding''''' contains the settings and logic required to exchange documents between Grooper and each distinct platform.
+* The '''''Exchange Binding''''' contains all the information Grooper uses to connect to Microsoft Exchange email servers (i.e. Outlook inboxes).
+* The '''''AppXtender Binding''''' contains all the information Grooper uses to connect to the ApplicationXtender content management system.
+* The '''''NTFS Binding''''' contains all the information Grooper uses to connect to a Windows file system.
+* And so on.
-''CMIS Bindings'' are used when creating a '''CMIS Connection''' object.  The first step to creating a '''CMIS Connection''' is to configure the '''''Connection Type''''' property.   Which binding you use (and therefore which platform you connect to) is set here.  First, the user selects which ''CMIS Binding'' they want to use, selecting which storage platform they want to connect to.   The second step is to enter the connection settings for that binding, such as login information for many bindings.
+When creating a '''CMIS Connection''' the first step to configure the '''''Connection Type''''' property.
+* When you select a '''''Connection Type''''' you're selecting which platform you want to connect to (using a '''''CMIS Binding''''').
+** First, you select which platform you want to connect to (which '''''CMIS Binding''''' you want to use)
+** Then, you enter connection settings unique to the platform (any values the ''''' CMIS Binding''''' needs to connect to the platform, like login information for many platforms)
-=== Current CMIS Bindings ===
+==== Current CMIS Connection Types ====
-Grooper can connect to the following storage platforms using below using ''CMIS Bindings'':
+Grooper can connect to the following storage platforms using below using '''''CMIS Bindings''''':
 * The [[AppXtender (CMIS Binding)|ApplicationXtender]] document management platform.
-* The [[Box (CMIS Binding)|Box]] cloud storage platform.
+* The [[Box (CMIS Binding)|Box]] cloud storage platform.* The Microsoft Windows [[NTFS (CMIS Binding)|NTFS]] file system.
-* The FileBound document management platform.
-* The IBM FileNet platform.
-* Content management systems using CMIS 1.0 or CMIS 1.1 servers.
 * The following Microsoft content platforms
 ** The [[Exchange (CMIS Binding)|Microsoft Exchange]] mail server platform.
@@ Line 57: / Line 104: @@
 * [[FTP (CMIS Binding)|FTP]] (File Transfer Protocol) and [[SFTP (CMIS Binding)|SFTP]] (SSH File Transfer Protocol) servers.
 * [[IMAP (CMIS Binding)|IMAP]] mail servers
-* The Microsoft Windows [[NTFS (CMIS Binding)|NTFS]] file system.
+* Content management systems using CMIS 1.0 or CMIS 1.1 servers.
+* The FileBound document management platform.
+* The IBM FileNet platform.
+<section end="cmisplus" />
 == See Also ==
@@ Line 64: / Line 114: @@
 * '''[[CMIS Import]]'''
 * '''[[Export (Activity)]]'''
-[[Category:Articles]]
-[[Category:Version 2021]]