Kim Greene - Introduction · Support for Sametime 7.0, 7.5 and 7.5.1 ended on September 30, 2011....

1

Agenda Key: 36AC

Session #: 580130

Kim Greene

[email protected]

507-367-2888

Skype/Twitter: iSeriesDomino

Kim Greene - Introduction� Owner of Kim Greene Consulting, Inc.

� Extensive iSeries background

� Services offered include:

� System and application performance optimization

� Administration

� Upgrades

� Troubleshooting

� Health, performance, security, etc. checks

� Migrations

� Custom development

� Enterprise integration

� Technical writer for Systems Magazine, IBM i Edition

� Blog: www.bleedyellow.com/blogs/dominodiva

� Twitter: iSeriesDomino

Copyright Kim Greene Consulting, Inc. All rights reserved worldwide. 2

2

Agenda� Upgrade best practices

� Planning an upgrade

� Preparing for an upgrade

� Executing an upgrade

� Upgrading Clients

� Smart Upgrade



3

Upgrading to Release 8.5.3

� Can upgrade from 6.x, 7.x , 8.0.x, or 8.5.x

� Not a complicated upgrade

� New ODS is key

� Features such as OOO, DAOS, compression options, etc service require it

� Notes.ini change to make it work

� May need to comment out or change some notes.ini variables


No longer available at 8.5.3

� Lotus Domino for i Navigator plug-in

� Also affects corresponding functions in System iNavigator Tasks on the Web

� HTTP Server (powered by Apache) plugin for Domino


http://www-01.ibm.com/support/docview.wss?rs=463&uid=swg21315471

4

Hardware Prerequisites

AIX IBM i Windows

Disk Space 1.5 GB 2 GB 1.5 GB per partition

Memory 512 MB per CPU 512 MB per Domino server 512 MB per CPU

Processor Power 4 & higher Power 520 Express & above

System i 9407-515, 9406-520,

9406-525 & aboveSystem i 9405-520 Express

models & 9406-520 Value model

with accelerator processor

feature

eServer i5 520-0901 & above

iSeries 800-2464 & above

8XX moels

Intel Pentium or higher

(32 & 64-bit)

Intel EMT64 or higher (64-bit)


https://www-304.ibm.com/support/docview.wss?uid=swg27022468

Software PrerequisitesAIX IBM i Windows

Operating

System

AIX 5.3(2)

AIX 6.1 Service Pack 4(2)

AIX 7.1(2)

i5.4(3)

i6.1(3)

i7.1(3)

2003 Enterprise Edition x86-32(1)

2003 R2 Enterprise Edition x86-32(1)


2003 Standard Edition x86-32(1)

2003 R2 Standard Edition x86-32(1)


2003 SP2 Standard Edition x86-64(2)







8

Notes:

� (1) 32-bit

� (2) 32-bit; 64-bit exploit

� (3) 128-bit; 64-bit exploit

� Java V6 J9 is required on IBM i

(www.ibm.com/support/docview.wss?rs=463&uid=swg27013079)

5

PTF and Service Pack Requirements

Copyright Kim Greene Consulting, Inc. All rights reserved worldwide.

AIX IBM i Windows

Operating

System

AIX 6.1:

• Service Pack 4

APAR IZ10223 APAR IZ09961

APAR IZ10288 APAR IZ08022

V7R1: 5770-SS1 PTFs

5770-999 PTFs

V6R1: 5722-JV1 PTFs5761-SS1 PTFs

5761-999 PTFsV5R4: 5722-JV1 PTFs

5722-SS1 PTFs

5722-999 PTFsGroup PTFs:

• Java• DB2/400

• IBM HTTP Server for i

• BRMS

2003 R2 or SP2

2008 R2

9

� IBM i PTF details can be found here:� http://www-01.ibm.com/support/docview.wss?rs=463&uid=swg21305543

What OS Versions are Supported?� Release compatibility levels for all platforms can be

found here:� http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.jsp


6

Using Release Compatibility Reports


Lotus Domino


7

IBM i Support for Domino Releases

� Note 1: (2) indicates a program conversion will occur

� Note 2: Support for Domino 7.0.x ended on April 30, 2011

� IBM i Release Compatibility Guide can be found here:� http://www-03.ibm.com/systems/resources/systems_power_ibmi_lotus_releasesupport.pdf


Finding Prerequisites


8

Finding Prerequisites


Domino Prerequisites


9

Domino on i PrerequisitesProduct i7.1 i6.1 i5.4

Portable App Solution

Env (PASE)

5770SS1 Opt 33 5761SS1 Opt 33 5722SS1 Opt 33

Java V6 J9 5761JV1 *BASE

Opt 11

5761JV1 *BASE

Opt 11

5722JV1 *BASE

Opt 11


� Details found here:

� http://www-01.ibm.com/support/docview.wss?rs=463&uid=swg27013079

Checklist for Upgrading

1. Determine if system will support version upgrading to

2. Determine if compatible OS level is being used

3. Verify all needed OS software options are installed

� Don’t forget about Java version on IBM i

4. Apply necessary PTFs and/or service packs

5. Obtain necessary hotfix(es)

6. Verify compatibility with Lotus extended products

7. Verify compatibility with 3rd party add-on products

� Spam, A/V, etc.


10


8. Plan for upgrading the Notes client

� Two versions: Standard and Basic

9. Set default size for the console log

� Console_log_max_kbytes=xxxxxx

� Now set for you in 8.5.3!

10. Plan for the new ODS level

� New ODS level is 51

� Create_R85_Databases=1



11. Remove unsupported notes.ini variables� PercentAvailSysResources

� ConstrainedSHM

� ConstrainedSHMSizeMB

� MEMAddressableMem

� MEMAddressableMemSizeMB

� MEM_EnablePreAlloc

� MEM_EnableSubAlloc

12. Plan to upgrade the Domino Directory design

� Type “Yes” on the console to upgrade the design after the upgrade

� Will show later after server start-up in 8.5.3 than in previous releases


11


13. Plan to upgrade the mail template

� mail85.ntf

14. Review template customizations

• Will custom template inherit new design or must new template be updated

• Have you customized the default ACL entries

• Have you set any custom application properties (for

example – DAOS)

15. Plan to test custom applications at new release


Checklist for Upgrading - iNotes

16. Plan to update the stlinks signed applet

� Required when using iNotes with the integrated Sametime and

the Firefox browser

� Domino 8.5.3 ships an outdated applet

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

� Get the updated applet from Fix Central

17. Plan for updated activeX control

� Will users have authority to update the control

� Accessing iNotes on Citrix

� Be sure to update the Citrix server


12

Doing the Actual Upgrade

1. Upgrade Notes clients for administrators

2. Remove any obsolete notes.ini variables

3. Backup Domino servers

4. Set the console log size if necessary

� console_log_max_kbytes=xxxxxx

5. Install Domino 8.5.3 code

� Upgrade all servers upon upgrade OR utilize multi-version support where applicable

� Avoid design ping-pong

6. Install required hotfixes


Doing the Actual Upgrade7. Upgrade Administration server first

� Start first OR issue UPDDOMSVR if on IBM i

� Type “Yes” at the console to upgrade the directory design

8. Upgrade other servers

� Development, Hub, Mail, SMTP, Application, …

9. Verify notes.ini

� Remove or change any entries added by default during the

upgrade (ServerTasksAt…)

10. Upgrade Domino extended products

11. Upgrade 3rd party products


13

Doing the Actual Upgrade12. Bring mail template customizations forward

13. Test custom applications

14. Upgrade users to new release of Notes

� Trick: Install Standard edition of the client, can change icon to point to nlnotes.exe if necessary

15. Upgrade mail files to new template (mail85.ntf)

� Remember the –u option� load convert mail –u mail/*.nsf * mail85.ntf

16. Take advantage of new ODS level

� Create_R85_Database=1

� Copy style compact (-c option)


Design Ping-Pong – What is it?


8.5.3 Server 8.5.2 Server

Updates design of mail

files to 8.5.3 design

Updates design of mail

files to 8.5.2 design

Replicates

design changes

to 8.5.3 server

Replicates

design changes

to 8.5.2 server

14

Preventing Design Ping-Pong� Replicating templates between servers

� Most templates share same replica ID across servers

� Latest design gets replicated

� Stops ping-pong chain of events

� Limiting Design task execution

� Runs by default at 1:00 AM along with Catalog task� ServerTasksAt1=Catalog, Design

� Remove ‘Design’ from this variable� set config ServerTasksAt1=Catalog

� Or edit notes.ini file directly

� Until all servers are at same code level


Preventing Design Ping-Pong� Selective replication

� Choose to not replicate design elements

� Remove templates from down-level servers

� Use with caution!!� Can cause performance issues for servers if servers or

clients attempt to replicate the removed templates


15

Domino Extended Products� Need to ensure release compatibility before upgrading

� Which version of extended product runs with which versions of Domino

� Which version of OS supports required Domino version

� Check one of these resources:

� All platforms� http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.jsp

� IBM i specific� http://www-03.ibm.com/systems/resources/systems_power_ibmi_lotus_releasesupport.pdf


Domino i Support for Extended Products

� Notes: 1. Support for Lotus Quickr 8.1 will end on April 30, 2012. 2. Domino Fax was withdrawn from marketing in January, 2011, and end of support is April 30, 2012.

3. Support for Sametime 7.0, 7.5 and 7.5.1 ended on September 30, 2011. 4. Support for Lotus Quickr 8.0.x and Lotus Enterprise Integrator 7.0.x ended on April 30, 2011.


16

Extended Product Release Compatibilities

� Notes: 1. Before upgrading a Lotus Quickr server to a later Domino release, verify that an enabling fix is available for that release:

www.ibm.com/systems/i/software/quickr/.

2. Domino Fax was withdrawn from marketing in January, 2011, and end of support is April 30, 2012. A Domino Fax update is required for Domino 8.0.x and 8.5.x (www.ibm.com/systems/i/software/domino/related/fxd/faxupdates.html )

3. Support for Lotus Domino 7.0.x, Lotus Quickr 8.0.x, and LEI 7.0.x ended on April 30, 2011. However, Domino 7.0.x can be used to run Domino Document Manager until support for that product ends on September 30, 2012.

31

Sametime Standard 8.5.2


17

Sametime Prerequisites


Sametime Prerequisites� To get the true picture of what you need:

� Sametime Entry 8.5.2� https://www-304.ibm.com/support/docview.wss?rs=477&uid=swg27019580

� Sametime Advanced 8.5.2� https://www-304.ibm.com/support/docview.wss?rs=477&uid=swg27020283

� Sametime for IBM i� https://www-304.ibm.com/support/docview.wss?rs=203&uid=swg21092193


18

Sametime Community Server� Two products:

� Instant messaging, free with Domino license

� 5723J23 *BASE on IBM i

� Web conferencing (a.k.a Classic Meeting Server)

� Purchasable product

� 5723J23 *BASE and Option 1 on IBM i

� Can only have ONE version installed per server / LPAR


Sametime Community Server� Steps for Upgrading Sametime Community Server

� Backup Sametime data

� Upgrade Domino server code

� End Domino server

� Install Sametime code

� Start Domino server


19

Quickr 8.5.1


Quickr Prerequisites


20

Quickr for Domino� Two versions of the product

� Entry

� Basic file management tasks such as uploading, downloading, and sharing files. Users can also sort and filter a list of files, as well as search for files.

� Standard

� Full team collaboration environment

� Can only have ONE version installed per server / LPAR


Quickr for Domino� Trial version of the product

� Only available on Windows

� Can purchase a single user license

� Servers are installed as Entry, need to change notes.ini to upgrade to Standard

� QRD_InstallType=2


21

Upgrading Quickr for Domino� Steps for upgrading Quickr

� Backup places and PlaceTypes

� Stop Domino server

� IBM i specific steps:

� Delete Quickr code via DLTLICPGM

� Upgrade Domino version

� Install Quickr code

� Start Quickr server


Upgrading Quickr for Domino� Next Steps for upgrading Quickr

� Unlock all places to prepare for upgrade

load qptool unlock -a

� Upgrade server

Load qptool upgrade -f -server

� Upgrade places and PlaceTypes

load qptool upgrade -f -a

� Unregister and re-register places with the Place Catalog

� If this is your first 8.x Quickr upgrade

Load qptool unregister -a -placecatalog

Load qptool register -a -placecatalog


22

Upgrading Quickr for Domino� Last Steps for upgrading Quickr

� Install connectors on client workstations

� Lock any previously locked places

load qptool lock -i qptool.lockedplaces.xml

� Update domcfg.nsf to point to new login form� If this is your first 8.x Quickr upgrade

� LotusQuickr/resources.nsf and the target form

is QuickPlaceLoginForm

� Consider upgrading ODS to 51 and enabling DAOS


LEI


23

LEI Prerequisites


LEI� Release of LEI has to match release of Domino

� Ex: LEI 8.5.3 on Domino 8.5.3

� Tips on upgrading LEI

� Remove LEI from the ServerTasks variable prior to upgrading the Domino server

� Upgrade Domino server

� Make sure this notes.ini variable is disabled

� debug_threadid=1

� Ready to upgrade LEI code level


24

Upgrading LEI

� Upgrade Domino server code first

� Upgrading LEI code

� Back up LEI administration, log, and vault databases

� End LEI

� Tell LEI quit

� Upgrade LEI

� Same installer upgrades and installs new

� Start LEI

� Start activities


Program Conversion

� IBM i specific

� Domino program conversion takes place when?

� During a restore

� STROBJCVN

� First touch

� How long does it take?

� Can be lengthy, depending on processor model!!

� Use ANZOBJCVN to predict conversion time

� See KB article 1294587 for details


25

Program Conversion� Only happens if:

� Installing 8.5.x on V5R4

� Installing 8.0.x on V6R1

� What gets converted?


Product Library to Convert

Domino & LEI QDOMINOxxx

Domino Document Manager QDOMDOC

Quickr or QuickPlace QQPLACE

Sametime QSAMETIME

IBM Integrated Domino Fax V4R5 QDOMFXD


26

Smart Upgrade� What you want…

� Automatically upgrade your user’s workstation

� Automatically upgrade

your user’s mail template

� To have it work like….

MAGIC!


Configuring Smart Upgrade1. Create a Desktop Policy (optional)

• Required to define a database for Smart Upgrade Tracking Reports

• Required for “Seamless Mail Upgrade” – in other words – to automatically update the mail template

2. Create a Smart Upgrade Kit Database

3. Create a Smart Upgrade Kit

4. Assign users to the Smart Upgrade Kit (optional)

5. Add an application link of the Smart Upgrade Kit database to the Server Configuration Document


27

Desktop Policy – Smart Upgrade Tab

� Deploy version is not required

� Specify a Smart Upgrade Tracking Reports Database here

Copyright Kim Greene Consulting, Inc. All rights reserved worldwide.53

Desktop Policy – Basics Tab� Seamless Mail Upgrade Settings


28

Create Smart Upgrade Database

� Use the smupgrade.ntf template

Copyright Kim Greene Consulting, Inc. All rights reserved worldwide.55

Smart Upgrade Kit: Basics Tab


29

Smart Upgrade Kit: Administration Tab� Use the “Allowed Users & Servers” field to limit upgrades to certain users when

testing Smart Upgrade

� Blank = All Users


Example Configuration Document� Do not perform this step until you are ready to deploy

smart upgrade

� Clients will begin to use the database immediately


30

What the client sees: 1




31





32

Smart Upgrade Tracking Reports� lndsutr.nsf database


Smart Upgrade Report – Part 1


33

Smart Upgrade Report – Part 2


Seamless Mail Upgrade

� When user is upgraded the following line is submitted to the console:

� Mail Convert: Started replacing design template '*' with 'StdR85Mail' in 'mail\utest1'

Easy


34

� Needed when users don’t have administrator rights to their PC

� Not supported on Windows 7 prior to 8.5.3

� Which means you need to get your clients to 8.5.3 and then you can use Smart Upgrade

� Requires that you create a new “kit” using the SUSetRunAs.exe wizard located in the executable directory of a Lotus Notes client

Smart Upgrade Run As


SUSetRunAs Wizard


35

SUSetRunAs Wizard


SUSetRunAs Wizard


36

SUSetRunAs Wizard


SUSetRunAs Wizard


37

SUSetRunAs Wizard


The SURunas.exe file can now

be attached to a Smart Upgrade

kit.

Troubleshooting Smart Upgrade� In testing you have changed the kit and now you want the

client to immediately retry the upgrade – How can this be done?

� End the client

� Remove SU related entries from the notes.ini� SU_IN_PROGRESS=0

� SU_NEXT_UPDATE=03/21/2011 08:20:39 AM� SU_FILE_CLEANUP=C:\Documents and

Settings\Administrator\Application Data\smkits� SUT_NEXT_UPDATE=03/21/2011 08:20:39 AM

� Restart the client


38

Debugging Smart Upgrade� Use DEBUG_SMART_UPGRADE=1 to determine why a client

is not getting prompted to upgrade

� SU: DoSessionMessage: SessMsg.MatchPatternSize :62

� SU: DoSessionMessage: ODSsizeof(SMART_UPDATE_MATCHPATTERN) :196

� SU: DoSessionMessage: User :CN=Upgrade Test1/O=lab

� SU: DoSessionMessage: FromVersion :Release 8.0.2|August 07, 2008

� SU: DoSessionMessage: PlatForm :Windows/32

� SU: DoSessionMessage: Localization :English|EN

� SU: DoSessionMessage: KitType :16

� SU: DoSessionMessage: Kit not available for user: CN=Upgrade Test1/O=lab running Release 8.0.2|August 07, 2008


Why may a kit not be available?� A mismatch of any of the following

- Source configuration- Source version

� Put an * (asterick) for all clients or make sure the version matches EXACTLY- Install Type- Operating System- Localization

� User not allowed based on the “Allowed users and servers” on the Administration tab of the kit

� File name of .exe attached is invalid

� Kit is not enabled

� User matches more than one kit document


39

Installing a client fixpack / CCH


Smart Upgrade Cannot…� The following is not supported with Smart Upgrade

- Backleveling

- Upgrading a Mac OS client from 7.x to 8.5

� See technote 1327065 for details

� Upgrades from 8.5.x to 8.5.3 are supported

- Switch client type

� Cannot switch from Single User Install to a Multi-user install

� Cannot go from Notes Client Only to All clients or vice versa


40

Single User to Multi-User Install� New with 8.5.3 is a single user to multi-user migration

assistant (MUMA) tool

� When to use?

- Clean single user Notes installation to multi-user installation within same release

- Simulated multi-user Notes installation (a Notes single user installation where each user's data directory is mapped to shared drives to simulate a multi user environment) to true multi-user installation within same release

� Detailshttps://www-304.ibm.com/support/docview.wss?uid=swg21459627


QuestionsThank you for attending.

Please fill out your session evaluations.


Date post:	14-Aug-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times