In some environments you might prefer using the manual upgrade
procedure. For example:

If you want to fully automate the upgrade as part of a repeatable
upgrade procedure

If you have restricted access to your Production environment
or cannot start the console

Upgrading the Identity Manager product might modify objects in the Identity Manager repository
and in some file system artifacts such as .jsp files, Identity Manager product
JARs, and third-party JARs.

When upgrading the Identity Manager product,
be aware of the following:

If you copy files from the installation media to your own
location, you must put the idm.war and install.class files
in the same directory.

Use only one Identity Manager server to import update.xml, and have only one Identity Manager server running during the upgrade.

If you start
any other Identity Manager servers during the upgrade, you must stop and restart
those servers before making them available.

If your application server is installed on a machine running
a UNIX® system, change directories
to the $WSHOME/bin directory and run the following command
to allow the scripts in this directory to be executed:

chmod -R +x *

For UNIX environments, be sure that you have an install directory
in one of the following locations and that you can write to that directory:

For Linux/HP-UX

/var/opt/sun/install

For SolarisTM

/var/sadm/install

Previously installed hotfixes are archived in the $WSHOME/patches/HotfixName directory.

The upgrade program has three steps: the upgrade pre-process
step, the upgrade step, and the upgrade post-process step. The upgrade post-process
step runs in a separate Java virtual machine and the default heap size for
this step is 1024 MB. If you experience out-of-memory exceptions during an
upgrade, set this value higher. To specify a custom value, set the JAVA_OPTS environment variable using the form —Xmx<heap size> where heap size is a value, such as 2048m.
An example is -Xmx2048m.

To Use the Identity Manager Installer

Use the Identity Manager installation and upgrade program to upgrade
your Development environment.

Use one of the following methods to start the installer:

To use the GUI installer, run install.bat (for
Windows) or install (for UNIX).

The installer
displays the Welcome screen.

To activate the installer in nodisplay mode,
change to the directory where the software is located, and type:

install -nodisplay

The installer displays the Welcome text, and then presents a list of
questions to gather installation information in the same order as the GUI
installer.

If no display is present, the installer defaults to the nodisplay option.

The installer does not install an older version of the software over
a newer version. In this situation, an error message displays and the installer
exits.

On the Welcome screen, click Next.

On the Install or Upgrade? screen, select Upgrade and click Next.

On the Select Installation Directory screen, select the directory
where the earlier Identity Manager version is located and click Next.

The installer displays progress bars for the pre-upgrade and post-upgrade
processes and then proceeds to Installation Summary screen.

For detailed information about the installation, click Details,
view the log file, and click Close to exit the installer.

Remove all of the compiled Identity Manager files from the work
directory of the application server.

Upgrading Manually

In some environments, you might want to perform the upgrade steps manually
instead of using the Identity Manager installation and upgrade program.

Make sure that you set the JAVA_HOME environment
variable.

Make sure that the bin directory in the JAVA_HOME directory is in your path.

Any previously installed hotfixes will be archived to the $WSHOME/patches/HotfixName directory.

Note –

The instructions in this section are based on installing Identity Manager on
a Tomcat application server. Depending on your application server, you might
have to use slightly different commands.

The upgrade post-process step runs in a separate Java virtual
machine. The default heap size for this step is 1024 MB. If you experience
out-of-memory exceptions during this step, set the maximum heap size value
higher. To specify a custom value, set the JAVA_OPTS environment
variable using the form —Xmx<heap
size> where heap size is a value, such as 2048m.
An example is -Xmx2048m.

The installer supports upgrading installations that have renamed,
deleted, or disabled the default Configurator account.

The installer
prompts you for the user name and password to import the update.xml during
the upgrade post process. If the user name or password is typed incorrectly,
you will be prompted (up to three times) to enter the correct name or password.
The error will be displayed in the text box behind it.

For manual installation, you must provide the -U username -P password flags
to pass the credentials to the UpgradePostProcess procedure.

If you installed into a staging directory, create a .war file
for deployment to your application server.

Remove the Identity Manager files from the application server work
directory.

To Perform a Manual Upgrade on a UNIX Platform

Perform the following steps to upgrade Identity Manager manually on a
supported UNIX platform:

The upgrade post-process step runs in a separate Java virtual
machine. The default heap size for this step is 1024 MB. If you experience
out-of-memory exceptions during this step, set the maximum heap size value
higher. To specify a custom value, set the JAVA_OPTS environment
variable using the form —Xmx<heap
size> where heap size is a value, such as 2048m.
An example is -Xmx2048m.

The installer supports upgrading installations that have renamed,
deleted, or disabled the default Configurator account.

The installer
prompts you for the user name and password to import the update.xml during
the upgrade post process. If the user or password is typed incorrectly, you
will be prompted (up to three times) to enter the correct name or password.
The error will be displayed in the text box behind it.

For manual installation, you must provide the -U username -P password flags
to pass the credentials to the UpgradePostProcess procedure.

Change directory to $WSHOME/bin/solaris or $WSHOME/bin/linux, and set permissions on the files in the directory
so that they are executable.

If you installed into a staging directory, create a .war file
for deployment to your application server.

Remove the Identity Manager files from the application server work
directory.

Troubleshooting Upgrade

If you encounter problems during the upgrade, check the upgrade log
files located in the $WSHOME/patches/logs directory. The file names for the logs are based on a time
stamp and the stage of the upgrade.