Skip to main content

Nuxeo

Nuxeo is a software company making an open source content management system.
More info on Nuxeo


Authentication Connection

The Nuxeo Authentication Connector contains configuration to authenticate with aNuxeo server for discovery, content sourcing, and content output. The Nuxeo Auth connector, like the other Nuxeo connectors, leverages Nuxeo's Java Client to communicate with your Nuxeo server. Click here for more information on setting up an Authentication Connection.

Configuration Options

  • Name: The name of the connector.
  • Nuxeo Username: The name of the user to authenticate with Nuxeo
  • Nuxeo Password: The password of the user authenticating with Nuxeo
  • Nuxeo URL: The url to the nuxeo ****endpoint
  • Use Caching: (required) Should the client use caching when making authentication requests?
  • Session Timeout: Maximum session timeout in ms
  • Transaction Timeout: Maximum transaction timeout in ms
  • Nuxeo Provider ID: The provider ID set in the Nuxeo's configuration for MIP (Manage-in-place/ Content federation).

Discovery Connector

Discovery Configuration with Auth

If you have created your Nuxeo Authentication Connector you can use it to facilitate Discovery by filling in the following fields.

  • Name: Unique Name for the Discovery Connection to identify it in the UI.
  • Authentication Connector: Select yourNuxeo Authentication Connector.
  • Collection: The name of your Mongo DB collection

Integration Connection

The Nuxeo Integration configuration only requires you to set an Authentication connection.

Also note that you can connect to a Nuxeo server using a CMIS repository connector and CMIS authentication connector as well. Provided are links to theCMIS Repository connector documentation and theCMIS Authentication connector documentation.

In the Server settings of the CMIS connector, your server for an Atom binding will look like as follows:(NUXEO_SERVER)/nuxeo/atom/cmis

Click here for more information on setting up an integration connection.

Integration Connection Configuration

  • Connection Name: This is a unique name given to the connector instance upon creation.
  • Description: A description of the connector to help identify it better.
  • Authentication Connection: Nuxeo Authentication

Job Configuration

Setting the Nuxeo query is done on a job by job basis. If a job has a Nuxeo repository set, a Nuxeo Query tab will appear at the top of the job for configuration. Click here for details on how to set up an integration job.


Content Service Connection

The Nuxeo Content Service Connection provides a full ECM API for interacting with files, folders, metadata, versions, and renditions. This includes functionality like check-in/out, upload new files, modify metadata, upload new versions, create folders, etc... More info

Basic Configurations

  • Connector ID: A unique identifier for this connection i.e. simflofy_demo(Alphanumeric, dashes and underscore characters only)
  • Description: The text that will be displayed on drop-downs etc. to identify this connection.
  • Type: The type of Search Connection (Solr, Mongo, Alfresco Faceted etc.)
  • Connection URL: Your server's web address
  • Security Mode: This is how to authenticate with the back-end search
  • Username: to authenticate with
  • Password: Password to authenticate with
  • Configuration Parameters: Extra parameters that can be passed to the content service connection and vary by connection. See the section on extra query parameters below.

Connection Configuration

A query_fq configuration param lets you define facet queries behind the scene. This is done to provide limited views or subsets of data in the search. Essentially you could create any number of views on the same date but each view would display different results. This can also be used in a role base system where you have views setup for specific user roles.

The syntax is:

query_fq for the first one

query_fq1 for the second

etc.

Unless the fq is already encoded, you will need to wrap it in the encode() function where it will be URLEncoded UTF-8.

The methods currently supported for this connector are:

  • Create File
  • Create Folder
  • Delete Folder
  • Delete Object By Id
  • Get File Content
  • Get Object Id By Path
  • Get Object Properties
  • Get Types
  • Get File Item
  • List Folder Items
  • Update File
  • Update Properties