Building and running the Documentum connector

The Documentum connector requires EMC's DFC product in order to be run, but is built against a set of stub classes. After building, you must install DFC on the build system, and locate the jars it installs. Copy - these jars to the directory dist/documentum-server-process/lib-proprietary.

For a binary distribution, copy the DFC jars to documentum-server-process/lib-proprietary instead.

If you have done everything right, you should be able to start the Documentum connector's registry and server processes, as per the instructions.

The FileNet connector requires IBM's FileNet P8 API jar in order to be run, but is built against a set of stub classes. After building, install the FileNet P8 API on your system, - and copy "Jace.jar" and the other dependent jars from that installation into dist/filenet-server-process/lib-proprietary.

If you have downloaded a binary distribution, place the jar in filenet-server-process/lib-proprietary.

If correctly done, you will be able to start the FileNet connector's registry and server processes, as per the instructions.

Note well: For SharePoint instances version 3.0 or higher, in order to support file and folder level security, you also must deploy a custom SharePoint web service on the SharePoint instance you intend to connect to. This is because Microsoft apparently overlooked support for web-service-based access to such security information when SharePoint 3.0 was released. This service can be found in the directory dist/sharepoint-integration after ManifoldCF is built. - To install it on your SharePoint 3.0 machine, follow the directions in the file Installation Readme.txt, found in that directory.

Note well: For SharePoint instances version 3.0 (2007) or higher, in order to support file and folder level security, you also must deploy a custom SharePoint web service + on the SharePoint instance you intend to connect to. This is because Microsoft apparently overlooked support for web-service-based access to such security information + when SharePoint 2007 was released. For SharePoint version 4.0 (2010), the service is even more critical, because backwards compatibility was not maintained and without + this service no crawling can occur. Two versions of this service can be found in the distribution directory sharepoint-integration. + Pick the version appropriate for your SharePoint installation, and install it following the instructions in the file Installation Readme.txt, found in the + corresponding directory.

Commands @@ -545,8 +551,9 @@ cd example

Deploying the mcf-crawler-ui, mcf-authority-service, and mcf-api-service web applications

If you built ManifoldCF using ant, then the ant build will have constructed three war files for you under dist/multiprocess-example/web. If you intend to run - ManifoldCF in multiprocess mode, you will need to deploy these web applications on you application server. There is no requirement that the mcf-crawler-ui, mcf-authority-service, and mcf-api-service web +

If you built ManifoldCF using ant, then the ant build will have constructed four war files for you under web/war. You should ignore the mcf-combined + war in this directory for this deployment model. If you intend to run ManifoldCF in multiprocess mode, you will need to deploy the other web applications on you application server. + There is no requirement that the mcf-crawler-ui, mcf-authority-service, and mcf-api-service web applications be deployed on the same instance of the application server. With the current architecture of ManifoldCF, they must be deployed on the same physical server, however.

For each of the application servers involved with ManifoldCF, you must set the following define, so that the ManifoldCF web applications can locate the configuration file:

Modified: manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml URL: http://svn.apache.org/viewvc/manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml?rev=1397942&r1=1397941&r2=1397942&view=diff ============================================================================== --- manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml (original) +++ manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml Sat Oct 13 20:42:19 2012 @@ -65,7 +65,8 @@

Check out the desired release from https://svn.apache.org/repos/asf/manifoldcf/tags, or unpack the desired source distribution.
cd to the top-level directory.
EITHER: overlay the lib directory from the corresponding lib distribution (preferred), OR run "ant make-core-deps" to build the code dependencies.
EITHER: overlay the lib directory from the corresponding lib distribution (preferred, where possible), OR run "ant make-core-deps" to + build the code dependencies. The latter is the only possibility if you are building from trunk, but it is not guaranteed to work for older releases.
Run "ant make-deps", to download LGPL and other open source but non-Apache compatible libraries.
Install proprietary build dependencies. See below for details.
Run "ant build".
CMIS authority
Documentum authority
LiveLink authority
Null authority connector
Null authority
LDAP authority

Finally, the following output connectors will be built:

Building and running the Documentum connector

documentum-server-process/lib-proprietary

For a binary distribution, copy the DFC jars to documentum-server-process/lib-proprietary instead.

If you have done everything right, you should be able to start the Documentum connector's registry and server processes, as per the instructions.

Building and running the FileNet connector

filenet-server-process/lib-proprietary

If you have downloaded a binary distribution, place the jar in filenet-server-process/lib-proprietary.

If correctly done, you will be able to start the FileNet connector's registry and server processes, as per the instructions.

Building and running the LiveLink connector

This connector needs OpenText's LAPI package in order to be run, but is built against a set of stubs. After building, copy the lapi.jar into the dist/connector-lib-proprietary - directory, and uncomment the LiveLink-related connector lines in dist/connectors.xml.

This connector needs OpenText's LAPI package in order to be run, but is built against a set of stubs. After building, copy the lapi.jar into the connector-lib-proprietary + directory, and uncomment the LiveLink-related connector lines in connectors.xml.

If you have downloaded a binary distribution, place the jar in connector-lib-proprietary, and modify the connectors.xml file.

http[s]://<server_name>/_vti_bin/webs.asmx

@@ -405,7 +411,7 @@ cd example

dist/multiprocess-example file/directory	Meaning
multiprocess-example file/directory	Meaning
web	Web applications that should be deployed on tomcat or the equivalent, plus recommended application server -D switch names and values
processes	classpath jars that should be included in the class path for all non-connector-specific processes, along with -D switches, using the same convention as described for tomcat, above
properties.xml	an example ManifoldCF configuration file, in the right place for the multiprocess script to find it

dist/multiprocess-example file/directory	Meaning
multiprocess-example file/directory	Meaning
web	Web applications that should be deployed on tomcat or the equivalent, plus recommended application server -D switch names and values
processes	classpath jars that should be included in the class path for all non-connector-specific processes, along with -D switches, using the same convention as described for tomcat, above
properties.xml	an example ManifoldCF configuration file, in the right place for the multiprocess script to find it