The eRoom connector will crawl content from an eRoom server instance (site) with an enabled XML Query option (Allow XML queries and commands from external applications).
On this page:
Table of Contents |
---|
Some of the features of the eRoom connector include:
The eRoom connector retries several types of documents, listed bellow are the inclusions and exclusions of these documents.
DiscussionDiscussion
NoteNote
Due to API limitations, eRoom connector has the following limitations:
Multi-Threads Technical limitation
Panel |
---|
With Aspire 3.1 we introduce a multi-threading platform to perform crawls, but due architecture / API limitations the eRoom Connector basically work as single thread connector. Seems to be that the server does not allow multiples connections performing queries at the same time. At some point of the crawl, the connector get this errors from the server "No target objects were found evaluating the command's select attribute" but the query that we are trying to execute works well (we tested using a SOAP/XML Test program provided for EMC). Also if you look at the lasted comments in this post from the EMC forums: Seems to be that eRoom is not multi-thread safe so when multiple processes are spawned you will get unpredictable behavior. So because of that, the eRoom Connector is single thread and that affect the performance due Aspire 3.1 is multi-thread. |
The connector will use SOAP / XML over HTTP or HTTPs to acquire information of eRoom content. The connector acquires content by doing the following: