Important considerations for updating to Feature Pack 1 from Sametime 9.0.1

FP1 is an update to IBM Sametime V9.0.1. Before beginning the update process, review the following information on product versions and installation sequence. Updating servers in the wrong sequence or with the wrong software will result in errors.

Plan for security
After you finish upgrading your deployment, you should immediately harden the security as follows:
Back up all customized files
Customized files might be overwritten during the upgrade to Sametime® 9.0.1. For best results, store copies of all customized files in a separate location so that you can recreate the changes in the newer versions of the files.
Installation Manager
Use IBM® Installation Manager 1.8.4.1 for installing Sametime 9.0.1 components; a copy is included in the eAssembly for Sametime. If you previously installed a different version of Installation Manager, you must replace it with V1.8.4.1 before attempting to install or upgrade Sametime.
WebSphere® Application Server
  • Use IBM WebSphere Application Server 8.5.5.11 (or higher) with Sametime 9.0.1 FP1.
    Note: You should already have Java 6 installed from the previous Sametime release; do not update it to Java 8 (Sametime 9.0.1 FP1 requires Java 6).
  • Do not enable TLSv1.2 before upgrading.

    Sametime 9.01 does not support TLSv1.2, do not enable it until you finish the upgrade to Feature Pack 1.

  • Verify that SSCConnector.ear module is mapped correctly to a valid Sametime server or cluster.
    Important: Before upgrading any Sametime server that runs on WebSphere Application Server, verify that the SSCConnector.ear module is mapped to a valid Sametime server or cluster. If this setting is mapped incorrectly, then the upgrade will fail. The upgrade instructions for each Sametime server include the steps for mapping this module.
Stopping and starting servers before upgrading
  • When updating a WebSphere Application Server, stop the WebSphere server before starting the update.
  • When updating a Sametime application server that runs on WebSphere Application Server, start the WebSphere Application Server (node agent) and be sure the Sametime application server is also running when you start the update. When the update is complete, restart the WebSphere server and the Sametime server.
  • When updating a Sametime server that does not reside on a WebSphere Server, be sure that the Sametime server you are updating is running.

For information about starting and stopping servers, see the topic Starting and stopping servers in a Sametime deployment.

Disk space
Verify that your computer has enough available disk space to perform the update. For details on disk space requirements, see the "Hardware" tab on the Sametime Detailed System Requirements page for your Sametime offering.
update sequence
Use the following sequence when upgrading single servers and clustered servers.
Note: For any clustered component, ensure the deployment manager isupdated first, and then the primary node next. The primary node installation includes the application itself, which is synchronized from the deployment manager to all cluster members. If secondary nodes are not updated in the same window of time as the primary node, they must remain offline until they are updated.
  1. Installation Manager

  2. WebSphere Application Server

  3. Sametime System Console
    Important: Update the Sametime System Console before attempting to update any other Sametime server.
  4. Sametime Community Server

    Apply any IBM Domino® update prior to updating the Sametime Community Server.

  5. Sametime Proxy Server and associated WebSphere proxy servers for a cluster

  6. Sametime Advanced Server and associated WebSphere proxy servers for a cluster

  7. Sametime Meeting Server and associated WebSphere proxy servers for a cluster

  8. Sametime Media Manager

    Update all Media Manager components in the same update window to ensure that all interdependencies are met.

    1. SIP Proxy/Registrar and associated WebSphere proxy servers for a cluster
    2. Video Manager
    3. Conference Manager and associated WebSphere proxy servers for a cluster
    4. Combined PR+CF components
    5. Video MCU
  9. Sametime Gateway Server and associated WebSphere proxy servers
Use the newest server versions and fixes
Be sure to download the newest versions of servers, plus any fixes, for updating Sametime.