ibm sametime 8.5.2 installation ”from zero to hero” upgrade to interims feature release 1

© 2009 IBM Corporation

Social Business

IBM Collaboration Solutions

IBM Sametime 8.5.2 Installation”From Zero to Hero” Upgrade toInterims Feature Release 1

Frank Altenburg | SME for Sametime IBM Collaboration Solutionsmailto:[email protected]

2 © 2010 IBM CorporationSocial Business

Agenda

● What is IBM Sametime 8.5.2 IFR1

● Requirements for a IBM Sametime 8.5.2 IFR1 Upgrade

● Architecture of a IBM Sametime 8.5.2 IFR1 deployment

● The 13 steps to a IBM Sametime 8.5.2 IFR1 deployment


What is IBM Sametime 8.5.2 IFR 1?

● IFR: Interim Feature Release● An add-on to IBM Sametime 8.5.2

● Installs on top of 8.5.2● It won't run on top of 8.5.1, 8.5.0 or

any other version of IBM Sametime● A set of new features and fixes to the

8.5.2 code base


IBM Sametime 8.5.2 IFR 1 themes

New mobile clients and capabilities

Make it easier to start down the UC path

Richer social interactions and community features

Stronger platform support

A superior user experience


IBM Sametime Mobile for iOSNew!

● A native client for iPhone and iPad devices

PresenceInstant messaging

Business card



Sametime Unified Telephony dialer

Preferred telephony device management for receiving calls

Stay online but disconnect to improve battery life when switching applications



Get notifications of incoming chats via Apple Notification System (iOS 4)

Get notifications of incoming chats via Apple Notification System (iOS 5)

Send pictures over a chat session directly from the device



Presence

Instant messaging

Sametime Unified Telephony dialer


Browser-based meetings on Android tablets and Apple iPads

● Browser-based meetings optimized for Android tablets:

New!


Browser-based meetings on Android tablets and Apple iPads

● Browser-based meetings optimized for Apple iPads:

New!


New capabilities designed to enable social interactions and community featuresNow available under the IBM Sametime Advanced license:

● Offline messaging● Multi-file and folder transfer● N-way file transfer● Organizational tree view● No Sametime Advanced server

installation required

New!


Offline messagingThe ability for Sametime Advanced users to send instant messages to other Sametime users whose status is Offline or Do-Not-Disturb.

● Sending a message to an offline contact

New!

All Sametime users can receive offline messages

As a Sametime Advanced user, Paul can send Samantha a message even when she's offline


Offline messaging

● Retrieving and replying to offline messages

Samantha can reply to an offline message by, first, selecting it from the list...

Next, she can start a chat session with Paul by clicking “Reply”. The offline message text will be added to the transcript of the new chat session.

Sametime will notify Samantha that she has offline messages waiting to be retrieved. She can access the Offline Messages viewer to check her messages by selecting it from the “More” menu on the Sametime Connect toolbar.

New!


Offline messaging

● Administrative controls

Enable or disable offline messaging.

Define storage quotas.

Define message longevity.

Define message persistence.

New!


Multi-file transferThe ability to send more than one file to another Sametime user.

● Sending files to an online contact

New!

Now Paul can send multiple files in a single transfer

Recipients get notification on the upcoming transfer


Folder transferThe ability to send a folder containing one or more files to another Sametime user.

● Sending a folder to an online contact

New!

Now Paul can send folders as well as files


Folder transferNew!

Recipients get notified of the upcoming folder transfer and they get details on the folder's contents

Senders get confirmation when the transfer is completed


N-way file transferThe ability to send a file to multiple Sametime users.

● Sending a single file to multiple online contacts

Amadou can send a file to multiple people in a group chat session

He can see progress on individual transfers

New!


Multi, n-way and folder transfer

● Administrative controls

Enable and disable multi, n-way and folder file transfer

Define file transferthroughput

New!


Organizational tree viewA shelf application within Sametime Connect that shows an organizational-tree view of the contact list.

● Hierarchical information fetched from the server

Pick a contact from your contact list and select to see that person's place in the organizational view

Managers show up at the top of the tree. Individual managers can be hidden from view

Expand nodes to see the people in that part of the organization

See presence and business card information. Launch chat sessions with individuals or start conversations with whole departments

Drag nodes to add organizational groups to the contact list

New!


Improved platform support for IBM Sametime Unified Telephony

● VMware support for the Telephony Application Server (TAS) and the Telephony Control Server (TCS)● Fully supported for production deployments● VMware ESXi v4.x

● 64-bit support for TAS on SUSE Linux Enterprise Server (SLES)● 64-Bit SLES 10 SP3● TAS in 32-Bit compatibility mode

● It no longer requires a dedicated 32-Bit server

New!


New browsers, servers and operating systems

● Browsers● Microsoft Internet Explorer 9● Mozilla Firefox 6 and 7

● Servers● Domino 8.5.3

● Operating systems● Mac OS 10.7● SUSE Linux Enterprise Server 64-Bit (TAS and TCS)

New!


Improvements to the meetings experience

Automatically mute participants upon joining a meeting with audio and video

Active speaker notification

New!

Optionally choose whether to video enable your session each time you enter your meeting room

Leave the meeting and keep the meeting room open or close the meeting for everybody


Improvements to the audio/video and telephony experience

● Custom video resolution

Select a standard video resolution...

… or define one or more custom resolutions to fit your video equipment

New!


Enablement of 3rd-party partner software to further enhance the telephony experience

● Extensions to the call window on Sametime Unified Telephony● Enables 3rd party software to identify a caller's name and replace their

image in the user interface with a photograph from other repositories

New!

Default

Default

Custom

CustomCustom

Default


Other improvements

● SRTP for group audio/video calls● Secure Real-Time Transport Protocol● Already supported in 8.5.2 for Sametime Unified Telephony calls and

person-to-person calls in Sametime● Now supported for multi way Voice and Video Chat and meetings

● Miscellaneous bug fixes and enhancements● Improved serviceability (more expressive log and error messages) on

● Installation process workflow● NAT ICE SDK● Meetings (application sharing)

● Auto-restart feature for TURN Server● Enhancements for cloud deployments (LotusLive)

New!


In summary...

● Sametime 8.5 and 8.5.1 introduced new interaction paradigms that fit very well in enabling social work patterns

● Sametime 8.5.2 continues along that vein providing additional features and refining existing ones

● Sametime 8.5.2 IFR 1 strengthens the 8.5.2 core themes with exciting new features to help make your business more social● New mobile clients and capabilities● Tools to enable richer social interactions and community features● Improvements to help you get started down the UC path● Stronger platform support● A superior user experience






Agenda


IBM Sametime 8.5.2 IFR1 Prerequisites● All Sametime components must be already on Sametime 8.5.2.

you can not install the IFR1 to a Sametime 8.5 or 8.5.1 or 8.5.1.1 Sametime component.

● Sametime System Console● Sametime Community Server● Sametime Proxy (webchat) Server● Sametime Meeting Server● Sametime Media Manager● Sametime Advanced Server● Sametime Gateway Server

● DB2 Server must be 9.5 FP4 or 9.7● If your servers are on an older level, upgrade to Sametime 8.5.2

first before continuing with this IFR1 upgrade.


● Software requirements● Client

● Windows XP (SP2), XP Tablet, Vista and Windows 7 – 32 and 64 bit● MAC OS X 10.6.2 x86-64 and future OS fix packs● RHEL 5.0 Update 4 Desktop Edition x86-32 and future OS fix packs● SLED 10.0 SP3 and 11.0 SP1 32 and 64 bit and future OS fix packs● Ubuntu 10.04 LTS x85-32 and future OS fix packs

● Server● Windows Server 2003/2008 - 32 and 64 bit (including R2)● Linux (RHEL, SLES) - 32 and 64 bit● AIX 5.3/6.1● i5/OS 5.4, 6.1● Solaris 10● ESX and ESXi 4.0, MS Hyper-V R2

● Browsers● Microsoft® Internet Explorer 6.x, 7.x, 8, 9 (Windows)● Firefox 3.5, 3.6, 6 and 7 (Windows, Mac, Linux)● Safari 5.0 (Mac)

● Other● Domino 8.5.1/8.5.2 for Community Server / 'Classic' meetings● WebSphere Application Server 7 for new servers and gateway (included)● DB2 9.7 for new servers and gateway (included)

IBM Sametime 8.5.2 IFR1 Prerequisites (continued)


● Software requirements● For WEB A/V

● Microsoft® Internet Explorer 6.x(!!), 7.x, 8.0 and 9.0 (Windows)● Firefox 3.5, 3.6, 6 and 7 (Windows, Mac)● Google Chrome 9, 10, 11, 12 and 13

SPECIAL NOTE: Apple Safari is not supported with Sametime Web Audio/Video Browser Plugin in this actual Sametime Version 8.5.2 IFR1.

We do not support any Linux based OS now for Browser A/V.

Microsoft Internet Explorer 6 should work and is officially supported. But it is not recommended to use this version because it can cause issues when several parallel connections needs to be established with the meeting server.

IBM Sametime 8.5.2 IFR1 Prerequisites (continued)


Other requirements

● Make sure that all servers you want to use can be resolved in DNS.

● If DNS is not available then list all full qualified server names and IP addresses from all servers in the hosts file and publish this file to all servers.

● The Media Manager Server does not work when installing with a DNS alias. You must configure the full qualified machine host name (including domain part) and use this for the installation. This name does not need to be configured anywhere else and the client does not see it.

● If you use Windows 2008 as Operating System, then you need to start all installations and configurations in „Administrative mode“.

● You need a LDAP Server hosting your user base. This can be a Domino LDAP or Microsoft Active Directory or any other supported V3 LDAP.

● The Sametime gateway requires a public, not NATed IP address. NAT does not work with SIP traffic (specially when using TLS encryption) because the SIP packages contain the sending IP address inside. Then the receiver refuses the SIP package coming from another address then the one inside the package.


Required files for a deployment on Windows

For a Windows update installation you need to download these files from Passport Advantage:

CI3Y8ML.exe IBM Sametime System Console 8.5.2 IFR1CI3Y9ML.zip IBM Sametime Community Server Standard 8.5.2 IFR1CI3YCML.zip IBM Sametime Proxy Server 8.5.2 IFR1CI3YDML.zip IBM Sametime Meeting Server 8.5.2 IFR1CI3YEML.zip IBM Sametime Media Manager Server 8.5.2 IFR1CI3YGML.zip IBM Sametime Connect Clients 8.5.2 IFR1CI3YJML.zip IBM Sametime Advanced Server 8.5.2 IFR1

Create a directory, for example “C:\Install”, on the servers where you want to install. Then unpack the downloaded files into this directory. Just unpack the files required for your deployment architecture on the particular server.






Agenda


IBM Sametime 8.5.2 IFR1 - Our pilot recommendation

It is known that implementing several components, who provides web services on one box, require special network configuration. The services needs to be bind to individual IP addresses. This configuration is described fully and detailed later here in the document.

This Update to IBM Sametime 8.5.2 IFR1 has some limitations that require a work around specially for this “multi components on one box” architectures with 2 ore more IP addresses and host names. This work around is described in detail in the Post Install sections after the Proxy and Meeting Server update.

The Sametime Advanced Server in this pilot deployment is optional and requires additional licensing. Do not install or update this server if you do not have purchased the required licenses. Without Sametime Advanced you can do the full installation of all components with just 2 machines.


IBM Sametime 8.5.2 IFR1 – our pilot deployment

Active Directory

LDAP

ldap.renovations.com

DB2 9.5 Server

Sametime System Console

Sametime Meeting Server

webchat.renovations.com

Sametime Proxy Server

meeting.renovations.com

Sametime Media

Manager

sametime.renovations.com

Sametime Community

Server

chat.renovations.com

Sametime Advanced

Server

advanced.renovations.com


● 1 Server for the IBM DB2 Server, IBM Sametime 8.5.2 System Console, IBM Sametime 8.5.2 Meeting Server, IBM Sametime 8.5.2 Proxy Server, IBM Sametime 8.5.2 Media ManagerQuad CPU, 8GB RAM or more, 100GB disk space or more, 64 Bit OS1 GBit Network Interface with 2 IP addresses and 2 additional DNS Alias entries.

● 1 Server for IBM Sametime 8.5.1 Community ServerSingle CPU, 2GB RAM or more, 10GB disk space or more, 32 or 64 Bit OS1 GBit Network Interface

● 1 Server for IBM Sametime 8.5.1 Advanced Server (Optional)Dual CPU, 4GB RAM or more, 20GB disk space or more, 32 or 64 Bit OS1 Gbit Network Interface

● Various client endpoints

Hardware required for this Pilot Example Deployment

With such a configuration you can host up to ● 500 concurrent Meeting Participants *● 10.000 concurrent Sametime Clients *● 300 concurrent Media Streams *● 3000 concurrent Proxy web client users *

* Ask you IBM representative for more detailed sizing information in a defined environment


Special IP configuration for the WebSphere based Server

As described before you should configure the machine hosting the WebSphere based servers with 2 IP addresses and 3 DNS entries.In this slide deck we use:

Host Name: sametime.renovations.comIP: 192.168.30.10This is the machines Host name. With this name we install the DB2 Server, the Sametime System Console and the Sametime Media Manager

DNS Alias: meeting.renovations.comIP: 192.168.30.10With this address we install the Sametime Meeting Server

DNS Alias: webchat.renovations.comIP: 192.168.30.30With this address we install the Sametime Proxy Server


Required technical users for IBM Sametime 8.5.2

IBM Sametime requires some technical users for components to communicate in an authenticated mode. All of this users should be configured so that the password never expires and never needs to be changed.

db2admin This user is created during installation of the DB2 server in the Operating System. Do not create this user in advance. It is the user for all IBM Sametime related components using DB2 to access their databases. Be sure to match the password policy requirements of the OS.

wasadminThis is the user to access the IBM WebSphere components and to administer the system. This user must not exist in your LDAP directory. It is created during WebSphere installation in a local file repository. You can use the same user name and password for all components (makes it easier) or different names and passwords. But again, it does not work when this user exists in the LDAP.


Required technical users for IBM Sametime 8.5.2 (cont)

Domino AdministratorThis user is created during installation of Domino for the IBM Sametime Community Server. It is a best practice to not use a existing administrative account because it is the account with that the IBM Sametime System Console communicates with the Community Server.

LDAP Bind UserThis is a user account in your LDAP directory. This account is used to connect in authenticated mode to the LDAP server to get all required attributes. It is possible to connect anonymously to the LDAP but then it does not work with some LDAP systems or the LDAP server requires special configuration to allow anonymous bind.


Audio/Video Plug-In for Browser access to Meeting Rooms

The Meeting Plug-In is shipped with the Media Manager in two formats.

1.) Download VersionThis version files needs to be copied onto a Web Server that can be accessed by the Browser from the client who want to access the Meetings using Audio and Video services. This could be the Domino based Sametime Community Server, the Sametime Proxy Server or the Sametime Meeting Server or any other web server in your organization.

In this pilot deployment recommendation we use the Sametime Proxy server for this service.

To download and install this Plug-In it is required to have Administrative access rights on Windows 7. With all other OS the user right is enough

2.) Deployment VersionThis version can be deployed using your preferred deployment tool. It contains a MSI installer file. But be careful in some operating systems as Windows 7, it is required to install this version with administrative rights.






Agenda


The 13 steps to a Sametime 8.5.2 IFR1 environment

1.Prepare the System for the Upgrade2.Update the IBM Sametime System Console Server3.Update the IBM Sametime Community Server4.Update the IBM Sametime Proxy Server5.Post Install Tasks for the IBM Sametime Proxy Server6.Create the IBM Sametime Proxy Server Database7.Update the IBM Sametime Meeting Server8.Post Install Tasks for the IBM Sametime Meeting Server9.Update the IBM Sametime Media Manager10.Update the IBM Sametime Advanced Server (optional)11.Post install tasks for the Sametime Advanced Server (optional)12.Configure the Apple Notification Service for iOS devices (optional)13.Update the IBM Sametime Client


STEP ONE: Prepare the System for the Upgrade

Summary

Before you can upgrade your Sametime environment to release 8.5.2 IFR1 some things needs to be checked and to be prepared.


Important: Sametime 8.5.2 Interim Feature Release 1 cannot be uninstalled. Back up key files before starting in case you want to restore the previous installation. See Backing up files before updating Sametime 8.5.2 on AIX, Linux, Solaris, or Windows.

● Download and extract the files for Interim Feature Release 1.● Update Installation Manager if the administrator name or password

has changed.● Update the Sametime System Console and optionally, the Sametime

Community Server, before you update any of the other Sametime servers that run on WebSphere Application Server.

● Start the Sametime System Console and the Deployment Manager.● Stop the WebSphere proxy server if it is enabled and running.● If you have multiple Sametime components on one computer, leave

the Sametime System Console running and stop all other WebSphere Application Server processes. If the computer runs only one Sametime component, you do not need to stop the Sametime server you are about to update.

● If you are upgrading a cluster, stop all the nodes in the cluster.


Enter the URLs „https://www-304.ibm.com/support/docview.wss?uid=swg21573958“.and“https://www-304.ibm.com/support/docview.wss?uid=swg21382867”Both technotes are pointing to the workaround here:“https://www-304.ibm.com/support/docview.wss?uid=swg21574839”

It is recommended to replace the file iscmod_uninstall.py as described in the technote before starting the update.

https://www-304.ibm.com/support/docview.wss?uid=swg21382867







The Update requires to stop all running WebSphere servers. If your Sametime System is installed the same way as the “Sametime 8.5.2 - From Zero To Hero – Part 1 Basics” then just stop the “STConsole_Server_DM” service. It will stop all other services as well.If you have installed using your own architecture, then all WebShere Servers and Nodeagents federated to the Cell of your Sametime System Console should be stopped.


The only remaining java.exe process is the NET Search Extension from DB2 when Sametime Advanced is installed as well.


It is recommended to set all services except the Sametime System Console services to “Manual” first. After the installation of one of the services a OS restart is recommended to start the corresponding WebSphere servers as Services. Otherwise the next installation will fail.

Open the Properties of each service and set the “Startup type” to “Manual”. Then click the “OK” button.


All services except the three for the System Console Server are set to “Manual” now. And all Sametime WebSphere services are stopped.


STEP TWO: Update the IBM Sametime System Console Server

Summary

This step updates the IBM Sametime 8.5.2 System Console Server to the IFR1 release.

We like to use a CMD command line window to enter some of the commands and start the installers. For that we have created a short cut in our fast start section.You can use the Windows Explorer as well to navigate to the destination directory and double click the installation file (setupwin32.exe)


Enter the command “cd \Install\IBM Sametime System Console” and press the “Enter” key. If you have unpacked the zip file to a different directory, then navigate to your directory where you can find the update.bat file.


Enter the command “update.bat” and press the “Enter” key.


The IBM Installation Manager is starting up.


Now click the “Update” button to continue.


Select the Product you want to upgrade. Here we select “IBM Sametime Server Platform”. Then click the “Next” button to continue


Click the “Next” button to continue


Be sure that all WebSphere Servers are shut down on this box and that all federated WebSphere Servers on other boxes are shut down as well before continuing with the SSC update. Then click the “Next” button to continue.


Click the “Update” button to install the Sametime System Console IFR1.


The Sametime System Console IFR1 Update is now installing. This step takes approximately 30 to 45 minutes.


When the installation has finished successfully, click the „Finish“ button to close the Installer.


Click “File” and then “Exit” to quit the Installation Manager.


The Sametime System Console is now updated to IFR1. The Services have not changed, but they seem not to be started.


But in the Task Manager you see that there are several java.exe processes running.Here is the same behavior as in earlier installations, the Installation Manager starts the services in the background but not using the OS Service start mechanism. The Service does not recognize that it is started and cant show this status in the Services view.


The best way to fix this issue is to just reboot the Operating System. Then all services who are set to start automatic, are starting using the service startup method.For this IFR1 upgrade that is a absolute required step. Otherwise the Upgrade of the next WebSphere based component - the Sametime Proxy Server - will fail.


In the Task Manager you can now see the 3 java.exe processes of the Sametime System Console and if installed, the DB2 Net Search Extension for the Sametime Advanced Server.


STEP THREE: Update the IBM Sametime Community Server

Summary

This step updates the IBM Sametime Community Server 8.5.2 to the IFR1 release.


To install the IBM Sametime Community Server 8.5.2 IFR1 Update the server must be quit first. Shut it down and be sure that there are no more tasks starting with the letters “st...” appear in the Task Manager.


In a CMD-Line window navigate to the directory to where you have unpacked the IFR1 Update package. Then enter the “setupwin32.exe” command to start the installer.


The IBM Sametime Community Server installer has started. Select your preferred language. We use just “English”. Then click the “OK” button to continue.


Click the “Next” button to continue.


Accept the terms in the license agreement and click the “Next” button to continue.


Click the “Install” button to start the installation.


The installation takes approximately 2 - 3 minutes.


The installer has installed the IFR1 update successfully. Click the “Finish” button to continue.


Now you can start your Domino Server to start your updated 8.5.2 IFR1 Sametime Community Server by clicking the “Lotus Domino Server” icon. You can reboot the OS or just start the Lotus Domino Server Service as well. All will work.

Click the “OK” button to continue.


The Domino Server starts the Sametime tasks automatically.


Wait until all 42 Tasks starting with the letters “ST...” are started. This can take up to 5 minutes.


Open your Browser and navigate to your Sametime System Console. Authenticate and then click on “Sametime System Console” - “Sametime Servers” - “Sametime Community Servers”. Here click the link “Community Server Global Settings”.


Check the box “Enable offline messages” to enable this new feature. But be aware this only works if your Sametime Community Servers and all clients are updated to the IFR1 release.

After enabling this setting it is required to restart all Sametime Community Servers.


STEP FOUR: Update the IBM Sametime Proxy Server

Summary

Use this procedure to apply the Interim Feature Release to IBM Sametime® Proxy Server, Sametime Media Manager, Sametime Meeting Server, and Sametime Advanced. Procedures for Sametime System Console, Sametime Community Server, and Sametime Gateway are explained in other topics.


Enter the command “cd \Install\IBM Sametime Proxy Server” and press the “Enter” key. If you have unpacked the zip file to a different directory, then navigate to your directory where you can find the update.bat file.


Enter the command “update.bat” and press the “Enter” key.


Be sure that all WebSphere Servers are shut down, except the IBM Sametime System Console and the DMGR of the cell. Then click the “Next” button to continue.


Click the “Update” button to install the IBM Sametime Proxy Server IFR1.


The IBM Sametime Proxy Server IFR1 Update is now installing. This step takes approximately 20 to 25 minutes.


Important to know...A new main feature in Sametime 8.5.2 IFR1 Proxy Server is the Apple iOS integration using an App that can be installed for free from the Apple App store.

This app then connects to your Sametime proxy Server through the Internet. That this can work, your Sametime Proxy Server must be accessible from the Internet.This means you need to set it up in your DMZ or configure a reverse proxy in your DMZ and forward the traffic to your Sametime Proxy in the intranet. But the recommended way is to implement your Sametime Proxy Server in your DMZ.

Another recommendation is that your Sametime proxy Server can communicate with the Apple notification service. For this to work you need to open 2 ports in your firewall to this servers in the internet. These ports are 2195 to the Apple notification server and port 2196 to the Apple feedback server.


When the installation has finished successfully, click the „Finish“ button to close the Installer. If you have installed the Sametime 8.5.2 environment exactly as described in the former “Zero To Hero” documents then you will see this warning messages. This means the upgrade was installed successfully but the registration of the upgrade into the System Console has failed. How to fix this issue is described in the next part. (Post Install Tasks)


STEP FIVE: Post Install Tasks for the IBM Sametime Proxy Server

Summary

This procedure is only required if you run into the Warning message after the installation as described in the step before.


In your file explorer navigate to the directory “C:\IBM\WebSphere\STPServerPN\console”


Open the file “console.properties” with your notepad or wordpad application


Enter the password of your “wasadmin” user after the “SSCPassword=” term. Then save and close the file.


Then open the file “productConfig.properties” with your notepad or WordPad text editor.


Check and correct the terms of “NodeIP=”, “NodeHostName=”, “WASHost=”. Enter the correct host name. Enter your “wasadmin” password in the “WASPassword=” field. And correct the”DepName=” field with the right Deployment Plan name from your Sametime System Console.


Open a CMD-Line Window and navigate to the directory “C:\IBM\WebSphere\STPServerPN\console”.


Run the command “registerProduct.bat -upgrade”.


To start the System Console registration just hit the ENTER key.


If you see the message “The upgrade process has completed successfully” then you are done. If not, then recheck and reconfigure the files “console.properties” and “productConfig.properties”. Then run the registerProduct.bat script again.


Open your browser and navigate to your Sametime System Console by entering the URL “http://sametime.renovations.com:8700/admin”.

http://sametime.renovations.com:8700/admin



Enter your “wasadmin” credentials and click the “Log in” button..


You can see that your Sametime System Console is already upgraded to release 8.5.2.1.


Click “Sametime System Console” - “Sametime Servers” - “Sametime Proxy Servers”. Then you can see that your Sametime Proxy Server is upgraded to release “8.5.2 IFR 1”


To configure the Sametime Proxy Server to use the Apple notification servers, click on “Sametime System Console” - “Sametime Servers” - “Sametime Proxy Servers”. Then click your Sametime Proxy Server.


The host names and ports of the Apple notification system are fixed and can not be changed. You only can disable or enable this push notification service and sending Photos. By default it is enabled.


Summary

This step is to create and configure the DB2 Database for the Sametime Proxy Server. This database is required to cache the Sametime messages sent to iOS mobile devices.

STEP SIX: Create the DB2 Database for the Sametime Proxy Server


Next is to create the database in the DB2 Server. If your DB2 Server is on a separate machine or on another machine, then you need to copy the database creation script files to this server first. Copy the files “createProxyDb.bat” and “proxyServer.ddl” to a directory on your DB2 Server. Then open a CMD window and navigate to this directory. In this Zero to Hero example we use just “C:\Install\IBM Sametime Proxy Server\DatabaseScripts”.


Run the database creation script with the command: “createProxyDb.bat STPR db2admin”. The term “STPR” is the name of the database and “db2admin” is the DB2 Database Server Administrator.


Be sure that you see the “...command completed successfully” message after all commands.


Open a File explorer and navigate to “C:\Install\IBM Sametime Proxy Server\DatabaseScripts”. If you have unpacked the install zip file to a different directory then use this one.


Open a second explorer window and navigate to the directory “C:\IBM\WebSphere\STPServerPN”. Then copy the file “proxyDBSetup.py” from the install directory to this directory.


Next is to navigate to the directory “C:\IBM\WebSphere\STPServerPN\SametimeProxyServerOffering\SametimeServer\STProxy\proxy”. In this directory open the file “proxy.properties” with Notepad or Wordpad or with your favorite text editor.


Edit the following values: * proxy.DbAppUser (db2admin) * proxy.DbAppUserPassword (db2admin password) * proxy.DataBaseServerName (host name of the DB2 server) * proxy.DataBaseServerPort (default port for DB2) * proxy.DbName (database name created earlier)

Then save and close the file.


Now it is required to configure the DB2 Database who caches messages to the iOS devices in the Sametime Proxy Server. For this a long command in a CMD line window is required. Several paths are required. To get and paste this path into a CMD-Line window it is easy to use the Windows Explorer. First navigate to the directory “C:\IBM\WebSphere\AppServer\profiles\webchatSTPProfile1\bin”. But do not mark the full path. Mark only the part starting from “AppServer\...”. Then press the Ctrl-C to copy this path to the dashboard.


Open a CMD-Line window and navigate to the directory “C:\IBM\WebSphere\STPServerPN”.


Now start entering the command. Begin just with “..\”. Next is to paste the part from the dashboard.


Continue with “\wsadmin.bat -lang jython -user wasadmin -password passw0rd -f “”Don't forget the “ at the end because the next part is a path that needs to be in doublequotes.


Now we need the path to the file proxyDBSetup.py including the filename.


Copy and paste the path from the explorer window, add the backslash and then copy and paste the filename from the explorer window. Add a doublequote sign at the end.


Now we need the path and filename of the proxy.properties file that we have edited just before.


Start with blank and double quotes then paste the path. Then add the backslash and then paste the filename. Add a double quote at the end.Now the command is completed and you can confirm with the “ENTER” key.


The script is now running.


The script has finished.


Next is to set both services for the Proxy Server (the nodeagent STProxyServer_NA and the Proxy Server STProxyServer) to automatic and then reboot the OS to be sure all services are starting up automatically.


When the reboot has completed and all services are started up then you should see this window in your services list.


Open your browser and navigate to your SSC – ISC. Login with your wasadmin user and then navigate to “Resources” - “JDBC” - “JDBC providers”. Here you should see the newly created datasource for your Proxy Server.


Now click on “Resources” - “JDBC” - “Data sources”. Here you should see your newly created Data Source.


Check mark the “STProxyDataSource” and click the “Test connection” button.


Be sure that the result says “successful”. The warning message can be ignored.


Next is to fix the virtual hosts configuration in the updated WebSphere applications. Click on “Applications” - “Application Types” - “WebSphere enterprise applications”. Then click the “SametimeProxy” application.


Click the “Virtual hosts” link on the right side.


All parts of the application are configured back to the “default_host” virtual hosts table.This needs to be changed.


Change all to “STProxy_host” and then click the “OK” button.


Click “Save” to save your last changes.


To synchronize the changes to all nodes just wait 2 minutes or click “System Administration” - “Nodes”. Then mark the “webchatSTPNode1” node and click the “Synchronize” button.


After the synchronization the Sametime Proxy Server needs to be stopped completely to update the next component. Select the nodeagent “STProxyServer_NA” and click the Stop icon.


Because of the dependency between the nodeagent and the Proxy Server you are asked to stop the proxy server as well. Just click the “Yes” button.


Now the Proxy Server and the nodeagent are stopped successfully.


Summary


STEP SEVEN: Update the IBM Sametime Meeting Server


Enter the command “cd \Install\IBM Sametime Meeting Server” and press the “Enter” key. If you have unpacked the zip file to a different directory, then navigate to your directory where you can find the update.bat file. Then run the “update.bat” command.


Click the “Update” button to install the IBM Sametime Meeting Server IFR1.


The IBM Sametime Meeting Server IFR1 Update is now installing. This step takes approximately 20 to 25 minutes.


When the installation has finished successfully, click the „Finish“ button to close the Installer. If you have installed the Sametime 8.5.2 environment exactly as described in the former “Zero To Hero” documents then you will see this warning messages. This means the upgrade was installed successfully but the registration of the upgrade to the System Console has failed. How to fix this issue is described in the next part. (Post Install Tasks)


Summary

In this step you manualy register the Sametime Meeting Server upgrade with the Sametime System Console if you are running into the warning message during the installation. Then you need to fix the virtual_hosts configuration.

STEP EIGHT: Post Install Tasks for the IBM Sametime Meeting Server


In your file explorer navigate to the directory “C:\IBM\WebSphere\STMServerPN\console”


Open the file “console.properties” with your notepad or wordpad application


Enter the password of your “wasadmin” user after the “SSCPassword=” term. Then save and close the file.


Then open the file “productConfig.properties” with your notepad or WordPad text editor.


Check and correct the terms of “NodeIP=”, “NodeHostName=”, “WASHost=”. Enter the correct host name. Enter your “wasadmin” password in the “WASPassword=” field. And fill the password of your LDAP Bind user in the “LDAPBindPwd=” line.


Fill the DBAppPassword with the password of your db2admin user. And correct the”DepName=” field with the right Deployment Plan name from your Sametime System Console.


Open a CMD-Line Window and navigate to the directory “C:\IBM\WebSphere\STMServerPN\console”. Then run the command “registerProduct.bat -upgrade”.


To start the System Console registration just hit the ENTER key.


If you see the message “The upgrade process has completed successfully” then you are done. If not, then recheck and reconfigure the files “console.properties” and “productConfig.properties”. Then run the registerProduct.bat script again.


Open your browser and navigate to your Sametime System Console by entering the URL “http://sametime.renovations.com:8700/admin”.




Enter your “wasadmin” credentials and click the “Log in” button..


Click “Sametime System Console” - “Sametime Servers” - “Sametime Meeting Servers”. Then you can see that your Sametime Proxy Server is upgraded to release “8.5.2 IFR 1”


Now click on “Applications” - “Application Types” - “WebSphere enterprise applications”. Then click the “Meeting Server Administration” application.


Click on “Virtual Hosts” on the right side.


Change the Virtual Hosts settings to “STMeeting_host” and click the “OK” button.


Now click the “Sametime Meeting Server” application.


Click on “Virtual Hosts” on the right side.


Change all Virtual Hosts settings to “STMeeting_host” and click the “OK” button.


Configure your 3 services for the Sametime Meeting Server to start up automatic. Then restart the OS.


After some time your OS has restarted and all already updates Sametime Servers are started up. - Your System Console, your Proxy Server and your Meeting Server.


Now its time to test if everything still works. Open your browser and navigate to your Meeting Server URL. “http://meeting.renovations.com”. Then click the “Log In” button.

http://meeting.renovations.com/

http://meeting.renovations.com/


Log In with one of your LDAP users.


You see the Meeting Server – Meeting Room interface works.


Close and reopen your Browser. Then navigate to your Proxy Server URL. “http://webchat.renovations.com”.


With IFR1 the user interface has changed now. Click the “Launch Sametime” button.


Authenticate with a LDAP user account and click the “Log In” button.


You are now logged in successfully to the Sametime Proxy Server.


Summary


STEP NINE: Update the IBM Sametime Media Manager Server


Stop the Sametime Meeting Server by selecting the “STMeetingServer_NA” service and click the Stop Service button.


Just click the “Yes” button and wait until all services are stopped.


Stop the Sametime Meeting Server by selecting the “STProxyServer_NA” service and click the Stop Service button.


Just click the “Yes” button and wait until all services are stopped.


Now all additional WebSphere services except the Sametime System Console, are stopped.


Enter the command “cd \Install\IBM Sametime Media Manager” and press the “Enter” key. If you have unpacked the zip file to a different directory, then navigate to your directory where you can find the update.bat file.Enter the command “update.bat” and press the “Enter” key.


Click the “Update” button to install the IBM Sametime Media Manager Server IFR1.


The IBM Sametime Media Manager Server IFR1 Update is now installing. This step takes approximately 20 to 25 minutes.


Click “File” and then “Exit” to quit the Installation Manager.You should reboot the machine to be sure all WebSphere servers are started up successfully as a Operating System Service.


Summary


STEP TEN: Update the IBM Sametime Advanced Server (Optional)


Enter the command “cd \Install\IBM Sametime Meeting Server” and press the “Enter” key. If you have unpacked the zip file to a different directory, then navigate to your directory where you can find the update.bat file.Enter the command “update.bat” and press the “Enter” key.


Click the “Update” button to install the IBM Sametime Advanced Server IFR1.


The IBM Sametime Advanced Server IFR1 Update is now installing. This step takes approximately 20 to 25 minutes.


Summary

In this step you configure Online Awareness for the Browser interface of your Sametime Advanced Server.

STEP ELEVEN: Post Install Tasks for the Sametime Advanced Server (optional)


Open your Sametime System Console and navigate to “Sametime System Console” - “Sametime Servers” - “Sametime Advanced Servers”. Then click your “Advanced Server” on the right side.


In the “Sametime Proxy Server” section enter the “Host name” of your Sametime Proxy Server and the “Port”. Then click the “Save” button.


Summary

This step is only required if your want to use iOS devices with the new IBM Sametime App. Then your IBM Sametime Proxy Server needs to connect directoy to the Apple Notification System Servers in the internet.

STEP TWELVE: Configure the Apple Notification Service (optional)


This slide shows the architecture of the Apple Notification Service.


For this APNS to work there are 3 requirements:

● The IBM Sametime Proxy Server must be able to connect to the APNS Servers “gateway.push.apple.com” on port 2195, and “feedback.push.apple.com” on Port 2196.

● You should open this ports in your firewalls and test with telnet that you can reach the servers.

● The device must be able to reach the IBM Sametime Proxy Server with http or https protocol. You can use a reverse proxy in your DMZ. NAT is no problem.

● The APNS service must be able to send a notification to your device.● If your device is connected to your intranet using Wireless lan, it mostly can not be

notified from the apple systems. Talk to your firewall admins to open the notification service for your Wifi LAN.


The IFR1 installer has an issue documented in the IBM Lotus Knowledge Base Technotehttp://www-01.ibm.com/support/docview.wss?uid=swg21576076

Use the next slides to fix this issue in your “Zero to Hero” environment.

Open your file explorer and navigate to the directory “C:\IBM\WebSphere\AppServer\profiles\STPSNAppProfile\config\cells\sametimeSSCCell\nodes\webchatSTPNode1”.Here you find the required file “apns-prod.pkcs12”.

http://www-01.ibm.com/support/docview.wss?uid=swg21576076


Open a second File explorer window and navigate to the directory “C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\config\cells\sametimeSSCCell\nodes\webchatSTPNode1”.


Copy the file from the first explorer window to the directory in the second explorer window.


To synchronize the changes to all nodes just wait 2 minutes or click “System Administration” - “Nodes”. Then mark the “webchatSTPNode1” node and click the “Synchronize” button.


Because this change is a mayor security change it is recommended to restart all WebSphere services including Deployment Manager. So just restart the OS of the box and wait until all services are up and running. You know this can take up to 10 minutes.


Summary

In this step you update your existing Sametime Connect or Notes embedded Sametime client.

STEP THIRTEEN: Update the Sametime Client


Updating your clients can be done just by starting the installer local on the machine or using your preferred deployment tools.

Unpack the client package to your preferred directory.

If you now open the embedded or standalone directory you can see the 3 installers for the supported OS – Windows – Mac - Linux.

In the Windows Directory you find the installation executable and a ZIP file.


Unpack the ZIP file and you can find the setup.exe and the msi installer for your deployment tool.


Additional Steps after the installation:Some additional Tuning steps can be done after all components are installed. You should consult the Sametime Product Documentation in the Internet about this steps here:http://www-10.lotus.com/ldd/stwiki.nsf/dx/Tuning_st852

If you want to implement SSL to access your Sametime Meeting or Sametime Proxy Server, additional configuration steps are required. See the Lotus Sametime InfoCenter for more details or contact the author of this document.

Automatic URL redirection to https (SSL) can be configured. To get the install instructions you can contact the author of this document.


Ports to access the Integrated Solutions Console of the particular Servers

This are the standard ports when the servers are installed with the Cell profile method.

HTTP HTTPSSametime Meeting Server 8500 8501Sametime Proxy Server 8600 8601Sametime System Console 8700 8701Sametime Media Manager 8800 8801

In this Pilot we only need the Sametime System Console and Sametime Media Manager ports for all administrative work in WebSphere and Sametime.


Legal Disclaimer

© IBM Corporation 2011. 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 presentation 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.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.Other company, product, or service names may be trademarks or service marks of others.

ibm sametime 8.5.2 installation ”from zero to hero” upgrade to interims feature release 1

Technology