Chapter 14 Instant Messaging

This chapter describes how to upgrade Instant Messaging to Java ES 2005Q4 (Release 4): Sun Java System Instant Messaging 7 2005Q4. The chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Java ES Release 4:



Note	File locations in this chapter are specified with respect to a directory path referred to as InstantMessaging-base. At least part of this path might have been specified as an installation directory when Instant Messaging was initially installed. If not, the Java ES installer assigned a default value. The default value of InstantMessaging-base is /opt/sun/im.

Overview of Instant Messaging Upgrades

This section describes the following general aspects of Instant Messaging that impact upgrading to Java ES 2005Q4 (Release 4):

About Java ES Release 4 Instant Messaging

Java ES Release 4 Instant Messaging mostly represents bug fixes. There is no major new functionality with respect to Release 3.

Instant Messaging Upgrade Roadmap

Table 14-1 shows the supported Instant Messaging upgrade paths to Java ES Release 4.

Table 14-1 Upgrade Paths to Java ES Release 4: Sun Java System Instant Messaging 7 2005Q4
Java ES Release	Component	General Approach
Release 3	Sun Java System Instant Messaging 7 2005Q1	Direct upgrade: Performed by applying patches.

Instant Messaging Data

The following table shows the type of data that could be impacted by an upgrade of Instant Messaging software.

Table 14-2 Instant Message Data Usage
Type of Data	Location	Usage
Configuration data:	Local configuration directory /etc/opt/sun/im/default/config/iim.conf /etc/opt/sun/im/default/config/registration.p	Broker and related services configurations
Instant Messaging Server Resources	Local configuration directory InstantMessaging-base/html	customized client files downloaded by end users to launch the Messenger client.
Dynamic data	runtimeFilesDir/default/db where runtimeFilesDir specified at installation: HP-UX: default runtimeFilesDir: /var/opt/sun/im	Track instant messaging clients that are online

Compatibility Issues

Release 4 Instant Messaging does not introduce any interface changes and is backwardly compatible with earlier versions.

Instant Messaging Dependencies

Instant Messaging dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Instant Messaging software. Changes in Instant Messaging interfaces or functions, for example, could require upgraded version of components upon which Instant Messaging depends. The need to upgrade such components depends upon the specific upgrade path.

Shared components. Instant Messaging has dependencies on specific Java ES shared components (see Table 1-6).

Web Container. Instant Messaging depends upon web container services, which can be provided either by Java ES Web Server or Java ES Application Server.

Directory Server (optional). Instant Messaging can be configured to store and access user data in Directory Server. As a result, Instant Messaging upgrades might require extensions of directory schema.

Access Manager (optional). For software solutions that support single user sign-on for web-based services, Instant Messaging can be configured to use Access Manager single sign-on capability.

Upgrading Instant Messaging from Java ES Release 3

This section includes the following information about upgrading Instant Messaging from Java ES Release 3 to Java ES Release 4. The section covers the following topics:

Introduction

When upgrading Java ES Release 3 Instant Messaging to Release 4, consider the following aspects of the upgrade process:

General Upgrade Approach. The upgrade is performed by applying patches to the Release 3 version. There is no re-configuration of Instant Messaging required.

Upgrade Dependencies. While Instant Messaging has dependencies on a number of Java ES shared components (see Table 1-6), Release 4 Instant Messaging requires only that IM-SDK be upgraded to Release 4. Upgrade of other shared components is optional with respect to upgrade of Instant Messaging to Release 4.

In addition, Release 4 Instant Messaging is dependent on a web container and optionally dependent on Access Manager, as described in Instant Messaging Dependencies. However, these are soft upgrade dependencies; upgrade the web container and Access Manager is optional with respect to upgrade of Instant Messaging to Release 4.

Instant Messaging Upgrade

This section describes how to perform an upgrade of Instant Messaging from Java ES Release 3 to Java ES Release 4. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Instant Messaging you should perform the tasks described below.

Verify Current Version Information

You can verify the current version of Instant Messaging using standard version checking utilities

Table 14-3 Instant Messaging Version Verification Outputs
Java ES Release	Instant Messaging Version Number
Release 3	Version numbers 7.0
Release 4	Version numbers 7.0.1

Upgrade Instant Messaging Dependencies

It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Java ES Release 4. However, Instant Messaging has a hard upgrade dependency only on the IM-SDK shared component. Upgrading of other Java ES Release 3 components upon which Instant Messaging depends is therefore optional.

If you choose to upgrade all Instant Messaging dependencies, they should be upgraded in the following order, all before you upgrade Instant Messaging. You can skip any that might already have been upgraded.

Shared Components. Instructions for upgrading IM-SDK and other Java ES shared components to Release 4 are provided in Chapter 2, "Upgrading Java ES Shared Components".

Web Container Software. Instructions for upgrading Web Server or Application Server are provided in Chapter 5, "Web Server" and Chapter 8, "Application Server", respectively.

Access Manager (optional). Instructions for upgrading Access Manager to Release 4 are provided in Chapter 9, "Access Manager".

Back Up Instant Messaging Data

The Instant Messaging upgrade from Release 3 to Release 4 does not modify configuration data. However, as a safety measure it is a good idea to back up the Instant Messaging database and any existing resource and configuration files you have customized before upgrading Instant Messaging. For more information, see the Sun Java System Instant Messaging 7 2005Q4 Administration Guide (http://docs.sun.com/doc/819-2503).

Obtain Required Configuration Information and Passwords

You have to log in as superuser to perform the upgrade. If you are using Web Server as a web container, no configuration information is needed. However if you are using Application Server as a web container, you will need the Application Server administrator user ID and password.

Upgrading Instant Messaging

This section discusses considerations that impact the upgrade procedure for Instant Messaging followed by a description of the procedure itself.

Upgrade Considerations

The upgrade of Instant Messaging software to Java ES Release 4 takes into account the following considerations:

Instant Messaging components should be shut down when patches are being applied to the installed image.

In architectures in which different Instant Messaging subcomponents reside on different computers, for example messenger resources on one computer, Instant Messaging server on another, and Instant Messaging Multiplexor on yet another, the upgrade must be performed on all such computers.

The Instant Messaging upgrade applies to multiple subcomponents of Instant Messaging on one computer using the same installed image.

The Release 4 Instant Messaging upgrade patch for HP-UX OS are shown in the following table:

Table 14-4 Patches1 to Upgrade Instant Messaging
Component	Patch-ID
Instant Messaging	121516-01
Instant Messaging locale	121926-01

1Patch revision numbers are the minimum required for upgrade to Java ES Release 4. If newer revisions become available, use the newer ones instead of those shown in the table.

Upgrade Procedure

The procedure documented below applies to Instant Messaging on the computer where the upgrade is taking place.

su root

Stop Instant Messaging if it is running.

InstantMessaging-base/sbin/imadmin stop

If not already done, upgrade the IM-SDK shared component to Release 4 and any other shared components you wish to upgrade.

Apply the appropriate Instant Messaging patches in Table 14-4.

swinstall -s <patch-location> <patch-ID>

Confirm that the upgrade was successful:

swlist | grep <patch_ID>

The output should return the versions of patch IDs applied in Step 5

Restart the Instant Messaging service that was stopped in Step 3.

InstantMessaging-base/sbin/imadmin start

Verifying the Upgrade

The upgrade of Instant Messaging to Release 4 is verified by confirming that the upgrade patches have been properly applied. The steps for this verification were included in Verifying the Upgrade.

You can also check the status of the various Instant Messaging subcomponents using the following command:

Post-Upgrade Tasks

Rolling Back the Upgrade

This section describes considerations that impact the upgrade rollback procedure for Instant Messaging followed by the procedure itself.

Rollback Considerations

The procedure for rolling back the upgrade to Release 4 of Instant Messaging is pretty much the reverse of the procedure for upgrading to Release 4.

Rollback Procedure

su root

Stop Instant Messaging if it is running.

InstantMessaging-base/sbin/imadmin stop

Remove the patches in Table 14-4.

swremove <patch-ID>

Restart the Instant Messaging service that was stopped in Step 2

InstantMessaging-base/sbin/imadmin start

Previous Contents Index Next
Sun Java Enterprise System Upgrade Guide for HP-UX