Connections 5.x to 6.0 migration

MWLUG 2017Moving Collaboration Forward

Migration from 5.x to Connections 6.0 – Been there, done that!

Tim Clark

BCC

@timsterc


Our Amazing Sponsors


Tim Clark

• Director of Services

• Domino Admin (ish)

• IBM Champion 2013-2017


What do you need to know?


• Plan– Gather your requirements

– Check system reqs

– Get the right software

• Test system first– If you don’t have one – build

one

• Side by side where

possible

• Backup your data

• Keep it simple– Upgrade first

– Test

– Add additional PINKcomponents

– Test again

• Do not use all or nothing– Can cause issues

– Difficult to debug

• Troubleshooting




• Your system must be at least V5 to go to 6– If not you must migrate the DBs to V5 before you start

• Essentially its like installing a new Connections system– There is no magical upgrade button

– Most components need updating or are new versions

– Sometimes the instructions for configuring have completely changed

• Know what to back up– Read the migration guide

– Backup the shared data, customizations and DBs before you start

• DO NOT just copy the customizations over– Often jsps or config has changed. Once new version is installed –

reapply the changes in the new file versions

• READ THE DOCUMENTATION – before you do anything


• Orient Me

• Notification Center

• Additional features –not magically installed as part of the standard 6 install

• Linux Only

– RHEL 7 / Centos 7

– VM needs some power:10GB Ram, 4 CPUs

• *Runs on new Pinkstack of Docker, cfc, mongoDB, redis etc

New Pink Features


Last upgrade you will do this way ….


Get the right stuff it’s not Rocket Science


Get the right stuff

• Regularly check requirement documents

• All versions are listed here:

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

• Check all notes, Download PDF

• Be careful with installation documents

– Sometimes wrong dependencies mentioned

– Supported statement does not mean it’s licensed

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


• Check the system requirements

• Make a list

• Get the correct versions

– WAS is mutli os, as are the fixes (8.5.5.10)

– Connections– os versions

– TDI – os versions (7.1.1 fp6)

– DB2 – os versions (11.1)

– Other DBs – use supported versions – or you may hit issuesOracle (12.1.0.2), MSSQL (2016)

• Install a DB Client

• Install 64 bit where possible

• Install an LDAP browser

• *Real* text editor – notepad is

useless

• Fiddler for support & its useful

• If Windows use a tool like baretail

for watching logs

• PINK

– IC-OrientMe-6.0.0.0.zip – from

fixcentral

– Must set Linux as the OS or you

can’t find it

– If installing TouchPoint for on-

boarding do OrientMe first (if you

want to use the new homepage).

Get the right stuff


Get yourself a test system


Test System is a must

• ALWAYS test a migration – did we mention ALWAYS!!

– A test or dev system is always a good idea

– Useful for migrations, fix packs, customization and config

changes

– Doesn’t have to be a mirror of live – can be a single node system

– VM or spare machine under a desk – it will do

– Same OS, DB, LDAP and HTTP server a must for sensible

testing

– Ensure your boss, project manager etc. knows how important a

test system is

– Add a test system to the requirements


Side by side - Vs In-Place


• There is NO TEST – all or nothing

• Once you have started there is no real roll back

• System is down when the migration takes place – users are off for however long it takes

• Much pressure if there is a problem

• Avoid where possible

• If there HAS to be an in place migration ensure sufficient offline backups and snapshots have been taken to allow a restore

• Have a plan to roll back, where possible migrate when system has down time (weekend, maintenance window etc)

• Stop EVERYTHING – your system will be completely offline whilst the update takes place

• Back it up : DBs and File System

• Uninstall Connections

• Ensure WAS profiles are clean (no apps or config), update WebSphere, recreate and configure (as per install)

• Install connections and configure

• Drop new Connections DBS, restore and update existing

• Configure connections, apply fixes, any customizations

• Test

NEVER do an in-place migration


• There is NO TEST – all or nothing

• Once you have started there is no real roll back

• System is down when the migration takes place – users are off for however long it takes

• Much pressure if there is a problem

• Avoid where possible

• If there HAS to be an in place migration ensure sufficient offline backups and snapshots have been taken to allow a restore

• Have a plan to roll back, where possible migrate when system has down time (weekend, maintenance window etc)

• Stop EVERYTHING – your system

will be completely offline whilst the

update takes place

• Back it up : DBs and File System

• Uninstall Connections

• Ensure WAS profiles are clean (no

apps or config), update WebSphere,

recreate and configure (as per

install)

• Install connections and configure

• Drop new Connections DBS, restore

and update existing

• Configure connections, apply fixes,

any customizations

• Test

NEVER do an in-place migration


• Completely separate environment – live

system can stay up whilst migration

testing / system building occurs

• Allows for full testing before go-live

• Any changes can be made to the new

system with little pressure as the live is

still functioning

• An actual live migration can be run when

the system has planned downtime

(weekend, maintenance window etc) –

can take as little as 4 hours (depending

on amount of data)

• If issues with live migration – existing

system is still available to roll back to in

seconds

• Less risk, less pressure, easier to debug

• Stop the Connections system – back up

everything

• If a test migration - Restart and let your

users carry on

• Install a fresh Connections system

elsewhere and configure it up as per

normal – apply fixes, customizations etc.

• Test the clean system to ensure it works

as expected – then BACK IT UP

• Migrate the data – File system

(Connections data shared)

• Migrate the DB’s – either with the DBT or

drop, restore and update

• Test

Side by Side –best practise (sensible) way


Back it up


• Data bases– ALL OF THEM!!

– Even if you are using the

Database transfer tool

(DBT)

• Shared File System

– Back up the whole of the

shared content store

– We can restore a subsetshared_content_store/audit

shared_content_store/activities/content

shared_content_store/activities/statistics

shared_content_store/blogs/upload

shared_content_store/communities/statistics

shared_content_store/customization*

shared_content_store/dogear/favorite

shared_content_store/files/upload

shared_content_store/forums/content

shared_content_store/profiles/statistics

shared_content_store/wikis/upload

Back everything up

* We refer to this not restore the whole folder


Migration – use the K.I.S.S method


• NEVER (seriously NEVER) do an in place migration

• Side by Side allows to test a clean system before running the data migration

• Use the same DB type (i.e DB2 to DB2)

• Install with example.com for mail notifications

• Run at least one test data migration

• Test all customisations with migrated data

• Document everything – record for go live and subsequent upgrades

• If an issue occurs fix it – don’t plough on regardless

• If you have to do an in place DB migration make sure DBA understands the steps and order things need to be run

• Firewalls / DNS / Network – get

these sorted before you start.

• Dedicated *Admin* user for install

• Simpler to implement phases to

minimise risk – allows testing at

each stage

• Test without proxies – add once

working – Keep it simple to install

K.I.S.S – its not brain surgery


Do not fall for ALL or Nothing

1. 5.X > 6

2. 6 + Pink

=


Never all or nothing• All or Nothing

• What happens when you try

to do too much at the same

time

• Issues with Cognos, Issues

with CCM, Issues with Docs,

Issues with data migration

• Issues were fixed, something

else broke

• Hard to debug as too much

going on at any one time.No quick wins, customer loses focus, many

PMRS opened, hard to resolve issues as

multiple products with problems.


Never all or nothing

• Phased• Connections upgrade from 4

to 5

• Deployed FEB for surveys,

add the additional

customization

• Deployed Cognos / Kudos for

metrics

• Connections Content

Manager

• Then last but not least IBM

DocsQuick wins, customer has working system, easy

to debug any issues.

Total time 6 weeks


TEST, test and test again


• Test a clean 6 system before

migrating data

• If in doubt test again before

installing / adding a new

feature

• Migrate to 6 before adding

PINK features

• Get *REAL* users to pre and

post migration

TEST !!!!!


What about this PINK stuff?


• Easy (ish) install on a newly

updated Centos 7 (or RHEL) box*

• Machine must have a resolvable

external DNS currently**

• For test/demo/small environments

a single VM will do

– Larger production

environments recommended 3

VMs***

• Disable machine firewall for install

• Ensure you have installed zip

• Networking is configured correctly

• ***If installing on multiple VMS –

set NFS file sharing up

• This is the FOUNDATION for

PINK

– As new features are rolled out

they will be deployed to this

“OrientMe” environment

Pink is the new Blue / Green / Yellow

* Take note of the system requirements (see the knowledge

center link on the next slide)

** work around for this here: http://bit.ly/PINK-DNS-FIX


• Extract IC-OrientMe-6.x.x.x.zip*

• Follow the instructions in

https://www.ibm.com/support/knowled

gecenter/SSYGQH_6.0.0/admin/install

/c_install_orient_me_homepage.html

• Prepare the install files

• Run the installer script – downloads

and deploys Docker, CFC and other

associated software.

• DO NOT change the default CFC

password of admin/admin until

everything is configured

• Create the storage

• Configure Connections 6 TDI / Profiles

• Install the Orient Me images

• Configure HTTP / Proxy

• Configure REDIS

• Run the people migrator for homepage

(might break here)

• Fix for SSL

• Configure the notification center

• Test via yourconnections.url/social

Pink – install info

*check fix central for latest version

https://www.ibm.com/support/knowledgecenter/SSYGQH_6.0.0/admin/install/c_install_orient_me_homepage.html


Note to IBM


And as if by magic …Connectios-Orientos-Pinkios


Post migration and troubleshooting


• Post migration tasks - Read

the KB http://bit.ly/cnx6-

postmigrate

• Migrate / rebuild search

• Clear all scheduled tasks

• Migrate community surveys

• Steps on profile / profile policy

types

• + More …

• Troubleshooting

– Start with clear logs & clear

<profile>/temp & wstemp

– Know where the logs are

• WAS, HTTP, Plugin,

DB2, Cognos, CCM,

Docs etc.

– Start with Systemout and

work backwards

– Test against WAS (no

HTTP) if HTTP issues

Post migration & Troubleshooting

http://bit.ly/cnx6-postmigrate


Troubleshooting PINK

• Check the datastores / pvs –

kubectl get pv,pvc

• Check the pods –

kubectl get pods

(use –o wide for more details)

• Check the services –

kubectl get svc


• If you see issues with the

pods you can redeploy

them

• Get the pod name from

runningkubectl get pods –o wide

• Simply delete it

i.e.kubectl delete pods orient-

webclient-2180930634-2831s

• Pods recreate themselves

• Great kunectl cheat sheet

here: http://bit.ly/kubecheat

• Blog post from Ben about

limiting resources for orient-

me:

http://bit.ly/limitorient-me

• If in any doubt ask in the

Connections Skype chat –

the PINK devs are listening

in

Troubleshooting PINK

http://bit.ly/kubecheat

http://bit.ly/limitorient-me


And you are done


Remember this is the last upgrade you will do this way


• Come and see us at our booth

• You could wina Ring (wifi doorbell)

• E - [email protected]

• W - www.bcchub.com

Thank you

Tim Clark

http://blog.tc-soft.com

timsterc

@timsterc


Our Amazing Sponsors

Connections 5.x to 6.0 migration

Technology

Transcript of Connections 5.x to 6.0 migration