Previous Contents Index Next |
BuyerXpert/SellerXpert 4.1 (BuyerXpert SP3) Administrator's Guide |
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
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
The tasks involved in administering LDAP entries are performed to ensure interoperability with other applications.Every organization domain, which spans the ownership of different related entities, is private to itself
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.
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.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.
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:
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.
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
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
User Mapping
A user entry has the following object classes:
person
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
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
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
Previous Contents Index Next
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.
Last Updated October 08, 2001