Delegated Administrator Installation, Upgrade, and Configuration Issues (Sun Java Communications Suite 5 Release Notes)

Sun Java Communications Suite 5 Release Notes

Delegated Administrator Installation, Upgrade, and Configuration Issues

6434047

You cannot upgrade Delegated Administrator from version 2004Q2 to version 6.4 (the current release) when Access Manager is deployed to an Application Server node agent.

This issue occurs when Delegated Administrator is deployed to Application Server and you upgrade Application Server from version 7 to version 8.x. The asupgrade utility migrates the Application Server 7 server1 instance into the Application Server 8.x server1 target running under a nodeagent. However, asupgrade changes the value of the virtual server from server1 in Application Server 7 to server in Application Server 8.x.

Workaround:

When you run the Delegated Administrator configuration program, config-commda , in the Application Server Preferences panel, specify these values for the target and virtual server:

Target: server1
Virtual Server: server

6376896, 6294603

Upgrading to Access Manager 7.0 without upgrading Delegated Administrator to version 6.4 (the current release) will cause user creation to fail.

Note –

This issue occurs only if you are currently running Delegated Administrator 6 2005Q1 (Java ES Release 3) or earlier. If you have installed Delegated Administrator version 6 2005Q4 (Java ES Release 4) or have already upgraded Delegated Administrator to version 6.4, this issue does not occur.

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

The recommended way to solve this issue is to upgrade Delegated Administrator to version 6.4. If you have a compelling reason not to upgrade Delegated Administrator, take the steps described in the following workaround.

Workaround:

Update the UserCalendarService.xml file, located by default in the following directory:
/opt/SUNWcomm/lib/services/UserCalendarService.xml
In the UserCalendarService.xml file, mark the mail , icssubscribed, and icsfirstday attributes as optional instead of required.
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

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

Restart the Web container.

6310711

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

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.

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

/var/opt/SUNWcomm/da/WEB-INF/classes/
com/sun/comm/da/resources/daconfig.properties

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

Redeploy the edited daconfig.properties file to the Web container used by the Delegated Administrator console.

Before the change can take effect, you must run the script that deploys the customized daconfig.properties file to your Web container.

For instructions on how to deploy a customized properties file to a particular Web container, see To Deploy a Customized Configuration File in Sun Java System Delegated Administrator 6.4 Administration Guide.

6218713

Values in the resource.properties files are overwritten when Delegated Administrator is reconfigured with the config-commda program.

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

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

jdapi-wildusersearchmaxresults=50

jdapi-wildorgsearchmaxresults=10

And then you ran config-commda. These properties would be reset to their default values, as follows:

jdapi-wildusersearchmaxresults=-1

jdapi-wildorgsearchmaxresults=-1

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 resource.properties file).

Workaround: 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:

Back up the resource.properties file.

The resource.properties file is located in the following default path:
da_base/data/WEB-INF/classes/sun/comm/cli/server/servlet/ resource.properties
Run the config-commda program.
Edit the new resource.properties file created by the config-commda program. Follow these steps.

(The new file is located in the default path shown in 1. Back up the resource.properties file, above.)
1. Open the new resource.properties file.
  
  Be sure to edit the resource.properties file in the original (standard) location in the Delegated Administrator installation directory, not the file deployed to the Web container used by the Delegated Administrator server.
2. Open your back-up copy of the resource.properties file.
3. Locate the properties that were customized in the back-up copy. Apply the customized values to the corresponding properties in the new resource.properties file.
  
  Do not simply overwrite the new resource.properties file with the entire back-up copy. The new file may contain new properties created to support this release of Delegated Administrator.
Redeploy the edited resource.properties file to the Web container used by the Delegated Administrator server.

Before the change can take effect, you must run the script that deploys the customized resource.properties file to your Web container.

For instructions on how to deploy a customized properties file to a particular Web container, see To Deploy a Customized Configuration File in Sun Java System Delegated Administrator 6.4 Administration Guide.

5107441

If the first part of the default organization name created in the Delegated Administrator configuration program (config-commda) matches the root suffix name, the organization cannot be created.

When you run the config-commda program, if you specify a default organization DN whose first characters are same as the root suffix, a Name Collision error occurs. For example, if you create an organization named o=ispsesta.com and the root suffix is o=isp, this error occurs.

Workaround: Run the config-commda program in silent install mode with a state file. In silent install mode, the configuration program does not validate the organization DN value, so the organization can be created.

Alternatively, make sure that the default organization DN does not start with the same string as the root suffix name.