Tuesday, January 31, 2017

Me? At a Hackathon? Lead a team? What?

I submitted a topic for Alan Hamilton's IBM Connect Hackathon which takes place the day before the event. It was accepted, my team "Domino Tweets" is good to go!
Our Motto : Stay at the pub longer, we'll tweet you if we need you, love your Domino Server!

Why? Because I have wanted one thing for a while, a DDM (Domino Domain Monitor) notification via Twitter.

As an admin DDM is my top inside the box tool. Notifications are usually in the database itself or in my case sent via emails. Emails can not be received when there is an SMTP issue or spam appliance failure. How do you get notified then? 

My answer is Twitter.

But it could just as well be Slack, IBM Watson Workspace, IBM Sametime, What's App, Google Hangouts or Skype, maybe Facetime (Ok, maybe not Facetime, unless I can use The T2 Arnold as the sender) to name a few variations.

Maybe we will do some of these, maybe only one, but whatever it is, this will be a giant step in moving DDM notifications forward with how admins work today.

The link to sign up and be a part of it is here. See you at the IBM Building Monday the 20th!

Thursday, January 26, 2017

Thursday Tips - Sametime Installations Gone Awry?

I recently inherited a failed Sametime Complete 9.0 Installation that was stuck on the proxy server.

This would be the 3rd time in the last 2 years I have had the same exact circumstance.

Thank you all for bringing these to me. The commonality in each case was a reliance on the Zero to Hero 900+ slide deck. While it is a great guide to follow, especially if internally you need screen shot by screen shot directions, it lacks a few things that are kind of important.

It makes it very clear everything is on one server, if anyone read the slides, this is not very feasible for the average installation.Why is this an issue? Websphere needs to be installed on each machine but is not mentioned anywhere. SSO is not mentioned. Creating the services, and dependencies for those services is only partially mentioned.Naming everything sametime.org.com is not going to work either.

There are many more items to consider and think about, in short, if you don't know enough about what is missing, don't start down this path.

So for those getting stuck along the way, and have yet to call me for help, here are some pieces of information which may help you along the way. None of this is new but sometimes you just need a bunch of help all in one place.

I will presume you know enough to download any updates from IBM's Fix Central, how to install Websphere and the Installation manager and all the other components. If not, call me.

In no particular order:
SSO import, export of the LTPA token to/from Websphere and the Community Server details can be found here.

Keep in mind the token name must be syntax correct and the same name used throughout the process.
You may want some more details from this post:

When you need to create the Domino SSO Configuration, use this guide.

You can have multiple Domino SSO Configuration documents, just name them differently.

We needed to do this in 2 of the 3 cases because we used the same Domino domain for Community servers and :LDAP servers. This is one case where creating a new OU inside your domain may help you, check with your trusted advisor.

Need to create a Windows Service, and Dependencies so on startup it loads all the WAS and server items properly? You need the sc.exe command tool .

The syntax is not fun, and be very careful with the CAPS letters and lower case ones as any diffrences will not let this work, see this for a massive example.

Here is an example of how I did a few. You start at the bin directory (I used a D Drive) and then enter the text starting with "sc config " after the ">" remember long names and spaces in between words need the quotation marks:

Proxy Server itself and has a dependency of starting AFTER the local nodeagent:
sc config "IBMWAS
85Service - STProxyServer" depend= "IBMWAS85Service - con-stproSTPPNProfile1_nod
 For the Sametime System Console (SSC) the Nodeagent has to start AFTER the Deployment Manager
sc config "IBMWAS
85Service - STConsoleServer_NA" depend= "IBM WebSphere Application Server V8.5 - STConsoleServer_DM"

If you need to remember the order of starting and stopping the Websphere Sametime Servers read this note.

Lastly, document that installation using my excel spreadsheet which you can get from this post of mine.

Tuesday, January 10, 2017

If You're going to San Francisco...

"You're gonna meet some gentle people there" 
- So sang the late Scott Mckenzie in May 1967 as an advertisement for the then upcoming Monterrey International Pop Music Festival.

One of them will be me, as I have been asked to speak about one of my clients about their journey to the IBM Connections Cloud.

The abstract officially says(link):
Getting to the cloud is half the battle; while getting your users to follow you (let alone understand what is where or how) is another story entirely. From CAPS-happy users to 75% traveling executives, and clients that are so well known we have perpetual attempts to defeat our security, these are some highlights of our experiences moving from on-premises to Connections Cloud.

Moscone West, Level 2 - Room 2011Wed, 22-Feb 01:00 PM - 01:45 PM
(time, date and location may change before the event)

This is a new location, a new venue, a new conference with the same friendly and smart people you know from past years plus more people from across the tech scene which we have yet to know and become friends and family with over time.

Many of my fellow IBM Champions will be there, presenting and attending as will IBM Product Managers and if you look hard enough, the IBM Developers. 

The future which includes an expanding universe of Watson Workspace, Verse, Verse on Premises, IBM Connections, plus some surprises I am sure from the opening keynote to keep everyone excited during the show.

See you all in San Francisco!

Tuesday, January 3, 2017

Mission Tools: Lotus Quickr to IBM Connections Cloud

Welcome to the 3rd installment of my migration project.

I am happy to say that we moved everything over, now we are verifying everything came over and cleaning up all the orphaned and misc. files that were found and cross linked at one time.

So, how did we get it all moved I bet you are asking.

There is an automated way, via IBM and their partner in Europe T-systems, which is part of T-Mobile it seems, they can help and their pricing is really for the bigger companies. They have a process and methodology and will then get working on it....but you still have limits of bandwidth and time although they claimed they could get this done in a week.

Our problem was, we could not have any down time, but also not have any duplication of data which they made it sound like they offload the data first then do a second synch afterwards.

If you want to go with them, contact me and I will connect you.

After weighing the pros and cons we decided to do it in house.

These are the tools I used, you may have other preferences.

IBM: IBM Connections Cloud Plugins for Windows and the plugins for Notes clients. You will also need the Quickr Places Monitor.

RPR Wyatt: Quickr Essential File Extractor and Essential Place Catalog. There are some fees with these and you need to ask for it as it no longer sits on the website. I previously worked with RPR Wyatt and was loaned the tools. I owe you drinks Jim! 

Microsoft: Windows Explorer

Lialis: MAC people this is for you, File Jockey, to have a plugin that doesn't cost you anything. As they state on the site:
"We also supply File Jockey for all IBM Connections Cloud users. It's 100% free, no limitations and no signup. Feel free to use it now by pressing the button above to read the how to guide."

And there you go. Nice and simple right? Off you go.

Not so fast. You will find a few things along the way that you also need this cute tool I found called  Bulk Rename Utility. It does exactly what it says and makes changing, say 800 folders that had an added _Folders added to them, magically disappear in seconds. No command line knowledge required. Ask me if you need help.

Why do we need this tool? Because the RPR Wyatt tool extracts all the attachments and maintains the folders layout but adds _Folder to everything, My main gripe, but a small one. The developer did not return my messages, hey it is free without support, I just wanted to make it a better tool. But since these posts are capping out at 200 views I figure no more than 200 Quickr shops exist and maybe it isn't a big enough group to warrant the effort. So if you still have Quickr and are thinking of migrating let me or RPR Wyatt know. There is safety in numbers.

The steps of my process was, after backing it all up someplace first:

  1. Use the RPR Wyatt Place Catalog tool first and review what we had and how much of it existed.
  2. Use the RPR Wyatt Extractor tool to extract the files from one place at a time. Why not all at once? 100's of GB and you know there will be issues, you want to progress, even if it is slowly.
  3. Once extracted and you installed all your plugins, login to IBM Connections Cloud and manually start making all of your Communities. If you read my post on automating this process you will think, cool I can load them all at once. Sorry to burst your bubble, but no. IBM in a PMR I raised outlined that you can only create 1 community at a time and only with one owner. Thus, the actual time it took me to create a community and configure it the way we needed and have all the proper owners and members was approximately 2-3 minutes each. Not so bad, but I really wish IBM had fixed their API.
  4. Next step is to add the Communities to the Windows Explorer plugin.
  5. Now copy and paste from one Windows Explorer window from the drive on teh server where you extracted the files to the other which has the Community list.
  6. Once done, delete all non admin members from the Place within a browser so users do not accidentally add or delete files that are needed.
  7. Continue until done.

The Lialis File Jockey was for the MAC people to start using Connections files the way they needed to for every day work. So technically I did not use it to do the migration, but I give them kudos for being there and were it NOT for them, the project might not have started as the office is moving over to all MACs.

Sounds easy, but what we found was rather dismaying.

  1. Cross linked files were everywhere. This was from various crashes over the years and while we knew we had some, I was not expecting the 100's of folders linked.
  2. Orphan files. The extractor tool was great about files and folders but sometimes random files just in a place did not get migrated. Always verify what you see is what you got.
  3. Hidden folders and other anomalies. Probably some bad drag and drop by someone left some folders in the oddest places.
  4. Size matters. What the Quickr server and the RPR WYatt tool showed us was not what we found when we extracted the data, In fact, we found we had about 60% of the data once extracted. As an example if we were told there were 10GB in a place we usually had about 6GB after extraction. SWEET! But left me wondering what was wrong. See cross linked files and you start to understand.

Thus while the project was completed by the time everyone started work today, I still have many folders and files to clean up, VERY manually eye balling everything. And I am sure I will get some panic call about a missing file or two, but at least to the employees, everything is moved.

There will be one more post in this series about what I learned about IBM Connections Cloud along the way, stay tuned.

So now that I am done with this project, anyone else need me to help migrate them to IBM Connections Cloud?