Mapping Rule Files

Mapping rule files define how attributes from one schema correspond to attributes in another schema, using the short names or tags from the schema definition files. Some attribute mappings are simple attribute-to-attribute pairings. For example, when the GroupWise directory is synchronized with Active Directory, the Exchange attribute PHONE is assigned the value of the attribute PHONE in the GroupWise directory (they even have the same names).

Other attribute values may go through a series of transformations as they are mapped to an attribute in the other directory. For example, the Exchange GroupWise address attribute (GWISEADDR) is assigned a combination of the GroupWise DOMAIN, POSTOFFICE, and OBJECT attributes, along with character literals to create an address of the form Domain.PostOffice.Object in Active Directory.

Note   Mapping rule files must contain only tags that are defined in the schema definition files.

Two files define the attribute mappings for each partner system. The first file defines how the attributes from the GroupWise or Notes directory correspond to Active Directory attributes (MapGwise.tbl or MapNotes.tbl); the second file defines how Active Directory attributes correspond to the GroupWise or Notes directory (Mapmex.tbl).

Examples

Two attribute mapping examples follow. The first example shows the Mapgwise.tbl file, which maps GroupWise schema attributes from the Gwamap.tbl file (on the right) to Active Directory attributes from the Mexamap.tbl file (on the left).

TA			= "GWISE:" DOMAIN "." POSTOFFICE "." OBJECT
UNID			= HASH(DOMAIN "." POSTOFFICE "." OBJECT)
GWISEADDR	 = DOMAIN "." POSTOFFICE "." OBJECT
DN			= ISEQUAL(FIRSTNAME AND(" ", LASTNAME), "", ISEQUAL(FIRSTNAME, "", ISEQUAL(LASTNAME, "", OBJECT, LASTNAME), FIRSTNAME), TRIM(FIRSTNAME AND(" ", LASTNAME),"B"))
ALIAS		 = OBJECT
FULLNAME		= ISEQUAL(FIRSTNAME AND(" ", LASTNAME), "", ISEQUAL(FIRSTNAME, "", ISEQUAL(LASTNAME, "", OBJECT, LASTNAME), FIRSTNAME), TRIM(FIRSTNAME AND(" ", LASTNAME),"B"))
NAME			= ISEQUAL(FIRSTNAME AND(" ", LASTNAME), "", ISEQUAL(FIRSTNAME, "", ISEQUAL(LASTNAME, "", OBJECT, LASTNAME), FIRSTNAME), TRIM(FIRSTNAME AND(" ", LASTNAME),"B"))
FIRSTNAME	 = FIRSTNAME
LASTNAME		= LASTNAME  
DEPARTMENT	= DEPARTMENT
TITLE		 = TITLE
PHONE		 = PHONE
FAX			 = FAX

The second example shows the Mapmex.tbl file, which maps Active Directory schema attributes from the Mexamap.tbl file (on the right) to GroupWise attributes from the Gwamap.tbl file (on the left).

GWADDR		= GWISEADDR
LASTNAME		= LASTNAME
FIRSTNAME	 = ISEQUAL(FIRSTNAME, "", ISEQUAL(LASTNAME, "", FULLNAME, FIRSTNAME), FIRSTNAME)
DESCRIP		 = FULLNAME
TITLE		 = TITLE
DEPARTMENT	= DEPARTMENT
PHONE		 = PHONE
FAX			 = FAX
EXCHANGEID	= "Microsoft Exchange Connector for Novell GroupWise"

Caution   If a directory attribute in the Exchange to GroupWise mapping file (Conndata\Dxagwise\Mapmex.tbl) is not assigned a value (that is, no character or no space is entered to the right of the equal sign), the connector will generate an error. The synchronization process will not complete until the error is corrected.

Each non-blank, non-comment line contains a rule that assigns a value to a single attribute in an entry in the target directory. The portion of the rule to the right of the equal sign (=) is a string expression made up of string constants, numeric constants, references to attributes in the source directory, and built-in string manipulation, or mapping functions. Note that the default mappings are, in general, one-to-one correspondences and do not contain mapping functions.

Important   If you make a change to a mapping rule file, you must restart the connector. Also, be sure that you map attributes to acceptable formats and values. For example, the Exchange GWISEADDR attribute expects a period literal character separating three values, as in Domain.PostOffice.Object.

Related Topics