2 Upgrading an Existing 11g Release 1 or 7.x Zip Distribution Installation

This chapter provides instructions for upgrading an existing 11g Release 1 or 7.x installation that was initially installed using a zip distribution. The following topics are included in this chapter:

Before You Begin Upgrading
Upgrading the Administration (DSCC) Host
Upgrading the Directory Server and Directory Proxy Server Hosts

For information about what happens during upgrading, and about the various upgrade and migration options, see Chapter 1, "Determing Whether to Upgrade or Migrate an Existing Installation."

2.1 Before You Begin Upgrading

Be sure you have resolved all issues listed in Section 1.3, "Completing Pre-Upgrade and Pre-Migration Tasks."
Although you will run commands named prepare-patch and complete-patch in the following procedures, you are actually upgrading (and not "patching") the software.
Upgrading must be performed by the user account that owns the Directory Server Enterprise Edition installation.
Identify the server that hosts Directory Service Control Center. Always upgrade the Administration (DSCC) host before upgrading any Directory Server host or the Directory Proxy Server host.
Upgrading requires two major procedures:
1. Upgrading the Administration (DSCC) Host
2. Upgrading the Directory Server and Directory Proxy Server Hosts

2.2 Upgrading the Administration (DSCC) Host

Before you can manage the Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) instances using Directory Service Contol Center (DSCC), you must first complete some preparation steps, and then redeploy the Directory DSCC WAR file. After the DSCC WAR file is redeployed, then you can start using Directory Service Control Center 11g Release 1 (11.1.1.7.0) to access existing version 6x, 7.0, and 11g Release 1 (11.1.1.5.0 or 11.1.1.3.0) instances.

2.2.1 Prepare to Redeploy the DSCC WAR File

Stop the Cacao module. For example:
Version 6.x Zip Distribution

# INSTALL_PATH/dsee6/cacao_2/usr/sbin/cacaoadm stop

Versions 11.1.1.3, 11.1.1.5, or 7.x Zip Distributions
```
# INSTALL_PATH/dsee7/bin/cacaoadm stop
```
# INSTALL_PATH/dsee7/bin/cacaoadm stop
For Native Package Installations

# /usr/sbin/cacaoadm stop

Run the following command:

# install-path/bin/dsccsetup prepare-patch

Install ODSEE 11g R1 (11.1.1.7.0), overwriting the existing installation.

See "Chapter 2, Installing Directory Server Enterprise Edition" in Oracle Directory Server Enterprise Edition Installation Guide.

Run the following command:

# install-path/bin/dsccsetup complete-patch

2.2.2 Redeploy the DSCC WAR File

Create the WAR file for DSCC.

# install-path/bin/dsccsetup war-file-create
Created install-path/var/dscc7.war

Make note of the WAR file location.

Deploy dscc7.war in an Application server.

For detailed instructions, see both of the following:

2.3 Upgrading the Directory Server and Directory Proxy Server Hosts

Perform this upgrade procedure on each Directory Server Enterprise Edition installation. However, identify the server that hosts Directory Service Control Center, and upgrade it first, before upgrading any other servers. See Section 2.2, "Upgrading the Administration (DSCC) Host."

Note:

Upgrading the Directory Server must be performed by the user account that owns the Directory Server Enterprise Edition installation.

Stop the Cacao module. For example:
Version 6.x Zip Distribution

# INSTALL_PATH/dsee6/cacao_2/usr/sbin/cacaoadm stop

Versions 11.1.1.3, 11.1.1.5, or 7.x Zip Distributions
```
# INSTALL_PATH/dsee7/bin/cacaoadm stop
```
# INSTALL_PATH/dsee7/bin/cacaoadm stop
For Native Package Installations

# /usr/sbin/cacaoadm stop
Run the following command.
```
# install-path/bin/dsccsetup prepare-patch
```
The dsccsetup prepare-patch command attempts to stop all running instances of Directory Server and Directory Proxy Server.
- If the following message is displayed, then skip to step 3:
```
You can now safely patch your installation.
```
- If the dsccsetup prepare-patch command does not have permission to stop a server instance, it displays a message that describes its failure, and you must manally stop the server before continuing. Go to step 2.
If the prepare-patch command did not stop the server (see Section 2.2.1, "Prepare to Redeploy the DSCC WAR File") then run one of the following commands to make sure that the server is stopped.

To stop a directory server, run this command:
```
# install-path/bin/dsadm stop instance-path
```
To stop a proxy server, run this command:
```
# install-path/bin/dpadm stop instance-path
```
Create a temporary directory TEMP_DIRECTORY, and store a copy of the installation file in it.
Type the following commands to install the Directory Server Enterprise Edition software.
```
# cd TEMP_DIRECTORY
# unzip -q ODSEE11_1_1_5_0_xxx.zip
# cd ODSEE_ZIP_Distribution
# unzip -q sun-dsee7.zip -d install-path
# cd install-path/dsee7
```
This step effectively overwrites the existing installation, so the install-path refers to the installation path used in Step 1. All existing files should be overwritten.
Run the following command:
```
# install-path/bin/dsccsetup complete-patch
```
The output of dsccsetup complete-path specifies the exact path and command you will launch in step 8. Make note of the path and command.
If you manually stopped the server in step 2 above, then the Directory Server instance was not automatically upgraded in Step 5. You must now manually upgrade the Directory Service instance by running the following command:
```
# install-path/bin/dsadm upgrade [-i] instance-path
```

Create a new DSCC agent and add the agent to the DSCC registry.

Create a DSCC agent using the exact path and command specified in step 5. For example:

# install-path/bin/dsccagent create
Enter DSCC agent password: ***
Confirm the password: ***
Agent instance install-path/var/dcc/agent has been created successfully
Run the following command to register the agent in the registry: install-path/bin/dsccreg add-agent install-path/var/dcc/agent

Register the new DSCC agent in the DSCC registry.

Use the command displayed at the completion of the previous step. For example:
```
# install-path/bin/dsccreg add-agent install-path/var/dcc/agent
```
Start the DSCC agent.
```
# install-path/bin/dsccagent start
```

Create an SNMP agent, and configure Directory Server instances to use the SNMP agent.

Create the SNMP agent.

# install-path/bin/dsccagent enable-snmp

Configure all Directory Server instances you want to manage through SNMP.

Run the following command to obtain the DS port number for an instance you want to manage through SNMP:

install-path/bin/dsconf set-plugin-prop dssnmp argument:on argument:3995 
Instance Path         :   install-dir/dsee7/var/dcc/agent
Owner                 :   root
JMX port              :   3997
SNMP port             :   3996
DS port               :   3995
State                 :   Stopped
PID                   :   -
DSCC hostname         :   host2
DSCC non-secure port  :   3998
DSCC secure port      :   3999
SNMP v3               :   Disabled
Instance version      :   A-A00

Run the following command using the DS port number obtained in the previous step to set the port number argument:

# install-patch/bin/dsconf set-plugin-prop dssnmp argument:on argument:3995

After upgrading is complete, when you start DSCC, it uses the new DSCC agent.