Social Conndections VI -- Debugging IBM Connections During Install And Operation

89
© 2014 IBM Corporation Martin Leyrer – IT-Specialist IBM Software Services for Collaboration 2014-06-17 Debugging IBM Connections during Install and Operation

description

With relational databases, LDAP servers, files shares and a lot of Java components, IBM Connections is a complex environment to install and operate. A diverse set of settings and tools is needed in case something does not work as expected. In this talk I will present you the debugging settings for Connections that will offer additional information quickly, in case something goes wrong. Also, there will be recommendations for tools your customer should provide you on the server so you can work out any issues efficiently.

Transcript of Social Conndections VI -- Debugging IBM Connections During Install And Operation

Page 1: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM Corporation

Martin Leyrer – IT-SpecialistIBM Software Services for Collaboration2014-06-17

Debugging IBM Connections during Install and Operation

Page 2: Social Conndections VI -- Debugging IBM Connections During Install And Operation
Page 3: Social Conndections VI -- Debugging IBM Connections During Install And Operation
Page 4: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration4/89

© 2012 IBM Corporation

Legal Disclaimer

● © IBM Corporation 2014. All Rights Reserved.

● The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

● References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

● Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

● All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

● IBM®, the IBM logo, Lotus®, Lotus Notes®, Notes®, Domino®, Quickr®, Sametime®, WebSphere®, UC2®, Connections, … are trademarks of International Business Machines Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

● Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

● Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

● UNIX is a registered trademark of The Open Group in the United States and other countries.

● Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

Page 5: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration5/89

© 2012 IBM Corporation

Navigation

● Plan Ahead– Tools– Software Planning– Deployment Planning

– “Security” Tools

● Version, Versions, Versions● Network & Infrastructure● Fileshares

● DB2● LDAP● Websphere Application Server● IBM HTTP Server● IBM Security Directory Integrator● How to Talk With IBM Support● Q & A

Page 6: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration6/89

© 2012 IBM Corporation

Plan Ahead – Tools – Editors

Page 7: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration7/89

© 2012 IBM Corporation

Plan Ahead – Tools – Log Viewers/Linux

Page 8: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration8/89

© 2012 IBM Corporation

Plan Ahead – Tools – Log Viewers/Windows

Get-Content SystemOut.log -wait | where { $_ -match “ E ” }

Page 9: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration9/89

© 2012 IBM Corporation

Plan Ahead – Browsers

Page 10: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration10/89

© 2012 IBM Corporation

Plan Ahead – Tools – Network

● ssh

● ping

● dig or nslookup

● telnet

– To install Telnet Client on Windows Server 2008 or later:pkgmgr /iu:"TelnetClient"

Page 11: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration11/89

© 2012 IBM Corporation

Plan Ahead – SW Planning – System Requirements

htt

ps:

//ib

m.b

iz/B

dR

WH

g

Page 12: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration12/89

© 2012 IBM Corporation

Plan Ahead – SW Planning – Updates & Hotfixes

htt

p:/

/ ww

w. ib

m.c

om

/su

pp

or t

/fix

cen

tra

l/

Page 13: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration13/89

© 2012 IBM Corporation

BP: Recheck System Requirements

● Verify BEFORE EVERY install

● Do not rely on the Installation Manager

● Do not forget DB2

● Do not forget TDI

● Check for updates via Cummulative Refreshs (CRs)

Page 14: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration14/89

© 2012 IBM Corporation

BP: Install Only Supported WAS Fixpacks

htt

p:/

/ww

w. ib

m.c

om

/su

pp

ort

/do

cvie

w.w

s s?

uid

=s w

g2

70

04

98

0

Page 15: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration15/89

© 2012 IBM Corporation

Plan Ahead – Deployment Planning

https://ibm.biz/Bdxhei

Page 16: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration16/89

© 2012 IBM Corporation

BP: Passwords● Avoid “special” characters

● Especially: @ ! < > { }

● No national language characters

● Stick to ASCII and 0-9 if possible

● No longer than 128 characters

● Watch out for differences in password rules between OS, LDAP, WAS and DB2

– WAS: http://www.ibm.com/support/knowledgecenter/SSHRKX_8.0.0/plan/sec_chars.dita

– DB2: https://ibm.biz/BdR7Jg

Page 17: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration17/89

© 2012 IBM Corporation

BP: Filehandling● Make sure you have “enough”

disk space available to install all components

● Make sure %TEMP% has at least 4 GB diskspace available

● Always transmit install files in tar/zip form

● Prepare installfiles in a reproducible and understandable form

Page 18: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration18/89

© 2012 IBM Corporation

BP: “Security”● Disable Virus Scanners, … on

the server during install

● Disable Firewalls between Servers during install

● Disable tools that “delete unknown directories in the root level of a drive” and similar

Page 19: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration19/89

© 2012 IBM Corporation

Navigation

● Plan Ahead● Version, Versions, Versions

– Connections– Websphere

– DB2, SDI (TDI)– Databases

● Network & Infrastructure● Fileshares● DB2

● LDAP● Websphere Application Server● IBM HTTP Server● IBM Security Directory Integrator● How to Talk With IBM Support● Q & A

Page 20: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration20/89

© 2012 IBM Corporation

Versions - Connections● F:\ibm\WebSphere\AppServer\bin\setupCmdLine.bat● cd F:\IBM\Connections\updateInstaller● updateSilent.bat -fix -installDir F:\IBM\ConnectionsIBM ConnectionsUpdate Installer Version 4.5.0.0, Dated 10/20/13Listing installed fixes: Fix name: LO77120-IC4500-CR03-Activities Fix name: LO77120-IC4500-CR03-Blogs Fix name: LO77120-IC4500-CR03-Bookmarks ... Fix name: LO77975 Fix name: LO78429-IC4500-CR04-Activities Fix name: LO78429-IC4500-CR04-Blogs Fix name: LO78429-IC4500-CR04-Bookmarks ...

http

s://

ibm

. biz

/Bd

R7

uy

Page 21: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration21/89

© 2012 IBM Corporation

Versions – Websphere Application Server

● cd F:\IBM\WebSphere\AppServer\bin● versionInfo.bat -long

Installed ProductName IBM WebSphere Application Server Network DeploymentVersion 8.0.0.6Installed FixpackVersion 8.0.0.6Installed IFixIfix ID 8.0.0.6-WS-WAS-IFPM85834Ifix ID 8.0.0.6-WS-WAS-IFPM94437Ifix ID 8.0.0.6-WS-WASProd-IFPM91417 Included Apars PM91417 PM94981 ht

tps:

//ib

m. b

iz/B

dR

7u

t

Page 22: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration22/89

© 2012 IBM Corporation

Versions – DB2● Log in as “db2admin”● Start “Command Window”

● db2levelDB21085I This instance or install (instance name, where applicable: "DB2") uses "64" bits and DB2 code release "SQL10012" with level identifier "0203010E".Informational tokens are "DB2 v10.1.200.238", "s121127", "IP23389", and Fix Pack "2".Product is installed at "F:\IBM\SQLLIB" with DB2 Copy Name "DB2COPY1".

http

s://

ibm

. biz

/Bd

R7

Lp

Page 23: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration23/89

© 2012 IBM Corporation

Versions – IBM Security Directory Integrator

● cd F:\IBM\TDI\bin

● applyUpdates.bat -queryreg

http

s://

ibm

. biz

/Bd

R7

L3

Information from .registry file in:F:\IBM\TDI

Edition: IdentityLevel: 7.1.0.7License: NoneFixes Applied=-=-=-=-=-=-=TDI-7.1-FP0007(7.1.0.0)Components Installed=-=-=-=-=-=-=-=-=-=BASE -TDI-7.1-FP0007SERVER -TDI-7.1-FP0007CE -TDI-7.1-FP0007

Page 24: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration24/89

© 2012 IBM Corporation

Versions – Databases

Mark Myers: Connections Db Schema Versions

Connections App: ProfilesBD: PEOPLEDBTable: SNPROF_SCHEMAConnections v4.0 BASE: 33Connections v4.0 CR1: 33Connections v4.0 CR2: 33Connections v4.0 CR3: 33Connections v4.0 CR4: 33Connections v4.5 BASE: 36...Connections v4.5 CR3: 36Connections v4.5 CR4: 36

http

s :/ /

ibm

. biz

/Bd

R7

9s

Page 25: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration25/89

© 2012 IBM Corporation

Navigation● Plan Ahead● Version, Versions, Versions● Network & Infrastructure

– Hostnames– BP: DNS– BP: Port Check– BP: Load Balancers

● Fileshares● DB2

● LDAP● IBM Installation Manager● Websphere Application Server● IBM HTTP Server● IBM Security Directory Integrator● On the Client● How to Talk With IBM Support● Q & A● Links and Backup-Slides

Page 26: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration26/89

© 2012 IBM Corporation

Network - Hostnames● Define all hostnames up front

– Only fully quallified hostnames (FQHN, eg. connections.example.com)

– No “flat” names or WINS name resolution

● Install with names for each service, even when on same machine

– Especially DB2, LDAP and Fileserver

● Verify, that all hostnames resolve

– on all servers

– on all test clients

– nslookup, dig and ping are your friend

Page 27: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration27/89

© 2012 IBM Corporation

Network – BP DNS

If the DNS is not working,if you can't resolve hostnames properly,

STOP!

Page 28: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration28/89

© 2012 IBM Corporation

Network – BP Port Check

● Of course, it is never the network, but …

● telnet is your friend

● Test connectivity to LDAP, SMTP, DB2, IHS, …

● Available everywhere

telnet mail.example.com 25

220 mail.example.com ESMTP Service (IBM Domino Release 9.0.1 HF402) ready at Thu, 12 Jun 2014 12:36:41 -0500

telnet dominoldap.example.com 389

Page 29: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration29/89

© 2012 IBM Corporation

Network – BP Load Balancers

● Be wary of Round Robin DNS

● Install and test Connections first

● Introduce Load Balancers, … once Connections works fine

● Connections Cluster– Debug with only one cluster partner started– Reproduce issues seperatly on both cluster partners– Fix on one cluster partner, sync, test other partner

Page 30: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration30/89

© 2012 IBM Corporation

Navigation

● Plan Ahead● Version, Versions, Versions● Network & Infrastructure● Fileshares

– BP: Shared content store

– BP: Username & Password

● DB2● LDAP

● Websphere Application Server● IBM HTTP Server● IBM Security Directory Integrator● On the Client● How to Talk With IBM Support● Q & A● Links and Backup-Slides

Page 31: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration31/89

© 2012 IBM Corporation

Network – BP Shared Content Store

● Always reference the “Shared Content Store” via Universal Naming Convention (UNC) paths

● Do not forget to run WAS as the Domain “fileshare-user”

● Always use a dedicated hostname for the “Shared Content Store”--share– even if on the same machine– a CNAME is sufficient– helps with a later migration/separation of servers

Page 32: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration32/89

© 2012 IBM Corporation

Fileshare – Know Your Credentials

● Dedicated Domain User aka. “fileshare-user”

● Password not allowed to expire!

● Require username and password before installing

● Test in the GUI by logging in as the “fileshare-user” and accessing the Fileshare

● Test via net use

net use X: \\ic-share01.example.com\ic-share passw0rd /USER:fsuser /PERSISTENT:NO

The command completed successfully.

Page 33: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration33/89

© 2012 IBM Corporation

Navigation● Plan Ahead● Version, Versions, Versions● Network & Infrastructure● Fileshares● DB2

– BP: Users & Connectivity– BP: Install & Updates– BP: Useful DB2 Commands– BP: IBM Data Studio– BP: Backup & Restore

● LDAP● Websphere Application Server● IBM HTTP Server● IBM Security Directory Integrator● On the Client● How to Talk With IBM Support● Q & A● Links and Backup-Slides

Page 34: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration34/89

© 2012 IBM Corporation

DB2 – BP Users

● You need at least “db2admin” and “lcuser”

● Password not allowed to expire

● Character restrictions

● Require usernames and passwords before installing

● Always use a dedicated hostname, even when installing on one host

Page 35: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration35/89

© 2012 IBM Corporation

DB2 – BP Connectivity

● Restart Connections if DB2 was down

● Test via IBM Data Studio● Test via db2 command line● Test via Telnettelnet db2.example.com 50000

● Test via Websphere ICS

Page 36: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration36/89

© 2012 IBM Corporation

DB2 – Fixpacks

htt

ps:

//ib

m.b

iz/B

dR

WH

J

Page 37: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration37/89

© 2012 IBM Corporation

DB2 BP: Connections Scripts

● ALWAYS run the DB2 database creation scripts or Wizards as db2admin and not as Administrator

Page 38: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration38/89

© 2012 IBM Corporation

DB2 – Useful DB2 Commands● List databases

db2 LIST DATABASE DIRECTORY

● Connect to databasedb2 connect to PEOPLEDB user db2admin using passw0rd

● List tables of a databasedb2 list tables for all

Page 39: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration39/89

© 2012 IBM Corporation

DB2 – IBM Data Studio

● IBM Data Studio Client “replaces” DB2 Control Center● Eclipse based● Installs via Installation Manager● Make sure you download the full product images

http

s://

ibm

. biz

/Bd

R7

6w

Page 40: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration40/89

© 2012 IBM Corporation

DB2 Backup (and Restore)

● Valdemar Lemche: DB2 backup scripts...DB2 BACKUP DATABASE HOMEPAGE TO "D:\Backup\DB2" WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT PROMPTING...

db2 restore database HOMEPAGE from "D:\Backup\DB2" REPLACE EXISTING WITHOUT ROLLING FORWARD

htt

ps:

//ib

m.b

iz/B

dR

WM

T

Page 41: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration41/89

© 2012 IBM Corporation

Navigation● Plan Ahead● Version, Versions, Versions● Network & Infrastructure● Fileshares● DB2● LDAP

– Prerequisites

– LDAP Browser– BP: Do's And Don't's

– BP: Webseal

● Websphere Application Server● IBM HTTP Server● IBM Security Directory Integrator● On the Client● How to Talk With IBM Support● Q & A● Links and Backup-Slides

Page 42: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration42/89

© 2012 IBM Corporation

LDAP - Prerequisites

● You need a “bind” user and a password, if no anonymous access

● Password not allowed to expire

● Know your BASE DN

● Know your Search filters

● Know your login fields

● Require these infos before installing

● Test connectivity from every server

telnet dominoldap.example.com 389

Page 43: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration43/89

© 2012 IBM Corporation

LDAP - Browser

● Apache Directory Studio

● Softerra LDAP Browser

● LDAP Browser in ISC

● LDAP Browser inside TDI

● Use Wireshark to read LDAP

● (command line ldap)

Page 44: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration44/89

© 2012 IBM Corporation

LDAP - Disabling global security in WAS

WSAS_inst_root/profiles/node_profile/config/cells/cellname/security.xml

WSAS_inst_root/profiles/dmgr_profile/config/cells/cellname/security.xml

● Open each security.xml file and search for the very first occurrence of enabled="true" inside the <security:> tag

● Change enabled="true" to enabled="false", then save the file

● Restart the Deployment Manager, the nodegent and the Application Servers, in that order.

● If are receiving security errors when trying to stop the WebSphere processes, then you will need to manually stop the Java processes.

htt

ps:

//ib

m.b

iz/B

dR

7U

5

Page 45: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration45/89

© 2012 IBM Corporation

LDAP – Domino And Complex Filters

● CCM and Cognos integration fails to look up users in environments using Domino LDAP with complex LDAP search filters

● Contact Domino Support to obtain a Hotfix for SPR CAHT959LQG for your specific Domino version

http

s://

ibm

. biz

/Bd

R7

UT

Page 46: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration46/89

© 2012 IBM Corporation

LDAP - Mismatch of realms

● com.ibm.websphere.security.auth.WSLoginFailedException: The user is from a foreign realm, websealldap.example.com:389, and this foreign realm is not trusted. Current realm is defaultWIMFileBasedRealm

● Change the Realm Name from “defaultWIMFileBasedRealm” to “websealldap.example.com:389”

Page 47: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration47/89

© 2012 IBM Corporation

Navigation● Plan Ahead● Version, Versions, Versions● Network & Infrastructure● Fileshares● DB2● LDAP

● Websphere Application Server– BP: Location, Location, Location– BP: Debugging/Tracing– BP: Backup config– BP: Houskeeping

● IBM HTTP Server● IBM Security Directory Integrator● On the Client● How to Talk With IBM Support● Q & A

Page 48: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration48/89

© 2012 IBM Corporation

WAS – Location, Location

● app_server_root – WAS installation directory– eg. F:\IBM\WebSphere\AppServer

● profile_root – WAS profile/ Deployment Manager profile directory– eg. F:\IBM\WebSphere\AppServer\profiles\profile_name

● log_root – path under which to store log files for your WAS profile– eg. F:\IBM\WebSphere\AppServer\profiles\profile_name\server_name

● connections_root – IBM Connections installation directory– eg. F:\IBM\Connections

http

s://

ibm

. biz

/Bd

RW

XU

Page 49: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration49/89

© 2012 IBM Corporation

WAS – Location, Location, Location

● SystemOut.log

● SystemErr.log

● trace.log

● StartServer.log

● stopServer.log

● ConnectionsCluster_server.pid

Page 50: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration50/89

© 2012 IBM Corporation

WAS – Trace And Logging Strings

● com.ibm.ejs.ras.*=all - enables tracing for all loggers with names starting with "com.ibm.ejs.ras.". If there is a logger named "com.ibm.ejs.ras" it will not have trace enabled.

● com.ibm.ejs.ras*=all - enables tracing for all loggers with names starting with "com.ibm.ejs.ras", such as com.ibm.ejs.ras, com.ibm.ejs.raslogger, com.ibm.ejs.ras.ManagerAdmin

● GrammarCOMPONENT_TRACE_STRING=COMPONENT_NAME=LEVEL

LEVEL = all | (finest | debug) | (finer | entryExit) | (fine | event )

| detail | config | info | audit | warning | (severe | error) | fatal | off

htt

ps:

//ib

m.b

iz/B

dR

WX

W

Page 51: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration51/89

© 2012 IBM Corporation

WAS – Tracing Levels and Targets

htt

ps:

//ib

m.b

iz/B

dR

WX

W

Trace option Output file

all trace.log

finest or debug trace.log

finer or entryExit trace.log

fine or event trace.log

detail SystemOut.log

config trace.log and SystemOut.log

info trace.log and SystemOut.log

audit trace.log and SystemOut.log

warning trace.log and SystemOut.log

severe or error trace.log and SystemOut.log

fatal trace.log and SystemOut.log

off trace.log and SystemOut.log

Page 52: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration52/89

© 2012 IBM Corporation

WAS – Debugging Connections

● Debugging/Trace strings are provided for all Connections Components● Part of the “Must Gather” aka. “Collect Data” Technotes● Consist of lines like:

– Component Trace:● *=info: com.ibm.lotus.connections.search.index.sand.*=all:

com.ibm.lotus.connections.search.admin.index.impl.*=all: com.ibm.lotus.connections.search.*=all

– Search Only:● *=info:com.ibm.lotus.connections.dashboard.search.parser.utils.*=finest:

com.ibm.lotus.connections.dashboard.search.parser.SeedlistIterator=finest: com.ibm.lotus.connections.dashboard.search.index.impl.*=finest

Page 53: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration53/89

© 2012 IBM Corporation

WAS – Collecting Data for Connections 4.5

● Profiles: https://ibm.biz/BdRWHF● Search: https://ibm.biz/BdRWHE● Files: https://ibm.biz/BdRWHX● Blogs: https://ibm.biz/BdRWHH● Activities: https://ibm.biz/BdRWH4● Forums: https://ibm.biz/BdRWHj● Wikis: https://ibm.biz/BdRWHZ● News: https://ibm.biz/BdRWH2● Waltz,Sonata: https://ibm.biz/BdRW8h

● Communities: https://ibm.biz/BdRWHs

● Bookmarks: https://ibm.biz/BdRWHi

● Homepage: https://ibm.biz/BdRWHr

● Cognos/Metrics: https://ibm.biz/BdRWHz

● CCM/Filenet: https://ibm.biz/BdRWHY

Page 54: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration54/89

© 2012 IBM Corporation

WAS – How To Enable Debug/Trace● Log in to the IBM WebSphere

Application Server (WAS) administration console using an administrator ID

● Go to Troubleshooting → Logs and Trace → Logging and Tracing → Server 1 (or the server the Connections Application is installed on) → Diagnostic Trace Server →Change Log Detail Levels

Page 55: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration55/89

© 2012 IBM Corporation

WAS – Backup Configuration

● Always backup before making configuration changes● From the deployment manager bin directory run the backupconfig(.sh)

– Backupconfig c:\backups\gdbackup.zip –nostop● The backup will be a zip file,● The –nostop command prevents backupconfig from stopping the deployment manager

before running

– Restoreconfig c:\backups\gdbackup.zip● Restore once you have stopped the server

● See “Connect 2014 BP304: What We Wish We Had Known: Becoming an IBM Connections Administrator” by Gabriella Davis and Paul Mooney for Details h

ttp

s://

ibm

.biz

/Bd

RW

Hq

Page 56: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration56/89

© 2012 IBM Corporation

WAS – BP: If Nothing Syncs ...

syncnode.bat is your friend in need

syncNode <deploymgr host> <deploymgr port> [options]

syncNode ssc.example.com 8879 -username wasadmin -password pass0rd

htt

ps:

//ib

m.b

iz/B

dR

WH

y

Page 57: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration57/89

© 2012 IBM Corporation

WAS – Ports Of Call

● All ports of all servers can be looked up in the ISC

● Go to Servers → Server Types → Websphere Application Servers → Select the server to check → Communications → Ports

● Deployment manager ports can be found in the ISC at System administration → Deployment manager → Ports

Page 58: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration58/89

© 2012 IBM Corporation

WAS – BP: Modify Configuration

● NEVER manually edit an XML configuration file, always use wsadmin which verifies the XML structure as it’s checked back in

● wsadmin –lang jython –username wasadmin –password passw0rd

● execfile(“connectionsConfig.py”)

● Checkout:LCConfigService.checkOutConfig(“F:/IBM/TMP”,AdminControl.getCell())

● Checkin (and validation) after edit:LCConfigService.checkInConfig()

htt

ps:

//ib

m.b

iz/B

dR

WH

S

Page 59: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration59/89

© 2012 IBM Corporation

WAS – Best Practices

● Install “plain” and get everything to work, then active SPNEGO, …

● Sometimes, you have to do things twice.– As demonstrated by @socialshazza in https://ibm.biz/BdRWHv

● “If in doubt at any point that something isn't working. Restart EVERYTHING. Websphere does like a good restart.”– Gab Davis in https://ibm.biz/BdRWHm

Page 60: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration60/89

© 2012 IBM Corporation

Navigation

● Plan Ahead● Version, Versions, Versions● Network & Infrastructure● Fileshares● DB2● LDAP● Websphere Application Server

● IBM HTTP Server– BP: Rewrite Logging– BP: Rotating Logs– BP: plugin-cfg.xml

– BP: TLS certificates

● IBM Security Directory Integrator● On the Client● How to Talk With IBM Support● Q & A

Page 61: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration61/89

© 2012 IBM Corporation

IHS – Rewrite Logging

● Needed for Reverse Proxy setups but can be tricky● Turn on Rewrite logging in the httpd.conf:

– RewriteLogLevel 3– RewriteLog "/usr/local/var/apache/logs/rewrite.log"

[example.com/sid#80077333][rid#800b7a33/initial] (2) init rewrite engine with requested uri /press/wp-comments-post.php[example.com/sid#80077333][rid#800b7a33/initial] (2) rewrite /press/wp-comments-post.php -> http://64.246.32.000/[example.com/sid#80077333][rid#800b7a33/initial] (2) explicitly forcing redirect with http://64.246.32.000/[example.com/sid#80077333][rid#800b7a33/initial] (1) escaping http://64.246.32.000/ for redirect[example.com/sid#80077333][rid#800b7a33/initial] (1) redirect to http://64.246.32.000/ [REDIRECT/301] h

ttp

s://

ibm

.biz

/Bd

RW

HK

Page 62: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration62/89

© 2012 IBM Corporation

IHS – Rotating Logs

● rotatelogs works in conjunction with Apache's piped logfile feature

● rotatelogs is part of IHS

● Supports rotation based on a time interval or maximum size of the log.

● daily rotating logs via http.conf:

– CustomLog "|/opt/ibm/HTTPServer/bin/rotatelogs /var/log/ihs/access_log.%Y.%m.%d 86400" common

– ErrorLog "|/opt/ibm/HTTPServer/bin/rotatelogs /var/log/ihs/error_log.%Y.%m.%d 86400"

Page 63: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration63/89

© 2012 IBM Corporation

IHS – Plugin Configuration

● Make sure your plugin-cfg.xmlis deployed to the “correct” directory, used by IHS

Page 64: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration64/89

© 2012 IBM Corporation

IHS – Certificates

If you are using TLS certificates, create a calender entry at least one week before the

certificate expires,to remind you to renew it.

Page 65: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration65/89

© 2012 IBM Corporation

Navigation

● Plan Ahead● Version, Versions, Versions● Network & Infrastructure● Fileshares● DB2● LDAP● Websphere Application Server

● IBM HTTP Server● IBM Security Directory Integrator

– Log Location– Dry Run

– Keep Temp Files– BP: Lock file

● On the Client● How to Talk With IBM Support● Q & A

Page 66: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration66/89

© 2012 IBM Corporation

TDI – Log File Location

● Depends on the location of your TDISOL directory

● eg.: F:\IBM\Wizards\TDIPopulation\win\TDI\logs

Page 67: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration67/89

© 2012 IBM Corporation

TDI – Trace Strings

● TDISOL\profiles_tdi.properties– source_ldap_debug=true– tds_changelog_debug=true– sync_updates_clean_temp_files= false

● \TDISOL\win\etc\log4j.properties directory:– look for

● log4j.rootCategory=INFO, Default

– change it to ● log4j.rootCategory=DEBUG, Default

Page 68: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration68/89

© 2012 IBM Corporation

TDI – Helpful Settings

● TDISOL\profiles_tdi.properties– sync_updates_show_summary_only=true

“dry run”, only show changes, do not execute them

– sync_updates_clean_temp_files=falsekeep working files, useful for debugging

Page 69: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration69/89

© 2012 IBM Corporation

TDI – BP: .lock File

● Gets created by sync_all_dns.bat● Prevents starts while other sync scripts are still running● Causes “Profiles do not get updated” calls

– Backup shuts down server, scheduled sync_all_dns.bat does not finish– sync_all_dns.lck prevents script from running from then on

● Fix– Schedule clearLock.bat accordingly (ugly hack)– Monitor for existence of sync_all_dns.lck and fix cause

Page 70: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration70/89

© 2012 IBM Corporation

TDI - Fixes

http

s://

ibm

. biz

/Bd

R7

L5

Page 71: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration71/89

© 2012 IBM Corporation

Navigation

● Plan Ahead● Version, Versions, Versions● Network & Infrastructure● Fileshares● DB2● LDAP

● Websphere Application Server● IBM HTTP Server● IBM Security Directory Integrator● How to Talk With IBM Support

– Language

– ESR, ECUREP– BP for opening a PMR

● Q & A

Page 72: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration72/89

© 2012 IBM Corporation

IBM Support – General Information

● Whenever using IBM software, a customer should buy „Subscription & Support“ aka „Maintenance“ (usually on a yearly basis)

● S&S allows you to receive and use software updates and fixes

● S&S allows you to contact IBM support (no limit on the contacts) for

– Reporting software defects, asking for a workaround or fix

– Reporting enhancement requests

– Usage Support

● No extra (per call) costs for contacting support

Page 73: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration73/89

© 2012 IBM Corporation

IBM Support – What is a PMR?

● IBM tracks support calls in PMRs

● A PMR is basically a help desk ticket number

● You can report only a single problem per PMR because a PMR is always assigned to a single team

● With Connections, Support finds the right team for you

Page 74: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration74/89

© 2012 IBM Corporation

IBM Support – Language

● Write PMR description in English– Saves on translation via 1st Level Support, faster roundtrips

● Supply English logs, if possible● Change Install/UI/Log language to English:

– IBM Installation Manager: https://ibm.biz/BdRWHG– DB2: https://ibm.biz/BdRWHn– TDI: https://ibm.biz/BdRWHe /HT @m0urs– WAS: https://ibm.biz/BdRWHp

Page 75: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration75/89

© 2012 IBM Corporation

IBM Support – How To Open A PMR● By phone

– Not recommended!– mistyped email address or misunderstood phone number– PMR may exist but IBM support can't contact you

● On the Web– http://www.ibm.com/software/support– Select Software product– Give a description of the problem– Select a Severity of the problem

● Sev 1 for highest prio to Sev 3 for minor problem with no urgency

Page 76: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration76/89

© 2012 IBM Corporation

IBM Support – Data Upload Via ECUREP

http://www-05.ibm.com/de/support/ecurep/send.html

Page 77: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration77/89

© 2012 IBM Corporation

IBM Support – BP PMR Handling

● If you receive an email from support, make sure to reply to the ticket system as well– [email protected] for ICS products– A PMR has a status, if you don't reply this way, the PMR will stay in status

„waiting for customer feedback“ and will not appear on a todo list and will not be catched by superisors if your analyst is out sick

● If you need assistance outside business hours, update the PMR AND give IBM a phone call asking for 7x24 assistance

Page 78: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration78/89

© 2012 IBM Corporation

Honorary Mention

Page 79: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration79/89

© 2012 IBM Corporation

Q & A

Martin LeyrerIBM Collaboration Solutions IT-Specialist with IBM Austria

IBM e-mail: [email protected]

E-mail: [email protected]

Twitter: http://www.twitter.com/leyrer

Facebook: https://www.facebook.com/leyrer

Blog: http://www.leyon.at

LinkedIn: http://at.linkedin.com/in/leyrer

Martin LeyrerICS IT-Specialist

Mail: [email protected]: +43 664 618 6826

Martin LeyrerICS IT-Specialist

Mail: [email protected]: +43 664 618 6826

Page 80: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration80/89

© 2012 IBM Corporation

Links

Page 81: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration81/89

© 2012 IBM Corporation

IBM Support – Link Collection● IBM Support Handbook

http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html

● Accelerated Value Programhttp://www-01.ibm.com/software/support/acceleratedvalue/

● IBM Lotus Software Security Bulletinshttp://www.ibm.com/developerworks/lotus/security/

● IBM Support: Fix Centralhttp://www-933.ibm.com/support/fixcentral/

● ECUREP data uploadhttp://www-05.ibm.com/de/support/ecurep/send.html

Page 82: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration82/89

© 2012 IBM Corporation

Picture references● Lemur catta running

http://commons.wikimedia.org/wiki/File:Lemur_catta_-_tail_length_01.jpg● Alien head

http://commons.wikimedia.org/wiki/File:Alien_head.jpg#file● Tea Seave

http://commons.wikimedia.org/wiki/File:Tea_Sieve.jpg● Search User Icon

http://www.iconhot.com/icon/bunch-cool-bluish-icons/search-user-2.html

Page 83: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration83/89

© 2012 IBM Corporation

Links

● Notepad++ https://ibm.biz/BdRWSd● gVim https://ibm.biz/BdRWSx● Baretail https://ibm.biz/BdRWSF● Tail for Win32 (command line) https://ibm.biz/BdRWSH● TailMe https://ibm.biz/BdRWS4● tail.exe @ Windows Server 2003 Resource Kit Tools

https://ibm.biz/BdRWSj

Page 84: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration84/89

© 2012 IBM Corporation

Backup Slides

Page 85: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration85/89

© 2012 IBM Corporation

Navigation● Plan Ahead● Version, Versions, Versions● Network & Infrastructure● Fileshares● DB2● LDAP● IBM Installation Manager

– BP: Location, Location, Location– BP: Settings

● Websphere Application Server● IBM HTTP Server● IBM Security Directory Integrator● On the Client● How to Talk With IBM Support● Q & A● Links and Backup-Slides

Page 86: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration86/89

© 2012 IBM Corporation

Installation Manager – Location, Location, Location

● Installation logs– Windows Server 2008 (root)

● C:\ProgramData\IBM\Installation Manager\logs

– Windows Server 2008 (non-root)● C:\Users\<user>\AppData\Roaming

\IBM\Installation Manager\logs

– Linux & Unix (root)● /var/ibm/InstallationManager/logs

– Linux & Unix (non-root)● /<user>/var/ibm/InstallationManager

● AgentDataLocation– data that is associated with an

application– includes the state and history of

operations

– Paths as listed to the left without the “logs” ;)

ht t

ps:

//i b

m. b

i z/ B

dR

WX

u

Page 87: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration87/89

© 2012 IBM Corporation

Installation Manager - Settings

● Disable Passport Advantage– File → Preferences– Passport Advantage– Uncheck option

● Keep installed packages around

Page 88: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© 2014 IBM [email protected], IBM Software Services for Collaboration88/89

© 2012 IBM Corporation

WAS - Location● If in doubt, check the WAS Environment variables for clues

Page 89: Social Conndections VI -- Debugging IBM Connections During Install And Operation

© IBM Corporation , IBM Software Services for Collaboration

© 2012 IBM Corporation