Familiarize Yourself with the Concepts and Terminology

Return-Path: Delivered-To: apmail-incubator-connectors-commits-archive@minotaur.apache.org Received: (qmail 6636 invoked from network); 22 Nov 2010 18:52:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Nov 2010 18:52:28 -0000 Received: (qmail 48914 invoked by uid 500); 22 Nov 2010 18:53:00 -0000 Delivered-To: apmail-incubator-connectors-commits-archive@incubator.apache.org Received: (qmail 48860 invoked by uid 500); 22 Nov 2010 18:53:00 -0000 Mailing-List: contact connectors-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: connectors-dev@incubator.apache.org Delivered-To: mailing list connectors-commits@incubator.apache.org Received: (qmail 48852 invoked by uid 99); 22 Nov 2010 18:53:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Nov 2010 18:53:00 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Nov 2010 18:52:59 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id EF86223888CD; Mon, 22 Nov 2010 18:51:27 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1037835 - in /incubator/lcf/trunk/site/src/documentation/content/xdocs: developer-resources.xml how-to-build-and-deploy.xml site.xml Date: Mon, 22 Nov 2010 18:51:27 -0000 To: connectors-commits@incubator.apache.org From: kwright@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20101122185127.EF86223888CD@eris.apache.org> Author: kwright Date: Mon Nov 22 18:51:27 2010 New Revision: 1037835 URL: http://svn.apache.org/viewvc?rev=1037835&view=rev Log: Promote javadoc, etc to the main navigation area. Modified: incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml incubator/lcf/trunk/site/src/documentation/content/xdocs/how-to-build-and-deploy.xml incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml Modified: incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml URL: http://svn.apache.org/viewvc/incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml?rev=1037835&r1=1037834&r2=1037835&view=diff ============================================================================== --- incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml (original) +++ incubator/lcf/trunk/site/src/documentation/content/xdocs/developer-resources.xml Mon Nov 22 18:51:27 2010 @@ -14,30 +14,6 @@

-

- Familiarize Yourself with the Concepts and Terminology -

Like any software project, ManifoldCF has its own underlying concepts and terminology. Read about that here. -

-

- -

- Interoperability Matrix -

The interoperability and testing matrix for ManifoldCF can be found here. -

-

- -

- How to Build and Deploy -

Building ManifoldCF requires ant 1.7 or greater. Instructions for building and deploying can be found here. -

-

- -

- How to Integrate -

ManifoldCF provides a number of API's and services. Documentation of these API's can be found here. -

-

-

Security Architecture Diagrams

For those who prefer a pictorial representation of ManifoldCF's security architecture, this might help.

@@ -63,7 +39,6 @@

Writing connectors for ManifoldCF is a great way to learn about the project and contribute something useful! Read about how to do that by navigating to the links provided below.

ManifoldCF Javadoc
How to write an output connector
How to write an authority connector
How to write a repository connector

The registry process in all cases must be started before the corresponding server process, or the server process will report an error. (It will, however, retry after some period of time.) The scripts all require an MCF_HOME environment variable pointing to the place where properties.xml is found, as well as a JAVA_HOME environment variable pointing the JDK. The server scripts also require other environment variables as well, consistent with the needs of the DFC or the FileNet API respectively. For example, DFC requires the DOCUMENTUM environment variable to be set, while the FileNet server script requires the WASP_HOME environment variable.

It is important to understand that the scripts work by building a classpath out of all jars that get copied into the jar directory underneath each process during the ant build. These jars come in part from the dfc> or filenet-api directories underneath the documentum or filenet connector directories. For the server startup scripts to work properly, therefore, these directories should have all of the jars needed to allow the api code to function, and the ant build scripts will take care of the rest.

It is important to understand that the scripts work by building a classpath out of all jars that get copied into the jar directory underneath each process during the ant build. These jars come in part from the dfc or filenet-api directories underneath the documentum or filenet connector directories. For the server startup scripts to work properly, therefore, these directories should have all of the jars needed to allow the api code to function, and the ant build scripts will take care of the rest.

Modified: incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml URL: http://svn.apache.org/viewvc/incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml?rev=1037835&r1=1037834&r2=1037835&view=diff ============================================================================== --- incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml (original) +++ incubator/lcf/trunk/site/src/documentation/content/xdocs/site.xml Mon Nov 22 18:51:27 2010 @@ -26,7 +26,12 @@ + + + + +