Ensuring a smooth upgrade to Sametime and IFR 1

Transcription

1 Ensuring a smooth upgrade to Sametime and IFR 1 Tony Payne, Sametime L3 February 29, IBM Corporation

2 Agenda Plan Prepare Execute Troubleshoot Validate Known Fixes 2011 IBM Corporation 2

3 Things to do before you start the upgrade process Review documentation Make backups Did any passwords change? WebSphere UpdateInstaller Windows Services Got SPNEGO? 2011 IBM Corporation 3

4 Things to do before you start the upgrade process Review documentation Upgrades AIX_Linux_Solaris_or_Windows_st IFR 1 Upgrades x_solaris_or_windows_st852ifr1 Best Practices Yes You must upgrade to before you can upgrade to IFR IBM Corporation 4

5 Things to do before you start the upgrade process Making backups before the upgrade is a best practice. By performing the actions listed below, you should be able to restore to a known point if you do not already have a snapshot you can revert to. Of course, if you are using virtualization, then that restore process might be easier than the actions outlined below. (Although even with virtualization, keep a recent copy of the zip file generated by Action #1 below handy.) Backup actions: ALWAYS run a "backupconfig.bat" command from the deployment manager (dmgr) profile/bin directory, and then copy the resulting zip file to a safe location. This action gives you the full WAS Configuration tree for the Cell and allows you to restore should it be needed. Make a backup of the binary folder (Websphere\Appserver) and use that to restore in case of a failure. To do that, with the services down, simply zip and copy the resulting zip to a safe location. In DB2, backup the STSC and the STMS databases IBM Corporation 5

6 Things to do before you start the upgrade process WebSphere UpdateInstaller If you have already upgraded the WebSphere Application Server (WAS) portions to FP15 (or later), you should make sure that the Update Installer is the proper version (or does not exist) to prevent a possible version mismatch with what the Installation Manager is expecting. For upgrading to 8.5.2, make sure that the Update Installer is earlier than *.15 (namely, version < 15). If the Installer is version 15 or a newer version (version >=15), uninstall it, and then remove the "UpdateInstaller" folder that is in the IBM/WebSphere folder. The Sametime upgrade will then install the version it expects to use and make any needed WebSphere updates and continue. It is generally not necessary to manually uninstall any fix packs. To identify the Update Installer version, you can run the update command to launch it and note the version in the interface, or check the version.txt file in the UpdateInstaller folder. If you are updating from to IFR 1 and the Update Installer is version 15, there is no need to uninstall it IBM Corporation 6

7 Things to do before you start the upgrade process A challenge for the upgrade process can be the stopping and starting of the services. Keep the following practices in mind: If using services, set the services to manual and reboot the operating system. This step insures that the services are stopped and that Windows does not maintain any file locks on the *.dll files. Make sure that you can start/stop the individual servers from a command line - for example the nodeagent and the STMeetingServer on that node - using the deployment manager (dmgr) administrator credentials. There will be a 'validation' of the administrator credentials screen that will indicate that the program could not validate those credentials. This message is fine, and can be ignored, as long as you are certain that the credentials used are valid (namely, have not changed since the install). If any of the WebSphere administrator (wasadmin) credentials have changed, follow the instructions in "Updating Installation Manager if the administrator name or password has changed." dministrator_name_or_password_has_changed_st852ifr IBM Corporation 7

8 Upgrading the Sametime System Console Start with the Deployment Manager (dmgr), nodeagent and STConsoleServer shutdown Review the following primary technote around and IFR 1 upgrades and the Sametime System Console: "Upgrading Sametime System Console to IFR 1 fails during installation" (# ) You can pro-actively take the steps noted in the technote's solution before the start of the upgrade, and you are highly recommended to do so. Performing the steps outlined in the solution prevent the most common issues that cause the upgrade to fail. The information contained in it is valid for upgrades and should be followed for that version as well. Steps 1 and 2 in technote are applicable to ALL Sametime components; Step 3 is specific to the Sametime System Console upgrade IBM Corporation 8

9 Upgrading the Sametime System Console Step 1 - Increase the JVM heap size for the Installation Manager Close Installation Manager Go to the Installation Manager install directory (C:\Program Files\IBM\Installation Manager\eclipse) Add the line "-Xmx1024m" to IBMIM.ini Run the offering launchpad again to invoke the installation Step 2 Clear the EJB Cache Open a command prompt and navigate to <WebSphere install root>/appserver/deploytool/scripts/install/ and execute the appropriate ejbdeployclear-cache for your OS, for Windows it would be 'ejbdeploy-clear-cache.bat' Step 3 (Applies to Sametime System Console Upgrades Only) Backup and replace the 'iscmod_uninstall.py' file that is located in the <WebSphere install root>/stscservercell directory with the copy that is attached to TN # IBM Corporation 9

10 Upgrading Sametime Components Update the servers in this order: Sametime System Console Sametime Community Server Sametime Proxy Server Sametime Media Manager Sametime Meeting Server Sametime Advanced, if applicable Sametime Gateway For IFR 1 - you do not need to re-install the Sametime Bandwidth Manager because it has not changed IBM Corporation 10

11 Upgrading Sametime Components Plan for 'more than enough' time Average upgrade cycle Is one hour per node All nodes of a given component should be down during the upgrade Start with the 'Primary Node' Depending on your change window, may need to split over a couple of days 2011 IBM Corporation 11

12 Upgrading Sametime Components For the upgrades of the Community, Media and Meeting Server(s), start with those services 'down' and the Sametime System Console running. If you installed any 'Secondary Node' profiles and did not use the same username/password as the Cell/Deployment Manager, then before attempting the upgrade, apply the steps in "Upgrade of a federated seconday node to Sametime IFR 1 fails" (# ). A common problem for the upgrade process is registering the update to the Sametime System Console, if this happens you can manually complete the registration by going to the console folder and executing 'registerproduct.bat -upgrade' Do not forget the '-upgrade' flag! If you have SPNEGO configured, disable it during the upgrade process When upgrading from BOTH the STProxy and STMeetings must be upgraded If you are starting a fresh install of 8.5.2, use DB2 9.7 If you are upgrading to 8.5.2, you can maintain the 9.5 release of DB2 if you prefer IBM Corporation 12

13 Upgrading to the SSC General Overview of procedure to convert to LDAP and register an existing community server after upgrading it to ctory_with_an_ldap_directory_sta852ifr1 Biggest challenge is often Name conversion AP_format_sta852ifr IBM Corporation 13

14 Upgrading to the SSC My approach - Build the new environment pointing to LDAP Copy vpuserinfo.nsf from existing environment to new Convert vpuserinfo.nsf to LDAP Validate new environment with a few users When ready to go live Push out client changes to end users Shut down old servers and point hostname to new environment. Advantages to this approach Gives time to validate name change Minimizes client disruption 2011 IBM Corporation 14

15 Validating upgrade was successful Bullets 2011 IBM Corporation 15

16 What to do if the upgrade fails Collect Logs Review for common issues Retry the upgrade 2011 IBM Corporation 16

17 Collecting Logs if something fails Bullets 2011 IBM Corporation 17

18 Collecting Logs if something fails Bullets 2011 IBM Corporation 18

19 Collecting Logs if something fails Bullets 2011 IBM Corporation 19

20 After the upgrade completes Resolve any custom settings Validate Sametime Policy Validate Sametime Proxy features Known Fixes 2011 IBM Corporation 20

21 Resolve custom settings There have been reports of custom settings being lost during the upgrade process. The two main areas affected are the Federated Repositories and the DataSource Connection Pool Settings. For the Federated Repositories, restoring the wimconfig.xml from the backup made prior to starting the upgrade process is normally sufficient to resolve the problem. The procedure is as follows: Shut down deployment manager and all nodes Restore the wimconfig.xml to the deployment manager configuration tree Restart the deployment manager and node nodeagents Synchronize the nodes Restart the application servers, and validate If you are running multiple Cell profiles, this procedure needs to be repeated on each Cell's deployment manager. For the DataSource Connection pools, use the information in "AIDSC0042E: Could not retrieve policies assigned to the user" (# ) to ensure they are set correctly IBM Corporation 21

22 Sametime Policy Validation In 8.5.2, the default value for policy assignment is UUID. By default, UUID is not used as a Sametime internal ID by the Community server. Therefore, also by default, the System Console adds the UUID attribute to the user/group search filter that is used to resolve a user/group name to Sametime internal ID as well as to resolve the user/group that policy is assigned to. This change to UUID by default is especially important in environments where custom Java filters are in use. You must update the custom filter to add the UUID to the searches. If the custom Java filter is not updated, then policies will not work. The only indication for this failure will be that the polices will not be applied to the users properly, and features that are dependent on policies, Audio/Video for example, will not work. For more information, refer to "Usage of UUID in policy assignment in Sametime System Console requires adding the UUID attribute to customized Java resolve filters on the Community Server" (# ) IBM Corporation 22

23 Sametime Policy Validation Another problem that can occur due to policies is as follows: After upgrading, when a user clicks the link in the web client to join a meeting room, they are presented with an empty or partially drawn Meeting room window and are unable to successfully join the meeting. This problem affects all users, both anonymous and authenticated users. This problem is caused by the policy templates not being upgraded to the version. They are missing the policy items that the Meeting application is looking for. For more information and steps to resolve, refer to "After upgrading to 8.5.2, users are no longer able to enter Sametime Meeting Rooms"(# ) IBM Corporation 23

24 Sametime Proxy Features After upgrading the Sametime Proxy Server to 8.5.2, new features that should be available (for example, Android client, Web A/V, base URL redirection) do not work. The technote "After upgrading Sametime Proxy Server to 8.5.2, no new features show" (# ) describes how to resolve this problem. (New installs of Sametime Proxy Server do not have this problem; all the new features work.) IBM Corporation 24

25 Known Fixes Sametime Community Public groups vanish after directory refresh Missing Group Members in LDAP Nested Groups Excessive network traffic when using Community Server Sametime System Console Sametime Proxy Administration - "domainlist" not displayed in UI. Sametime Proxy IE Receiving Messages will break chat editor when bringtofront is turned on and window is minimized. Unicode characters in new messages notifications on iphone devices are showing as? Sametime Meetings Change of address and meeting rooms 2011 IBM Corporation 25

26 Questions Press *1 on your telephone to ask a question. IBM Lotus Support page 2011 IBM Corporation 26

27 Legal Disclaimer IBM Corporation All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this publication to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. IBM, Lotus, Lotus Notes, Notes, and Domino are trademarks of International Business Machines Corporation in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. All references to renovations.com refer to a fictitious company and are used for illustration purposes only IBM Corporation 27