Appendix C       BuyerXpert/SellerXpert Mapping to LDAP


This appendix discusses the mapping from BuyerXpert/SellerXpert to LDAP. Table C-2 through Table C-6 contain the attribute equivalencies between LDAP and BuyerXpert/SellerXpert.

The following sections are contained in this appendix:

• About LDAP Mapping, DIT, and Schema

• Organization Mapping

• Organizational Unit Mapping

• User Mapping

• User Group Mapping

• Location Mapping

For information on iPlanet Directory Server documentation, refer to the documentation at:

http://docs.iplanet.com/docs/manuals/directory.html

About LDAP Mapping, DIT, and Schema

---

BuyerXpert/SellerXpert uses standard object classes which closely resemble many attributes that describe BuyerXpert/SellerXpert membership entities. Additional object classes are used as auxiliary classes to accommodate additional application-specific attributes.

BuyerXpert/SellerXpert as an application makes the following assumptions for the representation of membership data in an LDAP repository:

• Users have unique UIDs within an organization

• Every organization domain, which spans the ownership of different related entities, is private to itself

The tasks involved in administering LDAP entries are performed to ensure interoperability with other applications.

Creating an Entry

BuyerXpert/SellerXpert creates entries in the LDAP repository in accordance with the directory structure and schema described in later sections.

Modifying an Entry

BuyerXpert/SellerXpert modifies only those attributes that BuyerXpert/SellerXpert recognizes. This ensures that the values of any attributes BuyerXpert/SellerXpert does not recognize are preserved.

Deleting an Entry

BuyerXpert/SellerXpert cannot delete an entry from the directory which could potentially be used by another application. On a delete operation, BuyerXpert/SellerXpert marks such entries as deleted by setting the iplanetStatus attribute to Deleted.

LDAP DIT

The directory information tree (DIT) structure assumed by BuyerXpert/SellerXpert is shown in Figure C-1.

Figure C-1    LDAP DIT Structure

• All the organizations are represented by a subtree rooted at a node of type o, o=Acme.com.

• All users belonging to every organization are stored in the subtree ou=People one level below the organization node.

• All user groups belonging to every organization are stored in the subtree ou=Groups one level below the organization node.

• Organizational units are hierarchical and rooted from the organization node.

Sub-organizations also have their own subtree under the directory root designated for BuyerXpert/SellerXpert.All entries are uniquely identified by the iplanetECGuid attribute. The iplanetECParentOrgGuid attribute identifies the parent organization to which that entry belongs, as illustrated in Figure C-2.

Figure C-2    iplanetECGuid and iplanetECParentOrgGuid Attributes

Notice that the iplanetECGuid attribute is unique for every entry. The iplanetECParentOrgGuid attribute refers to the iplanetECGuid attribute regardless of the respective parent organizations. Thus, o=Acme.com is parent organization of o=Fall.com. The entry o=Acme.com does not have any value for the iplanetECParentOrgGuid attribute, indicating it is a top-level organization with o=Fall.com as a subsidiary organization.

LDAP Schema

The LDAP directory provides standard object classes and allows applications to extend the schema for application-specific support. BuyerXpert/SellerXpert uses as much common representation as possible to provide for operating within other directory-enabled applications.

The following files define the schema elements required for BuyerXpert/SellerXpert:

• iplanet-userx-schema.conf

• iplanet-ecommerce-schema.conf

• iplanet-vortex-schema.conf

• iplanet-buyer-schema.conf

These files are located in the BuyerXpert/SellerXpert <IASHOME>/buyer/sample_data/directory_ldif/buyer/iplanet directory. Similar definition is also available in LDIF format in the schema.ldif file for BuyerXpert and SellerXpertSchema.ldif file for SellerXpert in the same directory.

Table C-1 lists the common attributes that identify an LDAP entry as being enabled for iPlanet eCommerce.

Table C-1    Attributes Common to iPlanet Applications 

Type	iPlanet Attribute	Description
	iplanetECDefinableID	Unique identifier, such as an account number or employee number.
	iplanetECGuid	Globally unique ID—a unique identifier
	iplanetECParentOrgGuid	Reference to parent organization. Corresponds to the iplanetECGuid attribute of the parent organization.
	memberOf	DN reference to the user group this entry belongs to.
	iplanet<App/ServiceName>Status	Status values are: active, inactive, or deleted. Applications check these exact tokens. Absence of the attribute is treated as Active.
	iplanet<App/ServiceName> ValidFromDate	Start date; when the resource represented by this entry is valid or enabled. If attribute is absent, resource is treated as Active.
	iplanet<App/ServiceName> ValidToDate	End date; when the resource represented by this entry is no longer valid or enabled. If attribute is absent, resource is treated as Active.
Organization	displayName	Display name or short name.
	iplanetECDunsNumber	Dun and Bradstreet number.
	iplanetECLegalType	Type of business, such as, C-Corporation, Limited Liability Corp, Partnership, S-Corporation, or Unknown. An informational field.
	iplanetECFederalTaxID	9 digit federal tax ID. An informational field.
	iplanetECSalesTaxID	State tax file ID. An informational field.
Organizational Unit	displayName	Display name or short name.
User	iplanetECPreferredCurrency	Preferred currency.

Organization Mapping

---

An organization entry has the following object classes:

• organization

• iplanetECCommon (auxiliary object class)

• iplanetECOrganization (auxiliary object class)

• iplanetBuyerOrganization (auxiliary object class

  )
  

  Table C-2    Organization Attribute Mapping 
  
  

  BuyerXpert/SellerXpert Attribute	Directory Schema Attribute	Object Class	Syntax
  Name	o	organization	cis
  Display name	displayName	iplanetBuyerOrganization	cis
  Seller ID	iplanetECDefinableID	iplanetECOrganization	cis
  Description	description	organization	cis
  D-U-N-S number	iplanetECDunsNumber	iplanetECOrganization	ces
  Address (6 lines)	postalAddress	organization	cis
  Legal type	iplanetECLegalType	iplanetECOrganization	cis
  Phone	telephoneNumber	organization	tel (multi-valued)
  Fax	fax	organization	tel (multi-valued)
  Email addresses	mail	iplanetBuyerOrganization	cis (multi-valued
  Web sites	url	iplanetECOrganization	cis (multi-valued
  GUID	iplanetECGuid	iplanetECCommon	ces
  Status	iplanetBuyerStatus	iplanetBuyerOrganization	cis
  Effective from Date	iplanetBuyerStatus	iplanetBuyerOrganization	cis
  Effective to Date	iplanetBuyerValidToDate	iplanetBuyerOrganization	cis
  Federal tax ID	iplanetECFederalTaxID	iplanetECOrganization	ces
  Sales tax ID	iplanetECSalesTaxID	iplanetECOrganization	ces
  Internal attribute	iplanetParentOrgGuid	iplanetECCommon	dn

Organizational Unit Mapping

---

An organizational unit entry has the following object classes:

• organizationUnit

• iplanetECCommon (auxiliary object class)

• iplanetECOrganizationalUnit (auxiliary object class)

• iplanetBuyerOrganizationalUnit (auxiliary object class)

  
  

  Table C-3    Organizational Unit Attribute Mapping 
  
  

  BuyerXpert/SellerXpert Attribute	Directory Schema Attribute	Object Class	Syntax
  Name	ou	organizationalUnit	cis
  Display name	displayName	iplanetECOrganizationalUnit	cis
  Organization ID	iplanetECDefinableID	iplanetECCommon	cis
  Description	description	organizationalUnit	cis
  GUID	iplanetECGuid	iplanetECCommon	ces
  Status	iplanetBuyerStatus	iplanetBuyerOrganizationalUnit	cis
  Effective from Date	iplanetBuyerValidFromDate	iplanetBuyerOrganizationalUnit	cis
  Effective to Date	iplanetBuyerValidToDate	iplanetBuyerOrganizationalUnit	cis
  Manager	iplanetBuyerManager	iplanetBuyerOrganizationalUnit	dn
  Internal attribute	iplanetParentOrgGuid	iplanetECCommon	ces

User Mapping

---

A user entry has the following object classes:

• person

• inetOrgPerson

• organizationalPerson

• iplanetECCommon (auxiliary object class)

• iplanetECPerson (auxiliary object class)

• iplanetBuyerPerson (auxiliary object class)

  
  

  Table C-4    User Attribute Mapping 
  
  

  BuyerXpert/SellerXpert Attribute	Directory Schema Attribute	Object Class	Syntax
  First name	givenName	inetOrgPerson	cis
  Last name	sn	inetOrgPerson	cis
  Common name	cn	inetOrgPerson	ces
  Title	title	inetOrgPerson	cis
  Person ID	iplanetECDefinableID	iplanetECCommon	cis
  Login Name	uid	inetOrgPerson	cis, 1
  Description	description	inetOrgPerson	cis
  Organization unit	ou	organizationalPerson	dn
  Address (6 lines)	postalAddress	inetOrgPerson	cis
  GUID	iplanetECGuid	iplanetECCommon	ces
  Status	iplanetBuyerStatus	iplanetBuyerPerson	ces
  Effective from Date	iplanetBuyerValidFromDate	iplanetBuyerPerson	cis
  Effective to Date	iplanetBuyerValidToDate	iplanetBuyerPerson	cis
  Phone	telephoneNumber	inetOrgPerson	tel (multi-valued)
  Fax	fax	inetOrgPerson	tel (multi-valued)
  Email	mail	inetOrgPerson	cis (multi-valued)
  Internal attribute	iplanetParentOrgGuid	iplanetECCommon	ces
  Preferred currency	iplanetECPerferredCurrency	iplanetECPerson	ces
  Preferred time zone	preferredTimeZone	iplanetPreferences	cis
  Preferred locale	preferredLocale	iplanetPreferences	cis

User Group Mapping

---

A user group entry has the following object classes:

• groupOfUniqueNames

• iplanetECCommon (auxiliary object class)

• iplanetBuyerUserGroup (auxiliary object class)

  
  

  Table C-5    User Group Attribute Mapping 
  
  

  BuyerXpert/SellerXpert Attribute	Directory Schema Attribute	Object Class	Syntax
  User group name	cn	groupOfUniqueNames	cis
  Short name	displayname	iplanetBuyerUserGroup	ces
  Group ID	iplanetECDefinableID	iplanetECCommon	cis
  Description	description	groupOfUniqueNames	cis
  GUID	iplanetECGuid	iplanetECCommon	ces
  Status	iplanetBuyerStatus	iplanetBuyerUserGroup	cis
  Effective from Date	iplanetValidFromDate	iplanetBuyerUserGroup	cis
  Effective to Date	iplanetValidToDate	iplanetBuyerUserGroup	cis
  Manager	iplanetBuyerManager	iplanetBuyerUserGroup	dn
  Internal attribute	iplanetParentOrgGuid	iplanetECCommon	dn

Location Mapping

---

A location entry has little leverage from existing standard object classes.

Table C-6    Location Attribute Mapping 

BuyerXpert/SellerXpert Attribute	Directory Schema Attribute	Object Class	Syntax
Location name	cn	iplanetBuyerLocation	cis
Display name	displayname	iplanetBuyerLocation	cis
Location ID	iplanetDefinableId	iplanetECCommon	cis
Description	description	iplanetBuyerLocation	cis
GUID	iplanetECGuid	iplanetECCommon	ces
D-U-N-S number	iplanetECDunsNumber	iplanetBuyerLocation	ces
Address (6 lines)	iplanetAddressLine	iplanetBuyerLocation	cis
Sub-localities	iplanetSubLocalities	iplanetBuyerLocation	cis
Minor locality	iplanetMinorLocality	iplanetBuyerLocation	cis
Major locality	iplanetMajorLocality	iplanetBuyerLocation	cis
Postal code	postalCode	iplanetBuyerLocation	cis
Status	iplanetBuyerStatus	iplanetBuyerLocation	cis
Effective from Date	iplanetBuyerFromDate	iplanetBuyerLocation	cis
Effective to Date	iplanetBuyerToDate	iplanetBuyerLocation	cis
Phone	telephoneNumber	iplanetBuyerLocation	tel multi-value
Fax	telephoneNumber	iplanetBuyerLocation	tel multi-value
Email	mail	iplanetBuyerLocation	cis multi-value
Web sites	url	iplanetBuyerLocation	cis multi-value
Internal attribute	iplanetECParentOrgGuid	iplanetECCommon	dn