How to connect vTiger database to ODS - Revision history

Wmenn: /* ODS Assistant */

2011-12-14T15:57:03Z

‎ODS Assistant

Wmenn: /* ODS Assistant */

2011-12-14T15:56:21Z

‎ODS Assistant

Wmenn: /* LDAP Test */

2011-12-14T15:49:12Z

‎LDAP Test

Wmenn at 15:47, 14 December 2011

2011-12-14T15:47:52Z

Wmenn: /* Maintenance */

2011-12-14T15:45:41Z

‎Maintenance

Wmenn: /* Number conversion */

2011-12-14T15:45:23Z

‎Number conversion

Wmenn: /* Save Datasource configuration */

2011-12-14T15:45:07Z

‎Save Datasource configuration

Wmenn: /* LDAP Test */

2011-12-14T15:44:55Z

‎LDAP Test

Wmenn: /* Field Mappings */

2011-12-14T15:44:15Z

‎Field Mappings

Wmenn: /* Field Mappings */

2011-12-14T15:43:24Z

‎Field Mappings

← Older revision		Revision as of 15:57, 14 December 2011
Line 32:		Line 32:
	[[Image:ODS_vTiger_1.png\|500px]]		[[Image:ODS_vTiger_1.png\|500px]]

−
−	~~=== Database access===~~
−
−	~~'''ODBC driver'''~~

	vTiger bases on an mySQL database		vTiger bases on an mySQL database

@@ Line 27: / Line 27: @@
 == ODS Assistant ==
-=== Add new SQL Data Source to ODS ===
+=== Database ===
 [[Image:ODS_vTiger_1.png|500px]]
-===== Database access=====
+=== Database access===
 '''ODBC driver'''
@@ Line 44: / Line 39: @@
 vTiger bases on an mySQL database
-==== Database Table ====
+=== Database Table ===
 Within this example the table "vtiger_account" is selcted which contains the relevant user data
@@ Line 51: / Line 46: @@
 Note: Within V3R2 only one table can be selected here
-==== Field Mappings ====
+=== Field Mappings ===
 Within the penultimate step you map the SQL database table attributes to the Open Directory fields, which are finally presented by the LDAP server.
 [[Image:ODS_vTiger_4.png|500px]]
-==== LDAP Test ====
+=== LDAP Test ===
 Administration menue of Data Sources offers also the test of the configured parameters. Selection of the LDAP Test Tab allows user to check, if the the settings and configuration made before, deliver the requested data.
 [[Image:ODS_vTiger_5.png|500px]]

← Older revision		Revision as of 15:49, 14 December 2011
Line 60:		Line 60:

	[[Image:ODS_vTiger_5.png\|500px]]		[[Image:ODS_vTiger_5.png\|500px]]
−
−
−	Pressing the button “Run test” will seach within the configured datasource and displays all entries of the datasource and the content of the configured Open Directory Service data fields (LDAP fields).

@@ Line 54: / Line 54: @@
 Within the penultimate step you map the SQL database table attributes to the Open Directory fields, which are finally presented by the LDAP server.
-[[Image:Image:ODS_vTiger_4.png|500px]]
+[[Image:ODS_vTiger_4.png|500px]]
 ==== LDAP Test ====

← Older revision		Revision as of 15:45, 14 December 2011
Line 63:		Line 63:

	Pressing the button “Run test” will seach within the configured datasource and displays all entries of the datasource and the content of the configured Open Directory Service data fields (LDAP fields).		Pressing the button “Run test” will seach within the configured datasource and displays all entries of the datasource and the content of the configured Open Directory Service data fields (LDAP fields).
−
−	~~=== Maintenance ===~~
−
−	~~The maintenance screen allows you to check the current status of the Open Directory Service and to restart the service. The actual status is displayed in a status line .~~
−
−	~~[[Image:ODS_Inst_11.png\|500px]]~~
−
−	~~For better visibility a colored icon represents the status in addition to the plain text.~~
−
−	* Green: Status “Running” No action required
−	* Grey: Status “Not Running” Activation of the service required.
−
−	~~If a red, blinking dot apperas in the main navigation behind the Maintenance text an Open Directory Service restart is required due to configuration modifications.~~
−
−	The restart of the Open Directory Service can be performed by a mouse click on the Restart button. If the “Restart” button ist greyed out, Open Directory Service has to be activated first at the “Settings” page.
−
−	~~A succeeding dialog box informs you about the result of the restart action.~~

← Older revision		Revision as of 15:45, 14 December 2011
Line 55:		Line 55:

	[[Image:Image:ODS_vTiger_4.png\|500px]]		[[Image:Image:ODS_vTiger_4.png\|500px]]
−
−	~~==== Number conversion ====~~
−	~~Within a connected database telephone numbers could be stored in different formats.~~
−	~~The Number Conversion function allows you to normalize the the retrieved phone numbers into a full qualified number format (e.g. +12 (345) 678 90).~~
−	~~This is could be necessary for correct caller identification. Number conversion can be configured per data source.~~
−	~~The stored phone numbers within the source database are not modified.~~
−
−	~~[[Image:ODS_Inst_9.png\|500px]]~~
−
−	~~If You enable the function by a tic within the “Active” checkbox, the additional dial parameters are presented and can be populated.~~
−	You have to determine the localization, for which the telephonenumber were entered in teh database and enter the suitable data. In case that the data source is located at the same place as the ODS (OSO system) the apropriate settings can be imported from the OSO configuration by pressing the button "Query System Settings".
−	You can also configure if the phone numbers in the database starts with a dialout prefix or not. This setting is needed, as in some counties a ‘0’ as prefix cannot be differentiated from the national access prefix (e.g. in Germany).
−
−	~~'''Note:'''~~
−	~~Number conversation can fail in some cases, e.g. if parts of the phone number are missing or if an odd notation is used.~~
−	~~In this case the telephone number have to be corrected within the datasource.~~

	==== LDAP Test ====		==== LDAP Test ====

← Older revision		Revision as of 15:45, 14 December 2011
Line 79:		Line 79:

	Pressing the button “Run test” will seach within the configured datasource and displays all entries of the datasource and the content of the configured Open Directory Service data fields (LDAP fields).		Pressing the button “Run test” will seach within the configured datasource and displays all entries of the datasource and the content of the configured Open Directory Service data fields (LDAP fields).
−
−	~~==== Save Datasource configuration ====~~
−
−	~~At the end of the database configuration the settings should be saved. Afterwards the data source name is available within the left column under the “Data Sources” headline .~~
−	~~Further information about the data source is available within the Data Sources Main Window.~~
−	~~A data source can be modified or deleted by pressing the appropriate button after data source selection within the Main Window.~~

	=== Maintenance ===		=== Maintenance ===

@@ Line 75: / Line 75: @@
 Administration menue of Data Sources offers also the test of the configured parameters. Selection of the LDAP Test Tab allows user to check, if the the settings and configuration made before, deliver the requested data.
-[[Image:ODS_Inst_10.png|500px]]
+[[Image:ODS_vTiger_5.png|500px]]
 Pressing the button “Run test” will seach within the configured datasource and displays all entries of the datasource and the content of the configured Open Directory Service data fields (LDAP fields).
 ==== Save Datasource configuration ====

@@ Line 52: / Line 52: @@
 ==== Field Mappings ====
-Within the penultimate step you map the SQL database table attributes to the Open Directory fields, which are finally presented by the LDAP server. The mapping is done in the way, that the available attributes of the selected table are presented at the left side and the Open Directory Sevices (LDAP) field at the right side.
+Within the penultimate step you map the SQL database table attributes to the Open Directory fields, which are finally presented by the LDAP server.
-The table attribute can be chosen by a click to the attribute within the drop down menu. An already used and assigned attribute is presented in blue color. Multiple assignments of an attributes to different LDAP fields are allowed.
+[[Image:Image:ODS_vTiger_3.png|500px]]
 ==== Number conversion ====