Installation and Update Notes

This section provides information related to installing or updating, and the information is organized as follows:

A schema change occurs with most major Identity Manager releases. You must update your schema before upgrading to a new Identity Manager version. To upgrade to Identity Manager 7.1, run one of following schema upgrade scripts, depending on the version from which you are upgrading: (ID-15392 and ID-15722)

From Identity Manager 6.0, run the appropriate upgradeto71from60 script.

From Identity Manager 7.0, run the appropriate upgradeto71from70 script.



NoteS	When upgrading Identity Manager, be sure to review the installation section for your application server in Sun Java™ System Identity Manager Installation for application server-specific instructions. For more detailed information and instructions about upgrading, see Sun Java™ System Identity Manager Upgrade. If your current Identity Manager installation has a large amount of custom work, you should contact Sun Professional Services to assist in planning and executing your upgrade.

Installation Notes

The following information relates to the product installation process:

You must manually install Identity Manager on HP-UX.

The Identity Manager installation utility can now install or update to any installation directory name. You must create this directory prior to starting the installation process, or select to create the directory from the setup panel.

Running the Sun Identity Manager Gateway on a Windows NT system requires the Microsoft Active Directory Client extension. The DSClient can be found at the following location:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q288358



Note	Refer to the Sun Java™ System Identity Manager Installation publication for detailed product installation instructions.

On Unix/Linux, there are two additional installation requirements (ID-8403):

For 5.0 - 5.0 SP1:

/var/tmp must exist

/var/tmp must be writable by the user that executed the install

For 5.0 SP2 and later:

/var/opt/sun/install must exist

/var/opt/sun/install must be writable by the user that executed the install

Upgrade Notes

This section summarizes the tasks you must perform to upgrade Identity Manager from version 6.0 or version 7.0 to version 7.1. (See Identity Manager Upgrade Paths for information about which versions can be upgraded to Identity Manager 7.1.)

The information in this section is organized as follows:

Upgrade Issues

Using the Identity Manager Upgrade Program

Upgrading Manually

Upgrade Issues

After upgrading, the changedFileList and notRestoredFileLists will contain the following files. These files should not display, and no action is required. (ID 9228)

bin/winnt/nspr4.dll

bin/winnt/jdic.dll

bin/winnt/MozEmbed.exe

bin/winnt/IeEmbed.exe

bin/winnt/AceApi.dll

bin/winnt/DominoAPIWrapper.dll

bin/winnt/DotNetWrapper.dll

bin/winnt/gateway.exe

bin/winnt/lhpwic.dll

bin/winnt/msems.inf

bin/winnt/pwicsvc.exe

bin/winnt/remedy.dll

bin/solaris/libjdic.so

bin/solaris/mozembed-solaris-gtk2

bin/linux/librfccm.so

bin/linux/libsapjcorfc.so

bin/linux/libjdic.so

bin/linux/mozembed-linux-gtk2

If you are upgrading from a 6.x installation to version 7.0 or 7.1, and you want to start using the new Identity Manager end-user pages, you must manually change the system configuration ui.web.user.showMenu to true for the horizontal navigation bar to display. (ID-14901)

Also, if you want the new end user dashboard to display on the end-user home page, you must manually change the end user form mapping for Form Type 'endUserMenu'. Go to Configure -> Form and Process Mapping -> for Form Type 'endUserMenu' change the Form Name Mapped To to be 'End User Dashboard'.

You should also update the mapping for Form Type 'endUserWorkItemListExt'. Change the Form Name Mapped To to be 'End User Approvals List'.

If you are upgrading from 6.0 or 7.0 to version 7.1, and using LocalFiles, you must export all of your data before upgrading and then re-import the data after doing a clean installation of 7.1. (ID-15366)

When you are upgrading to Identity Manager 7.1 from a previous release, the WEB-INF/speConfiguration.xml file is not removed during the upgrade process. This file, however, is no longer used by the Service Provider feature and can safely be removed. Similarly, the spe.enableServer property might still appear in the Waveset.properties file. This property is also no longer used in the Identity Manager 7.0 or 7.1 releases. (ID-15765)

Using the Identity Manager Upgrade Program

This section describes the steps for upgrading Identity Manager using the Identity Manager installation and upgrade program.



NoteS	A schema change occurs with most major Identity Manager releases. You must update your schema before upgrading to a new Identity Manager version. To upgrade to Identity Manager 7.1, run one of following schema upgrade scripts, depending on the version from which you are upgrading: (ID-15722) From Identity Manager 6.0, run the appropriate upgradeto71from60 script. From Identity Manager 7.0, run the appropriate upgradeto71from70 script. For more information, see the Sun Java™ System Identity Manager Upgrade. In some environments, including on HP-UX, you may be required or prefer to follow the alternate, manual update procedures. If so, skip to Upgrading Manually. For UNIX environments, make sure that an install directory exists in one of the following locations, and that you can write to it: For Linux/HP-UX: /var/opt/sun/install For Solaris: /var/sadm/install During update, you will need to know the location where your application server is installed. Any previously installed hotfixes will be archived to the following directory: $WSHOME/patches/HotfixName Commands shown in the following steps are specific to a Windows installation and Tomcat application server. The commands you use may differ depending on your specific environment.

To upgrade Identity Manager:

Shut down the application server.

If you are upgrading to Identity Manager 6.0 or Identity Manager 7.0, you must upgrade the repository database schema, as follows:

Identity Manager 6.0 introduces a schema change that provides new tables for tasks, groups, orgs, and the syslog table. You must create these new table structures and move your existing data.

Identity Manager 6.0 stores user objects in two tables. You can use the sample scripts provided in the db_scripts directory to make schema changes. Refer to the db_scripts/upgradeto2005Q4M3.DatabaseName script to upgrade your repository tables.



Note	Before updating your repository schema, make a full backup of your repository tables. The upgrade of MySQL databases is highly involved. Refer to db_scripts/upgradeto2005Q4M3.mysql for more information.

Identity Manager 7.0 introduces new tables for user entitlements.
You must create these new table structures and move your existing data. You can use the sample scripts provided in the db_scripts directory to make schema changes.



Note	Before updating the repository schema, make a full backup of your Repository tables. Refer to the db_scripts/upgrade7.0.DBMSName script for more information.

If you are running Sun Identity Manager Gateway on the Identity Manager server, use the following command to stop the Gateway service:

net stop “Sun Identity Manager Gateway”

Use either of the following methods to start the installer:

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

The installer displays the Welcome panel.

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

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.



Note	If no display is present, the installer defaults to the nodisplay option. The installer will 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 panel, click Next.

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

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

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

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.

If you are running Gateway on a remote system, upgrade it by using the following steps.

Stop the Gateway service by running the command:

gateway -k

If using Windows 2000 or later, exit all instances of the Services MMC plug-in.

Use the following command to remove the Gateway service:

gateway -r

Back up and delete the existing Gateway files.

Extract the new Gateway files.

If you are installing the newly upgraded Gateway on a system that is not the Identity Manager server, then copy the gateway.zip file from the Identity Manager Installation CD.

Unpack the gateway.zip file into the directory where Gateway was installed.

Run the following command to install the Gateway service:

gateway -i

Run the following command to start the Gateway service:

gateway -s

Upgrading Manually

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



Note	Be sure 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.

On a Windows Platform

Use the following steps to upgrade Identity Manager manually on a supported Windows platform:

Stop the application server and Sun Identity Manager Gateway.

Update the Identity Manager database. (See Step 2 for detailed instructions.)

Enter the following commands to set your environment:

set ISPATH=Path to install software
set WSHOME=Path to Identity Manager Installation OR Staging Directory
set TEMP=Path to Temporary Directory

Run pre-process:

mkdir %TEMP%
cd /d %TEMP%
jar -xvf %ISPATH%\IDM.WAR \
WEB-INF\lib\idm.jar WEB-INF\lib\idmcommon.jar
set TMPLIBPTH=%TEMP%\WEB-INF\lib
set CLASSPATH=%TMPLIBPTH%\idm.jar;\
%TMPLIBPTH%\idmcommon.jar;
java -classpath %CLASSPATH% -Dwaveset.home=%WSHOME% \
com.waveset.install.UpgradePreProcess

Install software:

cd %WSHOME%
jar -xvf %ISPATH%\IDM.WAR

Run post-process:

java -classpath %CLASSPATH% -Dwaveset.home=%WSHOME%
com.waveset.install.UpgradePostProcess



Note	The installer supports upgrading installations that have renamed, deleted, or disabled the default Configurator account. The installer prompts you for user name and password to import the update.xml during the upgrade post process. If the user or password is entered incorrectly, you will be prompted (up to three times) to enter the correct 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.

If the upgrade process did not do so already, move any hotfix class files from the WEB-INF\classes directory to the $WSHOME\patches\HotfixName directory.

Start the application server.

Upgrade and then restart Sun Identity Manager Gateway. (See Step 10 for detailed instructions.)

On a UNIX Platform

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

Stop the application server and Sun Identity Manager Gateway.

Update the Identity Manager database. (See Step 2 for instructions.)

Enter the following commands to set your environment:

export ISPATH=Path to Install Software
export WSHOME=Path to Identity Manager Installation OR Staging Directory
export TEMP=Path to Temporary Directory

Run pre-process:

mkdir $TEMP
cd $TEMP
jar -xvf $ISPATH/idm.war \
WEB-INF/lib/idm.jar WEB-INF/lib/idmcommon.jar
CLASSPATH=$TEMP/WEB-INF/lib/idm.jar:\
$TEMP/WEB-INF/lib/idmcommon.jar:
java -classpath $CLASSPATH -Dwaveset.home=$WSHOME \
com.waveset.install.UpgradePreProcess

Install software:

cd $WSHOME
jar -xvf $ISPATH/idm.war

Run post-process:

java -classpath $CLASSPATH -Dwaveset.home=$WSHOME
com.waveset.install.UpgradePostProcess



Note	The installer supports upgrading installations that have renamed, deleted, or disabled the default Configurator account. The installer prompts you for user name and password to import the update.xml during the upgrade post process. If the user or password is entered incorrectly, you will be prompted (up to three times) to enter the correct 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 then 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.

If the upgrade process did not do so already, move any hotfix class files from the WEB-INF/classes directory to the $WSHOME/patches/HotfixName directory.

Start the application server.

Upgrade and then restart Sun Identity Manager Gateway. (See Step 10 for instructions.)