test

Oracle Waveset 8.1.1 Upgrade

Upgrade the Waveset Product

You can use either of the following methods to upgrade the Waveset product:

Both methods produce the same results.

Note –

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

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

When upgrading the Waveset product, be aware of the following:

ProcedureTo Use the Waveset Installer

Use the Waveset installation and upgrade program to upgrade your Development environment.

  1. 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.

  2. On the Welcome screen, click Next.

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

  4. On the Select Installation Directory screen, select the directory where the earlier Waveset 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.

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

  6. Remove all of the compiled Waveset 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 Waveset installation and upgrade program.

Note –

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

Refer to the appropriate chapter in Part II, Installing Waveset, in Oracle Waveset InstallationPart II, Installing Waveset, in Sun Identity Manager 9.0 Installation for application server-specific instructions.

ProcedureTo Perform a Manual Upgrade on a Windows Platform

Perform the following steps to upgrade Waveset manually on a supported Windows platform:

  1. Stop the application server and Gateway.

  2. Update the Waveset database.

  3. Enter the following commands to set your environment:


    set ISPATH=Path-to-install-software 
set WSHOME=Path-to-Waveset-Installation  OR Staging-Directory set TEMP=Path-to-Temporary-Directory
    Note –

    If you have a space in the path to the Waveset installation directory, you must specify the WSHOME environment variable without double quotes ("), as shown in the following example.

    Do not use trailing slashes (\) when specifying the path even if the path contains no spaces.


    set WSHOME=c:\Program Files\Apache Group\Tomcat 6.0\idm

    or 


    set WSHOME=c:\Progra~1\Apache~1\Tomcat~1\idm

    The following path will not work:


    set WSHOME="c:\Program Files\Apache Group\Tomcat 6.0\idm"

  4. Run the 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

  5. Install the software.


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

  6. Run the post-process. 


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

    • 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.

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

  8. Remove the Waveset files from the application server work directory.

ProcedureTo Perform a Manual Upgrade on a UNIX Platform

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

  1. Stop the application server and Gateway.

  2. Update the Waveset database.

  3. Set your environment. 


    export ISPATH=Path-to-Install-Software export WSHOME=Path-to-Waveset-Installation-or-Staging Directory 
export TEMP=Path-to-Temporary-Directory

  4. Run the 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

  5. Install the software.


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

  6. Run the post-process. 


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

    • 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.

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

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

  9. Remove the Waveset 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.