BP112 Twelve Things Your Mother Never Told You About Installing IBM Lotus Connections

download BP112 Twelve Things Your Mother Never Told You About Installing IBM Lotus Connections

of 66

  • date post

    08-May-2015
  • Category

    Technology

  • view

    15.437
  • download

    1

Embed Size (px)

description

My main session from Lotusphere 2010, delivered with Rob Wunderlich."It's a classic case of the "bark is worse than the bite." Installing Lotus Connections - admittedly - is a complex process, with many pre-requisites to be met, environment-specific decisions to be taken and almost endless opportunities for customization and integration. It might appear daunting at first; but don't fret just yet. This session will make it a whole lot easier! We'll use our in-depth real-world experience of installing Lotus Connections at many organizations in the US and Europe to explore a dozen lesser-known details of the installation process that are key to successful deployment. We'll show tips and tricks, "cheat sheets," install checklists and share the stuff that isn't in the manual. Priceless resources! Stuff even Mom never told you!"

Transcript of BP112 Twelve Things Your Mother Never Told You About Installing IBM Lotus Connections

  • 1.SESSION BP112: 12 Things Your Mother Never Told You About Installing Lotus Connections Stuart McIntyre | Technical Director, Collaboration Matters Rob Wunderlich | Independent Consultant Monday, 18 January 2010

2. About this session Frankly, we think Lotus Connections has gotten something of a bad rap when it comes to difficulty to install. Installing Lotus Connections admittedly is a complex process, but this session will make it a whole lot easier! Well show tips and tricks, cheat sheets, install checklists and share the stuff that isnt in the manual. 2Monday, 18 January 2010 3. About Rob Wunderlich Notes/Domino consultant since early '90s. Certified developer, system admin and Lotus instructor (although probably lapsed in most by now) Held positions at several Detroit-area IBM/Lotus business partners prior to joining IBM itself in 2006. Went independent in 2009 (meaning, I'm available!), targeting social technology, Notes/Domino and Lotus Connections Infrequently updates www.dominounplugged.com Twitter: rwunder email: rob@dominounplugged.com3Monday, 18 January 2010 4. About Stuart McIntyre Technical Director of Collaboration Matters (UK-based Lotus business partner), a social software evangelist and Lotus Connections specialist. Has been working with Lotus software for 18 years, and focused on Lotus Connections since 2007 launch, presenter at conferences such as Lotusphere, UKLUG and Collaboration University. Authors the Connections Blog: lotusconnectionsblog.com (amongst others) Twitter: stuartmcintyre Email: stuart@collaborationmatters.com4Monday, 18 January 2010 5. Agenda Introductions, housekeeping, etc. The 12 Things Summary5Monday, 18 January 2010 6. Agenda Introductions, housekeeping, etc.Evaluations, please!6Monday, 18 January 2010 7. Agenda Introductions, housekeeping, etc. The 12 Things Summary7Monday, 18 January 2010 8. The 12 Things list In the spirit of full disclosure:In all honesty, my mother never mentioned Lotus Connections to me at all, much less anything about installing it.8Monday, 18 January 2010 9. #1) Its easier than you think! Some key points: Connections does have a lot of moving parts, but they go together relatively easily Very limited expertise in each of the framework products - WebSphere, DB2, TDI - is required to just install a basic LotusConnections 2.5 system There is a wizard-driven Pilot install option for test/demonstration environments, but it is very limited - better to stick to the full install option Dont be frightened by the scary multi-node clustered install scenarios on the Connections Wiki and in some Lotusphere presentations - they are not needed in 80-90% of environments9Monday, 18 January 2010 10. #1) Its easier than you think! It doesnt have to be like this!10Monday, 18 January 2010 11. #1) Its easier than you think! The installation process: Has gotten easier over the versions, 1 -> 2 -> 2.5, big improvements in Lotus Connections 2.5, particularly in clustered environments Is mostly wizard-driven Is clearly documented in the Infocenter, though the correct order is not always clear Your first installation: A standard Microsoft Windows 2003 32-bit environment is ideal for your first install experience - Connections 2.5 will install fine on a single 2-CPU 4GB system, though two systems are better Allow a significant period of uninterrupted time - at least 2 days for a full installation and configuration Gather all the pre-requisite information before starting - LDAP server/bind information, hostnames etc. Take it step by step, and take backups and/or snapshots at all major changes Document everything!11 Monday, 18 January 2010 12. #1) Its easier than you think! But... Do not try to build a production environment as your first Lotus Connections install, there are too many places where mistakes can (and will) be made Dont use the Pilot install package unless you really understand the limitations You need to read and understand the instructions very carefully - dont make assumptions! Be ready to learn a lot from the experience and to install a second time to correct from the lessons learnt!12 Monday, 18 January 2010 13. #2) Read the $!@#% instructions !! Obviously, this is good advice for virtually ANY software product, but for Lotus Connections, it's even more critical Infocenter can be difficult to follow Lots of moving parts, key to know what changes in one application affect others Suggest building own set of instructions* based on your own experience, specific environment and install methodology (Mindmaps are great for this) Read all the way through before starting step one (seriously, trust us on this!) *also commonly known as 'cheatsheets' and we'll share one with you later! 13Monday, 18 January 2010 14. #2a) Correct order becomes important Some install steps will simply not work unless pre-requisites and co-requisites have been completed (examples, securing Websphere, creating plugin configuration) KISS methodology is critical, would suggest building test environment first, then production14Monday, 18 January 2010 15. #2a) Correct order becomes important Some install steps will simply not work unless pre-requisites and co-requisites have been completed (examples, securing Websphere, creating plugin configuration) KISS* methodology is critical, would suggest building test environment first, then production *KISS = well known rock band of the 1980's15Monday, 18 January 2010 16. #2a) Correct order becomes important Some install steps will simply not work unless pre-requisites and co-requisites have been completed (examples, securing Websphere, creating plugin configuration) KISS* methodology is critical, would suggest building test environment first, then production *KISS = well known rock band of the 1980's*KISS = Keep It Simple Stupid16Monday, 18 January 2010 17. #2a) Correct order becomes important Some install steps will simply not work unless pre-requisites and co-requisites have been completed (examples, securing Websphere, creating plugin configuration) KISS methodology is critical, would suggest building test environment first, then production Even in setting up and then starting services, there IS an order of dependencies ...17Monday, 18 January 2010 18. #3) The Secret is in the Preparation Some key points: There are a lot of components required for the install - products, update installers, patches, fixes Many components are larger than 500MB in size, at least 2GB in total Preparation is particularly important if no direct access to servers - images and fixes can take a very long time to copy if waiting Check and double-check ports and firewalls before starting - they may cause many and varied issues during and after install Install process is very disk intensive - slow disks (e.g. in VMWare environment) can more than double install duration 18Monday, 18 January 2010 19. #3) The Secret is in the Preparation What comes in the box? (Oh, alright then, in the eAssembly!) Lotus Connections 2.5 InstallerTivoli Directory Integrator 6.1.1 Lotus Connections 2.5 Wizards Tivoli Directory Server 6.0 (Optional)WebSphere Application ServerDB2 9.5 Network Deployment 6.1(Optional)WebSphere Application Server Network Deployment Supplements 6.1 WebSphere Application EdgeComponents 6.1 (Optional)19Monday, 18 January 2010 20. #3) The Secret is in the Preparation What you REALLY need! WAS ND 6.1 PA/PW LC 2.5 Installer PA/PW TDI 6.1.1 PA/PW WAS ND Supplements 6.1 PA/PW LC 2.5 Wizards PA/PWTDI 6.1.1 FP6 FCWebSphere UpdateInstaller 7.0.0.5 TN LC 2.5 UpdateInstaller FCWAS 6.1.0.23 FCAll current LC2.5 Fixes FCOracle 10g MS SQL ServerDB2 9.5 FP3 or Enterprise 2005 Enterprise DB2 9.1 FP6 FC10.2.0.4 SP2Domino 7.0.2 MS Active Tivoli DirectoryNovell eDirectorySun Java Directory FC Domino 8.0.2 Directory 2003 Server 6.0 FP3 8.8Server 5.2, 6.0Domino 8.5.x SP2+FC = FixCentral http://ibm.com/support/fixcentral TN = UpdateInstaller TechNote http://www-01.ibm.com/support/ 20 PA/PW = Passport Advantage (Customers) or PartnerWorld (Partners) docview.wss?rs=180&uid=swg24020212 Monday, 18 January 2010 21. #3) The Secret is in the Preparation Supported Server Platforms: Check OS requirements carefully - WAS/DB2 etc. are supported on more platforms than Lotus ConnectionsWindows 2008 Server (64 Bit only)AIX5L 5.3 TL4Windows 2003 Server SP2 (32 Bit only)SUSE Linux Enterprise Server 10 RHEL AS/ES 4.7 (32-bit only) (32-bit only)21Monday, 18 January 2010 22. #3) The Secret is in the Preparation Lessons learnt: If you are going to use a trusted SSL certificate, get it before installation - save you much pain later! Check and double-check the detailed system requirements Make your SysAdmins understand how important these pre-reqs are! Do not let them take Windows system updates automatically! 22Monday, 18 January 2010 23. #4) Plan twice thrice, install once! A lot of planning and design decisions taken early on in the install process can return to haunt you later, so get them right first time - WebSphere is much less forgiving than Domino in this regard It tends to be easier to scale up and out than to drop components at a later date: start small and correct, then build... rather than creating a grandiose server architecture that has issues and have to scale down to fix Set up your naming conventions early on: nodes servers clusters web servers Make life easy if you need to move physical servers or domains later: Always use short names for servers/hostnames - e.g. lcnode01 not lcnode01.myorg.com Always use logical names not physical/virtual machine names, e.g. lcnode01 not lcvm1n23p86! Even on simple one/two server installs, add aliases to hosts file(s)...23Monday, 18 January 2010 24. #4) Plan twice thrice, install once! Think very carefully about the feature:server/cluster ratio 11 features : 11 WAS servers (JVMs) is usually too many wasted memory, hard to maintai