Sun Java Communications Suite 5 Upgrade Guide |
Chapter 8
Upgrading Delegated AdministratorThis 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 UpgradesThis 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.
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/configWeb Server 6.x (Java Enterprise System 2004Q2, 2005Q1, and 2005Q4)
server.policy and server.xml files in
WebServer6-base/https-hostname/configApplication Server 8.x (Java Enterprise System 2005Q1, 2005Q4, and 5):
server.policy and domain.xml files in
AppServer8Config-base/domains/domainName/configApplication Server 7.x (Java Enterprise System 2004Q2):
server.policy and server.xml files in
AppServer7Config-base/domains/domainName/configConfiguration 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.propertiesDelegated Administrator console configuration
DelegatedAdmin-base/data/da/WEB-INF/classes/com/
sun/comm/da/resources/logger.propertiesDelegated Administrator console logging
DelegatedAdmin-base/data/da/WEB-INF/classes/com/
sun/comm/da/resources/security.propertiesDelegated 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:
- Shared components. Delegated Administrator has dependencies on specific Communications Suite shared components (see Table 1-6).
- Web Container. Delegated Administrator depends upon web container services, which can be provided either by Sun Java System Web Server or Sun Java System 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.
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.
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: serverFor details, see Upgrading 2004Q2 Delegated Administrator: Application Server Web Container
Upgrading Delegated Administrator from Communications Services 2005Q4This 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:
- General Upgrade Approach. The upgrade is performed by applying patches to the 2005Q4 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 Communications Suite shared components (see Table 1-6), Delegated Administrator 6.4 is compatible with the 2005Q4 versions of these components. Upgrade of these shared components is therefore optional with respect to upgrade of Delegated Administrator to version 6.4.
In addition, Delegated Administrator 6.4 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 5. (However, if Access Manager is upgraded, then Delegated Administrator must be upgraded also.)
In addition, Delegated Administrator 6.4 has a hard upgrade dependency on Directory Preparation Tool; Communications Suite 5 Directory Preparation Tool is required to prepare Directory Server for user provisioning operations.
- Backward Compatibility. Delegated Administrator 6.4 is backwardly compatible with the 2005Q4 version.
- Upgrade Rollback. Rollback of the 6.4 upgrade of Delegated Administrator to 2005Q4 is not supported.
- Platform Issues. The general approach for upgrading Delegated Administrator is the same on both Solaris and Linux operating systems, however the patching technologies are different. The upgrade process therefore includes platform-specific procedures.
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:
- Log in to the Delegated Administrator console using the top-level administrator user ID and password specified for the previous version of Delegated Administrator.
http://hostName:port/da/DA/Login
where hostName:port are values provided for the previous version of Delegated Administrator.
- 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
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.
- Shared Components. Instructions for synchronizing Communications Suite shared components to Communications Suite 5 are provided in Upgrading Communications Suite Shared Components.
- Directory Server. Instructions for upgrading Directory Server are provided in the Java Enterprise System Upgrade Guide.
- 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.
- Access Manager (Access Manager SDK). Instructions for upgrading Access Manager are provided in the Java Enterprise System Upgrade Guide.
- 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:
- Access Manager administrator user ID and password
- Access Manager internal LDAP password
- Top level administrator user ID and password
- Web container administrator user ID and password, depending on your web container
- Web container host and port
- If you are using Sun Java System Web Server, you also need to know the Web Server’s administration server host and port.
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:
- 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 Delegated Administrator 6.4 upgrade patch for Solaris 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.
Upgrade Procedure (Solaris)
The procedure documented below applies to Delegated Administrator on the computer where the upgrade is taking place.
- Obtain the required patches, based on Table 8-5.
Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
- Log in as root or become superuser.
su -
- If you have not already done so, synchronize all shared components to Communications Suite 5.
See Upgrade Delegated Administrator Dependencies.
- Apply the appropriate Delegated Administrator patches in Table 8-5.
patchadd patch_ID
- Confirm that the patch upgrade was successful:
showrev -p | grep patch_ID
The output should return the versions of patch IDs applied in Step 4.
- 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
- Re-configure Delegated Administrator.
Caution
Once you run the config-commda configuration script, you cannot roll back an upgrade from 2005Q4 to version 6.4 on Solaris.
- Make sure Directory Server is running.
- Make sure the web container running Access Manager and Delegated Administrator is running.
Web Server 6.x:
WebServer6-base/https-instanceName/startWeb Server 7.0:
Admin Server--
WebServer7Config-base/admin-server/bin/startserv
Instance Server--
WebServer7Config-base/https-configName/bin/startservApplication 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 domainNameAppServer8-base/sbin/asadmin start-node-agent
--startinstances=false --user admin_ID --password password
nodeagentNameAppServer8-base/sbin/asadmin start-instance --user admin_ID
--password password instanceNameIn the above commands, the following conventions are used:
- Run the Delegated Administrator configuration script.
DelegatedAdmin-base/sbin/config-commda
- Provide the location of the existing configuration data directory.
This is the value of the DelegatedAdminConfig-base path.
- When prompted, choose option #2: Upgrade.
- Provide the current configuration values.
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
- Enter values for the additional parameters in the following table:
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-3Virtual Server Identifier
Web Server 6.x
https-hostName.domainNameWeb Server 7
hostName.domainNameWeb server instance name
Web Server 6.x
https-hostName.domainNameWeb Server 7
hostName.domainNameApplication Server:
Scenarios 3 & 4 in Table 8-3Virtual 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.
- 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.
- Locate the <server-class-path> element in the server.xml file migrated to the deployed instance of Web Server 7.0.
The server.xml file is in the following directory:
WebServer7 Config-base/http-hostname/config/
- Remove the following classpath entries:
/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.)
- 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.
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.
- Stop and restart the Delegated Administrator web container.
Web Server 6.x:
WebServer6-base/https-instanceName/stop
WebServer6-base/https-instanceName/startWeb Server 7.0:
WebServer7Config-base/https-configName/bin/stopserv
WebServer7Config-base/https-configName/bin/startservApplication Server 8.x:
AppServer8-base/bin/asadmin stop-domain --user admin_ID
--password password domainNameTo 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 domainNameAppServer8-base/sbin/asadmin start-node-agent
--startinstances=false --user admin_ID --password password
nodeagentNameAppServer8-base/sbin/asadmin start-instance --user admin_ID
--password password instanceNameIn the above commands, the following conventions are used:
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
Upgrade Procedure (Linux)
The procedure documented below applies to Delegated Administrator on the computer where the upgrade is taking place.
- 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.
Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
- Log in as root or become superuser.
su -
- If you have not already done so, upgrade all shared components, the web container, and Access Manager (or Access Manager SDK).
See Upgrade Delegated Administrator Dependencies.
- Apply the RPMs for Delegated Administrator in Table 8-7.
rpm -Fvh sun-commcli-client-1.1-12.xx.i386.rpm
rpm -Fvh sun-commcli-server-1.1-12.xx.i386.rpm- Confirm that the patch upgrade was successful:
rpm -qa | grep sun-commcli
The new version numbers of the RPMs should be returned.
- 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:
- 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
where hostName:port are values provided during re-configuration of Delegated Administrator.
- Check the version number by clicking Version in the upper-left area of the Log-in page.
See Table 8-4 for output values.
- To verify the current version of the client component of Delegated Administrator (the Delegated Administrator command-line utility), enter the following command:
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 2005Q1The 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 2004Q2The 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.
- Shared Components. Instructions for synchronizing Communications Suite shared components to Communications Suite 5 are provided in Chapter 2, "Upgrading Communications Suite Shared Components".
- Directory Server. Instructions for upgrading Directory Server are provided in the Java Enterprise System Upgrade Guide.
- Web Container Software. Instructions for upgrading Web Server or Application Server are provided in the Java Enterprise System Upgrade Guide.
- Access Manager (Access Manager SDK). Instructions for upgrading Access Manager are provided in the Java Enterprise System Upgrade Guide.
- 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:
- Re-configure Delegated Administrator.
- Modify the AccessManagerConfig-base/config/AMConfig.properties file.
Replace the following line:
com.sun.identity.webcontainer=IAS7.0
with:
com.sun.identity.webcontainer=IAS8.1
- Make sure the upgraded Application Server instance, in which Delegated Administrator is deployed, is running.
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 domainNameAppServer8-base/sbin/asadmin start-node-agent
--startinstances=false --user admin_ID --password password
nodeagentNameAppServer8-base/sbin/asadmin start-instance --user admin_ID
--password password instanceNameIn the above commands, and in subsequent steps, the following conventions are used:
- Undeploy the commcli Delegated Administrator web application from the Application Server instance.
AppServer8-base/bin/asadmin undeploy --secure=false --user admin --target instanceName commcli
If asadmin is running under SSL, set secure=true.
- 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 Administrator Guide, http://docs.sun.com/doc/819-2658.
Specify the following parameters:
- The Access Manager host and port
- When asked where to deploy the Delegated Administrator console and Delegated Administrator server, specify the instance information for the upgraded Application Server instance where Access Manager is deployed.
- When asked to supply the Application Server configuration details, you must supply the following values for the target name and virtual server identifier:
Target name: server1
Virtual server identifier: server
You must specify these values because the asupgrade utility migrates the Application Server 7 server1 instance into the Application Server 8.x server1 target running under a nodeagent. However, asupgrade changes the value of the virtual server from server1 in Application Server 7 to server in Application Server 8.x.
These parameter values will cause Delegated Administrator to be redeployed to the instance in which Access Manager is deployed.