Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 2005Q4 Upgrade Guide 

Chapter 19
Delegated Administrator

This chapter describes how to upgrade Delegated Administrator to Java ES 2005Q4 (Release 4): Sun Java System Communication Services Delegated Administrator 6.3 2005Q4. The chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Java ES Release 4. The chapter covers upgrades on both the Solaris and Linux operating systems:

Overview of Delegated Administrator Upgrades

This section describes the following general aspects of Delegated Administrator that impact upgrading to Java ES 2005Q4 (Release 4):

About Java ES Release 4 Delegated Administrator

Java ES Release 4 Delegated Administrator new features with respect to Release 3 include calendar service provisioning, mail group provisioning, improved UI navigation based on usability feedback, and various bug fixes.

Delegated Administrator Upgrade Roadmap

Table 19-1 shows the supported Delegated Administrator upgrade paths to Java ES Release 4. The table applies to both Solaris and Linux operating systems.

Table 19-1  Upgrade Paths to Java ES Release 4:
Sun Java System Communication Services Delegated Administrator 6.3 2005Q4 

Java ES Release

Delegated Administrator Version

General Approach

Re-configuration Required

Release 3

Sun Java System Communication Services Delegated Administrator 6 2005Q1

Direct upgrade:
Performed by applying patches and running config-commda utility.

Configuration data

Release 2

Sun Java System Communication Services User Management Utility 1.1 (2004Q2)

Direct upgrade:
Performed by applying patches and running config-commda utility.

Configuration data

Release 1

User Management Utility (2003Q4)

Direct upgrade not certified:
But can be performed by applying patches and running config-commda utility.

Configuration data

Pre-dates Java ES releases

iPlanet Delegated Administrator

No direct upgrade

 

Delegated Administrator Data

The following table shows the type of data that could be impacted by an upgrade of Delegated Administrator software.

Table 19-2  Delegated Administrator Data Usage

Type of Data

Location

Usage

Directory schema

Directory Server user/group directory

For attributes needed to support end users, organizations, and services schema

Configuration data

DelegatedAdmin-base/data/WEB-INF/classes/sun/comm/cli/server/servlet/resource.properties

Delegated Administrator server configuration and customizations

DelegatedAdmin-base/data/da/WEB-INF/classes/com/
sun/comm/da/resources/daconfig.properties

Delegated Administrator console configuration

DelegatedAdmin-base/data/da/WEB-INF/classes/com/
sun/comm/da/resources/logger.properties

Delegated Administrator console logging

DelegatedAdmin-base/data/da/WEB-INF/classes/com/
sun/comm/da/resources/security.properties

Delegated Administrator console configuration

Web container configuration

Web Server:
server.policy and server.xml files in
WebServer-base/https-hostname/config

Application Server (Java ES Release 3 and 4):
server.policy and domain.xml files in
AppServer8Config-base/domains/domainName/config

Application Server (Java ES Release 2):
server.policy and server.xml files in
AppServer7Config-base/domains/domainName/config

Configuration of Delegated Administrator web container instance.

Compatibility Issues

Release 4 Delegated Administrator introduces graphical user interface changes but is backwardly compatible with earlier versions.

Delegated Administrator Dependencies

Delegated Administrator dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Delegated Administrator software. Changes in Delegated Administrator interfaces or functions, for example, could require upgraded version of components upon which Delegated Administrator depends. The need to upgrade such components depends upon the specific upgrade path.

Delegated Administrator has dependencies on the following Java ES components:

Upgrading Delegated Administrator from Java ES Release 3

This section includes information about upgrading Delegated Administrator from Java ES 2005Q1 (Release 3) to Java ES Release 4. The section covers the following topics:

Introduction

When upgrading Java ES Release 3 Delegated Administrator to Release 4, consider the following aspects of the upgrade process:

Release 3 Delegated Administrator Upgrade

This section describes how to perform an upgrade of Delegated Administrator from Java ES Release 3 to Java ES Release 4 on both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Delegated Administrator you should perform the tasks described below.

Verify Current Version Information

You can verify the current version of Delegated Administrator by entering the following command:

Apply Necessary Operating System Patches

On Solaris 10 operating system platforms, you need to apply an operating system patch to perform the Delegated Administrator upgrade procedure (see Required Operating System Patches).

Upgrade Delegated Administrator Dependencies

It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Java ES Release 4. However, Delegated Administrator has a hard upgrade dependency only on Directory Preparation Tool. Upgrading of other Java ES Release 3 components upon which Delegated Administrator depends is therefore optional.

However, if you choose to upgrade all Delegated Administrator dependencies, they should be upgraded in the following order, all before you upgrade Delegated Administrator. You can skip any that might already have been upgraded.

  1. Shared Components.  Instructions for upgrading Java ES shared components to Release 4 are provided in Upgrading Java ES Shared Components.
  2. Directory Server.  Instructions for upgrading Directory Server to Release 4 are provided in Chapter 4, "Directory Server and Administration Server".
  3. Web Container Software.  Instructions for upgrading Web Server or Application Server are provided in Chapter 6, "Web Server" and Chapter 9, "Application Server", respectively.
  4. Access Manager (Access Manager SDK).  Instructions for upgrading Access Manager to Release 4 are provided in Chapter 11, "Access Manager".
  5. Directory Preparation Tool.   Release 4 Directory Preparation Tool needs to have been run against Directory Server before using Release 4 Delegated Administrator. If Directory Preparation Tool has not already been run against Directory Server, upgrade Directory Preparation Tool to Release 4 and use it to modify and extend the schema of Directory Server (see Chapter 12, "Directory Preparation Tool" for procedures).
Back Up Delegated Administrator Data

The Delegated Administrator upgrade from Release 3 to Release 4 requires re-configuration of Delegated Administrator. It is a good idea to back up configuration data as a safety precaution, and to back up any Release 3 graphical user interface customizations.

Obtain Required Configuration Information and Passwords

You should know the following information about your currently installed version:

Upgrading Release 3 Delegated Administrator (Solaris)

This section discusses considerations that impact the upgrade procedure for Delegated Administrator followed by a description of the procedure itself.

Upgrade Considerations (Solaris)

The upgrade of Delegated Administrator software to Java ES Release 4 takes into account the following considerations:

Upgrade Procedure (Solaris)

The procedure documented below applies to Delegated Administrator on the computer where the upgrade is taking place.

  1. Obtain the required patches, based on Table 19-4.

    2. Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

  2. Log in as root or become superuser.

    3. su -

  3. If you have not already done so, upgrade all shared components, the web container, and Access Manager (or Access Manager SDK).

    4. See Upgrade Delegated Administrator Dependencies.

  4. Apply the appropriate Delegated Administrator patches in Table 19-4.

    5. patchadd patch_ID

  5. Confirm that the patch upgrade was successful:

    6. showrev -p | grep patch_ID

    The output should return the versions of patch IDs applied in Step 4.

  6. Reconfigure Delegated Administrator.
    1. Make sure Directory Server is running.
    2. Make sure the web container running Access Manager and Delegated Administrator is running.

      3. To start the web container:

      Web Server:
      WebServer-base/https-instanceName/start

      Application Server:
      AppServer8-base      /bin/asadmin start-domain domainName
           --user       admin_ID --password password

      where Access Manager and Delegated Administrator are deployed in a server instance in the domainName domain. The default domainName is domain1 and the default server instance is server1.

    3. Run the Delegated Administrator configuration utility.

      4. DelegatedAdmin-base/sbin/config-commda

      For details of how to use this utility, see Chapter 3 Configuring Delegated Administrator of the Sun Java System Communications Services 6 2005Q4 Delegated Administration Guide (http://docs.sun.com/doc/819-2658).

  7. Stop and restart the Delegated Administrator web container.

    8. Web Server:
    WebServer-base/https-instanceName/stop
    WebServer-base/https-instanceName/start

    Application Server:
    AppServer8-base/bin/asadmin stop-domain domainName
    AppServer8-base    /bin/asadmin start-domain domainName
         --user     admin_ID --password password

Upgrading Release 3 Delegated Administrator (Linux)

This section discusses considerations that impact the upgrade procedure for Delegated Administrator followed by a description of the procedure itself.

Upgrade Considerations (Linux)

The upgrade of Delegated Administrator software to Java ES Release 4 on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux Release 4 upgrade patches differ from the Solaris patches.

The Release 4 Delegated Administrator upgrade patch for Linux OS is shown in the following table:

Table 19-5  Patches1 to Upgrade Delegated Administrator on Linux 

Description

Patch ID and RPM names

Delegated Administrator

119779-09

  • sun-commcli-client-1.1-11.9.i386.rpm
  • sun-commcli-server-1.1-11.9.i386.rpm

1Patch revision numbers are the minimum required for upgrade to Java ES Release 4. If newer revisions become available, use the newer ones instead of those shown in the table.

Upgrade Procedure (Linux)

The procedure documented below applies to Delegated Administrator on the computer where the upgrade is taking place.

Caution

An upgrade from Java ES Release 3 to Java ES Release 4 on Linux cannot be rolled back.

  1. Obtain the required patches using the patch numbers and RPM names from Table 19-5. Use this information to obtain the version numbers for the RPM.

    2. Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

  2. Log in as root or become superuser.

    3. su -

  3. If you have not already done so, upgrade all shared components, the web container, and Access Manager (or Access Manager SDK).

    4. See Upgrade Delegated Administrator Dependencies.

  4. Apply the RPMs for Delegated Administrator in Table 19-5.

    5. rpm -Fvh sun-commcli-client-1.1-11.9.i386.rpm
    rpm -Fvh sun-commcli-server-1.1-11.9.i386.rpm

  5. Confirm that the patch upgrade was successful:

    6. rpm -qa | grep sun-commcli

    The new version numbers of the RPMs should be returned.

  6. Reconfigure Delegated Administrator.
    1. Make sure the web container running Access Manager and Delegated Administrator is running.

      2. To start the web container:

      Web Server:
      WebServer-base/https-instanceName/start

      Application Server:
      AppServer8-base      /bin/asadmin start-domain domainName
           --user       admin_ID --password password

      where Access Manager and Delegated Administrator are deployed in a server instance in the domainName domain. The default domainName is domain1 and the default server instance is server1.

    2. Run the Delegated Administrator configuration utility.

      3. DelegatedAdmin-base/sbin/config-commda

      For details of how to use this utility, see Chapter 3 Configuring Delegated Administrator of the Sun Java System Communications Services 6 2005Q4 Delegated Administration Guide (http://docs.sun.com/doc/819-2658).

  7. Stop and restart the Delegated Administrator web container.

    8. Web Server:
    WebServer-base/https-instanceName/stop
    WebServer-base/https-instanceName/start

    Application Server:
    AppServer8-base/bin/asadmin stop-domain domainName
    AppServer8-base    /bin/asadmin start-domain domainName
          --user     admin_ID --password password

Verifying the Upgrade

You can verify successful upgrade of Delegated Administrator as follows:

  1. Check the version number.

    2. DelegatedAdmin-base/bin/commadmin -V

    See Table 19-3 for output values.

  2. Log in to the Delegated Administrator console using the top level administrator user ID and password specified during re-configuration of Delegated Administrator.

    3. http://hostName:port/da/DA/Login

    where hostName:port are values provided during re-configuration of Delegated Administrator.

Post-Upgrade Tasks

There are no post-upgrade tasks beyond the steps described in Upgrade Procedure (Solaris) and Upgrade Procedure (Linux).

Rolling Back the Upgrade (Solaris)

Rollback of Delegated Administrator is not supported. Changes made during the upgrade procedure, such as entries in Directory Server or in deploying Delegated Administrator into the web container cannot easily be backed out.

Upgrading Delegated Administrator from Java ES Release 2

The procedure for upgrading Java ES 2004Q2 (Release 2) Delegated Administrator to Release 4 is the same as that for upgrading Release 3 Delegated Administrator to Release 4, with a couple of exceptions, noted below.

Upgrade Delegated Administrator Dependencies

The pre-upgrade tasks for upgrading Java ES Release 2 Delegated Administrator to Release 4 are similar to those for upgrading Release 3 Delegated Administrator to Release 4, with the exception that the upgrade of Delegated Administrator dependencies should include the upgrading to Release 4 of all shared components (see Table 1-6) and all locally-resident product components upon which Delegated Administrator depends.

When upgrading Delegated Administrator dependencies, they should be upgraded in the following order, all before you upgrade Delegated Administrator. You can skip any that might already have been upgraded.

  1. Shared Components.  Instructions for upgrading Java ES shared components to Release 4 are provided in Chapter 2, "Upgrading Java ES Shared Components".
  2. Directory Server.  Instructions for upgrading Directory Server to Release 4 are provided in Chapter 4, "Directory Server and Administration Server".
  3. Web Container Software.  Instructions for upgrading Web Server or Application Server are provided in Upgrading Web Server from Java ES Release 2 and Upgrading Application Server from Java ES Release 2, respectively.
  4. Access Manager (Access Manager SDK).  Instructions for upgrading Access Manager to Release 4 are provided in Upgrading Access Manager from Java ES Release 2.
  5. Directory Preparation Tool.  Directory Preparation Tool rarely resides on the same computer as Delegated Administrator, however, instructions for upgrading Directory Preparation Tool and running it against Directory Server are provided in Upgrading Directory Preparation Tool from Java ES Release 2.

Release 2 Delegated Administrator Upgrade

The procedure for upgrading Delegated Administrator from Release 2 to Release 4 depends on the web container in which you are deploying Delegated Administrator software.

Upgrading Release 2 Delegated Administrator: Web Server Web Container

To upgrade Release 2 Delegated Administrator to Release 4, when deploying into a Web Server web container that has been upgraded to Release 4, follow the instructions in Upgrading Release 3 Delegated Administrator (Solaris) or Upgrading Release 3 Delegated Administrator (Linux), except substitute Release 2 wherever Release 3 is referenced.

Upgrading Release 2 Delegated Administrator: Application Server Web Container

To upgrade Release 2 Delegated Administrator to Release 4, when deploying into a Application Server web container that has been upgraded to Release 4, you first follow the instructions in Upgrading Release 3 Delegated Administrator (Solaris) or Upgrading Release 3 Delegated Administrator (Linux), except substitute Release 2 wherever Release 3 is referenced.

The Release 2 Application Server instance in which Delegated Administrator was originally deployed (instanceName), when upgraded to Release 4, was migrated under a node agent created by the upgrade process.

Upgrade of Delegated Administrator in this situation requires you need to change Step 6 Reconfigure Delegated Administrator. (Solaris) or (more...) (Linux) as follows:



Previous      Contents      Index      Next     

Part No: 819-2331-13.   Copyright 2006 Sun Microsystems, Inc. All rights reserved.