IBM Connections

Latest News from IBM

The latest updates about Lotus Connections
  1. Google is ending support for Google Cloud Messaging (GCM) as soon as April 11, 2019. This iFix updates the Connections Mobile server to use the Firebase Cloud Messaging (FCM) server endpoint instead of the GCM endpoint. Note that Connections Mobile for Android application does not require an upgrade for this iFix. The mobile app will continue to receive push notifications after the upgrade to FCM.
  2. Users using IBM Connections Mobile will stop receiving Apple Push Notification Service (APNS) notifications after the certificates expire on August 23, 2018 (8/23/2018)
  3. This package contains APAR LO94051 for IBM Connections 6.0 CR1 & CR2 which uses Firebase Cloud Messaging Endpoint instead of Google Cloud Messaging Endpoint for Android Push Notification Support
  4. This package contains APAR LO94051 for IBM Connections 5.5 CR3 which uses Firebase Cloud Messaging Endpoint instead of Google Cloud Messaging Endpoint for Android Push Notification Support
  5. This package APAR LO94051 for IBM Connections 5.0 CR4 which uses Firebase Cloud Messaging Endpoint instead of Google Cloud Messaging Endpoint for Android Push Notification Support
  6. Connections Mobile Android 6.1.3 for MobileIron Wrapped with MobileIron 8.4.0.0 wrapper
  7. Ephox Editors for IBM Connections version 3.7.7.0 is a new update for IBM Connections 6.0 IFR1-CR4 and IBM Connections 5.5 CR3. Ephox Editors for IBM Connections Version: 3.7.7.0 includes an updated Textbox.io Version: 2.4.2.74
  8. This document describes the recommended strategy and steps for applying maintenance updates to IBM Connections 6.0. It includes important information on known issues.
  9. The pod security policy (psp) admission controller is an optional feature that can be enabled when setting up a Kubernetes cluster using kubeadm. If a cluster has been set up without enabling it and you would like to now enable it, it is possible to do this. Method 1: Blow away your cluster using "kubeadm reset" and redeploy it using the steps in the IBM Knowledge Centre. This approach should only be taken if you are OK with everything in the cluster being wiped. Method 2 (steps below): ...
  10. This document illustrates the steps followed by one administrator to upgrade a server from IBM Connections 6.0 CR3 to IBM Connections 6.0 CR4.