I believe a fix was made to the ElasticSearch connector a release or two ago that addresses this problem.  ElasticSearch once again changed their API without notice and this was necessary.  Please consider updating to the latest release of MCF.


On Tue, May 15, 2018 at 9:48 AM Shashank Saurabh LNU <slnu39@worldbankgroup.org> wrote:

Hi All,


I’m using the Documentum Repository Connector and ElasticSearch Output Connector with the specified Docbase and Webtop credentials to crawl the contents from Documentum and index it into ElasticSearch. I’m using the local server for indexing into ElasticSearch i.e. http://localhost:9200/.


Created the job, by giving required connections as Documentum in Repository and ElasticSearch in Output.


When I run the job, the History Status shows the fetch status as OK from the Documentum but shows as error during the indexing to ElasticSearch.

The error logged is: "error":"Content-Type header [application/x-www-form-urlencoded] is not supported.


Please do assist on this.


  • Using the setup in Windows Environment.



Attaching the screenshot for the reference.





Shashank Saurabh