FontoXML requires an external content repository to provide permanent storage of documents. This chapter describes the steps to take to integrate FontoXML in your environment. There are three different ways of integrating FontoXML with a Content Management System or Cloud storage. Each of these approaches enable the integration of FontoXML for different environments and systems.
- Requirements — In order to integrate FontoXML with your CMS, a number of requirements should be met by the CMS.
- Getting started — To make FontoXML work with documents in your CMS, a couple of steps need to be executed. The editor must be hosted by the CMS and a number of endpoints should be implemented.
- CMS Concepts — This chapter describes the concepts and terminology used throughout the documentation on the CMS integration.
- Use cases — This chapter describes several use cases which illustrates the ways the CMS connector can work.
- Implementation concerns — This section provides information about concerns that need to be thought of when implementing the CMS endpoints of these API contracts.
- FontoXML iframe CMS connector — The IFrame connector may be used to communicate with FontoXML using an IFrame. This may be necessary when it is technically infeasible to implement the endpoints in a CMS.
- Best practices for CMS integration — This chapter describes the best practices for integrating FontoXML with the CMS. It describes how the CMS endpoints should work.
FontoXML Standard CMS Connector
Using the FontoXML Standard CMS Connector, FontoXML connects directly to the Content Management System. This is done by making HTTP requests to FontoXML specific endpoints which must be implemented in the Content Management System. The specific endpoint specifications can be found in the CMS connectors API documentation.
FontoXML iframe CMS Connector
The FontoXML iframe CMS connector is a wrapper around the FontoXML Standard CMS Connector. Instead of sending HTTP requests to the Content Management System, it sends the same requests using HTML5 Web Messaging. This means all the requests are send to the parent window of the FontoXML editor instance (typically FontoXML is embedded in a (near) full body iframe). The parent frame can then in turn use, for example, native client side Content Management System methods for talking to the Content Management System.
FontoXML Demo Connectors
Fonto Connectors provides out-of-the-box connectivity for demo-grade integration of an FontoXML Editor instance with your existing Content Management System, Document Management System or Cloud storage service. FontoXML Connectors provides a way to connect your configured FontoXML Editor to your Content Management System or Cloud storage without the need to implement the contracts in the Content Management System.
Simply configure the Google Drive or Microsoft OneDrive connector for a quick proof-of-concept. For the next stage, or at any time of your choosing, the Cloud connector is simply swapped with a connector for the Enterprise Content or Document Management System of your choice.
The FontoXML Demo Connectors product is intended for demo-grade integration only. It is not intended for production use.
Choosing the right Connector
Different connectors have different requirements. Choose which connector fits your use-case best based on the following statements:
|FontoXML Standard CMS Connector||FontoXML iFrame CMS Connector||FontoXML Demo Connectors|
|Need to implement additional FontoXML editor specific endpoints other then the endpoints defined by the FontoXML Standard CMS Connector|
|The CMS does not support CMIS or WebDAV|
|Cannot host additional server applications|
|Cannot host the FontoXML editor on the CMS domain|
|Cannot implement new HTTP endpoints in the CMS|
|Production grade integration|
|Connect to a Content Management System using industry standards|
|Need to connect to the CMS using CMIS|
|Need to connect to the CMS using WebDAV|
|Connect to Cloud storage|
|Need to connect to Google Drive directly|
|Need to connect to Microsoft OneDrive directly|