Sie sind auf Seite 1von 289

SHOW202 Enterprise 2.0 Hero - a Beginner's Guide to Installing IBM Lotus Connections 3.

0
2011 IBM Corporation

This session
We will install from scratch a complete IBM Lotus Connections infrastructure. No smoke, no mirrors. You'll go away with all the materials needed to install Lotus Connections 3.0 from scratch, and become Enterprise 2.0 heroes! The Lotus Connections install process keeps improving with each release, introducing new wizards, reducing prerequisite steps, making the process more robust and Lotus Connections 3.0 goes a step further by using the new Installation Manager technology. But there are still a lot of moving parts. With over thirty successful Lotus Connections installations completed between us, we'll take attendees through the installation process step-by-step, from installing and patching IBM WebSphere and IBM DB2, connecting to LDAP, through installing Lotus Connections and onto securing the service, all in 90 short minutes!

2011 IBM Corporation

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

About Rob Wunderlich


IBM Lotus Notes/IBM LotusDomino 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.com

2011 IBM Corporation

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 its 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.com

2011 IBM Corporation

So what are we going to cover today?


How to install Lotus Connections 3.0 in a non-clustered Production environment Why default isnt necessarily best practice! EVERYTHING WE SHOW YOU IS ON THE HANDOUTS STEP BY STEP, SCREEN BY SCREEN

2011 IBM Corporation

Some Terminology...
Term WAS IHS DB2 LDAP TDI ISC Meaning IBM WebSphere Application Server (Network Deployment Edition) IBM HTTP Server (or IHS), based on ApacheTM IBM DB2 Enterprise Server Edition Lightweight Directory Access Protocol - the service used for authentication and population of data into Lotus Connections IBM Tivoli Directory Integrator Integrated Solutions Console (WAS Administration utility) We may also have used these abbreviations: LC ST LQ DMgr IBM Lotus Connections IBM Lotus Sametime IBM Lotus Quickr WAS Deployment Manager

2011 IBM Corporation

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

Whats in the Lotus Connections box?

Lotus Connections 3.0 Installer Lotus Connections 3.0 Wizards

Tivoli Directory Integrator 7.0.0 Tivoli Directory Server 6.2 (Optional)

WebSphere Application Server Network Deployment 7.0 WebSphere Application Server Network Deployment Supplements 7.0 (HTTP) WebSphere Application Edge Components 7.0 (Optional)

DB2 9.5 or 9.7 (Optional)

2011 IBM Corporation

What Versions Do We Need?


L C2 .5 WAS WAS6 .1 .0 .2 3 WASND 6 .1 .0 .2 3 DB 9 .1 .6 , 9 .5 .3 2 Orac le 1 0 g 1 0 .2 .0 .4 M ro so ft S S rve r 2 0 0 5 E rprise ic QL e nte WAS HS6 .1 .0 .2 3 /I I TDS6 .0 .0 .3 , 6 ,1 L tus Do m ino 7 .0 .2 , 8 .0 .x, 8 .5 .x o M ro so ft Ac tive Dire c to ry 2 0 0 3 ic S J TM S m Dire c to ry S rve r 5 .2 un ava yste e S J Platfo rm S un ava tand ard E itio n 6 .0 d No ve ll e Dire c to ry 8 .8 TDI 6 .1 .0 .6 L C3 .0 WASND 7 .0 .0 .1 1 DB 9 .5 .0 .5 , 9 .7 .0 .2 2 Orac le 1 0 g 1 0 .2 .0 .4 M S 2 0 0 5 E rprise S S QL nte P3 WAS HS7 .0 .0 .1 1 /I I TDS6 .2 .0 .2 L tus Do m ino 8 .0 .2 + o M AD 2 0 0 3 , ADAMM 2 0 0 8 S S S J S m Dire c to ry S rve r 6 .3 un ava yste e No ve ll e Dire c to ry 8 .8 .5

DB H TTP

LDA P

TDI

TDI 7 .0 .0 .5
2011 IBM Corporation

10

So Where Do We Get That Code From?

WAS ND 7.0 PA/ PW WAS ND Supplements 7.0 PA/ PW WebSphere UpdateInstaller 7.0.0.13 TN FC HTTP 7.0

LC 3.0 Installer PA/ PW LC 3.0 Wizards PA/ PW LC 3.0 UpdateInstaller FC All current LC3.0 Fixes FC

TDI 7.0 PA/ PW TDI 7.0 FP5 FC

Oracle 10g Enterprise 10.2.0.4

DB2 9.7 FP2 or DB2 9.5 FP5 FC

MS SQL Server 2005 Enterprise SP2 FP3

Tivoli Directory Server 6.2 FP2

FC

Domino 8.0.2 Domino 8.5.x

PA/ PW

MS Active Directory 2003 SP2+

Novell eDirectory 8.8

Sun Java Directory Server 5.2, 6.0

FC = Fix Cent ral ht t p:/ / ibm.com/ support / fix cent ral PA/ PW = Passport Advant age (Cust omers) or Part nerWorld (Part ners)

TN = Updat eInst aller TechNot e ht t p:/ / www01.ibm.com/ support / docview.wss?uid=swg24020212


2011 IBM Corporation

11

What Platforms are Supported?

Windows Server 2008 Enterprise Edition (64 Bit only - not R2!) Windows Server 2003 SP2 Enterprise Edition (32 Bit only) Windows Server 2003 SP2 Standard Edition (32 Bit only

IBM AIX 6.1 TL4 (64 Bit)

Red Hat Enterprise Linux 5.0 Advanced Platform SUSE Linux Enterprise Server 10 SP2 (System z) Update 4 (System z) SUSE Linux Enterprise Server 10 SP2 (32 Bit) Red HEL 5.0 Advanced Platform Update 4 (32 Bit or 64 SUSE Linux Enterprise Server 11 (System z - 64 Bit Tolerate) Bit) SUSE Linux Enterprise Server 11 (64 Bit Tolerate)

2011 IBM Corporation

12

In The Real World...


Most Lotus Connections 3.0 installations are:
Either Windows 2008 64-Bit or RHEL 64-Bit Run against Lotus Domino Directory or MS Active Directory LDAP Use DB2 (more on that in a bit...)

So, for this session we are using:


Windows 2008 Standard Server SP1 (not R2) Lotus Domino 8.5.2 LDAP DB2 9.7

Basic Windows install, plus


Google Chrome BareTail Softerra LDAP Administrator

Then cloned VM

2011 IBM Corporation

13

The Installation Environment


Were trying hard to mimic a real production environment, suitable for approximately 1000+ users, using VMWare virtual machines (VMs) Using two servers (via VMs):
Server Name Data (data.ls11.us) [Black Desktop] Running DB2 TDI LDAP (Domino) RAM 2GB

Connections (connections.ls11.us) [Purple Desktop]

WAS HTTP

2GB

In a production environment, would expect LDAP to already exist (Domino or AD), otherwise this environment built on VMWare ESX would work well.

2011 IBM Corporation

14

The Installation Environment (cont.)


Between those two servers (data and connections) we're going to build from scratch a working Lotus Connections instance during this session However, to avoid 90% of this session consisting of looking at progress bars, we're going to do some magic of television during the install (you know, where the chef puts all the ingredients together in a pot and 'through the magic of television' then pulls one out of the oven that's been cooking for two hours) We'll go through all the steps and initiate the installation we're working on, but then we'll switch to another VM instance where 45 minutes have elapsed and that part of the install says complete We have complete, total faith that we'll be successful in our endeavor, but just in case, we've got a VM of the finished product, as well

2011 IBM Corporation

15

In Your Environment, You Might...


Copy this installation environment (changing only hostnames, usernames and passwords as appropriate), giving you a flexible and responsive environment for testing, pilots and small-scale production Shift HTTP on to its own server (moving to a three-box install), aiding performance and scalability further Cluster WAS onto multiple nodes allowing growth to many thousands of concurrent users However, the installation process is much the same, so this approach and these notes will help you along the way. But were getting ahead of ourselves...

2011 IBM Corporation

16

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

17

SQL Server or Oracle customer, why use DB2?


If your organization currently uses either Microsoft SQL Server or Oracle, should you use DB2 for Lotus Connections or not?
Point one Lotus Connections happily supports all three databases (and, officially, supports all three equally) Point two updates, etc., for Connections and DB2 will happen in tandem and will be found all in one place. Oracle and SQL will not. Point three if your organization is already running SQL or Oracle (or DB2, for that matter), will you be allowed to use the existing infrastructure or will you need a database infrastructure of your own, anyway? Point four if your organization is running ANY ONE of the three DBs, are you running the right version ? Point five give thought to licensing. DB2 is free with Connections will you need additional licenses, even if the other DBs are available in your organization? Will you need additional CALs if EVERYONE in your organization will potentially be accessing your existing DBs ?

We're not saying you shouldn't use something else, but there are a lot of reasons why the 'included-in-the-box DB2' is the logical choice...

2011 IBM Corporation

18

Document, Document, Document!


Document every step of your installation. Include:
Naming conventions Host names and IP addresses Usernames and Passwords (and the specific role the user plays) Detailed commands, will come in useful for future installs, trouble-shooting etc. Mind Maps Evernote Screenshots Camtasia (or similar) to record install screens

Suggestions:

2011 IBM Corporation

19

Other tips...
We don't want to ruin all the surprises in our 12 Things Your Mother Never Told You session, but there are a couple critical tips to pass along:

Never install into c:\program files (or any path with spaces) Keep paths as short as possible If using VMs, take regular snapshots (so you can do a step over if needed) Use Baretail (or tail -f) to follow log files Use an LDAP browser Use cheat sheets (record frequently-used command lines in a txt file) Plan to spend three times more time planning than doing, and three times more time doing that on Profiles than anything else Always wear white at night (important general safety tip)

2011 IBM Corporation

20

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

21

Whats Changed for 3.0? (General)


Global Navigation and Theme (including drop-down menus) Home Page/News improved news feed and integration of status updates, email digest Communities invitations, improved Files integration, Activities integration, subcommunities, My Communities views Forums standalone service, tags, question/answer topics Profiles Do You Know, Things in Common, Social Path widgets, tabbed Profile Files collections changed to folders including drag and drop Wikis improved use of real estate, drag and drop navigation, My Wikis views Blogs improved authoring including new editor and more consistent navigation and entries Lists Linked Value SharePoint/Communities integration, new portlets, status updates Lotus Notes sidebar plug-in
2011 IBM Corporation

22

Whats Changed for 3.0? (Admin)


From the Administrator standpoint: The installation procedure has changed significantly
Connections 3.0 installer is based on the newest install technology IBM Rational Install Manager (2.5 was based on Install Shield). This is the same as used for Lotus Sametime 8.5.
The new installer has a more flexible GUI Supports installation of multiple product simultaneously Integrates install/uninstall/upgrade/modify into one GUI

Connections 3.0 installer supports Network Deployment version of WAS only


No longer support Stand-alone deployment (still able to migrate from 2.5 stand-alone to 3.0 ND)

Connections 3.0 installer supports installing multiple nodes at the same time
The installer will run directly against Deployment Manager and Managed Node rather than on unmanaged nodes (like 2.5)

Connections 3.0 installer is faster with reduced post-install steps

2011 IBM Corporation

23

Whats Changed for 3.0? (Admin - cont.)


From the Administrator standpoint:
The installation procedure has changed significantly Installation now much faster:
Actual installer still takes approximately an hour But start-to-finish now approximately 60% of Connections 2.5 install time

Upgrades from Connections 2.5.0.2 to Connections 3.0 will be supported New Database Wizard for Connections 3.0
Nanny mode enables you to look into the detailed commands the Wizard runs, selected by default Streamlined Wizard reduces number of questions asked

Population Wizard much improved too Uses TDI 7.0

2011 IBM Corporation

24

Are you ready? Sure?

2011 IBM Corporation

25

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

26

Installation Sequence
We will be following an install process that makes most sense on stage, given time and equipment constraints You do not need to perform the steps in exactly this order. The key is that all installation pre-requisites are met fully before installing Lotus Connections. The steps fall into four categories:
Pre-installation steps (installing foundational software) Configuring for Lotus Connections (create databases, etc.) Install Lotus Connections Post-Installation steps

2011 IBM Corporation

27

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

28

Pre-Installation Tasks
As per the previous slide, we need to get a bunch of foundational installs out of the way before we actually install Connections:
On our Data server:
Install DB2 Apply the DB2 license Install TDI Apply TDI Fixpack Install WAS Install HTTP and WAS Plug-ins Install WebSphere Update Installer Patch WAS, HTTP, Plug-ins to 7.0.0.11

On our Connections server:

2011 IBM Corporation

29

Step 1: Install DB2 9.7 on data


Download v9.7fp2_ntx64_server.exe from FixCentral
(There is no need to install full version of DB2 and then patch - just install the FixPack on a clean system)

Run v9.7fp2_ntx64_server.exe to unzip the contents (e.g. into c:\Install\db2_9702) Go to the "SERVER" directory and run setup.exe

2011 IBM Corporation

30

Step 1: Install DB2 9.7 on data (cont.)


The following panel is displayed:

Click the Install a Product link...

2011 IBM Corporation

31

Step 1: Install DB2 9.7 on data (cont.)


The following panel appears:

Click Install New...

2011 IBM Corporation

32

Step 1: Install DB2 9.7 on data (cont.)


The following panel appears:

Click Nex t...

2011 IBM Corporation

33

Step 1: Install DB2 9.7 on data (cont.)


The license agreement is displayed:

Accept and click Nex t...

2011 IBM Corporation

34

Step 1: Install DB2 9.7 on data (cont.)


Select the Typical install type:

Click Nex t...

2011 IBM Corporation

35

Step 1: Install DB2 9.7 on data (cont.)


Select the opt ion to install DB2:

Click Nex t...

2011 IBM Corporation

36

Step 1: Install DB2 9.7 on data (cont.)


Select the install location for DB2:

Choose a suitable location (C:\IBM\SQLLIB), and click Nex t...

2011 IBM Corporation

37

Step 1: Install DB2 9.7 on data (cont.)


Choose a username and password (were using db2admin and GetS0c1al):

Click Nex t...

2011 IBM Corporation

38

Step 1: Install DB2 9.7 on data (cont.)


Accept the defaults for DB2 instance details:

Click Nex t...

2011 IBM Corporation

39

Step 1: Install DB2 9.7 on data (cont.)


The DB2 Tools panel is displayed:

DB2 Tools are not required for this environment, click Nex t...

2011 IBM Corporation

40

Step 1: Install DB2 9.7 on data (cont.)


The DB2 Notifications panel is displayed:

DB2 Notifications are not required for this environment, deselect Set up your2011 IBM Corporation DB2
41

Step 1: Install DB2 9.7 on data (cont.)


The OS Security panel is displayed:

It is security best practice to enable Windows Security, though I do not always do so depending on organisational policy.

2011 IBM Corporation

42

Step 1: Install DB2 9.7 on data (cont.)


The confirmation panel is displayed:

Check the details and click Install...

2011 IBM Corporation

43

Step 1: Install DB2 9.7 on data (cont.)


Once installation is complete, this panel is displayed:

Check the details and click Finish.

2011 IBM Corporation

44

Step 1: Install DB2 9.7 on data (cont.)


The DB2 First Steps panel is then displayed:

Just close this window.

2011 IBM Corporation

45

Step 1: Install DB2 9.7 on data (cont.)


Check install using DB2 Control Center - right click green DB2 icon in the taskbar, and select DB2 Control Center

The Control Center will launch, showing the View panel. Ensure Advanced is selected, set to not show this window in the future, and click OK:

2011 IBM Corporation

46

Step 1: Install DB2 9.7 on data (cont.)


Expand the All Systems and Instances elements. You should see your system and an instance named DB2 listed.

Quit out of the Control Center.

2011 IBM Corporation

47

Step 1: Install DB2 9.7 on data (cont.)


You must create a user on the operating system for DB2 named lcuser (other user IDs can be used, but this is the default within the Lotus Connections installer). This user will be the owner of the databases when they are created. On the database machine, expand Computer Management > System Tools > Local Users and Groups > Users. Right click on Users and select New User...

2011 IBM Corporation

48

Step 1: Install DB2 9.7 on data (cont.)


Enter user and password details of lcuser:

Deselect the "User must change password at nex t logon" option, select Password never ex pires. Click Create
2011 IBM Corporation

49

Step 1: Install DB2 9.7 on data (cont.)


Once the user has been created, right-click the user and click Properties:

Select the Member of tab. The lcuser user must be added to the DB2USERS group. Click Add and type DB2USERS in the "Enter the object names to select" field:

Click OK until you are back to the Computer Management panel.

2011 IBM Corporation

50

An Aside: Installing DB2 on Linux


On Windows, a standard wizard-driven install of DB2 will automatically create a DB2 'instance' for Connnections to use. DB2 is also started and TCPIP communications configured. Easy-peasy! On Linux and AIX, things are a little different these steps need to be run manually, else the DB Wizard will not be able to find a database instance to install into...

2011 IBM Corporation

51

An Aside: Installing DB2 on Linux (cont.)


Here are example steps to get DB2 ready on Linux, firstly create instance...
Install DB2 using wizard Add groups and users:
groupadd -g 999 db2iadm1 useradd -u 999 -g db2iadm1 -m -d /home/db2inst1 db2inst1 -p password useradd -u 998 -g db2iadm1 -m -d /home/db2fenc1 db2fenc1 -p password useradd -u 997 -g db2iadm1 -m -d /home/db2adm1 db2adm1 -p password

Create instance (as root):


/opt/ibm/db2/V9.7/instance/db2icrt -u db2fenc1 db2inst1

Start DB2 (as db2inst1 have to 'chmod 755 db2start' as root)


cd /opt/ibm/db2/V9.7/adm; ./db2start

Create DB2 Admin Server (as root):


/opt/ibm/db2/V9.7/instance; ./dascrt db2adm1

Test:
Login as db2inst1 db2cc

2011 IBM Corporation

52

An Aside: Installing DB2 on Linux (cont.)


Then configure TCPIP communications:
Edit /etc/services (as root), add to bottom of file:
db2inst1 50000/tcp DB2_d2binst1_2 60002/tcp DB2_db2inst1 60003/tcp DB2_db2inst1_1 60004/tcp DB2_db2inst1_2 60005/tcp DB2_db2inst1_END 60006/tcp

Setup DB2 communications (as db2inst1)


cd ~/sqllib . ./db2profile db2
update database manager configuration using svcename db2inst1 db2stop Db2start get database manager configuration

db2set DB2COMM=tcpip db2stop;db2start


2011 IBM Corporation

53

An Aside: Installing DB2 on Linux (cont.)


Then test:
telnet localhost 50000

You should then be ready to run DBWizard... Also need to configure DB2 to start automatically, e.g.:
Edit /etc/rc.local as root, add the following:
#START DB2 for LOTUS CONNECTIONS DB2LOG=/tmp/startDB2.out.`date +"%y%m%d"` su db2inst1 -c /home/db2inst1/sqllib/adm/db2start >> $DB2LOG 2>&1

2011 IBM Corporation

54

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

55

Step 2: Apply DB2 License on data


Check status of current DB2 license by typing 'db2licm -l' at a command prompt:

DB2 is shipped with trial license, this needs to be replaced with limited license included with Lotus Connections...

2011 IBM Corporation

56

Step 2: Apply DB2 License on data (cont.)


Locate the DB2 license file named db2ese_o.lic (shipped in the DB2_ESE_Restricted_QS_Activation_97.zip package) Apply this file using the following commands: cd \install\DB2_ESE_ Restricted_QS_Activation_97\ese_o\db2\license (etc) db2licm -a db2exe_o.lic

2011 IBM Corporation

57

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

58

Step 3: Install TDI on data (cont.)


Download TDI 7.0 for Windows 64-bit (C1IF1ML.zip) and unzip, e.g. into c:\Install\TDI70_x64 Explore this directory, and run launchpad.ex e

2011 IBM Corporation

59

Step 3: Install TDI on data (cont.)


This splash panel is displayed:

Choose your language and click OK...

2011 IBM Corporation

60

Step 3: Install TDI on data (cont.)


This splash panel is displayed:

Click the Install IBM Tivoli Directory Integrator link...

2011 IBM Corporation

61

Step 3: Install TDI on data (cont.)


This panel is displayed:

Click the Tivoli Directory Integrator 7.0 Installer link...

2011 IBM Corporation

62

Step 3: Install TDI on data (cont.)


This first installer panel is displayed:

Click Nex t...

2011 IBM Corporation

63

Step 3: Install TDI on data (cont.)


The installer searches for previous installs:

Click Nex t...

2011 IBM Corporation

64

Step 3: Install TDI on data (cont.)


The license is displayed:

Accept, and click Nex t...

2011 IBM Corporation

65

Step 3: Install TDI on data (cont.)


The installation location panel is displayed:

Choose a suitable location that does not contain a space (e.g. C:\IBM\TDI\V7.0), and click Nex t...

2011 IBM Corporation

66

Step 3: Install TDI on data (cont.)


The installation type panel is displayed:

Choose Typical, and click Nex t...

2011 IBM Corporation

67

Step 3: Install TDI on data (cont.)


The Solutions Directory panel is displayed:

Choose Do not specify, and click Nex t...

2011 IBM Corporation

68

Step 3: Install TDI on data (cont.)


The ports panel is displayed:

Accept the defaults, and click Nex t...

2011 IBM Corporation

69

Step 3: Install TDI on data (cont.)


The Administration and Monitoring Console panel is displayed:

This is not necessary in this environment, click Nex t...

2011 IBM Corporation

70

Step 3: Install TDI on data (cont.)


The confirmation panel is displayed:

Check the details and click Install...

2011 IBM Corporation

71

Step 3: Install TDI on data (cont.)


Once installation is complete, this panel is displayed:

Check the details, deselect Start the Configuration Editor, and click Finish. IBM Corporation 2011
72

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

73

Step 4: Apply FixPack 5 to TDI on data


Unzip the file 7.0.0-TIV-TDI-FP0005.zip to create a folder with the same name (e.g. C:\Install\7.0.0-TIV-TDI-FP0005) Change to this directory and locate the UpdateInstaller.jar Jar file Copy and paste this file in the C:\IBM\TDI\V7.0\maintenance directory, replacing the existing file with the same name Start a command prompt, change to the C:\IBM\TDI\V7.0\bin directory and run the following command:
applyUpdates.bat -update C:\Install\7.0.0-TIV-TDI-FP0005\TDI-7.0-FP0005.zip

The status of the fixpack install can be checked with:


applyUpdates.bat -queryreg
2011 IBM Corporation

74

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

75

Step 5: Install WAS on connections


Unzip the file that you have downloaded in a directory on your hard disk Change to the directory and run launchpad.exe:

Click Launch the installation wizard for WebSphere Application Server NetworkIBM Corporation 2011
76

Step 5: Install WAS on connections (cont.)


The following panel is displayed:

Click Nex t...


2011 IBM Corporation

77

Step 5: Install WAS on connections (cont.)


The license is displayed:

Accept, and click Nex t...

2011 IBM Corporation

78

Step 5: Install WAS on connections (cont.)


The pre-requisites check is then executed. If it fails, cancel the install, check the prerequisites listed, and restart the WAS install:

Assuming that the check is passed, click Nex t...

2011 IBM Corporation

79

Step 5: Install WAS on connections (cont.)


The optional features panel is then displayed:

Leave all checkboxes disabled, click Nex t...

2011 IBM Corporation

80

Step 5: Install WAS on connections (cont.)


The installation location panel is displayed:

Choose a suitable location (C:\IBM\WebSphere\AppServer), and click Nex t... IBM Corporation 2011
81

Step 5: Install WAS on connections (cont.)


The server environment panel is displayed:

Select Cell* and click Nex t...

* Note: this is a change from 2.5

2011 IBM Corporation

82

Step 5: Install WAS on connections (cont.)


The administrative security panel is displayed:

Select Enable checkbox and enter username and password* and 2.5 t... * Note: this is a change from click Nex 2011 IBM Corporation

83

Step 5: Install WAS on connections (cont.)


A note on Admin Security:
Enabling during install is a change from 2.5 where best practice was to install with security disabled and enable after LDAP is configured The username used here must not be in LDAP, it is stored in the Local Reposit ory If username is in LDAP, it can cause a significant issue if LDAP server or OU structure is changed at a later date Typically use wasadmin, wsadmin or lcadmin for this role Store the password somewhere!

2011 IBM Corporation

84

Step 5: Install WAS on connections (cont.)


The repository panel is displayed:

Leave checkbox disabled and click Nex t...


2011 IBM Corporation

85

Step 5: Install WAS on connections (cont.)


The confirmation panel is displayed:

Check the details and click Nex t...


2011 IBM Corporation

86

Step 5: Install WAS on connections (cont.)


If all goes to plan, the following panel will display:

Click Finish...
2011 IBM Corporation

87

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

88

Step 6: Install HTTP and WAS Plug-ins on connections


Unzip the file that WAS Supplements archive in a directory on your hard disk Change to the IHS sub-directory and run install.exe:

Click Nex t...

2011 IBM Corporation

89

Step 6: Install HTTP and WAS Plug-ins on connections (cont.)


The license is displayed:

Accept, and click Nex t...


2011 IBM Corporation

90

Step 6: Install HTTP and WAS Plug-ins on connections (cont.)


The pre-requisites check is then executed. If it fails, cancel the install, check the prerequisites listed, and restart the install:

Assuming that the check is passed, click Nex t...

2011 IBM Corporation

91

Step 6: Install HTTP and WAS Plug-ins on connections (cont.)


The installation location panel is displayed:

Choose a suitable location (C:\IBM\WebSphere\HTTPServer), and click Nex t...


2011 IBM Corporation

92

Step 6: Install HTTP and WAS Plug-ins on connections (cont.)


The port values panel is displayed:

Accept the defaults, and click Nex t...


2011 IBM Corporation

93

Step 6: Install HTTP and WAS Plug-ins on connections (cont.)


The services panel is displayed:

Enable both checkboxes, enter the details of your Windows admin user, set startup type as Automatic and click Nex t...

2011 IBM Corporation

94

Step 6: Install HTTP and WAS Plug-ins on connections (cont.)


The Administration Server panel is displayed:

Create a new user ID for this purpose (e.g. ihsadmin, add a password, and click Nex t...

2011 IBM Corporation

95

Step 6: Install HTTP and WAS Plug-ins on connections (cont.)


The Plug-in panel is displayed:

Select to install the Plug-in, create web server definition (defaults to webserver1), check the hostname of the server (e.g. connections.ls11.us), and click Nex t...

2011 IBM Corporation

96

Step 6: Install HTTP and WAS Plug-ins on connections (cont.)


The confirmation panel is displayed:

Check the details and click Nex t...


2011 IBM Corporation

97

Step 6: Install HTTP and WAS Plug-ins on connections (cont.)


If all goes to plan, the following panel will display:

Click Finish...
2011 IBM Corporation

98

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

99

Step 7: Install WebSphere Update Installer


The latest version of the Update Installer tool can be found at this technote
http://www-01.ibm.com/support/docview.wss?uid=swg24020212

Its always best to download and use the latest release, e.g. 7.0.0.13.

2011 IBM Corporation

100

Step 7: Install WebSphere Update Installer (cont.)


Download and unzip the Update Installer package then run install.exe. This panel is displayed:

Click Nex t...

2011 IBM Corporation

101

Step 7: Install WebSphere Update Installer (cont.)


The license is displayed:

Accept, and click Nex t...


2011 IBM Corporation

102

Step 7: Install WebSphere Update Installer (cont.)


The pre-requisites check is then executed. If it fails, cancel the install, check the prerequisites listed, and restart the install:

Assuming that the check is passed, click Nex t...

2011 IBM Corporation

103

Step 7: Install WebSphere Update Installer (cont.)


The installation location panel is displayed:

Choose a suitable location (C:\IBM\WebSphere\UpdateInstaller), and click Nex t...


2011 IBM Corporation

104

Step 7: Install WebSphere Update Installer (cont.)


The confirmation panel is displayed:

Check the details and click Nex t...


2011 IBM Corporation

105

Step 7: Install WebSphere Update Installer (cont.)


If all goes to plan, the following panel will display:

Ensure Launch ... on exit is checked then click Finish...


2011 IBM Corporation

106

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

107

Step 8: Patch WAS to 7.0.0.11


After completing the previous task, the following panel will display:

Click Nex t...


2011 IBM Corporation

108

Step 8: Patch WAS to 7.0.0.11(cont.)


The following update packages need to be installed:
7.0.0-WS-WAS-WinX64-FP0000011.pak 7.0.0-WS-WASSDK-WinX64-FP0000011.pak 7.0.0.11-WS-WAS-IFPM12828.pak 7.0.0.0-WS-WAS-IFPM23410.pak 7.0.0.0-WS-WASJavaSDK-WinX64-IFPM24384

These need to be downloaded from FixCentral and stored in an easily accessible location, e.g. C:\Install\WASFixes

2011 IBM Corporation

109

Step 8: Patch WAS to 7.0.0.11(cont.)


The tool should find the correct location of the WAS install (plus the HTTP and Plugin locations):

Select the WAS installation (C:\IBM\WebSphere\AppServer) and click Nex t...

2011 IBM Corporation

110

Step 8: Patch WAS to 7.0.0.11(cont.)


The task selection panel is displayed:

Select Install maintenance package and click Nex t...


2011 IBM Corporation

111

Step 8: Patch WAS to 7.0.0.11(cont.)


The directory location is displayed:

Select the directory where the WAS fixes reside (e.g. C:\Install\WASFixes) and click Nex t...

2011 IBM Corporation

112

Step 8: Patch WAS to 7.0.0.11(cont.)


The available packages panel is displayed:

All applicable patches should be selected, check this and click Nex t ...
2011 IBM Corporation

113

Step 8: Patch WAS to 7.0.0.11(cont.)


The installation summary panel is displayed:

Click Nex t...


2011 IBM Corporation

114

Step 8: Patch WAS to 7.0.0.11(cont.)


If all goes to plan, the following panel will display:

Click Relaunch to restart the Update Installer...


2011 IBM Corporation

115

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

116

Step 9: Patch HTTP to 7.0.0.11


After completing the previous task, the following panel will again display:

Click Nex t...


2011 IBM Corporation

117

Step 9: Patch HTTP to 7.0.0.11(cont.)


The following update package needs to be installed:
7.0.0-WS-IHS-WinX64-FP0000011.pak

This need to be downloaded from FixCentral and stored in an easily accessible location, e.g. C:\Install\WASFixes Note: if the HTTP Server is installed on a different system to the WAS server, then this fix will also need to be installed:
7.0.0-WS-WASSDK-WinX64-FP0000011.pak

2011 IBM Corporation

118

Step 9: Patch HTTP to 7.0.0.11(cont.)


The tool should find the correct location of the WAS, HTTP and Plugin installs:

Select the HTTP installation (C:\IBM\WebSphere\HTTPServer) and click Nex t...


2011 IBM Corporation

119

Step 9: Patch HTTP to 7.0.0.11(cont.)


The task selection panel is displayed:

Select Install maintenance package and click Nex t...


2011 IBM Corporation

120

Step 9: Patch HTTP to 7.0.0.11(cont.)


The directory location is displayed:

Select the directory where the HTTP fixes reside (e.g. C:\Install\WASFixes) and click Nex t...

2011 IBM Corporation

121

Step 9: Patch HTTP to 7.0.0.11(cont.)


The available packages panel is displayed:

All applicable patches should be selected, check this and click Nex t ...
2011 IBM Corporation

122

Step 9: Patch HTTP to 7.0.0.11(cont.)


The installation summary panel is displayed:

Click Nex t...


2011 IBM Corporation

123

Step 9: Patch HTTP to 7.0.0.11(cont.)


If all goes to plan, the following panel will display:

Click Relaunch to restart the Update Installer...


2011 IBM Corporation

124

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

125

Step 10: Patch Plugins to 7.0.0.11


After completing the previous task, the following panel will again display:

Click Nex t...


2011 IBM Corporation

126

Step 10: Patch Plugins to 7.0.0.11 (cont.)


The following update package needs to be installed:
7.0.0-WS-PLG-WinX64-FP0000011.pak

This need to be downloaded from FixCentral and stored in an easily accessible location, e.g. C:\Install\WASFixes Note: if the HTTP Server is installed on a different system to the WAS server, then this fix will also need to be installed:
7.0.0-WS-WASSDK-WinX64-FP0000011.pak

2011 IBM Corporation

127

Step 10: Patch Plugins to 7.0.0.11 (cont.)


The tool should find the correct location of the WAS, HTTP and Plugin installs:

Select the Plugins installation (C:\IBM\WebSphere\HTTPServer/Plugins) and click Nex t...

2011 IBM Corporation

128

Step 10: Patch Plugins to 7.0.0.11 (cont.)


The task selection panel is displayed:

Select Install maintenance package and click Nex t...


2011 IBM Corporation

129

Step 10: Patch Plugins to 7.0.0.11 (cont.)


The directory location is displayed:

Select the directory where the HTTP fixes reside (e.g. C:\Install\WASFixes) and click Nex t...

2011 IBM Corporation

130

Step 10: Patch Plugins to 7.0.0.11 (cont.)


The available packages panel is displayed:

All applicable patches should be selected, check this and click Nex t ...
2011 IBM Corporation

131

Step 10: Patch Plugins to 7.0.0.11 (cont.)


The installation summary panel is displayed:

Click Nex t...


2011 IBM Corporation

132

Step 10: Patch Plugins to 7.0.0.11 (cont.)


If all goes to plan, the following panel will display:

Click Finish to close the Update Installer...


2011 IBM Corporation

133

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

134

Phew!
We've now finished the pre-requisite software install (all the foundational software we need for Connections is now in place) It's time to start actually configuring things for Connections Grab your favorite beverage and forge ahead!

2011 IBM Corporation

135

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

136

Configuring for Lotus Connections


Before we install Connections itself, a few final steps to get ready
Start Deployment Manager Configure Federated Repository Create the databases (in DB2 or other db) Connections needs (CRITICAL POINT Connections needs these in place before install) Populate Profiles database from LDAP

2011 IBM Corporation

137

Step 11: Start the Deployment Manager


The next step is to configure WebSphere Application Server ready for the Lotus Connections install. This requires the WAS Deployment Manager (DMgr) to be running. Open the Services pane and check:

If not started, right click and select Start

2011 IBM Corporation

138

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

139

Step 12: Configure Federated Repository


We need to tell Connections to use LDAP, so we need to tell WAS to use a Federated Repository. This step will set that up. Once the DMgr is up, connect to the Integrated Solutions Console (ISC) using a suitable web browser (were using Chrome throughout this session):
http://connections.ls11.us:9060/ibm/console

Log in with the user you defined as administrator during the WAS install (wasadmin / GetS0c1al)

2011 IBM Corporation

140

Step 12: Configure Federated Repository (cont.)


Expand the "Security" section and click Global security:

2011 IBM Corporation

141

Step 12: Configure Federated Repository (cont.)


Click Configure...:

2011 IBM Corporation

142

Step 12: Configure Federated Repository (cont.)


Click Add Base Entry to Realm...:

2011 IBM Corporation

143

Step 12: Configure Federated Repository (cont.)


Click Add Repository...:

2011 IBM Corporation

144

Step 12: Configure Federated Repository (cont.)


Type a name in the "Repository identifier" field, select a Directory type, type the "Primary host name," and then type the user name and password of the "Bind distinguished name." Use default values for the other fields. Click Apply:

2011 IBM Corporation

145

Step 12: Configure Federated Repository (cont.)


Access to the LDAP repository is then checked, and if the bind is made correctly, the option to Save appears at the top of the page with no errors:

Click Save

2011 IBM Corporation

146

Step 12: Configure Federated Repository (cont.)


Enter the base DN of the user container of your LDAP server. This changes depending on the LDAP server being used, this is documented in the Infocenter/Wiki. The second field defines the location in the LDAP directory information tree from which the LDAP search begins. The entries beneath it in the tree can also be accessed by the LDAP search. For Domino (which is being used here), both fields are usually of the form o=Org

When you are done, click Apply and then click Save
2011 IBM Corporation

147

Step 12: Configure Federated Repository (cont.)


Click OK and then click Save This is a good chance to verify that the new base entry and repository have been saved:

Click OK and then click Save

2011 IBM Corporation

148

Step 12: Configure Federated Repository (cont.)


Next, configure SSO for your domain. Expand Web and SIP security, then select Single sign-on (SSO):

Enter your IP domain name including a leading .. Select the "Interoperability Mode" check box. Click OK and then Save.

2011 IBM Corporation

149

Step 12: Configure Federated Repository (cont.)


Next, security needs to be enabled - this is the step that secures WAS ready for user access. Enable Administrative security and Application security. Do not enable Java 2 security.

Click Apply and then click Save

2011 IBM Corporation

150

Step 12: Configure Federated Repository (cont.)


Click the LogOut link and close your browser.

Then stop and restart the Deployment Manager using the Services panel:

Once the service has restarted, log into the ISC again using the browser.

2011 IBM Corporation

151

Step 12: Configure Federated Repository (cont.)


Expand Users and Groups and select Manage Users

Leave the search criteria as the defaults, and click Search. WAS will query the LDAP server and return a list of matching users:

NOTE: All ls11.us users and emails are fict it ious!

If the expected set of users is returned then LDAP is configured correctly.

2011 IBM Corporation

152

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

153

Step 13: Create Lotus Connections Databases


We must configure the databases used by the Connections features. DB2 9.5/9.7, Oracle 10.2.0.4 or SQL Server 2005 can be used. We are using DB2 9.7 here...

2011 IBM Corporation

154

Step 13: Create Lotus Connections Databases (cont.)


The system is now ready for the Lotus Connections databases to be created. Copy the Lotus Connections wizard package (Lotus_Connections30_Wzd_WIN_CZMD3ML) to the Data machine, and unpack e.g. into c:\Install\LCWizards In that directory, run dbWizard.bat. The following panel is displayed:

2011 IBM Corporation

155

Step 13: Create Lotus Connections Databases (cont.)


The Database Task Selection panel is displayed:

Ensure Create is selected, and click Nex t

2011 IBM Corporation

156

Step 13: Create Lotus Connections Databases (cont.)


The Database Selection panel is displayed:

Check the defaults are correct, and click Nex t

2011 IBM Corporation

157

Step 13: Create Lotus Connections Databases (cont.)


The Applications Selection panel is displayed:

Unless you have a very good reason not to, accept the default of all features, and click Nex t

2011 IBM Corporation

158

Step 13: Create Lotus Connections Databases (cont.)


The Task Summary panel is displayed:

Check the details, then click Create

2011 IBM Corporation

159

Step 13: Create Lotus Connections Databases (cont.)


The Detailed Commands panel is displayed:

Check the details, then click Ex ecute

2011 IBM Corporation

160

Step 13: Create Lotus Connections Databases (cont.)


During the database creation, the following panel is displayed:

Check Open log to review the log files as the wizard runs...

2011 IBM Corporation

161

Step 13: Create Lotus Connections Databases (cont.)


Once the wizard has completed its work, the following panel is displayed:

Check the details (ensuring all features created successfully), then click Finish.IBM Corporation 2011

162

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

163

Step 14: Populate Lotus Connections Profiles


So, we now have connected to LDAP and we've created the databases in DB2. Now, we need to populate the databases To accomplish that, we populate Lotus Connections Profiles from the LDAP directory This is again completed on the Data system (where TDI and DB2 are installed) This step requires the Databases to have been created and TDI to have been installed and patched successfully You will need the LDAP server details, search criteria, bind ID and password (as added to WAS earlier), plus the Database server details, username and password Lastly, you will need to have unpacked the Lotus Connections 3.0 Wizards package (as used in the Database Creation step)

2011 IBM Corporation

164

Step 14: Populate Lotus Connections Profiles (cont.)


To begin populating user data in the Profiles database, use Windows Explorer to open the Wizards directory and run the populationWizard.bat file. The following splash screen is shown:

Click Nex t

2011 IBM Corporation

165

Step 14: Populate Lotus Connections Profiles (cont.)


The Install Location panel is displayed. As we have not installed TDI into the Program Files directory, we are prompted to select the correct install location:

Select the correct location (c:\IBM\TDI\V7.0) and click Nex t

2011 IBM Corporation

166

Step 14: Populate Lotus Connections Profiles (cont.)


The Database Type panel is displayed:

As we are using DB2 here, we simply click Nex t

2011 IBM Corporation

167

Step 14: Populate Lotus Connections Profiles (cont.)


The Database Properties panel is displayed:

Enter the hostname of the database server and the LCUSER password.

With DB2 installed on the same system, we set the JDBC driver path to the java subdirectory of the DB2 install. With Oracle, SQL Server or a remote DB2 install, this 2011 IBM Corporation JDBC driver would need to be copied onto the system. Click Nex t 168

Step 14: Populate Lotus Connections Profiles (cont.)


The LDAP Server Connection panel is displayed:

Enter the full hostname of the LDAP server, and ensure that SSL is selected if required (were using standard port 389 here). Click Nex t

2011 IBM Corporation

169

Step 14: Populate Lotus Connections Profiles (cont.)


The LDAP Authentication Properties panel is displayed:

Enter the LDAP Bind ID and password as used in WAS earlier. Click Nex t

2011 IBM Corporation

170

Step 14: Populate Lotus Connections Profiles (cont.)


The BaseDN/Filter panel is displayed:

Enter the search base used in WAS earlier. The default LDAP search filter is2011 IBM Corporation usually

171

Step 14: Populate Lotus Connections Profiles (cont.)


The Database Mapping panel is displayed:

You can customize the mappings between the LDAP and profiles database if 2011 IBM Corporation required.

172

Step 14: Populate Lotus Connections Profiles (cont.)


The Optional Database Tasks panel is displayed:

You can customize the mappings between the attributes and full text fields (e.g. country codes) if required. Weve never needed to do this!

2011 IBM Corporation

173

Step 14: Populate Lotus Connections Profiles (cont.)


The Configuration Summary panel is displayed:

Check all the settings are correct, then click Configure

2011 IBM Corporation

174

Step 14: Populate Lotus Connections Profiles (cont.)


Depending on the number of users in the LDAP directory, plus the connection speed, the population may take a matter of seconds or a number of hours. During the population process, the following screen is displayed. As before, the logs can be viewed by clicking Open Log:

2011 IBM Corporation

175

Step 14: Populate Lotus Connections Profiles (cont.)


Once the population wizard has completed, it will display the following screen:

Check the section highlighted here, and if all is well, click Finish.

2011 IBM Corporation

176

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

177

Pre-Installation Complete
At this stage, all the pre-installation tasks are complete. This would be a very very good time t o take backups (having stopped the database, WAS and HTTP), or to take SnapShots if using virtual machines. At the very least, take a copy of the c:\IBM directory on the WAS server! Take lunch... Freshen up... Cross yourself (or praise a suitable deity)... Deep breath...

Lets go!

2011 IBM Corporation

178

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

179

Step 15: Run Lotus Connections Installer


Lets kick off with a checklist... To be ready to run the installer, you need to have:
Installed and patched WAS 7.0.0.11 Installed DB2 9.7.0.2 (or have other suitable DB available)
If running Oracle, you will need the appropriate ODBC driver installed on the WAS system

Configured LDAP and secured the WAS DMgr Created the Lotus Connections databases Populated the Profiles database from LDAP
Having installed installed and patched TDI7.0 first

Ideally backed up the current position

Now you need to:


Ensure database is started and available Ensure LDAP server is started and available Start Deployment Manager
Via Windows Services menu, or from command-line - startManager.[bat,sh]

Start Node Agent


The node agent should also be started so that re-synchronization is possible between the Deployment Manager and node when required 2011 IBM Corporation Via Windows Services menu, or from command-line - startNode.[bat,sh]

180

Step 15: Run Lotus Connections Installer (cont.)


Some considerations...
Rational Installation Manager
Lotus Connections 3.0 uses the Rational Installation Manager to provide an enhanced installation experience. Before beginning the installation, make sure to uninstall any older version of Rational Installation Manager (very important! Clean out the directories too). You are prompted to install this software when you launch the Lotus Connections 3.0 installation wizard

Shared Data Folder


This is a one-node deployment, so there is no need to mount a shared space for Lotus Connections data content to be stored During installation, you are prompted to provide the location of the shared data directory. In this case, the local disk drive is used. The shared data directory, however, must be mounted on each node when there is more than one node In addition:
On windows, the shared data folder path must use UNC name not a mapped drive It have read write access for the machine accounts hosting connections nodes Lastly, you may also need to add the SYSTEM user to the sharing properties in certain circumstances

2011 IBM Corporation

181

Step 15: Run Lotus Connections Installer (cont.)


Enabling DB2 JDBC
Before you begin to install Lotus Connections 3.0, you must copy the JDBC driver from the DB2 server These drivers are used by Lotus Connections to connect to the database On the DB2 machine, these drivers are located in the C:\IBM\SQLIB\java directory. The names of the drivers required are db2jcc.jar and db2jcc_licence_cu.jar, however usually copy whole directory Copy into c:\IBM\JDBC (for example) on the WAS system

2011 IBM Corporation

182

Step 15: Run Lotus Connections Installer (cont.)


If using Oracle or MS SQL Server:
JDBC drivers are required on WAS server, suggest also copying into c:\IBM\JDBC For Oracle:
Need ojdbc6.jar Download from the Oracle website at http://bit.ly/oraclejdbc Confusingly this is the JDBC driver for Oracle 11i which isnt supported as a repository yet

For MS SQL Server


Need Microsoft SQL Server 2005 JDBC Driver 1.2 Download from Microsoft site at http://bit.ly/mssqljdbc

2011 IBM Corporation

183

Step 15: Run Lotus Connections Installer (cont.)


Start the Deployment Manager (if it is stopped):
cd c:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin startManager.bat

2011 IBM Corporation

184

Step 15: Run Lotus Connections Installer (cont.)


Start the Node Agent:
cd c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin startNode.bat

2011 IBM Corporation

185

Step 15: Run Lotus Connections Installer (cont.)


Starting the installation... On the WAS machine, unpack the Lotus Connections Installer package (Lotus_Connections30_WIN_CZMC0ML), e.g. into c:\Install\LCInstaller:

In that Lotus_Connections_Install, run launchpad.exe.

2011 IBM Corporation

186

Step 15: Run Lotus Connections Installer (cont.)


This splash screen will be shown:

Click on Install Lotus Connections 3.0

2011 IBM Corporation

187

Step 15: Run Lotus Connections Installer (cont.)


Next:

Click on Launch the Lotus Connections 3.0 install wizard

2011 IBM Corporation

188

Step 15: Run Lotus Connections Installer (cont.)


The Installation Manager will then be started, displaying the Install Packages panel:

Ensure both the Installation Manager and Connections 3.0 are selected,

2011 IBM Corporation

189

Step 15: Run Lotus Connections Installer (cont.)


The License Agreement will be displayed:

Read every word and meditate on it, then accept and click Nex t:

2011 IBM Corporation

190

Step 15: Run Lotus Connections Installer (cont.)


The Install Packages panel will be displayed:

I know it will shock you, but we would recommend in the st rongest terms not IBM Corporation 2011 to

191

Step 15: Run Lotus Connections Installer (cont.)


Instead, set the paths to be in c:\IBM, and remove the space from Installation Manager:

2011 IBM Corporation

192

Step 15: Run Lotus Connections Installer (cont.)


Another Install Packages panel is displayed, showing Program Files:

Are you getting our theme yet? Dont do it!

2011 IBM Corporation

193

Step 15: Run Lotus Connections Installer (cont.)


Instead, change to c:\IBM\LotusConnections (no space):

Click Nex t

2011 IBM Corporation

194

Step 15: Run Lotus Connections Installer (cont.)


The feature selection panel is shown:

Unless you are limited by license, ensure all features are selected (they canbe IBM Corporation 2011

195

Step 15: Run Lotus Connections Installer (cont.)


The WAS Selection panel is displayed:

2011 IBM Corporation

196

Step 15: Run Lotus Connections Installer (cont.)


Click Browse to select the WAS install location, then navigate to the c:\IBM\WebSphere\AppServer directory and click OK:

If all is working correctly, the WAS DMgr will be detected and displayed:

2011 IBM Corporation

197

Step 15: Run Lotus Connections Installer (cont.)

Enter the hostname of the WAS server (connections.ls11.us in this case), the WAS Administration username and password, and then select Validate
2011 IBM Corporation

198

Step 15: Run Lotus Connections Installer (cont.)


The Installation Manager will then attempt to contact the DMgr and validate all settings. All being well, you will get the following confirmation:

Click OK then Nex t:

2011 IBM Corporation

199

Step 15: Run Lotus Connections Installer (cont.)


The Deployment topology panel comes next:

2011 IBM Corporation

200

Step 15: Run Lotus Connections Installer (cont.)


For this session, were sticking with the Small Deployment:

Select the Small Deployment option, enter a Cluster Name (e.g. connections) and click Nex t

2011 IBM Corporation

201

Step 15: Run Lotus Connections Installer (cont.)


The DB Location panel comes next:

2011 IBM Corporation

202

Step 15: Run Lotus Connections Installer (cont.)


Select whether on one or more servers, your DB type and JDBC location:

2011 IBM Corporation

203

Step 15: Run Lotus Connections Installer (cont.)


Then enter the user name and password for the DBs In our case, all DBs use same user (LCUSER) and password (GetS0c1al), so we check the box for same password, and enter it once:

Then click Validate

2011 IBM Corporation

204

Step 15: Run Lotus Connections Installer (cont.)


Access to each of the DBs will be validated If all are successful, we get the following dialog:

Click OK, then Nex t

2011 IBM Corporation

205

Step 15: Run Lotus Connections Installer (cont.)


Next, we have the Content Store Configuration dialog, which asks for directory locations. Guess what it defaults to?

2011 IBM Corporation

206

Step 15: Run Lotus Connections Installer (cont.)


Set directory paths to c:\IBM\LotusConnections\data\shared and c:\IBM\LotusConnections\data\local:

(On a multi-node environment, these paths would need to be in UNC format)

Click Validate If this is successful, we get the following dialog:

Click OK, then Nex t

2011 IBM Corporation

207

Step 15: Run Lotus Connections Installer (cont.)


Finally, we have the Notification Configuration panel:

2011 IBM Corporation

208

Step 15: Run Lotus Connections Installer (cont.)


Options here tend to be very particular to an organisations messaging infrastructure. Tend to recommend DNS MX Records as this removed need to reconfigure mail settings if mail servers are reconfigured, new gateways added etc. Here we have no mail server configured, so set to Do not enable Notification. It can always be changed later...

Click Nex t

2011 IBM Corporation

209

Step 15: Run Lotus Connections Installer (cont.)


The Installation Summary panel is displayed:

Check the details, click Install

2011 IBM Corporation

210

Step 15: Run Lotus Connections Installer (cont.)


Whilst installing, a progress panel is displayed:

If there are newer versions of any resources it will download them automatically The install should take in the region of one hour to complete

2011 IBM Corporation

211

Step 15: Run Lotus Connections Installer (cont.)


Once the install in complete, this panel will be displayed:

Check the Install Results pane, then click Finish

2011 IBM Corporation

212

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

213

Post-Installation Tasks
Note that there are a number of post installation tasks which must be performed to complete the configuration Before beginning these tasks, you must restart the Deployment Manager for changes to take effect
Either do this from the command line (stopManager.[bat,sh], startManager.[bat,sh]) or using the Windows Services panel - the wasadmin username and password will be needed for the stop command

2011 IBM Corporation

214

Post-Installation Tasks (cont.)


Take another backup or snapshot before going on from here! After the Deployment Manager has been restarted, follow these steps...

2011 IBM Corporation

215

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

216

Step 16: Configure the HTTP Server


Before beginning this task, ensure that the IBM HTTP Administration server is started The administration server must be started to synchronize configuration files between the HTTP Server and the Deployment Manager To start the admin server on Windows, go to Start > Programs > IBM HTTP Server V7.0 > Start Admin Server

(To start the admin server on Linux and AIX systems, use the terminal. Navigate to the HTTPServer/bin directory and issue the following command: ./adminctl start)
2011 IBM Corporation

217

Step 16: Configure the HTTP Server (cont.)


Next, we need to add the HTTP Server to the WebSphere configuration so that it can be managed and synchronised Open the WebSphere ISC at http://connections.ls11.us:9060/admin/console and login Go to System Administration - Nodes and click the Add Node button:

2011 IBM Corporation

218

Step 16: Configure the HTTP Server (cont.)


Select the Unmanaged node option and click Nex t

2011 IBM Corporation

219

Step 16: Configure the HTTP Server (cont.)


Enter a name for the Web Server (typically webserver1node), and the hostname of the HTTP server (connections.ls11.us here), ensure the platform is correct:

Click OK, then Save

2011 IBM Corporation

220

Step 16: Configure the HTTP Server (cont.)


The HTTP server will now be listed as a node:

2011 IBM Corporation

221

Step 16: Configure the HTTP Server (cont.)


Next, we need to add the Web server as a server in the configuration In the ISC, from Servers/Server Types/Web Servers, click the New button:

Choose a server type of Web server:

Click Nex t
2011 IBM Corporation

222

Step 16: Configure the HTTP Server (cont.)


Select the node we just created - webserver1node Enter a Server name of webserver1 - this is the same name that is provided during the plug-ins installation on the Web server:

Click Nex t

2011 IBM Corporation

223

Step 16: Configure the HTTP Server (cont.)


The Web Server Template panel is displayed:

Click Nex t

2011 IBM Corporation

224

Step 16: Configure the HTTP Server (cont.)


The Web Server Properties panel is displayed:

The locations need to be edited to remove Program Files (i.e. be C:\IBM\HTTPServer), and the correct username and password for the HTTP Admin 2011 IBM Corporation task need to be entered (as created in Step 6). Click Nex t 225

Step 16: Configure the HTTP Server (cont.)


The Confirmation panel is displayed:

Ensure all the details are correct, and then click Finish

2011 IBM Corporation

226

Step 16: Configure the HTTP Server (cont.)


The Web Server definition has been created:

Click Save to write the configuration to disk

2011 IBM Corporation

227

Step 16: Configure the HTTP Server (cont.)


Before continuing, it is important to synchronize these changes across the environment - i.e. between the DMgr and the node Go to System Administration/Nodes:

Select the connectionsNode01 and click Full Resynchonize


2011 IBM Corporation

228

Step 16: Configure the HTTP Server (cont.)


This may take a minute or so to complete. At first you will see this screen:

Wait for the synchronization to complete - when it does, the screen displays to updated status of the nodes:

2011 IBM Corporation

229

Step 16: Configure the HTTP Server (cont.)


This is a good opportunity to make a small change that helps a huge amount when managing a Lotus Connections environment Open System administration/Console Preferences Check the Synchronize changes with Nodes option, then click Apply:

This means that when a configuration change is saved to the repository, a re 2011 IBM Corporation synchronization is automatically executed 230

Step 16: Configure the HTTP Server (cont.)


Next, the WAS configuration needs to be passed to the HTTP Server so that the WAS plug-in can be used to forward requests to WAS Go to Servers/Server Types/Web Servers Generate the Plug-in:

You should see a result similar to this:

2011 IBM Corporation

231

Step 16: Configure the HTTP Server (cont.)


Next, the Plugin-in files need to be copied to the Web server key store directory Again, on the same screen, click webserver1 to open the Web Server Properties panel:

Then click Plug-in properties:

2011 IBM Corporation

232

Step 16: Configure the HTTP Server (cont.)


Click Copy to Web server key store directory:

2011 IBM Corporation

233

Step 16: Configure the HTTP Server (cont.)


Giving us this result:

This indicates the successful copy of these keys We need to restart the Web server for the plug-in changes to take effect:

2011 IBM Corporation

234

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

235

Step 17: Configure the HTTP Server for SSL


To support SSL, we create a self-signed certificate and then configure IBM HTTP Server for SSL traffic As done here, this certificate is passed to the users browser, and thus they would need to accept an untrusted certificate before continuing (behavior varies by browser) In production, this would be undesirable, to say to say the least! We would always recommend a certificate from a trusted certificate authority There are a number of methods that can be used to achieve this step (and weve tried a few!), but this one seems the most reliable and easy to follow...

2011 IBM Corporation

236

Step 17: Configure the HTTP Server for SSL (cont.)


The first step is to create a key file Start the IKEYMAN utility On Windows, this is in the Start menu - All Programs/IBM HTTP Server V7.0/Start Key Management Utility:

(On a Linux or AIX system, it is launched by executing ikeyman.sh from /opt/IBM/HTTPServer/bin - XWindows is required)

2011 IBM Corporation

237

Step 17: Configure the HTTP Server for SSL (cont.)


This panel is displayed:

Click on the left hand icon, to create a new key file


2011 IBM Corporation

238

Step 17: Configure the HTTP Server for SSL (cont.)


This panel is displayed:

Ensure Key database type is set to CMS (this is the default), enter a name for the file (e.g. webserver-key.kdb) and a location (this directory must have been created e.g. C:\IBM\Keyfiles). Click OK

Enter a password, and tick the Stash password to a file option. Click OK
2011 IBM Corporation

239

Step 17: Configure the HTTP Server for SSL (cont.)


You are returned to the IBM Key Management panel with the webserver-key.kdb opened:

2011 IBM Corporation

240

Step 17: Configure the HTTP Server for SSL (cont.)


Create a self-signed certificate. To do so, select Create/ New Self-Signed Certificate:

Add a Key Label and extend the Validity Period to a long period, were using 10 years here. If desired, add details of the organisation as well. Ensure the Common Name is correct (it is added by default). Click OK

2011 IBM Corporation

241

Step 17: Configure the HTTP Server for SSL (cont.)


The certificate now appears in the key file:

2011 IBM Corporation

242

Step 17: Configure the HTTP Server for SSL (cont.)


Ensure the HTTP Server is stopped Login to the ISC. Go to Servers/ Server Types/ Web servers

Ensure that the status of the HTTP Server is stopped (a red cross), then click webserver1

2011 IBM Corporation

243

Step 17: Configure the HTTP Server for SSL (cont.)


The HTTP Server properties are displayed:

Click Configuration File to open the HTTP Server configuration file (httpd.conf). This can also be edited manually in C:\IBM\HTTPServer\conf\httpd.conf...

2011 IBM Corporation

244

Step 17: Configure the HTTP Server for SSL (cont.)


The httpd.conf file is opened for editing in the browser:

2011 IBM Corporation

245

Step 17: Configure the HTTP Server for SSL (cont.)


The following lines need to be added to the bottom of the file: LoadModule ibm_ssl_module modules/mod_ibm_ssl.so <IfModule mod_ibm_ssl.c> Listen 0.0.0.0:443 <VirtualHost *:443> ServerName connections.ls11.us SSLEnable </VirtualHost> </IfModule> SSLDisable Keyfile "C:\IBM\Keyfiles\webserver-key.kdb" SSLStashFile "C:\IBM\Keyfiles\webserver-key.sth" (Obviously change the ServerName attribute to suit your environment)

Click OK to save the change

2011 IBM Corporation

246

Step 17: Configure the HTTP Server for SSL (cont.)


Start the HTTP Server To verify that the SSL settings are working, enter https://connections.ls11.us in a browser If the IBM HTTP Server page appears over HTTPS, this step was successful (you will likely be prompted to access the self-signed certificate as it will not be trusted by your browser):

2011 IBM Corporation

247

Step 17: Configure the HTTP Server for SSL (cont.)


The HTTP Server is now listening correctly on SSL Next, we need to add the new self-signed certificate to the WAS server so that it can be trusted by the Lotus Connections applications

2011 IBM Corporation

248

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

249

Step 18: Adding Certificates to the WebSphere Trust Store


From the ISC, go to Security/SSL Certificate and Key Management/Key stores and certificates Click the CelllDefaultTrustStore link as shown:

2011 IBM Corporation

250

Step 18: Adding Certificates to the WebSphere Trust Store (cont.)


Click Signer certificates as shown:

2011 IBM Corporation

251

Step 18: Adding Certificates to the WebSphere Trust Store (cont.)


Add the HTTP Servers signer to the trust store by clicking the Retrieve from port button:

2011 IBM Corporation

252

Step 18: Adding Certificates to the WebSphere Trust Store (cont.)


Enter the details of the HTTP Server into the next dialog, specifying a name for the alias to be created:

Click Retrieve signer information

2011 IBM Corporation

253

Step 18: Adding Certificates to the WebSphere Trust Store (cont.)


Check the details collected are correct:

Click OK

2011 IBM Corporation

254

Step 18: Adding Certificates to the WebSphere Trust Store (cont.)


Save the change (You will see that the changes are now synchronized with the node agent automatically:

Finally, restart the HTTP server to apply the changes The HTTP Server and WAS server can now communicate over SSL Next, we need to ensure that the URLs used by Lotus Connections are passed correctly to the WAS server
2011 IBM Corporation

255

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

256

Step 19: Update Web Addresses used by Lotus Connections to access Content
We need to edit the LotusConnections-config.xml file to remove the ports that the installer automatically adds, now that the HTTP Server is fronting the WAS environment The correct method to do this is to check out the file using WSAdmin, edit it and then check it back in again As discussed in our BP105 session, we are more pragmatic about this and often edit the file directly (having made a backup) However, lets do it correctly...

2011 IBM Corporation

257

Step 19: Update Web Addresses used by Lotus Connections to access Content (cont.)
First, lets remove the need to add usernames and passwords everytime we run WSAdmin and other WAS commands...
Using your favorite text editor, open C:\IBM\WebSphere\AppServer\profiles\Dmgr01\properties\soap.client.props Set: com.ibm.SOAP.securityEnabled=true com.ibm.SOAP.loginUserid=wasadmin com.ibm.SOAP.loginPassword=mypassword and save Then encode password so it is hidden in the future Start a Command Prompt
cd C:\IBM\WebSphere\AppServer\profiles\DMgr01\bin PropFilePasswordEncoder.bat ..\properties\soap.client.props com.ibm.SOAP.loginPassword

Do the same for the Connections server: Set same values in C:\IBM\WebSphere\AppServer\profiles\AppSrv01\properties\soap.client.props Then encode password so it is hidden in the future
cd C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin PropFilePasswordEncoder.bat ..\properties\soap.client.props com.ibm.SOAP.loginPassword
2011 IBM Corporation

258

Step 19: Update Web Addresses used by Lotus Connections to access Content (cont.)
Start a Command Prompt session
cd C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin wsadmin -lang jython

Once the wsadmin session has started:


execfile("..\config\bin_lc_admin\connectionsConfig.py") LCConfigService.checkOutConfig("C:\Temp","connectionsCell01")

This copies the current LotusConnections-config.xml file to C:\Temp (which needed to exist). Leave this WSAdmin session open... 2011 IBM Corporation

259

Step 19: Update Web Addresses used by Lotus Connections to access Content (cont.)
Edit C:\Temp\LotusConnections-config.xml using your favorite editor (e.g. Wordpad): Update all href= and ssl_href= values to reflect the host name of the HTTP Server. Do not include any port numbers e.g.

becomes: Do this for all features...

2011 IBM Corporation

260

Step 19: Update Web Addresses used by Lotus Connections to access Content (cont.)
Double-check your changes - it is very easy to make mistakes at this stage Save the file Go back to the WSAdmin session. Enter:
LCConfigService.checkInConfig()

Ensure the file is valid and gets checked back in Still in the WSAdmin session:
synchAllNodes()

This pushes the change to the node agent


2011 IBM Corporation

261

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

262

Step 20: Start Lotus Connections!


This completes the Web server, SSL, and certificate configuration for this scenario We now need to start the application itself. In the ISC, go to Servers/Clusters/WebSphere application server clusters:

Select the connections cluster and click Start This will kick off the start of the Connections environment:

2011 IBM Corporation

263

Step 20: Start Lotus Connections! (cont.)


We monitor the start of the Connections server by following the log file:
C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\connections_server1\SystemOut.log

e.g. using Baretail:

2011 IBM Corporation

264

Step 20: Start Lotus Connections! (cont.)


Once the cluster has started (approximately 5 minutes), we can test that the features have started by accessing:
http://connections.ls11.us/profiles (Profiles) http://connections.ls11.us/homepage (Homepage) http://connections.ls11.us/activities (Activities) http://connections.ls11.us/blogs (Blogs) http://connections.ls11.us/communities (Communities) http://connections.ls11.us/dogear (Bookmarks) http://connections.ls11.us/files (Files) http://connections.ls11.us/wikis (Wikis) http://connections.ls11.us/forum (Forum) http://connections.ls11.us/mobile (Mobile UI) http://connections.ls11.us/search (Search)

Note: always start with a fresh browser window! e.g.

2011 IBM Corporation

265

So close!
Were nearly there! The last couple of steps are upon us:
Configuring Application Administrators (users than can administer individual Lotus Connections features) Setting Blogs homepage

2011 IBM Corporation

266

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

267

Step 21: Configuring Application Administrators


Log in to the ISC and go to Applications/Application Types/WebSphere Enterprise Applications:

Click the Blogs link

2011 IBM Corporation

268

Step 21: Configuring Application Administrators (cont.)


Select "Security role to user/group mapping":

2011 IBM Corporation

269

Step 21: Configuring Application Administrators (cont.)


It is possible to map users and groups to different roles By default, there is no user assigned as admin:

Click the check box beside admin, then click Map Users...

2011 IBM Corporation

270

Step 21: Configuring Application Administrators (cont.)


Enter the user name (including wild cards if necessary) into the search string and click Search When the required user is found, select their name and click the right-facing arrow to assign this user to the role specified:

Add as many users as required, by searching and adding. Then click OK


2011 IBM Corporation

271

Step 21: Configuring Application Administrators (cont.)


When the admins have been assigned, they will be shown in the roles table:

Click OK and then Save Follow the same procedure to map groups or users to different roles in the various applications, such as admin or moderator where appropriate It is not required to restart the servers for this change to take effect, though synchronization can take a few minutes in complex clusters
2011 IBM Corporation

272

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

273

Step 22: Creating the Blogs Homepage


Log out of the ISC if still logged in Log in to Blogs (http://connections.ls11.us/blogs) as the newly-assigned administrator (in this case, Rob):

2011 IBM Corporation

274

Step 22: Creating the Blogs Homepage (cont.)


The Welcome to Blogs page is shown:

Click the New Blog Creation Page link


2011 IBM Corporation

275

Step 22: Creating the Blogs Homepage (cont.)


The Start a Blog panel is displayed:

Fill in the fields, ensuring that the Theme is set to Blogs Homepage and theBlog Corporation 2011 IBM

276

Step 22: Creating the Blogs Homepage (cont.)


The new blog is created:

Click on the Administration tab

2011 IBM Corporation

277

Step 22: Creating the Blogs Homepage (cont.)


The Blogs Configuration panel is displayed:

Set the Handle of blog to serve as Blogs Homepage to be the same as the value entered into the Blog address field when the blog was created (e.g. home) Click Save

2011 IBM Corporation

278

Step 22: Creating the Blogs Homepage (cont.)


Go to Apps/Blogs in the main Connections navigation:

Log out The Blogs feature will display its newly-configured homepage:

2011 IBM Corporation

279

Install Progress Report


Pre-Installation Tasks 1.Install DB2 2.Apply DB2 License 3.Install TDI 4.Apply TDI Fixpack 5.Install WAS 6.Install HTTP and WAS Plug-ins 7.Install WebSphere Update Installer 8.Patch WAS 9.Patch HTTP 10.Patch Plug-ins Configuring for Lotus Connections 11.Start Deployment Manager 12.Configure Federated Repository 13.Create databases for Connections 14.Populate Profiles Install Lotus Connections 15.Run Connections Installer Post-Installation Tasks 16.Configure HTTP 17.Configure HTTP for SSL 18.Add Certs to Trust Store 19.Update Web Addresses 20.Start Lotus Connections! 21.Configure Administrators 22.Configure Blogs Homepage

2011 IBM Corporation

280

We're done (but you're not !!)


We've now completed all the various steps to get Lotus Connections up and running:
Install the foundational software (DB2, etc.) Configuration of the foundation stuff (create the databases, etc.) Install Lotus Connections Do the post-installation tasks

However, your job isn't completely finished yet! NOW, you need to start thinking about:
Configuring for autostart Backups Redirect for Homepage Enabling two-way sync between Lotus Connections and your LDAP Customizing themes (well, at the very least add your logo!) Adding fields Adding sample content

2011 IBM Corporation

281

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

282

So, how long in the 'real world'


There's no absolute answer as to how long a real Lotus Connections install will take, but we all know you can't really do it in the less-than-two-hours that we did it in here in this Show-and-Tell session Luis Benitez had a great post on his blog not long ago:
I was pleasant ly surprised wit h all t he improvement s t hat have been done in t he inst aller of this new version. The inst all t ook about 6 hours t o get everything up and running. http://www.lbenitez.com/2010/12/my-experience-installing-lotus.html

In a real life environment, it will take longer than that If we were going to give a SWAG time estimate, we'd figure at least three days one for the 'foundation software' work, another for the actual Connections install(s), yet another for the post-install work. Then, add more time for customization, TDI assembly lines, customizing themes and skins, Sametime integration, etc., etc., etc.

2011 IBM Corporation

283

So, how long in the 'real world' (cont.)


It gets more complicated when Connections services are spread over multiple physical (or virtual) boxes you need multiple installs of both WAS and Connections once on each box It gets even more complicated when the Connections install team doesn't own all the parts (like, need to work with another team to implement SSO across production boxes)

2011 IBM Corporation

284

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

285

Official Documentation & Websites


Connections InfoCenter (for 2.5 documentation): publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/index.jsp Connections wiki (including LC3 documentation): www-10.lotus.com/ldd/lcwiki.nsf A 'redirect' site to all the Lotus product InfoCenters: lotusinfocenters.com A 'redirect' site to all the Lotus product wikis: lotuswikis.com Lotus Connections forum on LDD: www-10.lotus.com/ldd/lcforum.nsf IBM Lotus Connections product team blog: synch.rono.us Dave Hay: portal2portal.blogspot.com Luis Benitez's Socialize Me: www.lbenitez.com Mac Guidera: macguidera.blogspot.com
2011 IBM Corporation

286

Web Resources, blogs, etc.


Adam Brown: www.collaborationblueprint.com.au/blog Chris Miller: www.idonotes.com Jonathan Halman: jhalman.com Mikkel Heisterberg: lekkimworld.com Mitch Cohen: www.curiousmitch.com Stuart McIntyre & Sharon Bellamy: blog.collaborationmatters.com BleedYellow communities: www.bleedyellow.com/communities Always start from PlanetLotus: planetlotus.org

2011 IBM Corporation

287

Agenda
Introductions, housekeeping, etc. The Installation Environment General Advice Whats Changed for 3.0? Pre-installation Tasks Configuring for Lotus Connections Installing Lotus Connections Post-installation Tasks Summary Resources Q&A

2011 IBM Corporation

288

Legal Disclaimer
IBM Corporation 2011. 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 IBMs 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 IBMs 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.

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, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. 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.

All references to Renovations efer to a fictitious company and are used for illustration purposes only.

289

Das könnte Ihnen auch gefallen