Sun Java System Communications Services 2005Q4 Release Notes

Installation, Upgrade, and Configuration

When you upgrade from Application Server 7.x (Java ES Release 2) to Application Server 8.x (Java ES Release 4) and then upgrade to Delegated Administrator 6 2005Q4 (Java ES Release 4), Delegated Administrator fails to redeploy to the upgraded Application Server. (6319257)

After an upgrade to Application Server 8.x, applications such as Delegated Administrator are automatically redeployed to a non-DAS server1 instance. To maintain compatibility, the non-DAS instance runs on the same port as the previous release of Application Server.

However, Delegated Administrator uses the deploydir command to deploy to Application Server. In Application Server 8.x, the deploydir command only works on DAS instances. Delegated Administrator cannot be deployed to the non-DAS instance.


After you have upgraded to Application Server 8.x, take the following steps:

  1. Modify the following Access Manager configuration properties file:


    by replacing the following line:



  2. Before you run the Delegated Administrator configuration program, undeploy the /commcli and /da web applications from the server1 instance in the upgraded Application Server. Run the following commands:

    /opt/SUNWappserver/appserver/bin/asadmin undeploy 
    --secure=false --user admin --password xxxx
    --target server1 commcli

    /opt/SUNWappserver/appserver/bin/asadmin undeploy 
    --secure=false --user admin --password xxxx
    --target server1 da
  3. Run the Delegated Administrator configuration program, config-commda. When you are prompted for the Access Manager host and port, specify the port for the DAS server instance.

    Specify the DAS server instance, even though Access Manager is running on the non-DAS server1 instance.

    When the config-commda program asks you where to deploy the Delegated Administrator console and Delegated Administrator server, specify the DAS server information, not the server1 information.

    If you already have configured Delegated Administrator with the server1 port (if you have already run config-commda), modify the port information (to specify the DAS port) in the following two files:

  4. After you run config-commda, log in to the Application Server console. Copy all Access Manager library paths in the JVM settings for classpath-prefix and classpath-suffix entries from the server1 instance to the server instance. You can perform this task by copying the paths in the server1 domain.xml file to the server domain.xml file.

The Delegated Administrator configuration program allows you to enter invalid values in the Domain Separator field. (6310711)

In the configuration program, config-commda, you can enter invalid characters such as ^ in the Domain Separator field. You cannot log into the Delegated Administrator console using a login ID with the invalid domain-separator character.


Edit the value of the commadminserver.domainseparator property in the file, located in the following default path:


Use a valid value such as @, -, or _.

Upgrading to Access Manager 7.0 without upgrading to Delegated Administrator 6 2005Q4 (Java ES Release 4) will cause user creation to fail. (6294603)

When you upgrade to Java Enterprise System Release 4, if you upgrade Access Manager from version 6.x to 7.0 but do not upgrade Delegated Administrator to version 6 2005Q4 (Java ES Release 4), user creation with mail or calendar service will fail.


  1. Update the UserCalendarService.xml file, located by default in the following directory:


    In the UserCalendarService.xml file, mark the mail , icssubcribed, and icsfirsdayattributes as optional instead of required.

  2. In Access Manager, remove the existing xml file by running the amadmin command, as in the following example:

    amadmin -u amadmin -w netscape -r UserCalendarService
  3. In Access Manager, add the updated xml file, as in the following example:

    amadmin -u amadmin -w netscape  
    -s /opt/SUNWcomm/lib/services/UserCalendarService.xml
  4. Restart the Web container.

The Delegated Administrator configuration program (config-commda) can be slow if a very large number of organizations are deployed in the directory. (6219610)

If the directory contains a very large number of organizations (50,000 or more), the Delegated Administrator configuration program (config-commda) can take a long time to complete. Performance of administrative tasks related to Access Manager is slow.


Create a pres,eq index on the ou attribute.

Values in the files are overwritten when Delegated Administrator is reconfigured with the config-commda program. (6218713)

If you configure an existing, configured installation of Delegated Administrator by running the config-commda program again, the properties in the file are reset to their default values.

For example, if you previously set the following properties to these values:



and then run config-commda, these properties would be reset to their default values, as follows:



This issue is of concern only if you have changed the Delegated Administrator configuration (if you have enabled plug-ins or modified the values of any properties in the file).


If you need to upgrade Delegated Administrator, or if you need to rerun the config-commda program for any other reason, you can preserve your existing configuration by taking the following steps:

  1. Back up the file.

    The file is located in the following default path:

  2. Run the config-commda program.

  3. Edit the new file created by the config-commda program, as follows:

    (The new file is located in the default path shown in 1. Back up the file, above.)

    a. Open the new file.

    b. Open your back-up copy of the file.

    c. Locate the properties that were customized in the back-up copy. Apply the customized values to the corresponding properties in the new file.

Do not simply overwrite the new file with the entire back-up copy. The new file may contain new properties created to support this release of Delegated Administrator.