Configuring Corporate Directory Parameters in the db_config.properties File (Sun Java System Communications Express 6.3 Administration Guide)

Sun Java System Communications Express 6.3 Administration Guide

Configuring Corporate Directory Parameters in the `db_config.properties` File

Table 3–8 lists the default corporate directory parameters in the db_config.properties file. By default, all the LDAP related information is set based on the values mentioned for the user or group directory.

The db_config.properties file can be accessed from:WEB-INF/config/corp-dir/

Table 3–8 Corporate Directory Parameters


Parameter	Default Value	Description
`defaultserver.ldaphost`		Specifies the LDAP host for the Corporate Directory.
`defaultserver.ldapport`		Specifies the port for the Corporate Directory.
`defaultserver.ldapbinddn`		Specifies the DN used to bind to the Corporate Directory. If the login type is `restricted` or `proxy` it is mandatory to assign a value to `defaultserver.ldapbinddn`. If the login type is `anonymous` you need not enter a value for this parameter.
`defaultserver.ldapbindcred`		Specifies the bind password.
`entry_id`	uid	Specifies the key in the corporate directory used to identify a contact or group entry. You can set the `entry_id` to the UID or a key used to fetch the contact or group information, such as, `empid` or principal ID. In the `xlate-inetorgperson.xml` file replace “`uid`” in `<entry entryID= “db:uid”\>` with the `entry_id` value specified here.
`login_type`	restricted	Specifies the method using which the connection to the LDAP store is maintained. You can assign the following three values to this parameter: anon - Enables users to connect to the LDAP as an anonymous user. restricted - Enables users to connect as a user who has the rights to perform operations on the Address Book Store. proxy - Enables users to masquerade as a user who can perform operations on the Address Book Store. Assigning this value enhances performance as it bypasses the LDAP bind on each operation. NOTE: A Read only access is given to a masquerading user.
`defaultserver.ldappoolmin`	1	Specifies the minimum number of LDAP client connections maintained for Corporate Directory.
`defaultserver.ldappoolmax`	4	Specifies the maximum number of LDAP client connections maintained for Corporate Directory.
`defaultserver.ldappooltimeout`	60	Specifies the number of seconds before timing out an LDAP connection. Increase this value to accommodate large search results.
`lookthru_limit`	3000	Specifies the search query limit for a search.

Corporate Directory maintains the following two xlate files in the format xlate-objectclass-name.xml.

xlate-inetorgperson.xml for contacts
xlate-groupofuniquemembers.xml for groups

In xlate-objectclass-name .xml, objectclass-name represents the object class identifying a particular LDAP entry type. For example, xlate-inetorgperson.xml is an object class used to identify a contact, and groupofuniquemembers is an object class used to identify a group in Sun Java System Directory Server.

The xlate files contain the field mappings between an LDAP schema and the address book XML schema for a contact or group. The mapping is defined in terms of XML nodes. For example,

ab-xml-schema-keydb:LDAPField /ab-xml-schema-key

In this example:

ab-xml-schema-field is the value that the address book uses in the code.
LDAPField is the corresponding field name in LDAP.

You need to provide an appropriate field name for LDAPField. The value assigned to LDAPField should correspond to the value of LDAPField existing in your corporate directory LDAP schema.

Example 3–1 is an example of the xlate-inetorgperson.xml file.

Example 3–1 Default Contents of xlate-inetorgperson.xml

<abperson uid="db:uid">
  <entry entryID="db:uid">
    <displayname>db:cn</displayname>
    <description>db:multilineDescription</description>
    <creationdate>db:createtimestamp</creationdate>
    <lastmodifieddate>db:modifytimestamp</lastmodifieddate>
  </entry>
  <person>
    <givenname>db:givenname</givenname>
    <surname>db:sn</surname>
  </person>
  <organization>
    <company>db:company</company>
    <organizationalunit>db:ou</organizationalunit>
    <location>db:expr: db:iplanetbuildingnum+' '+db:iplanetbuildinglev+' '+db:roomNumber</location>
    <title>db:title</title>
    <manager>db:manager</manager>
    <secretary>db:secretary</secretary>
  </organization>
  <phone priority="1" type="work">db:telephoneNumber</phone>
  <phone priority="2" type="fax">db:facsimileTelephoneNumber</phone>
  <phone priority="3" type="mobile">db:mobile</phone>
  <phone priority="4" type="home">db:homePhone</phone>
  <phone priority="5" type="pager">db:pager</phone>
  <email priority="1" type="work">db:mail</email>
  <im priority="1" service="SunONE">db:uid</im>
  <im priority="2" service="AIM">db:aimscreenname</im>
  <im priority="3" service="ICQ">db:icqnumber</im>
  <postaladdress type="home">
    <street>db:homePostalAddress</street>
  </postaladdress>
  <postaladdress type="work">
    <street>db:postaladdress</street>
  </postaladdress>
  <weburl priority="1">
    <urladdr>db:labeleduri</urladdr>
    <description>URL</description>
  </weburl>
  <weburl priority="2">
    <urladdr>db:homepage</urladdr>
    <description>Home URL</description>
  </weburl>
  <calendar type="calendar">
    <urladdr>db:caluri</urladdr>
  </calendar>
</abperson>