Return-Path:
The OpenSearchServer Output Connection allow ManifoldCF to submit documents to an OpenSearchServer instance, via the XML over HTTP API.
+You may also refer to the OpenSearchServer's user documentation.
+The MetaCarta GTS output connection type is designed to allow ManifoldCF to submit documents to an appropriate MetaCarta GTS search Modified: incubator/lcf/branches/CONNECTORS-240/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml URL: http://svn.apache.org/viewvc/incubator/lcf/branches/CONNECTORS-240/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml?rev=1163956&r1=1163955&r2=1163956&view=diff ============================================================================== --- incubator/lcf/branches/CONNECTORS-240/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml (original) +++ incubator/lcf/branches/CONNECTORS-240/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml Thu Sep 1 09:15:42 2011 @@ -68,6 +68,7 @@
ManifoldCF is an effort to provide an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr. ManifoldCF also defines a security model for target repositories that permits them to enforce source-repository security policies.
-Currently included connectors support FileNet P8 (IBM), Documentum (EMC), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), Windows shares (Microsoft), and SharePoint (Microsoft). Also included are a general CMIS connector, a general file system connector, a general JDBC connector, a general RSS crawler, and a general web crawler. Currently supported targets include Apache Solr and QBase (formerly MetaCarta) GTS. The complete repository compatibility list can be found here.
+ManifoldCF is an effort to provide an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr or OpenSearchServer. ManifoldCF also defines a security model for target repositories that permits them to enforce source-repository security policies.
+Currently included connectors support FileNet P8 (IBM), Documentum (EMC), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), Windows shares (Microsoft), and SharePoint (Microsoft). Also included are a general CMIS connector, a general file system connector, a general JDBC connector, a general RSS crawler, and a general web crawler. Currently supported targets include Apache Solr, QBase (formerly MetaCarta) GTS and OpenSearchServer. The complete repository compatibility list can be found here.
The original ManifoldCF code base was granted by MetaCarta, Inc., to the Apache Software Foundation in December 2009. The MetaCarta effort represented more than five years of successful development and testing in multiple, challenging enterprise environments.
A very good place to start is to read the javadoc for the output connector interface. You will note that the javadoc describes the usage and pooling model for a connector class pretty thoroughly. It is very important to understand the model thoroughly in order to write reliable connectors! Use of static variables, for one thing, must be done in a very careful way, to avoid issues that would be hard to detect with a cursory test.
-The second thing to do is to examine some of the provided output connector implementations. The GTS connector, the SOLR connector, and the Null Output connector all are output connectors which demonstrate (to some degree) the sorts of techniques you will need for an effective implementation. You will also note that all of these connectors extend a framework-provided output connector base class, found at org.apache.manifoldcf.agents.output.BaseOutputConnector. This base class furnishes some basic bookkeeping logic for managing the connector pool, as well as default implementations of some of the less typical functionality a connector may have. For example, connectors are allowed to have database tables of their own, which are instantiated when the connector is registered, and are torn down when the connector is removed. This is, however, not very typical, and the base implementation reflects that.
+The second thing to do is to examine some of the provided output connector implementations. The GTS connector, the SOLR connector, the OpenSearchServer connector, and the Null Output connector all are output connectors which demonstrate (to some degree) the sorts of techniques you will need for an effective implementation. You will also note that all of these connectors extend a framework-provided output connector base class, found at org.apache.manifoldcf.agents.output.BaseOutputConnector. This base class furnishes some basic bookkeeping logic for managing the connector pool, as well as default implementations of some of the less typical functionality a connector may have. For example, connectors are allowed to have database tables of their own, which are instantiated when the connector is registered, and are torn down when the connector is removed. This is, however, not very typical, and the base implementation reflects that.