[teiid-commits] teiid SVN: r1076 - trunk/documentation/salesforce-connector-guide/src/main/docbook/en-US/content.

teiid-commits at lists.jboss.org teiid-commits at lists.jboss.org
Wed Jun 24 14:00:40 EDT 2009


Author: jdoyle
Date: 2009-06-24 14:00:40 -0400 (Wed, 24 Jun 2009)
New Revision: 1076

Modified:
   trunk/documentation/salesforce-connector-guide/src/main/docbook/en-US/content/connector.xml
Log:
Removed section and reformatted.

Modified: trunk/documentation/salesforce-connector-guide/src/main/docbook/en-US/content/connector.xml
===================================================================
--- trunk/documentation/salesforce-connector-guide/src/main/docbook/en-US/content/connector.xml	2009-06-24 16:07:46 UTC (rev 1075)
+++ trunk/documentation/salesforce-connector-guide/src/main/docbook/en-US/content/connector.xml	2009-06-24 18:00:40 UTC (rev 1076)
@@ -6,41 +6,6 @@
 		and UPDATE operations.
     </para>
     <sect1>
-        <title>Binding the Salesforce Connector</title>
-        <para>Once you have created the model of the Salesforce instance
-			and added that model to a VDB, you must bind the VDB to an instance
-			of a Salesforce Connector. On the Execute tab of the VDB click the
-			Edit button in the Connector Bindings panel. The Connector Binding
-			Wizard is displayed.
-        </para>
-		<!-- screenshot -->
-        <para>The Salesforce Importer generates a connector binding with
-			the correct credentials and URL when generating a new model. You
-			select that binding by clicking the Loaded Bindings tab and selecting
-			the binding with the name that corresponds to the model you are
-			binding.
-        </para>
-        <para>A binding can also be created manually. Select Salesforce
-			Connector from the Connector Types dropdown and enter a username and
-			password into the appropriate binding properties.
-        </para>
-        <para>
-			If you are connecting to a Sandbox instance of a Salesforce
-			application rather than a live instance, you can check the Show
-			Advance Properties checkbox, and change the Salesforce URL binding
-			property that is revealed to contain the URL to your sandbox
-			instance. For more information see the
-            <ulink
-				url="http://www.salesforce.com/platform/application-development/development-and-test-enviorment/">Salesforce Sandbox
-            </ulink>
-			information.
-        </para>
-        <para>You can now execute the VDB
-			and begin to query your Salesforce
-			instance.
-        </para>
-    </sect1>
-    <sect1>
         <title>SQL Processing</title>
         <para>Salesforce does not provide the same set of
 			functionality as a relational database. For example, Salesforce does
@@ -62,8 +27,7 @@
         <para>In cases where certain SQL capabilities cannot be pushed down
 			to Salesforce, Teiid will push down the capabilities that are
 			supported, and fetch a set of data from Salesforce. Then, Teiid
-			will
-			evaluate the additional capabilities, creating a subset of the
+			will evaluate the additional capabilities, creating a subset of the
 			original data set. Finally, Teiid will pass the result to the
 			client.
         </para>
@@ -82,8 +46,7 @@
          ]]>        
         </programlisting>
         <para>The sum() scalar function will be applied by the Teiid
-			Query
-			Engine to the result set returned by the connector.
+			Query Engine to the result set returned by the connector.
         </para>
         <para>In some cases multiple calls to the Salesforce application
 			will be made to support the SQL passed to the connector.
@@ -126,12 +89,9 @@
             </ulink>
         </para>
         <para>Teiid SQL does not support the includes or
-			excludes
-			operators, but the Salesforce connector provides user
-			defined function
-			definitions for these operators that provided
-			equivalent functionality
-			for fields of type multi-select. The
+			excludes operators, but the Salesforce connector provides user
+			defined function definitions for these operators that provided
+			equivalent functionality for fields of type multi-select. The
 			definition for the functions is:
         </para>
         <programlisting><![CDATA[
@@ -181,39 +141,29 @@
         <para>
 			The Salesforce connector supports the calling the queryAll operation
 			from the Salesforce API. The queryAll operation is equivalent
-			to the
-			query operation with the exception that it returns data about
+			to the query operation with the exception that it returns data about
             <emphasis role="strong">all current and deleted</emphasis>
 			objects in the system.
         </para>
         <para>The connector determines if it will call the
-			query or queryAll
-			operation via reference to the isDeleted property
-			present on each
-			Salesforce object, and modeled as a column on
-			each table generated by
+			query or queryAll operation via reference to the
+			 isDeleted property present on each  Salesforce object, 
+			 and modeled as a column on each table generated by
 			the importer. By default this value is set to
-			False when the model is
-			generated and thus the connector calls
-			query. Users are free to change
-			the value in the model to True,
-			changing the default behavior of the
-			connector to be queryAll.
+			False when the model is generated and thus the connector calls
+			query. Users are free to change the value in the model to True,
+			changing the default behavior of the connector to be queryAll.
         </para>
         <para>The behavior is different if isDeleted is used as a parameter
 			in the query. If the isDeleted column is used as a parameter
-			in the
-			query, and the value
-			is 'true' the connector will call queryAll.
+			in the query, and the value is 'true' the connector will call queryAll.
         </para>
         <programlisting><![CDATA[
 			select * from Contact where isDeleted = true;           
          ]]>
         </programlisting>
-        <para>If the
-			isDeleted column is used as a parameter in the query,
-			and the value
-			is 'false' the connector perform the default behavior
+        <para>If the isDeleted column is used as a parameter in the query,
+			and the value is 'false' the connector perform the default behavior
 			will call query.
         </para>
         <programlisting><![CDATA[
@@ -226,8 +176,7 @@
         <title>Selecting Updated Objects</title>
         <para>If the option is selected when importing metadata from
 			Salesforce, a GetUpdated procedure is generated in the model with
-			the
-			following sturcture:
+			the following sturcture:
         </para>
         <programlisting><![CDATA[
 			GetUpdated (ObjectName IN string,
@@ -250,8 +199,7 @@
         <title>Selecting Deleted Objects</title>
         <para>If the option is selected when importing metadata from
 			Salesforce, a GetDeleted procedure is generated in the model with
-			the
-			following sturcture:
+			the following sturcture:
         </para>
         <programlisting><![CDATA[
 			GetDeleted (ObjectName IN string,




More information about the teiid-commits mailing list