Date: Thu, 28 Mar 2024 16:40:59 -0500 (CDT) Message-ID: <99401207.27.1711662059426@slrs01vf4p1cn02.as.ad.digital.accenture.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_26_356334032.1711662059424" ------=_Part_26_356334032.1711662059424 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The eRoom connector will crawl content from an eRoom server in= stance (site) with an enabled XML Query option (Allow XML queries and = commands from external applications).
Some of the features of the eRoom connector include:
The eRoom connector retrieves several types of documents, list= ed below are the inclusions and exclusions of these documents.
Discussion
Note
Due to API limitations, the eRoom connector has the following = limitations:
Multi-Threads Technical limitation
With Aspire 3.3 we introduce a multi-threading platform to perform crawl= s, but due architecture / API limitations the eRoom Connector basically wor= k as single thread connector. Seems to be that the server does not allow mu= ltiples connections performing queries at the same time.
At some point of the crawl, the connector get this errors from the serve= r "No target objects were found evaluating the command's select att= ribute" 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 process= es are spawned you will get unpredictable behavior. So because of that, the= eRoom Connector is single thread and that affect the performance due Aspir= e 3.3 is multi-thread.
The connector will use SOAP / XML over HTTP or HTTPs to acquire informat= ion of eRoom content. The connector acquires content by doing the following= :