If you are configuring Delegated Administrator for the first time, you can skip this section and go directly to the section, Choose Which Components to Configure.
If you are upgrading to this release of Delegated Administrator from an earlier release, you might have to perform the following tasks before you configure Delegated Administrator:
For instructions on how to upgrade Delegated Administrator from a previous Sun Java version, see the chapter called “Upgrading Delegated Administrator” in theSun Java Communications Suite Upgrade Guide.
This section concerns you only if you previously have installed and configured Delegated Administrator and have customized the Delegated Administrator configuration.
If you have a customized configuration and you rerun the Delegated Administrator configuration program, config-commda, the properties in the configuration files are reset to their default values. These files are listed below, in Delegated Administrator Properties Files.
For information about how you can customize Delegated Administrator, see Chapter 4, Customizing Delegated Administrator.
You should preserve your customized configuration before you upgrade Delegated Administrator or rerun the Delegated Administrator configuration program for any other reason.
Delegated Administrator installs the following properties files:
Delegated Administrator utility
Delegated Administrator console
For the default location of the Delegated Administrator console files, see Original (Standard) Locations of the Configuration Files.
Delegated Administrator server
For the default location of the resource.properties file, see Original (Standard) Locations of the Configuration Files.
Back up the properties files you have customized.
For a list of the properties files, see Delegated Administrator Properties Files.
Run the config-commda program, as described in the following sections.
The remaining steps use the resource.properties file as an example. Repeat these steps for each file you have customized.
Edit the new resource.properties file created by the config-commda program, as follows:
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.
Open your back-up copy of the resource.properties file.
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.
This section concerns you only if you are upgrading from Communications Services 6 2005Q4 Delegated Administrator to Delegated Administrator 6.4 (the current release), and you created customized service packages in the previous release (6 2005Q4).
In Delegated Administrator 6.4, service package templates are located in a different node in the directory than they were in the previous (6 2005Q4) release.
When you run the Delegated Administrator configuration program, the previously installed sample Class-of-Service templates installed by the Delegated Administrator configuration program are upgraded automatically. (In the configuration program, you should select Load sample service packages in the Service Package and Organization Samples panel.)
If you use only the sample templates to assign service packages to users and groups, no action is required.
The configuration program does not upgrade customized service packages created in the 6 2005Q4 release. You must upgrade your customized service packages manually.
For information on how customized service packages are created, see Creating Your Own Service Packages.
Perform the following operations on the LDAP directory:
Copy your service package templates from this directory node:
to this directory node:
where service_target is one of the following:
mailuser calendaruser mailcalendaruser mailgroup
For example, if a service package template is called myservicepackage, and it provides mail service to users, the service package template's new dn would be:
Remove the entries for your service package templates from the original directory node:
Edit each customized service package by adding the following line to the ldif file defining the service package:
daServiceType:service type target
If your ldif file already contains the daServiceType attribute, you can skip this step.
The daServiceType attribute defines the type of service provided by the service package and the target for the service package.
The service can be mail or calendar.
The target can be users or groups.
daServiceType: mail user
The following example shows what the edited ldif file might look like:
dn: cn=myservicepackage,o=mailuser,o=cosTemplates,o=mycompanysuffix changetype: modify replace: daServiceType daServiceType: mail user
For example, you could run the following command:
ldapmodify -D <directory manager> -w <password> -f myservicepackagemodldif
<directory manager> is the name of the Directory Server administrator.
<password> is the password of the Directory Service administrator.
myservicepackagemodldif is the name of the ldif file containing the modifications described in the preceding steps.