Instant Messaging Upgrade

Skip to end of metadata
Go to start of metadata

Upgrading to Oracle Communications Instant Messaging Server
Version 9

This information describes how to upgrade to Oracle Communications Instant Messaging Server 9, from previous versions of Instant Messaging starting with Instant Messaging 7.3

You can upgrade to the Oracle Communications Instant Messaging Server only by using the Communication Suite installer.


Upgrading Instant Messaging Servers

The process for upgrading the Instant Messaging server and multiplexor is the same and should only take a few minutes. The upgrade procedure automatically copies the pre-upgrade release product configuration and other data to the post-upgrade version. If Instant Messaging is configured to provide email notifications, Calendar alerts, or Access Manager policy features such as authenticating or single-sign on, the configuration data of these features are migrated to the post-upgrade version.

When you upgrade to Instant Messaging 9, the iim.conf file is automatically upgraded to the iim.conf.xml file. You no longer edit this file directly. Instead, you use the imconfutil to make changes. For more information, see XML Configuration.
The new configuration system has backward compatibility. If support for any key is not available with imconfutil, or if a parameter is not found in iim.conf.xml, it uses the old iim.conf as a fallback. If you want to upgrade from releases prior to Instant Messaging 9, you must copy im.conf-pre9 to iim.conf for the fallback to work.
Due to bug 15964936, upgrading to Instant Messaging Server 9 Patch 1 on Oracle Enterprise Linux fails because of an incorrect ksh path in the preupgrade and postupgrade scripts. The upgrade uses /usr/bin/ksh whereas the default ksh location is /bin/ksh. As a workaround, create a symbolic link before you run the upgrade. For example:

To upgrade the Instant Messaging version, perform the following steps on an existing installation of Instant Messaging:

  1. Stop the Instant Messaging server.
  2. Use the Communications Suite installer to upgrade Instant Messaging.

    For more information, see commpkg upgrade Usage.

  3. Select the Instant Messaging 9 component from the Product Selection list.
  4. Respond to the Communications Suite installer prompts to upgrade.
  5. Restart the Instant Messaging server.
  6. (Optional) If you have deployed any Web applications, redeploy them.

    where app-name can be im, httpbind, imps, or all.
    This step completes the upgrade process and redeploys the specified component(s).

  7. If you had previously configured your deployment to use Service Management Facility (SMF), run the following command to enable SMF, as the upgrade does not preserve SMF status.
  8. When upgrading to Instant Messaging 9 Patch 1, the following applies if you are using any of these items and continue to use the old configuration file:
    • Components: Calendar Agent, HTTPBind, and so on
    • S2S Federation
    • Server Pool
    • Server health monitoring using Watchdog

      If you use any of these items, and if you continue to use the old configuration file, then you must set the iim_server.useport parameter to true by using the imconfutil command. For example:

Rolling Back to the Legacy Instant Messaging Version

If the upgrade fails or if you need to go back to the previously working version of Instant Messaging, you can roll back the upgrade process.

To roll back the upgrade process, perform the following steps:

  1. Stop all services.
  2. Remove the Instant Messaging 9 packages by using the pkgrm command.
  3. Install the old version of Instant Messaging, for example, version 7.2 ,7.3, or 8.3, by using the Communications Suite installer for that version.
    When you upgrade the server, all previous configuration data is overwritten. The old configuration files are backed up in the config directory with the string -pre 9 suffixed to the filename. For example, the old iim.conf file is backed up as iim.conf-pre9. This file can be used to roll back to the previous working version in case of a upgrade failure.
  4. Rename the old configuration files with their correct names.
    That is, rename iim.conf-pre9 to iim.conf.
  5. Restart the services.
redeploy redeploy Delete
upgrading upgrading Delete
instantmessaging instantmessaging Delete
guide guide Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.

The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.