News for Ex Customers of Domino, Notes, Connections….

Here’s something I found out from HCL recently that I don’t think is widely known and is really good news for anyone who has let their licenses lapse. Previously if you chose not to renew IBM would require a penalty payment (usually equal to 2.5x what would have been your annual subscription) to re-establish your licenses. That meant once lapsed it became prohibitively expensive to start up again.

HCL does not want penalty payments. If you have let your licenses lapse you can re-activate them by paying the last subscription price you paid plus any % annual increases since then. Basically paying just the current annual renewal price even if you didn’t renew 3 year’s ago.

With the investment in the products HCL have already demonstrated and committed to (one major release a year for example) there are lots of good reasons to re-establish your maintenance. If you previously let your licensing lapse but still have Notes, Domino, Connections or Sametime , renewing your subscription gets you access to the latest versions and support so you can benefit from all the TCO and development enhancements already in v10 as well as what’s coming in v11 this year such as

  • the Nomad client for tablet and smartphone enabling you to access your existing Notes applications with no code changes,
  • the app dev pack enabling Node servers to access your Domino data and for web applications to be written using Angular , React or other frameworks accessing Domino data
  • S3 cloud storage for file attachments that can be shared across multiple servers delivering an even bigger saving in storage than DAOS does currently
  • A browser based lightweight Notes client that will support all your existing Notes apps with no additional development
  • Continual development of the web based Verse client for mail, calendar and sametime
  • A browser based low and pro code development environment
  • Sametime on mobile entitlement

Hopefully you’ve been hearing all the announcements coming out of HCL since early July In addition to many TCO features already in v10, we have heard what’s coming up for developers in v11 and the work already underway for v12. If you want to know more go here to find detailed presentations from the recent factory tour where HCL showed their current and future plans.

To get a renewal quote you can contact a Business Partner, or reach out to HCL directly

customersuccess@hcl.com

Or the sales directors for each region

EMEA Paul Mason (paul.mason@hcl.com)

North America Peter Phillips (peter.phillips@hcl.com)

APAC Sushovan Chatterjee (SushovanC@hcl.com)

Whooomf – All Change. HCL Buys The Shop…

According to this Press Release as of mid June 2019, HCL take ownership of a bunch of IBM products including Notes, Domino and Connections on premises. Right now and since late 2017 there has been a partnership with IBM on some of the products such as Notes, Domino, Traveler and Sametime* so this will take IBM out of the picture entirely. Here are my first “oh hey it’s 4am” thoughts on why that’s not entirely surprising or unwelcome news ..

HCL are all about leading with on premises, not cloud. The purchase of Connections is for on premises and there are thousands of customers who want to stay on premises. Every other provider is either entirely Cloud already or pushing their on premises customers towards it by starving their products of development and support (waves at Microsoft). *cough*revenue stream*cough*

HCL have shown in 2018 that they can innovate (Domino’s TCO offerings, Notes on the iPad, Node integration etc) , develop quickly and deliver on their promises. That’s been a refreshing change.

They must be pleased with the current partnership products to buy them and more outright.

When HCL started the partnership with IBM they brought on some of the best of the original IBM Collaboration development team and have continued to recruit at high speed. It was a smart move and one I hope they repeat across not just development but support and marketing too.

HCL already showed with “Places” that they have ideas for how collaboration tools could work (see this concept video https://youtu.be/CJNLmBkyvMo) and that’s good news for Connections customers who gain a large team and become part of a bigger collaboration story in a company that “gets it”.

Throughout 2018 HCL have made efforts to reach out repeatedly to customers and Business Partners, asking for our feedback and finding out what we want. From sponsoring user group events (and turning up in droves) around the world to hosting the factory tour in June at their offices in Chelmsford where we had two days of time with the developers and their upcoming technologies. I believe they have proven they understand what this community is about and how much value comes from listening and – yes – collaborating.

Tonight I am more optimistic for the future of these products and especially Connections than I have been in a while. HCL, to my experience, behave more like a software start up than anything else, moving fast, changing direction if necessary and always trying to lead by innovating. I hope many of the incredibly smart people at IBM (yes YOU) who have stood alongside these products for years do land at HCL if that’s what they want, it would be a huge loss if they don’t.

*HCL have confirmed that Sametime is included

Integration Verse On Premises & Connections – Small Problem

This week I have been working on integrating Verse On Premises running on Domino 9.0.1 with IBM Connections.  Alright Connections 6 which isn’t supported right now.  The actual configuration is fairly simple and detailed on one page of IBM documentation.  It involves pasting some CORS redirection lines from the IBM document into your httpd.conf file and then replacing the server hostname with your own.

When I first did it against new servers the profiles integration worked fine but the Files (both accessing and uploading) as well as Follow/Unfollow actions failed.  That pointed fairly clearly to an issue with the OPTIONS request type and firebug confirmed that was throwing a 401 unauthorized error.  Finally I started to run out of ideas and asked Roberto Boccadaro if he could share his httpd.conf with me.  When I compared three separate environments the most glaring difference was with the SetEnvIf variable which is Step 5d on this page

SetEnvIf Origin “^https://(vop_server_hostname\.)?(domain_name)$” origin_is=$0

IBM’s instructions on that page tell us to use escape characters before each full stop so my variable setting would be

SetEnvIf Origin “^https://(mail\.)?(turtleweb\.com)$”origin_is=$0

However that was the problem.  The https:// caused the 401 error and I had to replace it with escaped forward slashes so my new URL is

SetEnvIf Origin “^https:\/\/(mail\.)?(turtleweb\.com)$”origin_is=$0

I applied that single change and everything immediately worked.

I have let the IBM documentation team know but if you have the same problem, check your SetEnvIf variable.

A Few Things From Connections 6 System Requirements

Connections 6 is due to be released on Friday but yesterday we had the announcement and the system requirements.  I took a look at them here and there’s a few things to be aware of if you’re an existing Connections customer

Operating Systems

  • Windows 2012 R2 and 2016 are both supported as server platforms but that’s it
    *Connections Content Manager isn’t supported on Windows 2016
  • Linux OS is SLES 12 or RHEL 7 so if you will almost certainly need to upgrade your OS if you’re already on Linux
  • Only 64bit OS are supported for servers
  • Installation Manager remains at 1.8.5 / 6 which can be upgraded in place if necessary
  • WebSphere Application Server is 8.5.5.10 which again can be upgraded in place if necessary
  • DB2 requires 11.1 minimum
  • SQL Server 2016 only
  • IBM HTTP Server 8.5.5 fixpack 10 required
  • Tivoli Directory Integrator 7.1.1 fixpack 6 is a minimum requirement and can be upgraded in place
  • Sametime integration requires Sametime 9.0.1 for chat and meetings

 

So those are the highlights that jumped out at me but the installation documentation isn’t out yet so I’ll find out more on Friday hopefully.  Start your engines…….

 

 

Fidgets.. taps fingers.. waits for the pinkish hue..

Connections 6 including customisable communities and Orient Me – the first component of Connections Pink is due today.

Or this week.

Or in the next two weeks.

Or very soon at least.

Usually I’m not that desperate to be first in line but I am currently writing a presentation about integrating Verse on Premise with Connections and I really really want to write it using a new Connections 6 install….

C’MON!!!

Connections Futures – IBM Connect Review #3

We interrupt this blog to apologise. Usually I like to sanity check my statements before publishing them but 80%+ of presentations from IBM Connect are missing online. That means my notes are all I have right now.

So let’s talk about IBM Connections and where it’s going.  You’ve probably heard references to Connections 6 as well as Connections Pink maybe Muse or Livegrid so let’s try and clear some of that stuff up.

First Connections 6 will be shipping in Q2 (tbc) and will be an upgrade from Connections 5.5 (possibly 5.x). It will have the same architecture as existing Connections and that means WebSphere, DB2/SQL/Oracle ,TDI etc.  There are some much needed new features in Connections 6 like the ability to customise as well as copy Communities. It will also ship with the first component of Connections Pink in Orient Me which will be an optional service offering an intelligent newspaper like homepage that customises itself for each person and their activities / interests.

To get to Connections Pink you’ll first need to be on Connections 6 so let’s talk about Pink and what it is.

To quote IBM Pink “is a Vision, not a Release”.  It is the future of Connections reconceived from the ground up.  There are several principles behind that Vision

  1. Currently there are multiple code streams for Connections depending on whether you are in the cloud or on premises.  There will be a single code stream
  2. Websphere will be gone
  3. Everything will be delivered as a microservice inside a docker container
  4. DB2/SQL/Oracle will be gone and replaced by MongoDB
  5. You will be able to choose the location of data for each service/component so if you want your Activities data in the cloud but your profiles on premises you can have that
  6. Every service / component will have a published API
  7. You will be able to develop your own extensions and publish them to your own github repository to deploy

There’s a lot more but essentially the ties to the legacy IBM architecture are gone. The keywords (as far as I could tell) are customisable,  flexible and developer focused. If you’re an admin then things should get much easier as you’ll be deploying services that are prebuilt inside docker containers and can automatically pick up updates directly from IBM as you would any other online software update.

So let’s take a brief timeout and discuss docker.  If you’re a developer you probably already know and maybe use docker but as an admin, especially one managing production environments it’s likely you haven’t come across it.  A docker container can be deployed anywhere as inside it are both the software code and application and the operating system needed to run it.  In theory simply starting a docker container will enable you to run the application inside it without ever having installed anything.  As you can imagine that’s a very tempting idea for Connections where we have 14+ individual applications that could then each be run inside their own individual docker containers.  Now that seems simple but as admins we will still have to understand docker behaviour, networking, container to container communications and so on.  It does mean however that add / removing / upating services becomes a simpler task.

One of the important goals of Pink is that there is to be no migration effort  from Connections 6 to Pink.  As they are doing with Orient Me, IBM will gradually introduce Pink elements into the existing Connections architecture and those elements will read data from the legacy components into their new Pink components so that at some time in the future it’s all Pink.  I stole this chart from Maureen Leland’s presentation and there are three important things to note from it.

  1. Yes those are a lot of scary looking technologies
  2. No you do not and will not need to learn or understand any of them. That entire middleware layer will be invisible to you
  3. The takeway from the diagram is that the Connections cloud code (Green) and the Connections blue code (on premises) will seemlessly transition to the Connections Pink code without you touching a thing.  Like magic.

screen-shot-2017-02-28-at-22-04-00

The other feature I want to talk about is the Muse Proxy.  Overlaid on top of Connections it will allow us to customise our Connections UI.  If you want to add a button on screen or  javascript action somewhere one doesn’t exist, you can do that using Muse and without touching the docker containers that have the services in them.  Think of it like a really powerful stylesheet (well I’m an admin so that’s how i’m going to think of it).  Now imagine your docker containers continue to update with the latest code but your configuration settings via your Muse proxy don’t change. We can separate the customisation elements from the service elements.

So I could type pages more on this and I will in future blogs when I want to talk about all of the technologies that you should not need to learn but want to be aware of.  Livegrid for instance is a new development platform for Connections and that gets a blog all of its own. The good news here is that IBM are dismissing the more lumbering dated and complex technologies and trying to replace them with architecture designed as if they were a new startup with all the technologies in the world to choose from and not just ones branded IBM.  It’s a big vision thing and I hope they can pull it off.

To quote Jason Roy Gary the Director of Software Development for IBM Connections

“We don’t want to develop software for you, we want to develop it with you”

– I applaud both the intent and the HUGE effort being put in.  As partners and customers we will do what we can to contribute to that end goal.

So to summarise, you need to get ready for Connections 6 not just for its new features (of which the Community customisations would be worth the upgrade alone) but because you will get the first Pink service (Orient Me) and have everything in place for the Pink updates and services as they arrive.  Connections 6 should be the last whole system upgrade you need to do.(that’s me saying that not IBM) 🙂