6 Upgrading Instant Messaging Server

This chapter explains how to upgrade your existing system to the latest release of Oracle Communications Instant Messaging Server.

Note:

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

About Upgrading Instant Messaging Server

The process for upgrading the Instant Messaging server and multiplexor is the same and should take only 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 Server is configured to provide email notifications, or calendar alerts, the configuration data of these features is migrated to the post-upgrade version.

Upgrading from 9.0.1.4 to 9.0.2.6

You can upgrade from release 9.0.1.4 to 9.0.2.6.

If you are not yet running a version of Instant Messaging Server 9, see "Upgrading Instant Messaging Server (Prior to Version 9 to 9.0.2.6)".

Note:

Java is no longer bundled with the Oracle Communications Unified Communications Suite installer and requires manual installation. It is important that you install the correct version of Java for Instant Messaging 9.0.1.4.0. For information, see "Installing Java".

Upgrading Instant Messaging Server (9.0.1.4 to 9.0.2.6)

To upgrade to 9.0.2.6:

Stop Instant Messaging Server.
```
imadmin stop
```
Use the Communications Suite installer to upgrade Instant Messaging.
```
commpkg upgrade
```
For more information, see the commpkg upgrade documentation at:

https://wikis.oracle.com/display/CommSuite/commpkg+upgrade+7.0.6+Usage
Select the Instant Messaging Server 9.0.2.6.0 component from the Product Selection list.
Respond to the Communications Suite installer prompts to upgrade.
Restart Instant Messaging Server.
```
imadmin start
```
(Optional) If you have deployed any Web applications, redeploy them.
```
iwadmin redeploy app_name
```
where app_name can be im, httpbind, or all.

This step completes the upgrade process and redeploys the specified component(s).
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.
```
imadmin smf-register
```
When upgrading to Instant Messaging Server 9.0.1.4.0, check if you are using any of the following items and do not wish to reconfigure:
- 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 existing configuration file and do not wish to reconfigure, then you must set the iim_server.useport property to true by using the imconfutil command. For example:

imconfutil -c xml_config_file set-prop iim_server.useport=true

Upgrading Instant Messaging Server (Prior to Version 9 to 9.0.2.6)

Upgrading to Instant Messaging Server 9.0.2.6.0 from an Instant Messaging Server release prior to version 9 is a two step process. You must first upgrade to Instant Messaging Server 9. Then, you upgrade to Instant Messaging Server 9.0.2.6.0.

To upgrade from a version prior to Instant Messaging Server 9:

To upgrade to Instant Messaging Server 9, see the upgrade documentation at:

https://wikis.oracle.com/display/CommSuite7U2/Instant+Messaging+Upgrade

Run the following commands for the Instant Messaging Server 8 parameters that did not get migrated:

imconfutil set-listener-prop -u -c /opt/sun/comms/im/config/iim.conf.xml c2s port=45222 worker-out=muxout
worker-in=muxin protocols=c2s
imconfutil set-prop -u -c /opt/sun/comms/im/config/iim.conf.xml iim_server.deliverofflinechat=true
iim_mux.jvm.maxmemorysize=2048 iim_ldap.conferencecontainer="ou=sunConferences" iim.policy.cachevalidity=3600

To upgrade from Instant Messaging Server 9 to Instant Messaging Server 9.0.2.6.0, see "Upgrading Instant Messaging Server (9.0.1.4 to 9.0.2.6)".

Post-Upgrade Tasks

See known problems in Instant Messaging Server Release Notes for post-upgrade tasks that might be necessary.

Upgrading from 9.0.1.4 to 9.0.2.6 in a Highly Available Environment

Upgrading Instant Messaging Server in an HA environment consists of upgrading the Instant Messaging Server software followed by upgrading the Instant Messaging Server Sun Cluster Agent.

To Upgrade to Instant Messaging Server 9.0.2.6 in an HA Environment

Disable the Instant Messaging Server resource.
```
scswitch -n -j im-server-resource
```
Make sure that the non-active node does not have access to the configuration directory.
Run the commpkg upgrade command on all cluster nodes.
Copy the Instant Messaging 9 configuration file iim.conf.xml to the iim.conf file with the same permissions.

Also copy the iim.conf.xml file to iim.conf after any future configuration changes as cluster uses the iim.conf file.

To use the new 'GatewayConnector' service in HA, update this service configuration with the virtual host name or IP address and port number as follows:

imconfutil --config config_file set-prop iim_gwc.hostport=virtual host-name or ip:port

For example:

imconfutil --config /DATA1/default/config/iim.conf.xml set-prop iim_gwc.hostport=192.10.12.11:22222

Enable the Instant Messaging server resource.
```
scswitch -e -j im-server-resource
```

To Upgrade to Instant Messaging Server 9.0.2.6 Sun Cluster Agent (IM_SCHA)

Run the commpkg upgrade command on all nodes on the cluster. If cluster node is a non-global zone, run commpkg upgrade in global zone as well as in non-global zones.

Rolling Back an Upgrade

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

To roll back the upgrade process:

Stop all services.
```
imadmin stop
```
Remove the Instant Messaging Server 9.0.2.6 packages.

For example, on Solaris, use the pkgrm command.
Install a prior version of Instant Messaging Server by using the Communications Suite installer for that version.