Sametime 9.0.1 announced and available for download (update)

IBM announced today the IBM Sametime version 9.0.1. You can download this from IBM Passport Advanced site.

IBM Link: IBM Sametime 9.0.1 Complete – download sheet & IBM partnumbers

IBM Link: IBM Sametime 9.0.1 – Detailed System Requirements

UpdatedIBM Sametime 9.0.1 Documentation Wiki is now online

  • IBM DB2 10.5 + FP 7
  • IBM Installation Manager 1.8.4.1
  • IBM Webpshere 8.5.5 + Fixpack 5 (there is no information about higher fixpack level)
  • IBM Sametime 9.0.1 System Console, Meeting, Proxy, Gateway, Advanced, Media (also Video Manager & MCU) and Community Server
  • ST 9.0.1 Mac Client (64 Bit with A/V)
  • new Meetingcenter UI
    2016-05-04_18-33-02
  • and more What’s new in this release?
    • Live Update for Sametime Clients
    • Preconfigured configuration keys for the Sametime Meeting Server (not sure what this means)
    • First Party Call Control (access a third-party SIP server directly from their Sametime Client)
By Alexander Novak Posted in Sametime

IBM Sametime Proxy updated APNS certificate (Apple Push Notification)

The IBM Sametime Proxy Server uses a local certificate to correctly connect to the Apple push notification service (aka APNS) so that you can see a chat request inside your IOs mobile notification screen (otherwise you have to open the IBM Sametime chat app directly to see the chat).

This is gateway.push.apple.com via port 2195 and feedback.push.apple.com via port 2196.

Because the local certificate has a limited date it will expire may the 5th 2016 and you need to exchange the certificate file on your server (with the updated certificate).

Just download the new apns certificate from the IBM fixcentral website

IBM documentation: Updated security certificate for Push Notifications (iOS)


To check if the new certificate is working just use (and download) the APNSTest tool „New Sametime Proxy APNs test application“ from collaborationben site

java -jar apnstest.jar -k apns-prod.pkcs12

Beware you need three things to work to connect to APNS

  1. You need to resolve the dns addresses for gateway.push.apple.com and feedback.push.apple.com
  2. You need to be able to connect to these addresses via port 2195 and 2196 (entire 17.0.0.0/8 net)
    IP Address Range Used by the Push Service
  3. You need a valid apns certificate

Alternatively you could update to the latest Sametime Proxy fix from april 2016, but you have to update the Sametime System Console first to fix april 2016.

Sametime System Console Hotfix – ST30.25 build or 9.0.1 [April 2016]

Cumulative Hotfix for Sametime Proxy -ST30.25 build or 9.0.1 [April 2016]


APNS explained

  • gateway.push.apple.com:2195 = Apple notification server host name and port are used by the Sametime Proxy Server to send Sametime instant messages, meeting invitations, and announcements to iPhone users. When a user pauses receipt of messages, the Sametime Proxy Server database holds messages until the user views the messages or the mobile device’s pause time expires.
  • feedback.push.apple.com:2196 = Apple feedback service keeps track of which iPhone mobile devices are still valid and sends the information to the Sametime Proxy Server.
By Alexander Novak Posted in Sametime

Sametime Video Manager expired certificate – exchange root cert and trust 15 years

This is an old one, but it seems it happens a lot of again.

With the installation of the IBM Sametime Video Manager gold edition (sept. 2013), the Video Manager generates an self-signed one year valid ssl certificate.

2016-04-22_11-46-20

This certificate has to be trusted inside the Sametime Media System to connect via port 5061/5081 between Media Conference Bridge and Video Manager

IBM Wiki: Import the Video Manager’s certificate to the Conference Manager

After a year you get a new self-signed certificate on the Video manager and the connection between Media Conference Bridge and Video Manager ist broken (error 503). You could trust the new Video Manager certificate inside the Media Conference Bridge, but this is – again – for one year.

IBM already documented to change the certificate to a longer valid certificate or root certificate (15 years).

IBM Docu: Sametime 9 Video Manager – A/V call fails due to default root certificate expires in one year

Because of many people having problem with this documentation i will give you some more details and screenshots for this to work (from zero2hero)


  1. Login to the Sametime Video Manager ISC (https://yourvmgrserver:9043/ibm/console)
  2. Navigate to Security > SSL certificate & key management > key stores & certificates
  3. Select the option (or key store) NodeVMGRKeyStore
  4. Navigate to personal certificate and press the button „import certificate from a key
    2016-04-22_11-52-39-2
  5. Select the key store NodeDefaultKeyStore and enter the key store password (use „WebAS“ because it is the default password for all websphere based keystores) and press button „Get key store aliases
  6. Select in the field certificate alias to import the value default and press the button OK
    2016-04-22_11-49-31

  7. You should now see a certificate called default with a self-signed root certificate (valid for 15years) in common.
    Press SAVE to write the master configuration.
    2016-04-22_11-52-39
    You now need to assign the new certificate to the application server
  8. Navigate to Security > SSL certificate & key management > Manage endpoint security configurations
    • Expand the INBOUND tree until you see the application server name STMediaServer
    • Klick on the servername STMediaServer
    • Select „override inherited values„, select NodeDefaultSSLSetting configuration, select default certificate alias and press the button OK
      2016-04-22_11-53-46
      Repeat this for the OUTBOUND tree until you see the application server name STMediaServer
    • Expand the OUTBOUND tree until you see the application server name STMediaServer
    • Klick on the servername STMediaServer
    • Select „override inherited values„, select NodeDefaultSSLSetting configuration, select default certificate alias and press the button OK
  9. Press SAVE to write the master configuration.
  10. Check the values in the endpoint security tree
    2016-04-22_11-54-32
  11. Restart the Sametime Video Manager in the following order
    • stop STMediaServer_was.init (via service or batch)
    • stop soliddb (via service or batch)
    • start soliddb (via service or batch)
    • WAIT 60 seconds
    • start STMediaServer_was.init (via service or batch)

After this you need to import the new Video Manager certificate into the Media Conference Bridge.

  1. Login to the Sametime System Console ISC (https://yoursscserver:8701/ibm/console)
  2. Navigate to Security > SSL certificate & key management > key stores & certificates
  3. Select the option (or key store) CellDefaultTrustStore
    >> you could delete the old Video Manager certificate if you wish
  4. Navigate to signer certificate and press the button „retrieve from port
    2016-04-22_15-40-30
  5. Enter the hostname for the Video Manager (e.g. myvmgrserver.dns.local) enter the port 5061 (or any other ssl port) an press the button „Retrieve signer information
    You should see now the new Video Manager root certificate – valid for 15 years
    2016-04-22_12-22-55
  6. Enter an alias name for the certificate e.g. vmgr_cert  and press the button OK
  7. You should now see a trust certificate called vmg_cert  (valid for 15years).
    2016-04-22_15-40-30-2
    Press SAVE to write the master configuration.
  8. Navigate to System administration > Nodes select all nodes and press „full synchronize“ to push the new certificate to the all applications servers
    2016-04-22_12-24-32
    Because of having problems with the shutdown of the application server(s) after importing or changing certificates (shutdown is waiting to manually accept new certificates) i do manually retrieve the keys from the node with the following command
    >>  „<appserverbin>\profiles\<profilename>\bin\retrievesigners -host stsscserver -port 8703
    Systemdesign2
  9. Restart the Sametime Media Server (proxy registrar and/or conference bridge)
  10. Navigate to Sametime System Console > Sametime Servers > Sametime Video Manager Servers and check if you could connect to the Video Manager configuration
    2016-04-22_12-56-08

All done

By Alexander Novak Posted in Sametime

Sametime 9.0 Upgrade (poodle patch) of System Console fails

IBM announced new updates of Sametime because of SSLv3 vulnerability (PODDLE) for all Sametime comoponents on february this year

Security Bulletin: Vulnerability in SSLv3 affects Sametime (CVE-2014-3566)

After two month of upgrading today i got this strange error if i try to upgrade the Sametime System Console.

„A problem occurred during the execution of the ….WebSphere\STSCCell\build_meeting.xml file“

Analyzing the xml file (build_meeting.xml) there was a problem starting the application server STConsoleServer within the upgrade phase.
So i checked if there are problems with the registered os services to start – but this was not the problem (upgrade also failed). Looking inside the application server configuration i found out that the application server was  set to have dependencies with its nodeagent (monitoring policy = RUNNING).

So therefore the upgrade fails because of waiting for the nodeagent to start. You need – only for the upgrade process – to set the setting from RUNNING to STOPPED.

There is an IBM technote with a little more information about this setting.

Using the Monitoring Policy to automate the server startup may interfere with Application updates

 

Sametime Proxy – expired APNS certificate drops down STProxy application

IBM announced that the Apple Push Notification Service (APNS) certificate within the Sametime 8.5.x/9.0.x Proxy installation will get expired on june, 19th 2014

Updated security certificate for Push Notifications (iOS)

So please make a update NOW !!!

If you do not update the certificate (or forgot) your Sametime Proxy webchat client will not work anymore. You should get error messages inside the
proxy log (systemout.log) like this.

APNSService   W   com.ibm.collaboration.realtime.stproxy.services.APNS.APNSService.isPushAvaialble() – Connection to APNS Failed. Returning false. Exception thrown
                                 java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream.java:179)
    at com.ibm.jsse2.b.a(b.java:146)
    at com.ibm.jsse2.b.b(b.java:174)
    at com.ibm.jsse2.b.a(b.java:38)
    at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:209)
    at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:643)
    at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:106)
    at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:304)
    at com.ibm.collaboration.realtime.stproxy.services.APNS.APNSService.getSSLConnection(APNSService.java:429)
    at com.ibm.collaboration.realtime.stproxy.services.APNS.APNSService.testConnection(APNSService.java:507)
    at com.ibm.collaboration.realtime.stproxy.services.push.PushService$1$1.run(PushService.java:84)

Another problem coudl be that you can´t change the Samtime Proxy configuration inside the Sametime System console, after saving you get an error

AIDSC1608E: Unable to reach the Sametime Proxy host name
Sametime Proxy error

This could be solved by updating the APNS key OR i had the same problem at a customer because the APNS Servernames

feedback.push.apple.com
gateway.push.apple.com

could not be resoved by DNS (so i added tha APNS addresses to the local hostfile).

Sametime 9 Hotfix(es)

IBM brought some Hotfixes for IBM Sametime 9 which are resolving some problems found in 9.0 Gold (Sept. 2013).

Sametime 9.0 – generelly Hotfix 1 (04-01-2014)

Sametime 9.0 – Hotfixes for Proxy (18-12-2013)

9000-ST-Proxy-FP-JCHG-9EGGAT

Sametime 9.0 – Hotfix for Media Server (30-01-2014)

9000-ST-Media-FP-RVVV-9FELQY

Sametime 9.0 – Hotfix for Client (31-01-2014)

9001-ST-Client-FP-LQIU-9FK83A

If you plan to install Sametime 9 as new – you do not have to install 9.0 Gold first, you just need to download ST 9 Hotfix 1 from IBM Fixcentral
and just add/insert the file repository.config to the IBM Installation Manager repository.

e.g. …/SametimeProxyServer/disk1/STProxy/respository.config

Sametime 8.5.2.x DB2 Migration to Sametime 9

IBM published the document for migrate your DB2 data (like SSC policies or Meeting DB) to the new Sametime 9 enviroment.

Sametime 8.5.2.x Migration to Sametime 9

Migrating from Sametime 8.5.2x (Wiki Doku)

You can either stay on DB2 Version 9.5 (Sametime 8.5.0/8.5.1) or 9.7 (Sametime 8.5.2) or you can upgrade DB2 to Version 10.1 (see the IBM statement)

„Please note that none of the deprecated or discontinued features in 10.1 have a direct impact on Sametime deployments.“

Here is a „shorcut“ for the steps

Because IBM references directly to the DB2 documentation i will give you a indeep migration step.

Keep Sametime Community Server before upgrading

  • unregister ST Community Server(s)/MUX from ST System Console
    • check entries in  …/domino/console/productconfig.properties & console.properties
    • …/domino/console/unregisterproduct.bat > should remove ST Community Server from SSC
    • Deregistration will you disconnet from SSC policies and policies in stpolicy.nsf will take place !!!

Uninstall Sametime 8.5.2.x enviroment

  1. Start Installation Manager and deinstall all components within
  2. Deinstall Installation Manager 1.4.2
  3. Delete or Move kept Installation folder \Websphere\*

in-place DB2 Server Upgrade to Version 10.1 (or you can stay on Version 9.5 or 9.7)

  1. Check if databases are DB2 V10.1 compatible
    • Extract DB2 V10.1 Installation package
    • C:\install\db2v10setup\WSER\image\db2\Windows\utilities\db2ckupgrade.exe STMS -L c:\db2.log -u db2admin -p passwort
      Message should be like this >> DBT5508I  The db2ckupgrade utility completed successfully. The database or databases can be upgraded.
  2. Check/Show DB2 instances C:\IBM\SQLLIB\BIN>db2ilist
  3. Install/Update DB2 to Version 10.1
  4. Install DB2 NetExtender Addon

Upgrade DB2 database(s) to Version 10.1

  1. Drop/Disconnet all connections to DB2
    • C:\IBM\SQLLIB\BIN>db2stop force    >>> Disconnects all users and stops the instance
      SQL1064N  DB2STOP processing was successful.
      C:\IBM\SQLLIB\BIN>db2 terminate   >>> Terminates back-end process
      DB20000I  The TERMINATE command completed successfully.
  2. Check if upgrade of DB2 is needed
    • C:\IBM\SQLLIB\BIN>db2level
      DB21085I  Instance „DB2“ uses „64“ bits and DB2 code release „SQL10010“ with
      level identifier „0201010E“.
      Informational tokens are „DB2 v10.1.0.872“, „s120403“, „NTX64101“, and Fix Pack  „0“.
      Product is installed at „C:\IBM\SQLLIB“ with DB2 Copy Name „DB2COPY1“.
    • Otherwise use C:\IBM\SQLLIB\BIN>db2iupgrade DB2 /u:db2admin.password
  3. Upgrade Sametime DB2 database – otherwise you get the error message „The database must be upgraded to the current release.
    • C:\IBM\SQLLIB\BIN>db2 upgrade database STMS
    • C:\IBM\SQLLIB\BIN>db2 upgrade database STADV

System Console (you will loose all your configuration, so you have to document it first and then reasign it to the new SSC)

==> NOVI recommendation: Write down all Policy Settings and recreate the settings in the new STSC DB in Sametime 9 SSC

  • >>> Miss Step 1 & 4
  1. Export Policy Tables POLICY.TEMPLATE & POLICY.ASSIGNMENT from ST 8.5 SSC
  2. Backup/Delete old STSC database
    • Backup/Rename STSC database if needed
      • create db2rename.cfg file manually
           DB_NAME=STSC,STSC85
           DB_PATH=c:\
           INSTANCE=DB2
           NODENUM=0
      • C:\IBM\SQLLIB\BIN>db2stop
      • C:\IBM\SQLLIB\BIN>db2relocatedb.exe -f c:\install\db2rename.cfg
        Files and control structures were changed successfully.Database was catalogued successfully.DBT1000I  The tool completed successfully.
    • Delete STSC database
      • C:\IBM\SQLLIB\BIN>db2 drop database STSC
  3. Create a NEW SSC Database (e.g. STSYCON)
  4. Import Policy Tables into ST 9 SSC
    >> Just check before if you need this step or if it is faster to recreate the policies again
  5. Install new Sametime 9 System Console Server (with the new STSYSCON DB)
    • Install Installation Manager 1.6.2 (IM)
    • Import Websphere 8.5.5 & WAS iFixes for Sametime into IM
    • Install Websphere without config
    • Install ST System Console Server

Meeting Server

==> If you change the DB2 to other operating system you have to move the db2 completly – see this link about it

  1. Update schema for Meeting DB to get new tables for the Sametime 9 features
    >> C:\install\st9meetingsetup\….DatabaseScripts\….\applyDDLUpdate.bat migration_meetingServer_85x-90.dll STMS db2admin
  2. Add the Meeting DB to the Sametime Configuration Application (deployment plan)
  3. Create a new Meeting Server deployment plan and add the existing Meeting DB
  4. Install new Sametime 9 Meeting Server
    • Install Installation Manager 1.6.2 (IM)
    • Import Websphere 8.5.5 & WAS iFixes for Sametime into IM
    • Install Websphere without config
    • Install ST Meeting Server

Proxy Server

  1. Shut down the Sametime 8.5.x Proxy Server to get exclusiv access to the Proxy DB
  2. Drop the Proxy DB and create a new Proxy DB with the Sametime 9 database script
    !!! Please use the database create scripts from the actual Sametime proxy package – otherwise you will loose tables you need !!!
    I had to learn this the hard way because i used the db scripts from 9.0 gold release with the 9.0 Fix1 :-((
  3. Add the Proxy DB to the Sametime Configuration Application (deployment plan)
    THATS a NEW one (in ST 8.5 you had to start db2 scripts yourself)
  4. Create a new Proxy Server deployment plan and add the existing Proxy DB
  5. Install new Sametime 9 Advanced Server
    • Install Installation Manager 1.6.2 (IM)
    • Import Websphere 8.5.5 & WAS iFixes for Sametime into IM
    • Install Websphere without config
    • Install ST Proxy Server

Advanced Server

  1. Shut down the Sametime 8.5.x Advanced Server to get exclusiv access to the Advanced DB
    NO SCHEMA UPDATE NEEDED
  2. Add the Advanced DB to the Sametime Configuration Application (deployment plan) and add 3 NEW tables manually
    • INSERT INTO ORGCOL.PC_SETTING (SETTING_NAME,SETTING_TYPE,SETTING_VALUE) VALUES (‚admin.only.delete‘, 3, ‚false‘);
    • INSERT INTO ORGCOL.PC_SETTING (SETTING_NAME,SETTING_TYPE,SETTING_VALUE) VALUES (‚remove.invalid.members‘, 3, ‚true‘
    • INSERT INTO ORGCOL.PC_SETTING (SETTING_NAME,SETTING_TYPE,SETTING_VALUE) VALUES (‚wildcard.search.enabled‘, 3, ‚false‘);
  3. Create a new Advanced Server deployment plan and add the existing Advanced DB
  4. Install new Sametime 9 Advanced Server
    • Install Installation Manager 1.6.2 (IM)
    • Import Websphere 8.5.5 & WAS iFixes for Sametime into IM
    • Install Websphere without config
    • Install ST Advanced Server

    !!! If you restricted the ST Advanced Users because of license limitation in version 8.5  you have to change manually
           the table: ORGCOL.LICENSE
           the parameter: LIC_COUNT
           set from the number counted to ZERO (0)

The documentation also shows how you could change the data sources (e.g. for testing) for DB2 databases.
I think that is a bad idea because the DB name is also referenced inside the SSC application DB (see deployment name) and this could be a problem for further updates !!!