CMIS Binding - Revision history

Randallkinard: Changed redirect target from CMIS+#CMIS Bindings (AKA Connection Types) to CMIS+ (Concept)#CMIS Bindings (AKA Connection Types)

2024-04-16T20:39:57Z

Changed redirect target from CMIS+#CMIS Bindings (AKA Connection Types) to CMIS+ (Concept)#CMIS Bindings (AKA Connection Types)

← Older revision		Revision as of 15:39, 16 April 2024
Line 1:		Line 1:
	#REDIRECT [[CMIS+#CMIS Bindings (AKA Connection Types)]]		#REDIRECT [[CMIS+ (Concept)#CMIS Bindings (AKA Connection Types)]]

Dgreenwood: Changed redirect target from CMIS+ to CMIS+#CMIS Bindings (AKA Connection Types)

2023-12-22T17:22:26Z

Changed redirect target from CMIS+ to CMIS+#CMIS Bindings (AKA Connection Types)

← Older revision		Revision as of 12:22, 22 December 2023
Line 1:		Line 1:
	#REDIRECT [[CMIS+]]		#REDIRECT [[CMIS+#CMIS Bindings (AKA Connection Types)]]

Dgreenwood: Redirected page to CMIS+

2023-09-28T18:49:36Z

Redirected page to CMIS+

← Older revision		Revision as of 13:49, 28 September 2023
Line 1:		Line 1:
	~~<onlyinclude>~~		#REDIRECT [[CMIS+]]
	~~<blockquote style="font-size:125%>~~
	~~A '''''CMIS Binding''''' provides connectivity logic for external storage platforms, allowing '''[[CMIS Connection]]''' objects to import and export content.~~
	~~</blockquote>~~

	~~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 distinct '''''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. The ''Exchange Binding'' contains necessary logic to connect to Microsoft Exchange email servers (like an Outlook inbox). The ''NTFS Binding'' allows connectivity to a Windows file system.

	'''''CMIS Bindings''''' are referenced when creating a '''CMIS Connection''' object and configuring its '''''Connection Type''''' property. Which binding you use (and therefore which platform you connect to) is set by the '''''Connection Type'''''.
	* First, the user selects which '''''CMIS Binding''''' they want to use, selecting which storage platform they want to connect to.
	* Second, the user enters connection settings for that binding, such as login information for many of the '''''CMIS Bindings'''''.
	~~</onlyinclude>~~
	~~=== Current CMIS Bindings ===~~

	~~Below is a list of all current platforms with their own '''''CMIS Bindings''''':~~

	* The [[AppXtender (CMIS Binding)\|ApplicationXtender]] document management platform.
	* The [[Box (CMIS Binding)\|Box]] Content Management System.
	* The FileBound document management 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.
	** The [[OneDrive (CMIS Binding)\|Microsoft OneDrive]] cloud storage platform.
	** [[SharePoint (CMIS Binding)\|Microsoft SharePoint]] sites.
	* [[FTP (CMIS Binding)\|FTP]] (File Transfer Protocol) and [[SFTP (CMIS Binding)\|SFTP]] (SSH File Transfer Protocol) servers.
	* The [[Box (CMIS Binding)\|Box]] cloud document management system.
	* [[IMAP (CMIS Binding)\|IMAP]] mail servers
	* The Microsoft Windows [[NTFS (CMIS Binding)\|NTFS]] file system.

	~~[[Category:Articles~~]]

Dgreenwood at 16:22, 9 December 2022

2022-12-09T16:22:11Z

← Older revision		Revision as of 11:22, 9 December 2022
Line 27:		Line 27:
	* [[IMAP (CMIS Binding)\|IMAP]] mail servers		* [[IMAP (CMIS Binding)\|IMAP]] mail servers
	* The Microsoft Windows [[NTFS (CMIS Binding)\|NTFS]] file system.		* The Microsoft Windows [[NTFS (CMIS Binding)\|NTFS]] file system.

			[[Category:Articles]]

Dgreenwood at 18:34, 5 April 2022

2022-04-05T18:34:48Z

← Older revision		Revision as of 13:34, 5 April 2022
Line 4:		Line 4:
	</blockquote>		</blockquote>

	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'''''.		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 distinct '''''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. The ''Exchange Binding'' contains necessary logic to connect to Microsoft Exchange email servers (like an Outlook inbox). The ''NTFS Binding'' allows connectivity to a Windows file system.

	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.		'''''CMIS Bindings''''' are referenced when creating a '''CMIS Connection''' object and configuring its '''''Connection Type''''' property. Which binding you use (and therefore which platform you connect to) is set by the '''''Connection Type'''''.

	'''''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.		* First, the user selects which '''''CMIS Binding''''' they want to use, selecting which storage platform they want to connect to.
	* Second, the user enters connection settings for that binding, such as login information for many of the '''''CMIS Bindings'''''.		* Second, the user enters connection settings for that binding, such as login information for many of the '''''CMIS Bindings'''''.
Line 14:		Line 13:
	=== Current CMIS Bindings ===		=== Current CMIS Bindings ===

	Below is a list of all current '''''CMIS Bindings''''':		Below is a list of all current platforms with their own '''''CMIS Bindings''''':

	* The [[AppXtender (CMIS Binding)\|ApplicationXtender]] document management platform.		* The [[AppXtender (CMIS Binding)\|ApplicationXtender]] document management platform.

Dgreenwood at 18:16, 5 April 2022

2022-04-05T18:16:55Z

← Older revision		Revision as of 13:16, 5 April 2022
Line 1:		Line 1:
	<onlyinclude>		<onlyinclude>
	<blockquote style="font-size:125%>		<blockquote style="font-size:125%>
	A ''CMIS Binding'' provides connectivity logic for external storage platforms, allowing '''[[CMIS Connection]]''' objects to import and export content.		A '''''CMIS Binding''''' provides connectivity logic for external storage platforms, allowing '''[[CMIS Connection]]''' objects to import and export content.
	</blockquote>		</blockquote>

	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~~.		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'''''.

	''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 of the ''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.

			'''''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.
			* Second, the user enters connection settings for that binding, such as login information for many of the '''''CMIS Bindings'''''.
	</onlyinclude>		</onlyinclude>
	=== Current CMIS Bindings ===		=== Current CMIS Bindings ===

	Below is a list of all current CMIS Bindings:		Below is a list of all current '''''CMIS Bindings''''':

	* The [[AppXtender (CMIS Binding)\|ApplicationXtender]] document management platform.		* The [[AppXtender (CMIS Binding)\|ApplicationXtender]] document management platform.

Dgreenwood at 15:59, 27 September 2021

2021-09-27T15:59:10Z

← Older revision		Revision as of 10:59, 27 September 2021
Line 14:		Line 14:
	* The [[AppXtender (CMIS Binding)\|ApplicationXtender]] document management platform.		* The [[AppXtender (CMIS Binding)\|ApplicationXtender]] document management platform.
	* The [[Box (CMIS Binding)\|Box]] Content Management System.		* The [[Box (CMIS Binding)\|Box]] Content Management System.
	* The [[FileBound ~~(CMIS Binding)\|FileBound]]~~ document management platform.		* The FileBound document management platform.
	* ~~[[CMIS (CMIS Binding)\|~~Content management systems]] using CMIS 1.0 or CMIS 1.1 servers.		* Content management systems using CMIS 1.0 or CMIS 1.1 servers.
	* The following Microsoft content platforms		* The following Microsoft content platforms
	** The [[Exchange (CMIS Binding)\|Microsoft Exchange]] mail server platform.		** The [[Exchange (CMIS Binding)\|Microsoft Exchange]] mail server platform.

Dgreenwood at 16:07, 24 September 2021

2021-09-24T16:07:04Z

← Older revision		Revision as of 11:07, 24 September 2021
Line 1:		Line 1:
	<onlyinclude>		<onlyinclude>
	<blockquote style="font-size:~~14pt~~>		<blockquote style="font-size:125%>
	A ''CMIS Binding'' provides connectivity logic for external storage platforms, allowing '''[[CMIS Connection]]''' objects to import and export content.		A ''CMIS Binding'' provides connectivity logic for external storage platforms, allowing '''[[CMIS Connection]]''' objects to import and export content.
	</blockquote>		</blockquote>

Dgreenwood at 15:50, 24 September 2021

2021-09-24T15:50:51Z

← Older revision		Revision as of 10:50, 24 September 2021
Line 8:		Line 8:
	''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 of the ''CMIS Bindings''.		''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 of the ''CMIS Bindings''.
	</onlyinclude>		</onlyinclude>

	=== Current CMIS Bindings ===		=== Current CMIS Bindings ===

Dgreenwood at 15:42, 24 September 2021

2021-09-24T15:42:36Z

← Older revision		Revision as of 10:42, 24 September 2021
Line 4:		Line 4:
	</blockquote>		</blockquote>

	Grooper's [[CMIS+]] ~~infrastructure~~ 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.		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.

	''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. 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~~.		''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 of the ''CMIS Bindings''.
	</onlyinclude>		</onlyinclude>