|
| |
| Sun Java Enterprise System Upgrade Guide for Microsoft Windows | |
Chapter 17
Delegated AdministratorThis chapter describes how to upgrade Delegated Administrator from previous Java ES versions to Java ES 2005Q4 (Release 4): Sun Java System Communication Services Delegated Administrator 6 2005Q4.
The chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Java ES Release 4.
Overview of Delegated Administrator UpgradesThis 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 17-1 shows the supported Delegated Administrator upgrade paths to Java ES Release 4.
Delegated Administrator Data
The following table shows the type of data that could be impacted by an upgrade of Delegated Administrator software.
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:
- Shared components. Delegated Administrator has dependencies on specific Java ES shared components (see Table 1-6).
- Web Container. Delegated Administrator depends upon web container services, which can be provided either by Java ES Web Server or Java ES Application Server.
- Directory Server. Delegated Administrator stores application and user data in Directory Server.
- Directory Preparation Tool. Delegated Administrator uses the Directory Preparation Tool to prepare the directory to support Delegated Administrator user provisioning functions. As a result, Delegated Administrator upgrades might depend upon preparation of the directory to support new functions.
- Access Manager (Access Manager SDK). Delegated Administrator depends upon Access Manager to register services and to make entries into Directory Server.
Upgrading Delegated Administrator from Java ES Release 3This 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:
- General Upgrade Approach. The upgrade is performed by applying patches to the Release 3 version. Re-configuration of Delegated Administrator is achieved by running the config-commda configuration utility.
- Upgrade Dependencies. While Delegated Administrator has dependencies on a number of Java ES shared components (see Table 1-6), Release 4 Delegated Administrator is compatible with the Release 3 versions of these components. Upgrade of these shared components is therefore optional with respect to upgrade of Delegated Administrator to Release 4.
In addition, Release 4 Delegated Administrator is dependent upon a web container and on Access Manager, as described in Delegated Administrator Dependencies. These are soft upgrade dependencies; upgrade of these components is optional with respect to upgrade of Delegated Administrator to Release 4.
However, Release 4 Delegated Administrator has a hard upgrade dependency on Directory Preparation Tool; Release 4 Directory Preparation Tool is required to prepare Directory Server for user provisioning operations.
Delegated Administrator Upgrade
This section describes how to perform an upgrade of Delegated Administrator from Java ES Release 3 to Java ES Release 4. 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:
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.
- Shared Components. Instructions for upgrading Java ES shared components to Release 4 are provided in Chapter 2, "Upgrading Java ES Shared Components".
- Directory Server. Instructions for upgrading Directory Server to Release 4 are provided in Chapter 3, "Directory Server and Administration Server."
- Web Container Software. Instructions for upgrading Web Server or Application Server are provided in Chapter 5, "Web Server" and Chapter 8, "Application Server", respectively.
- Access Manager (Access Manager SDK). Instructions for upgrading Access Manager to Release 4 are provided in Chapter 9, Access Manager.
- 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 10, "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 Delegated Administrator
This section discusses considerations that impact the upgrade procedure for Delegated Administrator followed by a description of the procedure itself.
Upgrade Considerations
The upgrade of Delegated Administrator software to Java ES Release 4 takes into account the following considerations:
- Delegated Administrator should not be used while patches are being applied to the installed image.
- When re-configuring Delegated Administrator, it should be deployed to the same web container as Access Manager.
- The Release 4 Delegated Administrator upgrade patch is shown in Table 1-3.
Upgrade Procedure
The procedure documented below applies to Delegated Administrator on the computer where the upgrade is taking place.
- Obtain the required patches, based on Table 1-3.
Patches can be downloaded from:
- Run the prepatch.pl as follows:
perl prepatch.pl <WebServer-RootPath> <instance name>
- Apply the appropriate Delegated Administrator patches by executing the corresponding <patch-id>.exe
- Run perl postpatch.pl <WebServer-RootPath> <instance name>
- Reconfigure Delegated Administrator.
- Make sure the web container running Access Manager and Delegated Administrator is running.
To start the web container:
Web Server:
<WebServer-base>\https-instanceName\start
Application Server:
<ApplicationServer-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.
- Run the Delegated Administrator configuration utility.
<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).
- Stop and restart the Delegated Administrator web container.
Web Server:
<WebServer-base>\https-instanceName\stop
<WebServer-base>\https-instanceName\start
Application Server:
<ApplicationServer-base>\bin\asadmin stop-domain domainName
<ApplicationServer-base>\bin\sadmin start-domain domainName
--user admin_ID --password password
Verifying the Upgrade
You can verify successful upgrade of Delegated Administrator as follows:
- Check the version number.
<DelegatedAdmin-base>\bin\commadmin -V
- Log in to the Delegated Administrator console using the top level administrator user ID and password specified during re-configuration of Delegated Administrator.
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.
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.