To configure Personal Address Book to use directory server other than user group directory server, set the following configuration parameters:

• ab.pstore.[identifier].ldaphost - Set this parameter to the host name of the LDAP server.

• ab.pstore.[identifier].ldapport - Set this parameter to the port number on which the LDAP server listens.

• ab.pstore.[identifier.ldapbinddn - Set this parameter to the LDAP bind dn value of the LDAP server.

• ab.pstore.[identifier].ldapbindcred - Set this parameter to the Bind credentials of the LDAP server.

The following example shows the configuration parameter settings:

iwcadmin -o ab.pstore.[psidentifier1].ldaphost -v host.siroe.com
iwcadmin -o ab.pstore.[psidentifier1].ldapport -v 400
iwcadmin -o ab.pstore.[psidentifier1].ldapbinddn -v "cn=Directory Manager"
iwcadmin -o ab.pstore.[psidentifier1].ldapbindcred -v dmcredentials

Personal store can be configured with multiple directory servers. In this example psidentifier1 is used to identify personal store configuration for siroe.com.

If the configured directory server needs to act as the personal store's default server, then set the ab.pstore.defaultserver configuration parameter. For example:

iwcadmin -o ab.pstore.defaultserver -v psidentifier1

To configure corporate directory to use directory server other than user group directory server, set the following configuration parameters:

• ab.corpdir.[identifier].ldaphost

• ab.corpdir.[identifier].ldapport

• ab.corpdir.[identifier].ldapbinddn

• ab.corpdir.[identifier].ldapbindcred

The following example has the configuration parameters settings:

iwcadmin -o ab.corpdir.[identifier].ldaphost -v host.siroe.com
iwcadmin -o ab.corpdir.[identifier].ldapport -v 400
iwcadmin -o ab.corpdir.[identifier].ldapbinddn -v "cn=Directory Manager"
iwcadmin -o ab.corpdir.[identifier].ldapbindcred -v xyzxyz

Where identifier identifies the corporate directory configuration for host.siroe.com. For a single corporate directory configuration, you must use default as the identifier.

See "Setting Up Multiple Corporate Directories" for information about configuring and enabling multiple corporate directories.

To enable autocomplete of email address for Corporate Directory, you must set the client.enablecorpabautocomplete configuration parameter to true.

iwcadmin -o client.enablecorpabautocomplete -v true

You can set up a domain based configuration for Personal Address Book and Corporate Directory.

To set up domain-based configuration for Personal Address Book, set the following parameters by using the iwcadmin command:

• ab.{identifier}.psrootpattern

• ab.{identifier}.pstore.defaultserver

• ab.{identifier}.pstore.[domain].ldaphost

• ab.{identifier}.pstore.[domain].ldapport

• ab.{identifier}.pstore.[domain].ldapbinddn

• ab.{identifier}.pstore.[domain].ldapbindcred

The following example shows the configuration parameter settings:

iwcadmin -o ab.{domain.com}.psrootpattern -v ldap:///piPStoreOwner=%U,o=%D,o=PiServerDb
iwcadmin -o ab.{domain.com}.pstore.defaultserver -v domainid1
iwcadmin -o ab.{domain.com}.pstore.[domainid1].ldaphost -v host.xyz.com
iwcadmin -o ab.{domain.com}.pstore.[domainid1].ldapport -v 400
iwcadmin -o ab.{domain.com}.pstore.[domainid1].ldapbinddn -v "cn=Directory Manager"
iwcadmin -o ab.{domain.com}.pstore.[domainid1].ldapbindcred -v xyzcred

Where domain.com is the domain (within curly braces).

All the configuration data for the domain domain.com is grouped in to one logical set identified by using the identifier domainid1.

The example shows the minimum set of configuration parameters that you need to set for the domain based configuration for Personal Address Book. However, you can set other configuration parameters.

To set the lookthrulimit to 2000 for Personal Address Book in domain domain.com, type the following command:

iwcadmin -o ab.{domain.com}.pstore.lookthrulimit -v 2000.

To set up domain-based configuration for Corporate Directory:

1. Set the following configuration parameters:

   • ab.{identifier}.corpdir.[domain].urlmatch

   • ab.{identifier}.corpdir.[domain].searchattr

   • ab.{identifier}.corpdir.[domain].lookthrulimit

   • ab.{identifier}.corpdir.[domain].ldaphost

   • ab.{identifier}.corpdir.[domain].ldapport

   • ab.{identifier}.corpdir.[domain].ldapbinddn

   • ab.{identifier}.corpdir.[domain].ldapbindcred

   For example:

   iwcadmin -o ab.{domain.com}.corpdir.[corpdomainid1].urlmatch
   -v ldap://corp-directory1
   iwcadmin -o ab.{domain.com}.corpdir.[corpdomainid1].searchattr
   -v entry/displayname,@uid
   iwcadmin -o ab.{domain.com}.corpdir.[corpdomainid1].lookthrulimit
   -v 3000
   iwcadmin -o ab.{domain.com}.corpdir.[corpdomainid1].ldaphost
   -v host.abc.com
   iwcadmin -o ab.{domain.com}.corpdir.[corpdomainid1].ldapport
   -v 389
   iwcadmin -o ab.{domain.com}.corpdir.[corpdomainid1].ldapbinddn
   -v "cn=Directory Manager"
   iwcadmin -o ab.{domain.com}.corpdir.[corpdomainid1].ldapbindcred
   -v abcabc
   

   Where domain.com specifies the domain. All the configuration data for the domain domain.com is grouped in to one logical set identified by using identifier corpdomainid1.

   Note:

   The value for the urlmatch configuration parameter must be unique. Format for urlmatch is ldap://unique_value or ldap://host:port/DN e.g. ldap://corp-directory1 ,ldap://corporatedirectory2, ldap://somehost:390/ou=people,o=ab.org etc.

   First time when user does address book operation (apart from login.wabp), corporate directory entry (under piPStoreOwner=user, o=domain, o=PiServerDb) with piRemotePiURL attribute value as urlmatch gets created. After this if urlmatch is changed, either delete such entries so that this entry gets created when first AB command is issued or update corporate directory entry for all users with new urlmatch value.

2. Copy dictionary-locale.xml (for example: dictionary-en.xml) from Convergence_Home/config/templates/ab/domain/defaultps to Convergence_Home/config/templates/ab/domain/domain-directory. The dictionary-locale.xml file can be updated in order to change or to customize display name and description.

In some cases, you might want to disable your corporate directory in certain domains. To do so, follow these steps:

1. Set both personal address book and Corporate Directory settings as described in "Setting Up Domain-Based Configuration for Address Book".

2. Disable the Corporate Directory for the specific domain:

   iwcadmin -o ab.{domain.com}.corpdir.[default].enable" -v false
   

3. Restart the Oracle WebLogic server.

   Note:

   You can ignore errors or exceptions in the log files.

To change the default corporate directory search filter, set the ab.corpdir.[identifier].searchfilter configuration parameter with the search criteria you want to base your corporate directory searches on.

The following example shows the usage of search customization:

iwcadmin -o ab.corpdir.[default].searchattr -v entry/displayname,@uid,person/surname
iwcadmin -o ab.corpdir.[default].searchfilter -v '(&(&([filter])(|(objectClass=GROUPOFUNIQUENAMES)(objectClass=GROUPOFURLS) \\
(objectClass=ICSCALENDARRESOURCE)(objectClass=INETORGPERSON)))(objectClass=*))'

Where [filter] is replaced with the search generated by the ab.corpdir.[identifier].searchattr configuration option.

The example produced the following LDAP output in the corporate LDAP directory access logs when an end-user searched for "bob":

[13/Oct/2008:11:51:54 +1100] conn=686404 op=30 msgId=576 - SRCH base="o=sun.com,o=isp" scope=2
filter="(&(&(|(|(cn=bob*)(uid=bob*))(sn=bob*))(|(objectClass=GROUPOFUNIQUENAMES)(objectClass=GROUPOFURLS)
(objectClass=ICSCALENDARRESOURCE)(objectClass=INETORGPERSON)))(objectClass=*))"
attrs="objectClass createTimestamp cn uid description mail multiLineDescription modifyTimestamp"

Follow these steps to configure Convergence to make use of virtual list view (VLV):

1. Configure Directory Server with VLV. For more information on creating and managing browsing indexes in Directory Server:

   • See Configuring VLV Browsing Indexes for Directory Server.

   • See Configuring VLV Indexes in Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory.

     Note:

     The following steps are applicable only if the Convergence Deployment is using the Convergence Address Book. When Contact Server is used as Address book service, the settings have to be changed in Contact Server. When Contact Server is configured in VLV mode, then all searches (for example, people, group, resources) use VLV.

2. Set the VLV filter and scope in the corporate directory.

   iwcadmin -o ab.corpdir.[default].vlvfilter -v  "(&(&(objectclass=inetorgperson)(mail=*)(cn=*)(!(psIncludeInGAB=false)))(objectClass=*))"
   iwcadmin -o ab.corpdir.[default].vlvscope -v 2
   iwcadmin -o ab.corpdir.[default].vlvsearchbase -v "o=example.com,o=usergroup"
   iwcadmin -o ab.corpdir.[default].vlvsortby -v "entry/displayname"
   

3. Enable the ab.corpdir.[default].vlvpaging configuration parameter to true.

   iwcadmin -o ab.corpdir.[default].vlvpaging -v true

Convergence supports the following vCard standards:

• vCard 2.1

• vCard 3.0

Convergence supports the following encoding formats for importing and exporting vCard:

• UTF-8

• ISO-8859-1

• BIG5

• EUC-CN

• EUC-JP

• EUC-KR

• SHIFT_JIS

Convergence supports the following locales by default:

• English

• Japanese

• French

• German

• Spanish

• Korean

• Traditional Chinese

• Simplified Chinese

For each locale, configuration parameters for import and export exist in the Convergence server. By default, these configuration parameters are assigned a character encoding when you install Convergence.

Table 6-1 shows the default encoding formats for locales when Convergence is installed. The table also lists the configuration parameters that are assigned for storing the import and export preference for the locale.

In the previous table, the character encoding for English is set to UTF-8. This setting means that when you import or export vCard contacts to or from the Convergence client, the vCard entries are imported or exported in the UTF-8 format character set. In this case, UTF-8 is the default setting for English users.

To enable the Convergence client to import or export vCard entries to other character sets, set the address book vCard configuration parameter in the Convergence server.

Type the iwcadmin command to set the import and export character set preferences for the configuration parameters of the locale. This command enables you to change the character set encoding for importing or exporting vCard entries.

To change the character encoding for the Japanese user vCard from UTF-8 to Shift_JIS for example, set the corresponding configuration parameters for import and export.

To set the character encoding to import vCard entries for the Japanese locale, type the following command:

iwcadmin -o ab.import.vcard.misc.ja -v Shift_JIS

To set the character encoding to export vCard entries for the Japanese locale, type the following command:

iwcadmin -o ab.export.vcard.misc.ja -v Shift_JIS

The vCard entries are imported or exported in the Shift_JIS encoding character set.

vCard 3.0 enables users to include photos in their contacts. By default, Convergence does not import or export photos of your contacts. If you want photos to be imported or exported, you must enable the ab.exportphoto and ab.importphoto configuration parameters.

To enable exporting of contacts with photo in Vcard 3.0 format, type the following command:

iwcadmin -o ab.exportphoto -v true

To import contacts with photo in Vcard 3.0 format, type the following command:

iwcadmin -o ab.importphoto -v true

When looking in the Corporate Directory of the default domain all the administrative accounts are being displayed. These can be hidden by using psIncludeInGAB attribute in the ldap server. The default value of this attribute is true.

If you want to hide users in the Corporate Directory, set in a first step the psIncludeInGAB attribute to false for these users. Next, the corporate directory search filter needs to exclude these users with their psIncludeInGAB attribute set to false. For example:

iwcadmin -o ab.corpdir.[default].searchfilter  -v
'(&([filter])(!(psIncludeInGAB=false)))'

If a contact has been deleted by the end user, Convergence determines what do to with that information based on how you set the ab.pstore.deleteperm configuration parameter. If you set the parameter to true, the contact is deleted from the user's personal address book entries on Directory Server. If, however, you set ab.ps.deleteperm to false, the following attribute/value pair is added to the deleted contact in Directory Server:

delete: true

The contact no longer appears in Convergence as if it were permanently deleted from the Directory Server.

This task can be particularly useful when you are synchronizing deleted contact entries in Microsoft Outlook and Convergence when using Connector for Microsoft Outlook.