Chapter 35. Web services

Table of Contents

35.1. Audit web service
35.2. Remoting web service
35.3. Indexing gateway service
35.4. Metro web services

You will find the list of deployed J2EE compatible web services on your host at the following location: http://localhost:8080/jbossws. From there you can view all the web services descriptions (WSDL files).

35.1. Audit web service

This web service enable to query all logged events.

TODO: verbose

35.2. Remoting web service

TODO: verbose

35.3. Indexing gateway service

Nuxeo EP provides a WebService API that enables an external indexer to index the documents that are inside the Nuxeo repository. In this scenario, Nuxeo keeps it's internal indexing backend, and may contiue to use it for search.

This service is provided as an addon called nuxeo-platform-indexing-gateway that need to be deployed in the nuxeo.ear/plugins directory.

The data exchange between the external indexer and Nuxeo is done in a pull mode: the external indexer queries Nuxeo for new documents to index.

Here is a simple summary of the responsibilities between the external indexer and Nuxeo server:

Externalindexer:

  • query nuxeo to know what document may be indexed

  • query nuxeo to get document informations

  • manages indexing configuration

Nuxeo:

  • provides an API to browse repository

  • provides an API to know what documents needs to be indexed

  • may include some transformation of data before exportation to make

  • external indexer easier (like ACP/ACL/ACE preprocessing) may notify external indexer that some data need to be (re)indexed

35.4. Metro web services

The WS stack used is Metro 1.4. The stack is deployed by default by running "ant patch" in the nuxeo sources directory. It also removes the default JBoss WS stack. Some examples on how to set up such web services can be found at http://hg.nuxeo.org/sandbox/nuxeo-platform-webservice-example/

The README.txt should be a good start.