test

Sun Java System Communications Express 6 2005Q4 Administration Guide

ProcedureAccessing Address Book

A “Server Error” occurs when Address Book is accessed. The Web Server log records an exception “org.apache.xml.utils.WrappedRuntimeException: The output format must have a ’{http://xml.apache.org/xslt}content-handler’ property!”

This exception is thrown by Web Server when JDK Web Server points to a version lower than JDK 1.4.2. The Communications Express uses the latest version of xalan and xerces for XML/XSL parsing. This error can appear when:

Steps

  1. You are using Web Server 6.1 not deployed using JES installer. JDK 1.4.1 is usually bundled with Web Server 6.1.

  2. The version of the shared xalan and xerces components shipped with Java Enterprise System, are not the latest.

    Work around

    • If the error appears because you have not installed Web Server from the JES installer, manually upgrade the JDK version of the web container that is defined as java_home attribute of java tag in server.xml Web Server configuration file.

      or

      Re-install webserver from Java Enterprise System, and have the install process upgrade JDK automatically.

    Note –

    If this step is performed, all the other web-applications must be redeployed. As a precaution, take a backup of the server.xml file.

    • If the error appears because the version of the shared xalan and xerces components are not the latest, remove the symbolic links for xalan.jar and xerces.jar from uwc-deployed-path/WEB-INF/lib.

      For example:

      # cd /var/opt/SUNWuwc/WEB-INF/lib

      # rm xalan.jar xercesImpl.jar

      Then, restart the Web Server.

    The message “An error occurred during this operation” appears when Address Book is accessed from Communications Express.

    This error occurs when the LDAP configuration for Personal Address Book (PAB) is not correct. When the Address Book tab is accessed, Communications Express connects to the personal address book store, that is, the LDAP configured for PAB. If the personal address book store is unable to establish a connection, the error is displayed.

    Work around

  3. Check the LDAP configuration in WEB-INF/config/ldappstore/db_config.properties .

  4. Edit the incorrect configuration settings.

  5. Restart the Web Server where Communications Express is deployed.

    For more information, refer to the section Configuring Corporate Directory Parameters db_config.properties File

    Corporate Directory shows an inline error when search is performed.

    This could happen if LDAP configuration for Corporate Directory is not configured properly.

    Work around.

    Check the LDAP configuration in WEB-INF/config/corp-dir/db_config.properties for any misconfigurations, correct them and then restart Communications Express.

    For more information, refer to the section Configuring Corporate Directory Parameters db_config.properties File

    Viewing contacts of Corporate Directory shows error in View window

    This error is displayed when the key to access a contact entry in Corporate Directory is not “uid.”

    uid is the default value set by Communications Express.

    Work around

    To access the contacts from Corporate Directory the key value should be set to the desired value in db_config.properties and xlate-inetorgperson.xml configuration files in uwc-deployed-path/WEB-INF/config.

    Make the following changes in the files:

  6. Set the appropriate key value in uwc-deployed-path /WEB-INF/config/WEB-INF/config/corp-dir/db_config.properties.

  7. Set the appropriate key in place of “uid” in entry entryID="db:uid" in

    uwc-deployed-path/WEB-INF/config/WEB-INF/config/corp-dir/xlate-inetorgperson.xml .

  8. Restart the Web Server where Communications Express is deployed.

    For more information, refer to the section Configuring Corporate Directory Parameters db_config.properties File

    The value of psRoot cannot be set.

    The LDAP attribute psRoot in User Preferences is used for Addressbook Server Horizontal Scalability. For more details, see the section, Supporting Horizontal Scalability of Addressbook Server deployment does not require Addressbook Server Horizontal Scalability, you may ignore this error.

    When a user logs into Communications Express for the first time, the psRoot is attempted to be set automatically, but sometimes the value may not be automatically set. This typically happens when the Java Enterprise System Directory Server has not been installed and comm_dssetup.p1 for Java Enterprise System has not be run after installing Java Enterprise System Directory Server. This results in the LDAP Schema not being updated.

    Since the schema is not updated, the psRoot attribute cannot be manually set even when the attribute is required for a horizontally scalable Addressbook Server deployment.

    Work around

    To enable the setting of the psRoot attribute, update the Directory Server to include the psRoot attribute. To do this, include the attribute psRoot in the definition of ipUser object class in

    Directory ServerInstance/ config/schema/99user.ldif.

    Note –

    You need to update the Directory Server to include the psRoot attribute only if in the current deployment, the Java Enterprise System Directory Server has not been installed and you have not run comm_dssetup.p1 for Java Enterprise System after installing Java Enterprise System Directory Server.