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 Java Enterprise System 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 System version, see the chapter called “Upgrading Delegated Administrator” in the Sun Java Enterprise System 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:
Default location: /var/opt/SUNWcomm/config
Back up the properties files you have customized.
For a list of the properties files and their default locations, 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.
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.
This section concerns you only if you are upgrading from Communications Services 6 2005Q1 Delegated Administrator to Communications Services 6 2005Q4 Delegated Administrator, and you created customized service packages in the previous release (6 2005Q1).
In the current (6 2005Q4) release of Delegated Administrator, service packages can provide calendar service and mail service, and they are targeted either at users or at groups. In the previous (6 2005Q1) release, service packages provided mail service to users only. Service package definitions include a new attribute to support the new functions.
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 2005Q1 release. You must upgrade your customized service packages manually.
For information on how customized service packages are created, see Creating Your Own Service Packages.
Edit each customized service package by adding the following line to the ldif file defining the service package:
daServiceType: mail user
The daServiceType attribute defines the type of service (mail or calendar) and the target (users or groups).
Service packages created in the previous release only provided mail service to users. Thus, the value of daServiceType should be mail user.
The following example shows what the edited ldif file might look like:
dn: cn=myservicepackage,o=cosTemplates,o=mycompanysuffix changetype: modify replace: daServiceType daServiceType: mail user
Use the LDAP directory tool ldapmodify to update the service package in the directory.
For example, you could run the following command:
ldapmodify -D <directory manager> -w <password> -f myservicepackage
<directory manager> is the name of the Directory Server administrator.
<password> is the password of the Directory Service administrator.
myservicepackage is the name of the ldif file defining the customized service package.