ISBG 2015

Tools Every Domino Admin Needs

Gabriella Davis - Technical DirectorThe Turtle Partnershipgabriella@turtlepartnership.com

Domino Admin Client Files Tab

Domino Admin Client Group Membership

Domino Admin Client ACLS

Domino Admin Client Console Filters

DDM Collections

❖ Create collections in events4.nsf

❖ Group servers together so you can review all activity by server role e.g.

❖ all mail servers

❖ all iNotes servers

❖ all application servers

Directory Performance

DDM Agent Performance

Security Stronger Certificates

Security Catalog.nsf

❖ Not every database is immediately visible but they are all there (just hidden with selection formulae)

❖ It’s a good place to start looking for multiple replica

❖ It’s a good place to find ACL issues

❖ Replicates around your domain and updates overnight

Security DDM Probes

Decommission Analysis

Cluster Analysis

QoS - Quality of Service❖ Monitor server health and performance

❖ Monitors application behavior, stability and hangs

❖ Restarts Domino if it thinks there are memory issues or an application is hung

❖ Shuts down Domino if a clean shutdown doesn’t happen and the server hangs

❖ Controlled via notes.ini settings and dcontroller.ini

❖ Requires Domino to be running under the Java Controller

❖ nserver -jc

QoS Configuration❖ Starting Domino under Java Controller should create a dcontroller.ini

file

❖ QOS_Enable=1

❖ In Notes.Ini

❖ QOS_ProbeInterval (defaults to 1 min)

❖ QOS_ProbeTimeout (defaults to 5 mins)

❖ QOS_ShutDown_Timeout

❖ QOS_Apps_Timeout

❖ QOS_Shutdown_Timeout

QOS - Potential Problems

❖ QOS doesn’t support passwords on server ids , the restart will pause at the password entry screen

❖ QOS timeouts being too low

❖ Don’t enable QOS on servers without transaction logging

Enhanced Fault Reporting❖ Fault Reporting Database -lndfr.nsf

❖ Expanded to include a by Disposition view

❖ all faults when analyzed have a disposition value that categorises as

❖ Problem

❖ Possible Problem (possibly actionable )

❖ Possible Problem (likely NOT actionable )

❖ Informational

❖ Unknown (investigate)

Possible Problem - Actionable❖ Out Of Memory: Represents a crash in which the Java virtual

machine (JVM) ran out of a memory resource such as heap space.

❖ Launched Notes multiple times: Indicates that the user quickly launched multiple instances of the Notes client

❖ Possible hang: Indicates that the Notes client was manually terminated while it appeared to be doing useful work.

❖ User Kill: Indicates that the user manually terminated the client while it appeared to be waiting for input or network timeout

Database Management Tools❖ DBMT Server Command

❖ runs copy-style compact operations

❖ purges deletion stubs

❖ expires soft deleted entries

❖ updates views

❖ reorganizes folders

❖ merges full-text indexes

❖ updates unread lists

❖ ensures that critical views are created for failover

❖ Replaces Updall

❖ Load updall - nodbmt tells updall to run but not perform the functions that DMBT already does

DBMT Parameters❖ -compactThreads

❖ -updallThreads

❖ -ftiThreads

❖ -timeLimit refers to compact timeout for DBMT

❖ -range starttime stoptime

❖ compactNdays (run Compact every x days)

❖ ftiNdays (run FT Index every x days)

❖ force d (day Sunday =1) fixup if compact fails for consecutive day

Domino Configuration Tuner

❖ Domino Configuration Tuner is an analysis tool based on a set of pre-configured best practice/worst practice rules

❖ The Rules are shipped by IBM with the Lotus installs and are updated via a public update site

❖ Makes recommendations on configuration changes to enhance performance and security and reduce TCO

How does it work?❖ Run and installed via the Domino Configuration Tuner database

❖ Updated by online template updates and rule updates

❖ DCT rules and results are held in a local database and will require a restart of the client for changes to take effect

❖ Scans

❖ Server documents

❖ notes.ini settings

❖ advanced database properties

❖ Intended to scan servers in a single domain

How does it work?

❖ Creates reports on each scanned server based on the rules you select

❖ Each report contains

❖ Issues

❖ recommendations for adjustments

❖ links to supporting documentation

Pre-requisites

❖ v8 Notes client (standard or basic) or administrator

❖ dct.nsf database and dct.ntf template

❖ servers 7.x or higher

Setup

❖ DCT.NSF

❖ StdDominoConfigTuner Template (dct.ntf)

❖ ID must have reader access to names.nsf

❖ ID must have ‘View Administrator’ rights

❖ Requires no server or domain changes

View Administrator Rights❖ Server Document

❖ Security Tab

❖ View Administrator is a subset of ‘Administrator’ rights

❖ Think of it as ‘Show’ not ‘Tell’ rights

❖ Sh users - YES

❖ tell http refresh - NO

DCT Preferences

❖ List of all rules

❖ Review rule , description and supporting documentation

❖ All rules are enabled by default for all scans

❖ Enable and Disable rules

DCT Updates

❖ Connects to the IBM site to download

❖ must have outbound connectivity

DCT Updates

❖ Click ‘check for updates’

❖ Connects to an external IBM site to identifies any template or rule updates

DCT Updates

❖ Accept license and updates download

❖ It’s not possible to selectively download

DCT Updates - Finished

❖ “Successful” screen will notify you to restart your client

❖ You may need to do 2 client restarts before DCT can be used

Running the tuner

❖ First select the servers in your current domain you want to run against

❖ The list of servers is retrieved from the domain of the home server identified in your location document

❖ Change locations to scan a different domain

Running the tuner❖ You can manually type in the full hierarchical names of

any other servers you want to scan as part of this analysis

❖ Separate multiple server names with commas, semi colons or new lines

❖ You can only scan servers you can reach so you need a connection document to any you list

❖ or the server needs to be available via your passthru server in your location

Understanding the Results

❖ Summary results

❖ Issues by criticality

Understanding the Results

❖ Summary results

❖ Servers that failed to scan

❖ reason why scan failed

Understanding the Results❖ Summary results

❖ Detailed list of rules evaluated

Understanding the Results

❖ View the current report

❖ Select ‘change’ to view a different report

Understanding the Results

❖ Filter results to make analysis easier

❖ by server

❖ by specific rules

❖ by severity

Understanding the results

❖ Categorised results of recommendations

❖ Sorted by criticality and then by server name

Understanding the results

❖ Each recommendation comes with an explanation so you can evaluate on a result by result basis if you want to make the change

Understanding the results

❖ Each recommendation is provided with a link to a best / worst practices supporting documentation

Working with Rules

❖ Disabling and enabling rules can be done through the ‘Preferences’

Working with Rules

❖ Selecting a rule shows the description and links to the best / worst practice documentation

Questions

How to contact me: Gabriella Davis

gabriella@turtlepartnership.com Twitter: gabturtle