Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Communications Suite 5 Upgrade Guide 

Chapter 8
Upgrading Delegated Administrator

This chapter describes how to upgrade Sun Java System Delegated Administrator to version 6.4 (Communications Suite 5). The chapter provides an overview of upgrade considerations for the different upgrade paths supported by version 6.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 version 6.4:

About Delegated Administrator

Delegated Administrator represents a minor update with respect to 2005Q4. The only new feature, along with bug fixes, is support for calendar group provisioning.

Delegated Administrator Upgrade Roadmap

Table 8-1 shows the supported Delegated Administrator upgrade paths to version 6.4. The table applies to both Solaris and Linux operating systems.

Table 8-1  Upgrade Paths to Communications Suite 5: Sun Java System Delegated Administrator 6.4 

Communications Suite Release

Delegated Administrator Version

General Approach

Re-configuration Required

2005Q4

Sun Java System Communication Services Delegated Administrator 6.3 2005Q4

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

Configuration data

2005Q1

Sun Java System Communication Services Delegated Administrator 6 2005Q1

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

Configuration data

2004Q2

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

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

Configuration data

2003Q4

User Management Utility (2003Q4)

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

Configuration data

Pre-dates Communications Suite 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 8-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

Delegated Administrator variable data

DelegatedAdminConfig-base

Silent install saveState files and so forth.

Web container access control and configuration files

Web Server 7.0 (Java Enterprise System 5)
server.policy and server.xml files in
WebServer7Config-base/https-configName/config

Web Server 6.x (Java Enterprise System 2004Q2, 2005Q1, and 2005Q4)
server.policy and server.xml files in
WebServer6-base/https-hostname/config

Application Server 8.x (Java Enterprise System 2005Q1, 2005Q4, and 5):
server.policy and domain.xml files in
AppServer8Config-base/domains/domainName/config

Application Server 7.x (Java Enterprise System 2004Q2):
server.policy and server.xml files in
AppServer7Config-base/domains/domainName/config

Configuration of Delegated Administrator web container instance

Configuration data

(2005Q1 and 2005Q4)

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

Configuration data

(6.4)**

.../commcli/WEB-INF/classes/sun/comm/cli/server/ servlet/resource.properties1

Delegated Administrator server configuration and customizations

.../da/WEB-INF/classes/com/sun/comm/da/resources/daconfig.properties1

Delegated Administrator console configuration

.../da/WEB-INF/classes/com/sun/comm/da/resources/logger.properties1

Delegated Administrator console logging

.../da/WEB-INF/classes/com/sun/comm/da/resources/Security.properties1

Delegated Administrator console security configuration

1The unspecified part of the path is the location of the corresponding web application directory of the Web Server or Application Server instance providing the web container.

**For information about how to deploy the Delegated Administrator 6.4 configuration data to the web container directories, see “Deploying a Customized Configuration File” in “Chapter 4: Customizing Delegated Administrator” in the Sun Java System Delegated Administrator 6.4 Administration Guide.

Delegated Administrator Upgrade Strategy

Your strategy for upgrading Delegated Administrator depends on the many considerations discussed in Chapter 1, "Planning for Upgrades": upgrade path, dependencies between Communications Suite components, selective upgrade versus upgrade all, multi-instance deployments, and so forth.

This section is to particularize that general discussion to Delegated Administrator by presenting issues that might influence your Delegated Administrator upgrade plan.

Compatibility Issues

Delegated Administrator 6.4 introduces no changes in public interfaces and is backwardly compatible with earlier versions.

Delegated Administrator Dependencies

Delegated Administrator dependencies on other Communications Suite 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 Communications Suite components:

Web Container Upgrade Scenarios

Delegated Administrator can be deployed in a web container provided by either Web Server or Application Server. As a result, the upgrade of Delegated Administrator to version 6.4 can be complicated by the possibility of also having upgraded to Java ES 5 the web container in which it is deployed. In this regard, there are a number of web container upgrade scenarios possible, enumerated in the following table.

Table 8-3  Web Container Upgrade Scenarios for Delegated Administrator Upgrade 

Scenario

Web Container in which Delegated Administrator is Originally Deployed

Web Container in which Delegated Administrator is Deployed After Upgrade

Applicable
Delegated Administrator
Upgrade Paths: Upgrades From

Scenario 1

Web Server 6.x

Web Server 6.x

2005Q1
2005Q4

Scenario 2

Web Server 6.x

Web Server 7.0

2004Q2
2005Q1
2005Q4

Scenario 3

Application Server 8.1

Application Server 8.1

2005Q1
2005Q4

Scenario 4

Application Server 8.1

Application Server 8.2

2005Q1
2005Q4

Scenario 5

Application Server 7x

Application Server 8.2

2004Q2

You must be careful when upgrading Delegated Administrator (for example when re-configuring or re-deploying Delegated Administrator) to provide values appropriate to the upgrade scenario that applies, especially when there is a major version upgrade of the web container.

This consideration applies particularly to Scenario 5, when you upgrade Application Server 7.x to Application Server 8.2, and you upgrade Delegated Administrator from 2004Q2 to 6.4. In Scenario 5, you must supply the following values when you run the Delegated Administrator configuration program, config-commda:

Application Server target name: server1
Application Server virtual server identifier: server

For details, see Upgrading 2004Q2 Delegated Administrator: Application Server Web Container

Upgrading Delegated Administrator from Communications Services 2005Q4

This section includes information about upgrading Delegated Administrator from Communications Services 2005Q4 to version 6.4. The section covers the following topics:

Introduction

When upgrading Communications Services 2005Q4 Delegated Administrator to version 6.4, consider the following aspects of the upgrade process:

2005Q4 Delegated Administrator Upgrade

This section describes how to perform an upgrade of Delegated Administrator from 2005Q4 to version 6.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.

Back Up Delegated Administrator Data

The Delegated Administrator upgrade from 2005Q4 to version 6.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 2005Q4 graphical user interface customizations.

For information about preserving customized data from a previous version, see “If You Are Upgrading From a Previous Release of Delegated Administrator” in “Chapter 3: Configuring Delegated Administrator” in the Sun Java System Delegated Administrator 6.4 Administration Guide.

Verify Current Version Information

You can verify the current version of Delegated Administrator in the console:

  1. Log in to the Delegated Administrator console using the top-level administrator user ID and password specified for the previous version of Delegated Administrator.

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

    where hostName:port are values provided for the previous version of Delegated Administrator.

  2. Click Version in the upper-left area of the Log-in page.

You can also verify the current version of the client component of Delegated Administrator (the Delegated Administrator command-line utility) by entering the following command:

DelegatedAdmin-base/bin/commadmin -V

Table 8-4  Delegated Administrator Version Verification Outputs 

Release

Delegated Administrator Version Number

2004Q2

User Management Utility 1.1

2005Q1

User Management Utility 6 2005Q1

2005Q4

Delegated Administrator 6.3-0.09

Communications Suite 5

Delegated Administrator 6.4-0.x

Upgrade Delegated Administrator Dependencies

It is generally recommended that all Communications Suite components on a computer system (and in a computing environment) be upgraded to Communications Suite 5. However, Delegated Administrator has a hard upgrade dependency only on Directory Preparation Tool. Upgrading of other 2005Q4 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 synchronizing Communications Suite shared components to Communications Suite 5 are provided in Upgrading Communications Suite Shared Components.
  2. Directory Server.  Instructions for upgrading Directory Server are provided in the Java Enterprise System Upgrade Guide.
  3. Web Container Software.  Instructions for upgrading Web Server or Application Server are provided in the Java Enterprise System Upgrade Guide. When you’re upgrading from Web Server 6.x and 7.x, be sure to change the FQDN (Fully Qualified Domain Name) host name to https-FQDNhostname to comply with Web Server 7.x.
  4. Access Manager (Access Manager SDK).  Instructions for upgrading Access Manager are provided in the Java Enterprise System Upgrade Guide.
  5. Directory Preparation Tool.  Directory Preparation Tool needs to have been run against Directory Server before using Delegated Administrator 6.4. If Directory Preparation Tool has not already been run against Directory Server, upgrade Directory Preparation Tool to Communications Suite 5 and use it to modify and extend the schema of Directory Server (see Chapter 3, "Directory Preparation Tool.").
Obtain Required Configuration Information and Passwords

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

For a complete list of the information you should know, see “Gather Your Delegated Administrator Configuration Information” in “Chapter 2: Planning for Installation and Configuration” in the Sun Java System Delegated Administrator 6.4 Administration Guide.

Upgrading 2005Q4 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 version 6.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 8-5.

    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, synchronize all shared components to Communications Suite 5.

    4. See Upgrade Delegated Administrator Dependencies.

  4. Apply the appropriate Delegated Administrator patches in Table 8-5.

    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. In the case of the following dependency upgrade scenario:
    • 2005Q1 or 2005Q4 Web Server has been upgraded to Java Enterprise System 5 Web Server (web container upgrade Scenario 2 in Table 8-3)
    • 2005Q1 or 2005Q4 Access Manager has not been upgraded to Java Enterprise System 5 Access Manager.

      • You must modify the AccessManagerConfig-base/config/AMConfig.properties file by replacing the following line:

      com.sun.identity.webcontainer=WEB_SERVER

      with:

      com.sun.identity.webcontainer=WS7

  7. Re-configure Delegated Administrator.

    8. Caution

    Once you run the config-commda configuration script, you cannot roll back an upgrade from 2005Q4 to version 6.4 on Solaris.

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

      3. Web Server 6.x:
      WebServer6-base      /https-instanceName/start

      Web Server 7.0:
      Admin Server--
      WebServer7Config-base/admin-server/bin/startserv
      Instance Server--
      WebServer7Config-base/https-configName/bin/startserv

      Application Server 8.x:
      To start the Application Server instance, you start the Domain Administration Server (DAS), then the node agent under which the instance was migrated, and finally the instance itself using the following commands:

      AppServer8-base/sbin/asadmin start-domain --user admin_ID
           --password password  domainName

      AppServer8-base/sbin/asadmin start-node-agent
           --startinstances=false --user       admin_ID --password password
           nodeagentName

      AppServer8-base/sbin/asadmin start-instance --user admin_ID
           --password password  instanceName

      In the above commands, the following conventions are used:

      • nodeAgentName has the form hostName
      • The default domainName is domain1
      • The default instanceName is server1

        • 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 script.

      4. DelegatedAdmin-base/sbin/config-commda

      1. Provide the location of the existing configuration data directory.

        2. This is the value of the DelegatedAdminConfig-base path.

      2. When prompted, choose option #2: Upgrade.
      3. Provide the current configuration values.

        4. The values provided in previous runs of the config-commda script can be found in the saveState file in the following location:

        DelegatedAdminConfig-base/setup/config-commda_YYYYMMDDHHMMSS

      4. Enter values for the additional parameters in the following table:

        5. In the case where Web Server has been upgraded to Java Enterprise System 5 (Scenario 2 in Table 8-3), the default virtual server name value must be replaced by the actual virtual server name, which is the virtual server name migrated from 2005Q4. See the Java Enterprise System Upgrade Guide for more information.

        Table 8-6  Information Requested by config-commda Script for Delegated Administrator Upgrade 

        Web Container

        Parameter

        Default Value

        Web Server:
        Scenarios 1 & 2
        in Table 8-3

        Virtual Server Identifier

        Web Server 6.x
        https-hostName.domainName

        Web Server 7
        hostName.domainName

        Web server instance name

        Web Server 6.x
        https-hostName.domainName

        Web Server 7
        hostName.domainName

        Application Server:
        Scenarios 3 & 4 in Table 8-3

        Virtual Server Identifier

        server

        App Server Target Name (This is the App Server instance name where you want Delegated Administrator to be deployed.)

        server

        For additional details of how to use the config-commda script, see Chapter 3, “Configuring Delegated Administrator,” in the Sun Java System Delegated Administrator 6.4 Administration Guide, http://docs.sun.com/doc/819-4438.

  8. In the case in which 2005Q1 or 2005Q4 Web Server has been upgraded to Java Enterprise System 5 Web Server (Scenario 2 in Table 8-3), remove obsolete Web Server 6.x classpath entries.
    1. Locate the <server-class-path> element in the server.xml file migrated to the deployed instance of Web Server 7.0.

      2. The server.xml file is in the following directory:

      WebServer7 Config-base/http-hostname/config/

    2. Remove the following classpath entries:

      3. /opt/SUNWcomm/data/WEB-INF/classes;
      /opt/SUNWcomm/lib/jars/commcli-client.jar;
      /opt/SUNWcomm/lib/jars/jdapi.jar;

      (The required Delegated Administrator classpath is now appended to the JVM class-path-suffix.)

    3. Use the Web Server 7.0 command-line utility, wadm, to bring the modified configuration in the Web Server 7.0 instance back into the Web Server 7.0 configuration store, so that the deployed instance and central configuration store remain in sync.

      4. For example, type the following command:

      WebServer7-base/bin/wadm pull-config --config=configName nodehost

      where configName is the name of the Web Server 7.0 instance (typically, the host name where the Web Server 7.0 instance is running)

      and nodeHost is the name of the host where the Web Server 7.0 central configuration has been deployed.

  9. Stop and restart the Delegated Administrator web container.

    10. Web Server 6.x:
    WebServer6-base    /https-instanceName/stop
    WebServer6-base/https-instanceName/start

    Web Server 7.0:
    WebServer7Config-base    /https-configName/bin/stopserv
    WebServer7Config-base/https-configName/bin/startserv

    Application Server 8.x:
    AppServer8-base    /bin/asadmin stop-domain --user admin_ID
         --password password domainName

    To start the Application Server instance, you start the Domain Administration Server (DAS), then the node agent under which the instance was migrated, and finally the instance itself using the following commands:

    AppServer8-base/sbin/asadmin start-domain --user admin_ID
         --password password  domainName

    AppServer8-base/sbin/asadmin start-node-agent
         --startinstances=false --user     admin_ID --password password
         nodeagentName

    AppServer8-base/sbin/asadmin start-instance --user admin_ID
         --password password  instanceName

    In the above commands, the following conventions are used:

    • nodeAgentName has the form hostName
    • The default domainName is domain1
    • The default instanceName is server1

Upgrading 2005Q4 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 version 6.4 on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux 6.4 upgrade patches differ from the Solaris patches.

The Delegated Administrator 6.4 upgrade patch for Linux OS is shown in the following table. Patch revision numbers are the minimum required for upgrade to 6.4. If newer revisions become available, use the newer ones instead of those shown in the table.

Table 8-7  Patches to Upgrade Delegated Administrator on Linux 

Description

Patch ID and RPM names

Delegated Administrator

121583-12

  • sun-commcli-client-1.1-12.xx.i386.rpm
  • sun-commcli-server-1.1-12.xx.i386.rpm

Upgrade Procedure (Linux)

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

Caution

An upgrade from 2005Q4 to version 6.4 on Linux cannot be rolled back.

  1. Obtain the required patches using the patch numbers and RPM names from Table 8-7. 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 8-7.

    5. rpm -Fvh sun-commcli-client-1.1-12.xx.i386.rpm
    rpm -Fvh sun-commcli-server-1.1-12.xx.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. Proceed, beginning with Step 6 through Step 9 in the procedure for Upgrading 2005Q4 Delegated Administrator (Solaris). Use these same steps to upgrade on Linux.

Verifying the Upgrade

You can verify successful upgrade of Delegated Administrator as follows:

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

    2. http://hostName:port/da

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

  2. Check the version number by clicking Version in the upper-left area of the Log-in page.

    3. See Table 8-4 for output values.

  3. To verify the current version of the client component of Delegated Administrator (the Delegated Administrator command-line utility), enter the following command:

    4. DelegatedAdmin-base/bin/commadmin -V

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

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 2005Q1

The procedure for upgrading 2005Q1 Delegated Administrator to verison 6.4 is the same as that for upgrading 2005Q4 Delegated Administrator to 6.4.

To upgrade 2005Q1 Delegated Administrator to version 6.4, use the instructions in Upgrading Delegated Administrator from Communications Services 2005Q4, except substitute 2005Q1 wherever 2005Q4 is referenced.

Upgrading Delegated Administrator from 2004Q2

The procedure for upgrading 2004Q2 Delegated Administrator to version 6.4 is the same as that for upgrading 2005Q4 Delegated Administrator to 6.4, with a couple of exceptions, noted below.

Upgrade Delegated Administrator Dependencies

The pre-upgrade tasks for upgrading 2004Q2 Delegated Administrator to version 6.4 are similar to those for upgrading 2005Q4 Delegated Administrator to 6.4, with the exception that the upgrade of Delegated Administrator dependencies should include the synchronizing of all shared components to Communications Suite 5 (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 synchronizing Communications Suite shared components to Communications Suite 5 are provided in Chapter 2, "Upgrading Communications Suite Shared Components".
  2. Directory Server.  Instructions for upgrading Directory Server are provided in the Java Enterprise System Upgrade Guide.
  3. Web Container Software.  Instructions for upgrading Web Server or Application Server are provided in the Java Enterprise System Upgrade Guide.
  4. Access Manager (Access Manager SDK).  Instructions for upgrading Access Manager are provided in the Java Enterprise System Upgrade Guide.
  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 Chapter 3, "Directory Preparation Tool."

2004Q2 Delegated Administrator Upgrade

The procedure for upgrading Delegated Administrator from 2004Q2 to version 6.4 depends on the web container in which you are deploying Delegated Administrator software.

Upgrading 2004Q2 Delegated Administrator: Web Server Web Container

To upgrade 2004Q2 Delegated Administrator to version 6.4, when deploying into a Web Server web container that has been upgraded to 5, follow the instructions in Upgrading 2005Q4 Delegated Administrator (Solaris) or Upgrading 2005Q4 Delegated Administrator (Linux), except substitute 2004Q2 wherever 2005Q4 is referenced.

Upgrading 2004Q2 Delegated Administrator: Application Server Web Container

To upgrade 2004Q2 Delegated Administrator to version 6.4, when deploying into an Application Server web container that has been upgraded to 5, you first follow the instructions in Upgrading 2005Q4 Delegated Administrator (Solaris) or Upgrading 2005Q4 Delegated Administrator (Linux), except substitute 2004Q2 wherever 2005Q4 is referenced.

The 2004Q2 Application Server instance in which Delegated Administrator was originally deployed, when upgraded to 5, was migrated under a node agent created by the upgrade process.

Upgrade of Delegated Administrator in this situation requires you to change Step 7 as follows:



Previous      Contents      Index      Next     

Part No: 819-7561-10.   Copyright 2007 Sun Microsystems, Inc. All rights reserved.