IBM Connections 4.0 Installation From Zero To Social Hero - 1.03 with AD LDAP

For Active Directory LDAP

IBM Collaboration Solutions

IBM Connections 4.0
Installation
”From Zero to Social Hero”
Frank Altenburg | SME for IBM Sametime
IBM Collaboration Solutions
mailto:frank.altenburg@de.ibm.com

Social Business

Version 1.03, released Nov. 02. 2012
© 2009 IBM Corporation

Agenda

● Introduction

● Requirements for a IBM Connections 4.0 installation

● Architecture of a IBM Connections 4.0 Server deployment

● The 15 steps to a IBM Connections 4.0 Server deployment

Social Business 2 © 2010 IBM Corporation

Introduction
● This document describes how to implement, in a very fast way, the infrastructure for a
small deployment of a IBM Connections 4.0 Server.

● It is designed for a Proof of Concept, Proof of Technology or a small test pilot
deployment only.

● It does not contain information how to implement a high available infrastructure.

● You can start with this document just to "make your bosses happy". But to make the
system available for a larger number of users, it is recommended to invite IBM Services
to plan and implement a clustered IBM Connections infrastructure in your organization
that is fully supported.

● The Author has tested this scenario with the Hardware specification and Software
components described in this document.

● You can use the official IBM support channels for any issue you raise when you use just
this document to install your IBM Connections server.

● You need IBM Connections Licenses to download the code from Passport Advantage
and to install and use this software.


What is IBM Connections?

IBM® Connections is social networking software that consists of these applications: Activities,
Blogs, Bookmarks, Communities, Files, Forums, Home page, Metrics, Profiles, and Wikis.

Use the IBM Connections applications to accomplish the following goals:

● Activities
Collaboration tool for collecting, organizing, sharing, and reusing work that is related to
a project goal.

● Blogs
Online journals that you can use to deliver timely information with a personal touch.
You can use a blog to present your ideas and get feedback from others or learn from
the expertise of others who blog.

● Bookmarks
Social bookmarking tool for saving, organizing, and sharing Internet and intranet
bookmarks. Discover bookmarks that have been created by others with similar interests
and expertise.
Note: The application was previously named Dogear.

What is IBM Connections? (cont)

● Communities
A website where people who share a common interest can interact with one another,
share information, and exchange ideas. Community members can participate in
community-specific activities and forums, and can share blogs, bookmarks, feeds, and
files.

● Files
A common repository in which you can upload files and share them with others. Store
versions of a file, view who has downloaded a file or commented on it, and see highly
recommended files.

● Forums
A place to brainstorm and collect feedback on topics that are relevant to you and your
colleagues. Statements and comments are collected in a format that captures the
exchange of ideas and presents them as an ongoing conversation.



● Home page
A central location that provides a snapshot of the latest updates collected from IBM
Connections. Perform in-context actions on entries in your activity stream, check the
latest updates from the content and people that you are following, stay up to date with
the latest notifications and updates that require a response from you, or post your own
status updates.

● Profiles
Directory of the people in your organization, including the information you need to form
and encourage effective networks across your organization.

● Metrics
Statistics tool that collects and displays information about how people use Connections
applications. Community metrics show details on a particular community while global
metrics show information across all of Connections.



● Wikis
A tool for creating wikis that individuals, groups, and communities can use to capture,
share, and coauthor information. View page changes, recommendations, and
comments.

Together, these tools will help you and your colleagues interact with one another more
effectively.


Administrators: Deploying the preview guide to your users
The IBM® Connections 4 preview guide is available for you to distribute to your users for new
installations and upgrades to IBM Connections 4. This guide is designed to help your users
become productive on the new software quickly, and to provide them with links to
documentation resources for further help.

This guide provides the following information for this release:

● Overview of several new applications
● Important changes from the previous release
● Familiar applications that remain the same
● Links to product tours, reference cards, and product documentation
● A few key productivity tips


Administrators: Deploying the preview guide to your users

You can download the preview guide from the IBM Connections wiki at
http://www-10.lotus.com/ldd/lcwiki.nsf

There are two files available to you:

● An Adobe® PDF file, ready for emailing, printing, or distributing to your organization.
● An IBM Symphony™ ODT file that can be customized for your organization; for example,
you can add contact information for your Help Desk.

Note: This file includes instructions in blue text for customizing information. Remember to
remove these instructions before rolling out the file to your organization.

It is recommended that you distribute the guide to your users before their new IBM
Connections software is installed or updated.


Audience

This Installation Guide assumes that you have prior experience with products that support
enterprise web applications.

IBM® Connections has dependencies on a number of other products. This guide assumes that
you have a basic knowledge of those products, including how to:

● Install, configure, secure, and administer IBM WebSphere® Application Server.
● Install IBM Tivoli® Directory Server, Microsoft® Active Directory, Sun Java™ System
Directory Server, or IBM Lotus® Domino® LDAP directory, and then configure
WebSphere Application Server to use that LDAP directory with federated repositories.
● Create, manage, and drop IBM DB2®, Oracle, or Microsoft SQL Server databases.
● Install IBM HTTP Server, and then configure it to interact with IBM WebSphere
Application Server over HTTP and HTTPS.


Agenda

● Introduction





Detailed system requirements for IBM Connections

You can find the official IBM Connections System Requirements here:

IBM Connections Mail 1.0 system requirements (for IBM Connections 4) (#7036069)

IBM Connections 4.0 system requirements (#7035893)


IBM Connections 4.0 Server Prerequisites

For this pilot deployment you need
● a LDAP directory server that is supported (see system
requirements) in this example we use Active Directory LDAP
● a Windows Server 2008 64Bit box for the installation
● Network and DNS configuration
● to download the required installation files from Passport
Advantage and Fix Central
● some special administrative user accounts
● a trusted certificate (optional)


Hardware required for this Pilot Example Deployment
● 1 Server that will host the following applications:
● IBM DB2 Server
● IBM Tivoli Directory Integrator
● IBM Connections 4.0 Server
● IBM HTTP Server

Quad CPU, 16GB RAM or more, 100GB disk space or more, 64 Bit OS
1 GBit Network Interface with 1 IP addresses and a DNS Alias entry.

● Supported OS for the IBM Connections Server components are:
- Windows Server 2008, 64 Bit
- Linux Enterprise Server RHEL or SLES
- AIX

This document describes how to install the components on a Microsoft Windows
Server 2008 R2 64 Bit Service Pack 1 platform.

A 32Bit Windows OS is not supported with this IBM Connections Server
components.


OS and Network requirements
● Make sure that all servers you want to use can be resolved in DNS.

● If DNS is not available then list all full qualified server names and IP addresses
from all servers in the hosts file and publish this file to all servers.

● If your machine has multiple NIC and / or multiple IP addresses and / or multiple
hostnames and / or multiple aliases in DNS then this can cause issues that we
have not tested. We recommend to have a machine only with one NIC and one
IP address, a full qualified host name in the OS network preferences and if
required one DNS Alias for example “connections.renovations.com” if the
machine name is cryptic and you don't want to use it as access point for your
users.

● If you use Windows 2008 as Operating System, then you need to start all
installations and configurations in „Administrative mode“.


Required files for a deployment on Windows
For a Windows installation you need to download these files from Passport Advantage:

CZ19IML.zip IBM DB2 ESE 9.7 Win x86-64
CZ381ML.zip IBM DB2 ESE Restricted QS Activation 97
CZ9MKML.zip IBM Tivoli Directory Integrator V7.1 Win x86-64
C1G2JML.zip IBM WebSphere Application Server Network Deployment V7.0 Win x86-64
C1G2KML.zip IBM WebSphere Application Server Network Deployment V7.0
Supplements (1 of 2) Win x86-64
CIA3DML.exe IBM Connections 4.0 Win
CIA3GML.exe IBM Connections 4.0 Wizards Win

To update the WebSphere system to the required level you need to download these files from
Fix Central:
v9.7fp6_ntx64_server.exe DB2-ntx64-server-9.7.600.458-FP006
7.0.0-WS-WAS-WinX64-FP0000021.pak
7.0.0-WS-WASSDK-WinX64-FP0000021.pak
7.0.0-WS-IHS-WinX64-FP0000021.pak
7.0.0-WS-PLG-WinX64-FP0000021.pak
7.0.0.21-WS-WAS-IFPM65486.pak
7.0.0.21-ws-was-ifpm56596.pak
7.0.0.1-ws-was-ifpm60895.pak
7.1.0-TIV-TDI-FP0006.zip

Create a directory, for example “C:Install”, on the servers where you want to install.
Then unpack the downloaded files into this directory. Just unpack the files required for
your deployment architecture on the particular server.


The Directory “C:InstallDB2” contains the subdirectories “ESE” for the DB2 installer,
“ese_o” for the license and “SERVER” for the upgrade to FP6 installer.


IBM Connection 4 was released in Sept 2012
IBM released a Cumulative Release (CR1) for IBM Connections 4 in late Oct 2012

To update IC4 to this latest CR1 release download these files from Fix Central.

4.0.0.0-IC-Multi-Activities-CR1-LO71534.jar
4.0.0.0-IC-Multi-BLOGS-CR1-LO71537.jar
4.0.0.0-IC-Multi-BOOKMARKS-CR1-LO71552.jar
4.0.0.0-IC-Multi-COMMON-CR1-LO71564.jar
4.0.0.0-IC-Multi-COMMUNITIES-CR1-LO71544.jar
4.0.0.0-IC-Multi-CONTAINER-CR1-LO71567.jar
4.0.0.0-IC-Multi-FILES-CR1-LO71562.jar
4.0.0.0-IC-Multi-FORUMS-CR1-LO71560.jar
4.0.0.0-IC-Multi-HOMEPAGE-CR1-LO71555.jar
4.0.0.0-IC-Multi-METRICS-CR1-LO71563.jar
4.0.0.0-IC-Multi-MOBILEADMIN-CR1-LO71729.jar
4.0.0.0-IC-Multi-MOBILE-CR1-LO71556.jar
4.0.0.0-IC-Multi-MODERATION-CR1-LO71568.jar
4.0.0.0-IC-Multi-NEWS-CR1-LO71557.jar
4.0.0.0-IC-Multi-PROFILES-CR1-LO71545.jar
4.0.0.0-IC-Multi-SEARCH-CR1-LO71559.jar
4.0.0.0-IC-Multi-WIKIS-CR1-LO71561.jar
4.0-IC-Multi-UPDI-20120913.zip

Create a subdirectory “IC4_Fixes” under the “C:Install” directory. Copy the 17 JAR files
into this directory and unzip the MultiUPDI ZIP file to there.


Required technical users for IBM Connections 4.0
IBM Connections requires some technical users for components to
communicate in an authenticated mode. All of this users should be
configured so that the password never expires and never needs to be
changed.

db2admin
This user is created during installation of the DB2 server in the
Operating System. Do not create this user in advance.
It is the user for all IBM Connections related components using DB2 to
access their databases. Be sure to match the password policy
requirements of the OS.

LCUSER
This user is created manually after installation of the DB2 server in the
Operating System. Do not create this user in advance.
It is the user for all IBM Connections related components using DB2 to
access their databases. Be sure to match the password policy
requirements of the OS.


Required technical users for IBM Connections 4.0
LDAP Bind
This user is to send authenticated requests to your LDAP directory
server. This is required to get back all required information from the
LDAP. Here the Full Qualified Distinguished Name in AD is:
“CN=LDAP Bind,CN=Users,DC=ad,DC=renovations,DC=com”

wasadmin
This is the user to access the IBM WebSphere components and to
administer the system. This user must not exist in your LDAP directory.
It is created during WebSphere installation in a local file repository. You
can use the same user name and password for all components (makes
it easier) or different names and passwords. But again, it does not work
when this user exists in the LDAP.

ihsadmin
This is the user to access the IBM HTTP Server components and to
administer the system. This user must not exist in your LDAP directory.
It is created during IHS installation in a local file repository. But again, it
does not work when this user exists in the LDAP.


Agenda

● Introduction





Deployment options

Install IBM® Connections in one of three deployment topologies to achieve optimum scaling,
load balancing, and failover.

A network deployment can consist of a single server that hosts all IBM Connections
applications or two or more sets of clustered servers that share the workload. You must
configure an additional system with WebSphere® Application Server Network Deployment
Manager.

IBM Cognos® Business Intelligence is an optional component in the deployment. If used,
Cognos must be federated to the same Deployment Manager as the IBM Connections servers.
However, Cognos servers cannot be configured within an IBM Connections cluster.

A network deployment provides the administrator with a central management facility and it
ensures that users have constant access to data. It balances the workload between servers,
improves server performance, and facilitates the maintenance of performance when the
number of users increases. The added reliability also requires a larger number of systems and
experienced administrative personnel who can manage them.


When you are installing IBM Connections, you have three
deployment options:

● Small deployment
Install all IBM Connections
applications on a single
node in a single cluster. This
option is the simplest
deployment but has limited
flexibility and does not allow
individual applications to be
scaled up. All the
applications run within a
single Java™ Virtual
Machine (JVM).
Note: The diagram depicts a
topology with up to 8
servers. If you install the
servers on shared systems,
you do not need to deploy 8
separate systems.


● Medium deployment
Install a subset of applications
in separate clusters. IBM
Connections provides three
predefined cluster names
shared among all of its
applications. Use this option
to distribute applications
according to your usage
expectations. For instance,
you might anticipate higher
loads for the Profiles
application and install it in its
own cluster, while other
applications could be installed
in a different cluster. This
option allows you to maximize
the use of available hardware
and system resources to suit
your needs.


● Large deployment
Install each application in
its own cluster. IBM
Connections provides a
predefined cluster name
for each application. This
option provides the best
performance in terms of
scalability and availability
options but also requires
more system resources.
In most cases, you should
install the News and
Home page applications
in the same cluster.


Different ways to a IBM Connections 4.0 Server deployment

As you could see in the previous slides you can install Connections on one box and
have up to nearly unlimited number of boxes for a really large high available
deployment.

The largest customer environment that I know is of more then 50 boxes where all 10
IBM Connections components run on a cluster of 3 servers and a high available
dedicated IBM HTTP Server in front.

In this pilot we use just one box for the IBM Connections Server and we assume you
have a already existing Domino LDAP with user data.

Everything between one box and many boxes is possible. For your production
environment a detailed architecture design and sizing is urgently recommended.

We now will install one large box that will contain the DB2 Databases for all the IBM
Connections Applications, the TDI to move personal data from the LDAP server to the
People database, the IBM Connections server by itself and the IBM HTTP server for
caching and SSL security in front.


Agenda

● Introduction





The 15 steps to a IBM Connections 4.0 Pilot deployment

Pre Installation Tasks
1.Prepare your machine and the network
2.Prepare your LDAP
3.Install the IBM DB2 Server, add the license and create users
4.Run the Database Creation Wizard
5.Install IBM Tivoli Directory Integrator and update to FP6
6.Run the Population Wizard
7.Install IBM WebSphere Application Server, IHS and the Plugin
8.Update WAS, IHS and Plugin to the required level
9.Setup LDAP with Federated Repositories in WAS


The 15 steps to a IBM Connections 4.0 Pilot deployment

Installation
10.Install the IBM Connections Server

Post Installation Tasks
11.Reviewing the JVM heap size
12.Configure the IBM HTTP Server IHS
13.Configuring the Home page administrator
14.Configure services to start and stop the server automatic
15.Install the CR1 Fixpack


STEP ONE: Prepare your machine and the network

Summary

Before you can install your IBM Connections Server environment, some things needs to
be checked and prepared.


The machine that you run the IBM Connections 4.0 Server and the DB2 Database Server
can be a virtual machine or a hardware box. Both work.

It is possible to use Linux as OS, but this document describes how to install on Windows.

If you use Linux you can use most parts of this document and most installation instructions
and screen shots are identical. Mostly the paths are different.
In Linux it is recommended to have the graphical system installed for this installation and
then use a x-server on our client.

These instructions work with Windows Server 2008 in 64Bit only. You can use the R2
Version of the supported OS.

Be sure that your Firewall Admin has opened all ports in the firewalls. Test all connections
using the telnet command in a CMD line window.

Be sure the used host names or DNS alias is listed in the DNS and can be used and
resolved in the internet and in your intranet.


More information can be found in the official IBM Connections
Documentation at this URL:

http://www-10.lotus.com/ldd/lcwiki.nsf/xpDocViewer.xsp?
lookupName=IBM+Connections+4.0+documentation

The IBM Connections Installation and the IBM Sametime Installation
– “From Zero To Hero” documents can be found here:

https://www-304.ibm.com/connections/blogs/sametimeguru/?
lang=en_us


STEP TWO: Prepare your LDAP
Before you begin
Ensure that you have installed a supported LDAP directory. For more
information about supported LDAP directories, see the IBM Connections
detailed system requirements topic.

To ensure that the Profiles population wizard can return the maximum number
of records from your LDAP directory, set the Size Limit parameter in your
LDAP configuration to match the number of users in the directory. For
example, if your directory has 100,000 users, set this parameter to 100000.
For more information, see the documentation for your LDAP directory. If you
cannot set the Size Limit parameter, you could run the wizard multiple times.
Alternatively, you could write a JavaScript™ function to split the original LDAP
search filter, then run the collect_dns_iterate.bat file, and finally run the
populate_from_dns_files.bat file.

Note: For information about a limitation in environments with a Turkish locale,
see the Base entry comparison for Turkish locale technote.

The LDAP Server
In most environments a LDAP server is already present. If you use Domino it
is simple to just enable LDAP on one of the Domino Directory Servers. If you
use an existing LDAP Server other then Domino, it is important to use a V3
compliant LDAP.

Make sure you have all relevant data from the LDAP system. (use ldapsearch,
Apache LDAP studio or another LDAP browser to get the relevant LDAP
information - an LDIF extract of a user and a group)

A security related recommendation is to have a Bind DN. This means a user
record in the LDAP that can be used for authenticated access to the data in
the LDAP server. We use the „LDAP Bind“ user in this example.
This is a technical user. His password should never expire. Otherwise the
systems can not connect to the LDAP server anymore when this password is
expired.

The LDAP connection can be configured with SSL encryption. To configure
your Connections Servers connecting to LDAP with SSL (LDAPS), additional
steps are required. Make sure that you have access to the required certificate.
But we recommend to start without SSL and when all components work, start
implementing LDAPS.


An LDAPSEARCH response for a AD user:


A LDAPSEARCH response for a AD group:


STEP THREE: Install the IBM DB2 Server, add the
license and create users
Summary

This step installs the IBM DB2 Database Server release 9.7 and the FP6
update, installs the license key into the server and then creating a user for
IBM Connections to connect to the databases.


You need to check your local password security policy that the users can be created
and the passwords you want to use can be used. In your Windows 2008 server click on
“Start” - “Administrative Tools” - “Local Security Policy”.


If the Password complexity setting is enabled then the password must contain characters
in upper and lower case and a number. If you want easier passwords the set this flag to
“Disabled”.


To disable just select the “Disabled” check box and click the “OK” button. Then close
the Local Security editor.


You can start now with the DB2 installation. Open your Windows Explorer or just the
“Computer” and navigate to the unpacked installation files for IBM DB2. In this example
this can be found in “C:InstallDB2ESEimage”. Right click the “setup.exe” file and
then “Run as Administrator”.


Click “Install a Product” on the left side.


Click the “Install New” button under the DB2 Enterprise Server Edition 9.7 section.


It takes some seconds to load the DB2 Setup Wizard.


The DB2 Setup Wizard is now initializing.


The DB2 Setup Wizard is now ready to go. Click the “Next” button to continue.


Select the check box to accept the terms in the license agreement. Then click the
“Next” button to continue.


Leave the “Typical” installation defaults and just click the “Next” button to
continue.


Select the first option “Install DB2 Enterprise Server Edition on this computer” and
click the “Next” button to continue.


We recommend to remove the “Program Files” part in the path. It works with the default
path as well. Click the “Next” button to continue.

We recommend to use path names without spaces (as some scripts may require this) and
also shorten the path name so that the typical limits of some operating systems and
applications for path + file name length are avoided.


We recommend to leave the default user name “db2admin” in here. But enter a password
that fits the password security settings twice and then click the “Next” button to continue.


Just click the “Next” button to continue.


Click the “Next” button to continue.


Un-check the box “Set up your DB2 Server to send notifications”. Then click the


Click the “Install” button to start the installation.


The installation of the DB2 Server will take approximately 5 to 10 Minutes.


Click the “Finish” button to end the Installation Wizard.


After some seconds this “DB2 First Steps” window appears. You can close it.


Next step is to install the IBM DB2 FP6. In your File Explorer navigate to the directory
“C:InstallDB2Server”. Then right click the “Setup” icon and select “Run as administrator”.


Click the “Install a Product” link on the left side.


Under the “DB2 Enterprise Server Edition Version 9.7 Fix Pack 6” click the “Work with
Existing” button.


Click the “Launch DB2 Setup wizard” button to continue.


Click the “Yes” button to stop the running services and tasks.


The DB2 Fix Pack 6 installation takes approximately 4 – 5 minutes.


Click the “Finish” button to exit the Install wizard.


Close the “First Steps ...” window.


Now we need to add the DB2 License. We need a DB2 command line window with
Administrator privileges. Click on “Start” - “All Programs” - “IBM DB2” - “DB2COPY1”
- “Command Line Tools” - “Command Window - Administrator”.


Enter the command “db2licm -l”. you will see that the license is not registered.


Enter the command “db2licm -a C:installDB2ese_odb2licensedb2ese_o.lic”.
Dependant of the path to where you have unpacked the license ZIP file.


The license was added successfully.


Confirm that the license was added by entering again the command “db2licm -l”.


Configuring the DB2 databases for unicode ensures that DB2 tools like export and import
do not corrupt unicode data.
In the existing actual DB2 command window run the following commands:
“db2set DB2CODEPAGE=1208”
“db2stop force”
“db2start”
Run the following commands to check the new configuration:
“db2set”
This should return DB2CODEPAGE=1208. If not, it is not configured correctly and you
should try Step 4 again.


Next step is to create a specific user for the IBM Connections Server to access the
databases on the IBM DB2 Server. Click “Start” - “Administrative Tools” - “Computer
Management”.


Select “System Tools” - “Local Users and Groups” - “Users”.


In the Menu click “Action” and then “New User...”.


For this pilot we recommend to use the name “LCUSER” because this is the default
name used in the database creation wizard. Enter a valid password (take note on the
Password security policy). Deselect the box “User must change password at next
logon” and select the box “Password never expires”. Then click the “Create” button.


We don't need an other user. So just click the “Close” button.


The user “LCUSER” is now created. Double click the user to administer the group
memberships.


Click the “Member Of” tab.


Click the “Add...” button.


Enter the goup name “DB2USERS” and click the “Check Names” button.


The group was found in the system so you can click the “OK” button.


We are done with creation and configuration of the user. Click the “OK” button
to close the window. Then close the “Computer Management” console.


STEP FOUR: Run the Database Creation Wizard

Summary

When you are creating a database either with the database wizard or SQL
scripts, you must log into the system where the database is hosted with
the database administrator account. The default values for DB2® are
db2admin on Microsoft™ Windows™.

If you use only one database instance and if that instance includes other
databases besides IBM Connections, configure the numdb parameter to
match the total number of databases on the instance.


Now open a file explorer and navigate to the directory “C:InstallWizards”. Right Click
the “dbWizard” and select “Run as Administrator”.


The Database Wizard for IBM Connections is starting up. Click the


In this example we dont want to install the Cognos part. We don't need the “Metrics” and
“Cognos” databases. Deselect them and click the “Next” button to continue.


Click the “Create” button to continue.


Click the “Execute” button to continue.


The Database creation wizard is now creating the required databases. This step takes
approximately 10 minutes.


To see if all works fine just click the “Open Log” button.


You can see a log file for each individual step that the wizard is creating. To view a log file
you can open it with a double click.


The IBM Connections Database wizard has now successfully created the required
databases and granted access for the LCUSER account. Click the “Finish” button to end
the wizard.


The DB2 Server uses a configuration parameter for the maximum number of databases that
can be opened simultaneously. This is set to 8 by default. We have created 10 databases
and the wizard has set this parameter to 12. To enable the new setting we need to stop and
start the database server. One way we have already seen after the import of the license file
with the db2stop and db2start commands. Here is an other way to stop and start the DB2
database server:
In your task bar you can find the green bubble for DB2. Right click this bubble and then
select “Stop (DB2)”.


Click the “OK” button to continue.


You can now see the red square on the bubble. This means the DB2 Database server is
stopped.
To start it again right click on the bubble and select “Start (DB2)”.


STEP FIVE: Install the IBM Tivoli Directory
Integrator and update to FP6

Summary

This step installs the Tivoli Directory Integrator component on your IBM
Connections Server machine to fill your Profiles Database with predefined
information from your LDAP and other sources.


In your File Explorer navigate to the directory “C:InstallTDI” and right click the
“launchpad”. Then click the “Run as Administrator” option.


Click the “Install IBM Tivoli Directory Integrator” link.


Click the “Tivoli Directory Integrator 7.1 Installer” link


The TDI installer is initializing.


Accept he terms in the license agreement and click the “Next” button to continue.


Remove the part with the unwanted space in the path and click the “Next” button.


Select the “Do not specify – use current working directory at startup time” option and


Click the “Install” button to continue.


The Tivoli Directory Integrator is installing. This step takes approximately 2-3 minutes.


When the installation has finished, deselect the “Start configuration Editor” check box
and click the “Done” button to exit the installer.


Click the “Exit” link to continue.


Click the “OK” button to end this installation step.


Open a CMD-Line window in Administrative mode and enter the command “cd
Install7.1.0-TIV-TDI-FP0006” to change to the TDI FP6 directory. Then enter the
command “IBMTDIV7.1binapplyUpdate.bat -update TDI-7.1-FP0006.zip”.


The FP6 installation takes approximately 2 minutes. Then you should see this messages.


To control the updated version is correct enter the command
“IBMTDIV7.1binapplyUpdates.bat -queryreg”. You should see this response.


STEP SIX: Run the Population Wizard

Before you begin
● Spend time planning your Profiles population, integration, and customization.
● Involve all the relevant stakeholders at an early stage of the planning process.

● If possible, phase the Profiles rollout and get feedback from pilot users.

● Prepopulate Profiles photos.

● Plan for business card use and for Sametime® presence awareness.

● Ensure that Tivoli® Directory Integrator is correctly configured.

● Consider using Tivoli Directory Integrator to populate the LDAP and then to populate the

Profiles database.

In this example we make it simple by just running the population wizard and copy the data
from the LDAP to the PEOPLE DB2 database.


Edit the “ibmdisrv.bat” file to increase runtime memory and disable the JIT compiler. To
increase the runtime memory, add the two “-Xms256M -Xmx1024M” space-separated
arguments to the Java™ invocation command; to disable the JIT compiler, add the “-
Xnojit” argument. The ibmdisrv file is stored in the TDI directory.

In your file explorer navigate to the directory “C:IBMTDIV7.1”.


Then right click the file “ibmdisrv.bat” and select “Edit”.


In the line starting with “%TDI_JAVA_PROGRAM%” add the parameters “-Xms256M
-Xmx1024M -Xnojit”. See below in the screen shot, how this should look like. Then save
and close the file.


In your File Explorer navigate to the “C:InstallWizards” directory, right click the file
“populationwizard.bat” and select “Run as administrator”


Select the path “C:IBMTDIV7.1” to where you have installed your TDI components, and


In the “Host name” field enter the host name of your IBM DB2 server. In this case it is our
machine where you install connections. In the “JDBC Driver library path” line enter the
path where the 2 files db2jcc.jar and db2jcc_license_cu.jar can be found. In this installation
you can use “C:IBMSQLLIBJAVA”. In the Password field enter the password for the
“LCUSER” that you have created after the DB2 Server installation.
Then click the “Next” button to continue.


In the “LDAP server name” field enter the host name of your LDAP server. Change the
“LDAP Server port” to the AD LDAP port. We use the port “3268”.


Enter the LDAP Bind User name and password. Then click the “Next” button to
continue.


If you are using Domino LDAP, leave the “LDAP user search base” field empty. If you
use another LDAP then this field has to be filled. Mostly it detects the base DN's and you
can just choose the right one. For AD LDAP you need to change the “LDAP user search
filter” field. Here you need to enter:
“(&(sAMAccountName=*)(opjectclass=organizationalPerson))”.


With AD LDAP you can leave everything as it is. Then click the “Next” button to continue.


In this simple pilot we dont use any more csv files for additional data. Just click the “Next”
button to continue.


Click the “Configure” button to start the data population.


The population wizard is now working. If you want to see the logs click the “Open Log”
button.


The population wizard has successfully populated the data from LDAP to the IBM DB2
PEOPLEDB database. Click the “Finish” button to continue.


STEP SEVEN: Install IBM WebSphere Application
Server, IBM HTTP Server and the HTTP Server
Plugins
Before you begin
WebSphere Application Server Network Deployment is provided with IBM
Connections.

To establish an environment with one Deployment Manager and one or more
managed nodes, use the following table to determine the installation option that
you should choose. The IBM Connections installation wizard creates server
instances that require each node to have an application server. Choose one of
these options when installing WebSphere Application Server to ensure that each
node has an application server.

IBM Connections deployment
● Deployment Manager and one node on the same system (use this now)

● Deployment Manager and nodes on separate systems


To install IBM WebSphere Application Server for IBM Connections, open your File Explorer
and navigate to the directory “C:InstallWAS”. Then right click the “launchpad” and select
“Run as administrator”.


Click the “WebSphere Application Server Installation” link.


Click the “Launch the installation wizard for the WebSphere Application Server
Network Deployment” link.


Accept the terms in the license agreement and click the “Next” button to continue.


Remove the part with the blank character in the path and click the “Next” button to
continue.


In this pilot we want to have all IBM connections components on a single box. So we use
the “Cell...” deployment. Then click the “Next” button to continue.


Leave the “Enable administrative security” checked and enter a username and password
for your WebSphere Administrator user. Be sure that this user does not exist in your LDAP
that you plan to use. Click the “Next” button to continue.


IBM WebSphere Application Server is now installing. This step takes approximately 5 to 10
minutes.


The installer has successfully installed the IBM WebSphere Application Server Network
Deployment as a Cell. Click the “Finish” button to continue.


In this “First Steps” screen just click the “Exit” link to close. For this IBM Connections
installation it is not required to do the Installation verification.


Next step is to install the IBM HTTP Server. Click the “IBM HTTP Server Installation” link.


Click the “Launch the installation wizard for IBM HTTP Server” link.


Remove the part with the blank character in the path and click the “Next” button to continue.


Select “Log on as a local system account” and click the “Next” button to continue.


Enter a user name and password for your IBM HTTP Server Administrator. This user should
not exist in the LDAP that you plan to use. Then click the “Next” button to continue.


The IBM HTTP Server is now installing. This step takes approximately 2-3 minutes.


IBM HTTP Server is now installed successfully. Click the “Finish” button to continue.


STEP EIGHT: Update IBM WebSphere Application
Server, IBM HTTP Server and the IHS Plugin to
the required level
Summary

In this step you install the IBM WebSphere Update Installer and update the
already installed components (IBM WebSphere Application Server, IBM HTTP
Server and IBM HTTP Server Plugin) to the required fix and patch level for IBM
Connections 4.0.


Click the “IBM Update Installer for WebSphere Software Installation” link.


Click the “Launch the installation wizard for IBM Update Installer” link.


Remove the part with the blank character in the path and click the “Next” button to continue.


The IBM Update Installer is now installing. This step takes approximately 2-3 minutes.


Check the “Lanuch IBM Update Installer...” check box and click the “Finish” button to
continue.


Change the path using the “Browse...” button to your “C:Install” directory. Then click the


Confirm that this 7 fixes are selected. Then click the “Next” button to continue.


The IBM Update Installer installs the selected fixes. This step takes approximately 4-5
minutes.


Click the “Relaunch” button now, because we need to update the IHS and the Plugin.


Select the “C:IBMHTTPServer” directory now and then click the “Next” button to continue.


The IBM Update Installer is installing the fixpack for the IBM HTTP Server. This step takes
approximately 1-2 minutes.


It is still not finished with updating. Click the “Relaunch” button again to continue.


Select the “C:IBMHTTPServerPlugins” directory and click the “Next” button to continue.


The IBM Update Installer is now installing the required fixes to the IBM HTTP Server
Plugin. This step takes approximately 1-2 minutes.


Updating is finished now. Click the “Finish” button to continue.


Click the “Exit” link.


STEP NINE: Setup LDAP with Federated Repositories
in IBM WebSphere Application Server

Summary

Use this procedure to configure your installed WebSphere Server to connect
to your LDAP server for user and group look-ups and for user authentication.

In this document we use a Microsoft Active Directory LDAP. If you plan to
use Lotus Domino LDAP then consult the Domino LDAP version of this
document.


The IBM WebSphere Application Server Deployment Manager “dmgr” needs to be started
first. In the “Start” menue click on “All Programs” - “IBM WebSphere” - “Application Server
Network Deployment” - Profiles” - “Dmgr01” - “Start the deployment manager”.


The dmgr server process is starting up. Wait until this has finished and the cmd line
window disappears.


In the Task Manager you can see the “java.exe” process.


Open your favorite browser and enter the URL to your dmgr admin interface. In this example
we use: “http://connections.renovations.com:9060/admin”


In Microsoft Internet Explorer just select “Continue loading the Web Site”. In Mozilla
Firefox select “I Understand the Risks”.


Then click the “Add Exception...” button.


Then click the “Get Certificate” button and the “Confirm Security Exception” button.


Enter the user name and password of your IBM WebSphere Application Server
Administrator user. Then click the “Log in” button.


You have now entered the IBM WebSphere Integrated Solutions Console. The Admin
Console for most of the WebSphere administration tasks. Here click the “Security” link on
the left side.


Click the “Global security” link.


At the bottom of the screen click the “Configure...” button.


Click the “Add Base entry to Realm...” button.


Click the “Add Repository...” button.


In this form you need to fill all data of your LDAP. The “Repository Identifier” is just a name
that you can chose. Select your “Directory type”. Enter the “Primary host name” and the
“Port” of your LDAP. Fill the “Bind distinguished name” and “Bind password” fields and in
the “Login Properties” field enter “uid;mail;cn”.


At the bottom of the form click the “Apply” button.


Click the “Save” link to save the configuration changes.


Your new created Repository configuration should appear in the “Repository” field now.
Enter a value in the “Distinguished name of a base entry that uniquely identifies
this ...”. We recommend to use the baseDN of your AD LDAP. Fill the second field with the
baseDN of your AD LDAP. Then click the “Apply” button.


Click the “Save” link to save the last configuration changes.


Click the “Save” link again.


Click the “Global security” link on the top of the screen.


Click the “Set as current” button.


Check the “Enable application security” check box.


Now click the “Apply” button.


Click the “Save” link to save the last changes.


Log out from the Integrated Solutions Console by clicking the “Logout” link.


Changes in the Security configuration always require to restart the deployment manager
and all configured nodes and servers. To stop the dmgr process click the “Start” menu and
then “All Programs” - “IBM WebSphere” - “Application Server Network Deployment” -
“Profiles” - “Dmgr01” - “Stop the deployment manager”.


The Deployment Manager dmgr is now stopping. When the CMD-Line window disappears
the dmgr has stopped.


Now start again the dmgr process click the “Start” menu and then “All Programs” - “IBM
WebSphere” - “Application Server Network Deployment” - “Profiles” - “Dmgr01” - “Start
the deployment manager”.


You want to be sure that the LDAP connection is working. Open your browser and navigate
to the Integrated Solutions Console. Did you bookmark it before?


Log in with your IBM WebSphere Application Server Administrator user name and
password.


Click on “Users and Groups” and then on “Manage Users”.


Click the “Search” button.


Aaaaah – the AD Users are listed.......


To check the groups click on “Manage Groups”.


Click the “Search” button.


The groups in your AD LDAP are listed. Now the LDAP configuration has finished
successfully.


STEP TEN: Install the IBM Connections Server

B e fo re y o u b e g in

Ensure that you complete all the prerequisite tasks that are relevant for your
environment. For more information, see the Before installing topic.

A b o u t th is ta s k
To install IBM Connections, run the IBM Installation Manager wizard on the
system where the Deployment Manager is installed.


If an error occurs during installation, IBM Installation Manager cancels the installation and
rolls back the installation files. Installation errors are usually caused by environment
problems such as insufficient disk space, privilege issues, or corruption of a WebSphere®
profile. If your installation is canceled, complete the following steps:

● Identify and resolve the error that caused the cancellation. After canceling the installation,
IBM Installation Manager displays an error message with an error code. You can look up the
error code in the Installation error messages topic or check the log files.

● Restore the Deployment Manager profile from your backup.

● Delete the connections_root directory.

● Start this task again.


Do not stop the dmgr process. It must be running for the IBM Connections Server
installation.
Open your File Explorer and navigate to the directory
“C:InstallIBM_Connections_Install”. Right click the “Launchpad” and select “Run as
administrator”.


On the left side click “Install IBM Connections 4.0.0”.


Click “Launch the IBM Connections 4.0.0 install wizard”.


Remove the part with the blank character in both path fields and click the “Next” button to
continue.


In this pilot we don't want to install the Metrics part with Cognos components. Un check the
“Metrics” check box and click the “Next” button to continue.


Click the “Browse” button and select the IBM WebSphere Application Server directory
“C:IBMWebSphereAppServer”. Then click the “OK” button.


Enter the host name of your Connections Server and the password of the IBM WebSphere
Application Server Administrator. Then click the “Validate” button.


The install wizard checks the connectivity to the dmgr process of your
WebSphere Application Server.

When the validation was successful click the “OK” button to continue.


Select the first Deployment type “Small – all applications are grouped on the same
cluster”.


Enter a name for the cluster. We just use “CLUSTER” in this example. Select the node and
enter a name for the server. In this example we use “connections_server”. Then click the


Next step is to configure the IBM DB2 server and databases. Enter the name of your IBM
DB2 server. We use just “connections.renovations.com” because the IBM DB2 Server is
on the same box as the IBM Connections server. Select the path to the JDBC driver. Here it
is “C:IBMSQLLIBjava”.


Check the box “Use the same password for all applications” and enter the password of
your “LCUSER” user that you have created after the IBM DB2 Server installation. Then click
the “Validate” button.


The install wizard is testing the connection to all required databases on the IBM DB2
Server.

When the validation was successful click the “OK” button.


Remove the part with the blank character in the two path lines and click the “Validate”
button.


When the validation was successful click the “OK” button to continue.

It is known that the validation process is not consistent in the install wizard. Sometimes
you get a button dialog “Validation successful” and sometime just the “Validation”
button text that changes to “Validated”. Don't worry and take it as it is.


In this installation we dont want to configure notification. Just select “None”.


IBM Connections is now installing. This step takes approximately 60 to 90 minutes. A good
time to go for lunch.


You have finished your lunch and can see this screen now? Fine, you are nearly done. Just
the Post Install Tasks need to be done. Click the “Finish” button to close the Install Manager.


Click the “Exit” link to close the launchpad.


You need to restart your dmgr process. We did this already before. Click “Start” - “All
Programs” - “IBM WebSphere” - “Application Server Network Deployment” - “Profiles” -
“Dmgr01” - “Stop the deployment manager”.


The Task Manager does not show any “java.exe” tasks.


And now starting the Deployment Manager. Click “Start” - “All Programs” - “IBM
WebSphere” - “Application Server Network Deployment” - “Profiles” - “Dmgr01” -
“Start the deployment manager”.


The installer has installed the IBM Connections Server into the existing node. You need to
start the node. First you need to start the nodeagent and synchronize the configuration.
Open a CMD line window and navigate to the profile directory with the command “cd
C:IBMWebAphereAppServerprofilesAppSrv01bin”. Then enter the command
“startnode”.


The nodeagent has started successful.


In the task manager you can see that the process db2syscs.exe now uses much more
memory and 2 java.exe processes are running. One is the dmgr and the other is the
nodeagent. They are consuming a lot of CPU time in the next minutes because they are
synchronizing the configuration from the dmgr to the node.


The synchronization process is starting automatically. You don't need to initiate it manually. To
check that it works, open a File Explorer and navigate to the directory
“C:IBMWebSphereAppServerprofilesAppSrv01installedAppsconnectionsCell01”. You
should see that the synchronization creates this 16 directories. Wait until all of them are
created and the 2 java.exe process in the task manager don't consume CPU time anymore.


Open your browser and navigate to the Integrated Solutions Console. Log in with your IBM
WebSphere Application Server Administrator account.


The official IBM Connections documentation says to do a full resynchronize. Lets do it to
be sure all works properly. In the ISC navigate to “System administration” - “Nodes”.


Select the “connectionsNode01” node and click the “Full Resynchronize” button.


The synchronization was initiated. This takes normally only some seconds. But wait a
minute to be sure all works well.


In the past we used the start menu to start and stop the dmgr service. Now we use an
other method to start and stop the IBM WebSphere services. Reuse the CMD window
from before and enter the command “stopserver nodeagent -username wasadmin
-password passw0rd”. Where “wasadmin” is your IBM WebSphere Application Server
Administrator name and “passw0rd” is the password for this user.


The nodeagent process has stopped successfully.


Change to the dmgr profile with the command “cd ....Dmgr01bin” and enter the
command “stopserver dmgr -username wasadmin -password passw0rd”. (see the
previous slides regarding username and password)


The dmgr process has stopped successfully. Now restart it with the command
“startserver dmgr”. You can use the command “startmanager” as well.


The dmgr has started successfully. Now change to the application server directory with the
command “cd ....AppSrv01bin”. Then enter the command “startserver nodeagent”. You
can use the command “startnode” as well.


The nodeagent has started successfully. Start the IBM Connections Server now with the
command “startserver connections_server”.


Starting the connections server can take up to 5 minutes. Be sure that you don't see any
java exceptions in your SystemOut.log.


Lets have a look if your new installed IBM Connections Server works. Open your browser and
enter the URL: “http://connections.renovations.com:9081/homepage”.


Enter the user name and password of a LDAP user and click the “Log In” button.


Here we are. Select the “Do not show this screen at startup” and click the “My Page” link.


Wow – Connections 4.0 is working. How long did you need for this installation?


STEP ELEVEN: Reviewing the JVM heap size

A b o ut th is ta s k

If you selected the Small or Medium deployment option when you installed IBM®
Connections, IBM Installation Manager set the Maximum Heap Size of the Java
Virtual Machine (JVM) on each application server. This setting is designed to avoid
out-of-memory errors.

Review the heap size on each server to ensure that you are allocating enough
memory for IBM Connections but also to ensure that you are not allocating more
memory than the physical capabilities of the systems where the JVMs are deployed.

Whether you installed a Small, Medium, or Large deployment of IBM Connections,
you should review the JVM heap sizes in your deployment and make adjustments, if
necessary.

To review the JVM heap size, complete the following steps:


Start your Browser and log in to the Integrated Solutions Console with your IBM WebSphere
Application Server Administrator account.


Click on “Servers” - “Server Types” - “WebSphere application servers”.


The test and demonstration server that was created during installation of the IBM
WebSphere Application Server is not required anymore. Check the check box near the
“server1” and click the “Delete” button.


Click the “connections_server” link.


On the right side click “Java and Process Management” and then “Process definition”.


Click “Java Virtual Machine”.


Check that the field “Maximum Heap Size” contains “2506” MB.


STEP TWELVE: Configure the IBM HTTP Server
When you have successfully installed IBM Connections to run on WebSphere®
Application Server, you can configure IBM HTTP Server to handle web traffic by
completing the following tasks:

1.Defining IBM HTTP Server
Define IBM HTTP Server to manage web connections.

2.Configuring IBM HTTP Server for SSL
Configure IBM HTTP Server to use the SSL protocol.

3.Adding certificates to the WebSphere trust store
Import a self-signed IBM HTTP Server certificate into the default trust store of
IBM WebSphere Application Server.

4.Updating web addresses in IBM HTTP Server
Update the web addresses that IBM HTTP Server uses to access IBM
Connections applications.


Defining IBM HTTP Server

Before you begin
Install web server plug-ins for IBM HTTP Server, if they are not already installed. For more
information, go to the Installing web server plug-in web site.

About this task
IBM Connections uses a web server as the entry point for all the applications.

This procedure describes how to create a web server using the Integrated Solutions
Console. There are other ways to create the web server. See the IBM WebSphere
Application Server information center for more information.


Go to your Services view and start the “IBM HTTP Administrator 7.0” service.


The service has now started successfully.


In the Integrated Solutions Console Browser window click on “System Administration” -
“Nodes”.


Click the “Add Node” button.


Select “Unmanaged node” and click the “Next” button to continue.


Enter a name for this node and the host name of your connections server. In this example
we use just “IHS_Node” and the connections server DNS name
“connections.renovations.com”. Then click the “OK” button to continue.


The unmanaged “IHS_Node” is now created successfully.


Now click “Servers” - “Server Types” - “Web servers”.


Click the “New” button to create a new Web server.


Select the just created “IHS_Node” node and enter a name for this Web server. We
recommend to use the name “webserver1” because it is the standard. Then click the “Next”
button to continue.


Remove the part with the blank character in the two path lines. Enter the IBM HTTP Server
Administrator Account name and password. Then Click the “Next” button to continue.


Click the “Finish” button to continue.


Click “System administration” - “Nodes”.


Select all nodes and click the “Synchronize” button.


Next click “Servers” - “Server Types” - “Web servers”.


Select the “webserver1” and click the “Generate Plug-in” button.


The Web Server Plug-in configuration file was created successfully.


Select the “webserver1” again and click the “Propagate Plug-in” button.


The Web Server Plug-in configuration file was propagated successfully.


Open the web server configuration by clicking the “webserver1” link.


Click the “Plug-in properties” link on the right side.


Click the “Copy to Web server key store directory” button.


The Plug-in keyring file is propagated successfully.


Go back to “Servers” - “Server Types” - “Web servers”.


Select the “webserver1” and click the “Start” button.


The Web Server has started successfully.


Configuring IBM HTTP Server for SSL

About this task
To support SSL, create a self-signed certificate and then configure IBM HTTP Server for
SSL traffic. If you use this certificate in production, users might receiver warning
messages from their browsers. In a typical production deployment, you would use a
certificate from a trusted certificate authority.

To configure IBM HTTP Server for SSL, complete the following steps:


In your File explorer navigate to the directory “C:IBMHTTPServerjavajrebin”. Double
click the “ikeyman” application.


Click the button to create a new keyring file.


Enter a file name for the keyring file. In this example we use “key.kdb”. Select the location
to save the keyring file. We use just “C:IBMHTTPServer” in this example. Then click the
“OK” button to continue.


Enter a password twice to secure your keyring file. It is important to check the “Stash
password to a file” option. Then click the “OK” button to continue.


Click the “New Self Signed...” button.


Give the certificate a name. In this example we use “Connections”. Then click the
“OK” button to continue.


The new self signed certificate is created and stored in the keyring file. Close the ikeyman
application.


In the File Explorer navigate to the directory “C:IBMHTTPServer”. There you can see the 3
files that where created with the ikeyman application.


In the Integrated Solutions Console navigate to “Servers” - “Server Types” - “Web servers”.


Select the “webserver1” server and click the “Stop” button.


The webserver1 has stopped successfully. Now click the “webserver1” link to open the
configuration page.


On the right side click the “Configuration File” link.


At the end of the file add this lines:


LoadModule ibm_ssl_module modules/mod_ibm_ssl.so

<IfModule mod_ibm_ssl.c>

Listen 0.0.0.0:443

<VirtualHost *:443>

ServerName connections.renovations.com

#DocumentRoot C:IBMHTTPServerhtdocs

SSLEnable

</VirtualHost>

</IfModule>

SSLDisable

Keyfile "C:IBMHTTPServerkey.kdb"

SSLStashFile "C:IBMHTTPServerkey.sth"


Click the “Apply” button to continue.


Now click the “OK” button to close the editor.


Click the “Web servers” link.


Select the webserver1 and click the “Start” button.


The Web server has started successfully.


Logout from the Integrated Solutions Console


The IBM Connections documentation contains two additional steps here:

● Adding certificates to the WebSphere trust store
● Adding certificates to IBM HTTP Server

In a production environment, specially if the IBM HTTP server is on a separate box and
communicates with the IBM WebSphere Application Server through the LAN, it is
recommended to have this communication SSL encrypted. Then you need to configure
this two additional steps.

In this test environment we already have copied the keyring file from IBM WebSphere to
the IHS servers Plugin directory in an earlier step. And that makes this 2 steps obsolete.


Updating web addresses in IBM HTTP Server

By default, the web address that you enter to access IBM Connections applications
includes the port number for each application. To avoid using port numbers, update the
web addresses by editing the LotusConnections-config.xml file. IBM HTTP Server can
then redirect requests to the appropriate port for each application.

To update the web addresses to your IBM Connections applications, complete the
following steps:


First you need to stop your IBM Connections Application Server.
Open a CMD Line window and navigate to the directory “cd
C:IBMWebSphereAppServerprofilesDmgr01bin”. Then enter the command
“stopserver connections_server -username wasadmin -password passw0rd”.
Wait until the server has stopped.


When the server has stopped, change the directory to the Dmgr Profile directory with the
command “cd IBMWebSphereAppServerprofilesDmgr01bin”. Then enter the
command “wsadmin -lang jython -username wasadmin -password passw0rd”.


The wsadmin command has started successfully. Now you can see the “wsadmin>”
command prompt.


To initialize the Connections Administration enter the command
“execfile(“..configbin_lc_adminconnectionsConfig.py”)”.


Then enter the command to check out the Connections Configuration file:
“LCConfigService.checkOutConfig(“C:Install”,”connectionsCell01”)”.
The first parameter in the command contains the destination directory. This directory must
exist. If you use the “C:Install” directory you can be sure it exists. The second parameter in
the command is the name of your Cell. It is based on the hostname of the machine. You
can find it here: “C:IBMWebSphereAppServerprofilesDmgr01configcellsxxxxx”


Open your File Explorer and navigate to the directory “C:Install”. Then open the file
“LotusConnections-config.xml” for editing.


In this file you can find many lines containing the port number in the path. This needs to be
changed.


Find the string
href=”http://connections.renovations.com:9081”
Replace with
href=”http://connections.renovations.com”
Click the “Replace All” button.


Find the string
ssl_href=”https://connections.renovations.com:9444”
Replace with
ssl_href=”https://connections.renovations.com”


Find the string
href=”https://connections.renovations.com:9444”
Replace with
href=”https://connections.renovations.com”


Switch back to the CMD line window with the IBM Connections Config Admin console
and enter the command: “LCConfigService.checkInConfig()”.


Enter the command “synchAllNodes()”.


To exit the wsadmin console enter the command “exit”.


Now you can start up your IBM Connections Application Server with the commands:
“cd IBMWebSphereAppserverprofilesAppSrv01bin”.
And then “startserver connections_server”.


Wait 5 minutes until the server is started completely. Then enter the URL
“https://connections.renovations.com/homepage” in your Browser.


Understand the Risks


Add the exception


Get the certificate and confirm the Security Exception


Enter the credentials of a LDAP directory user and click the “Log in” button.


IBM Connections and the IBM HTTP Server are now configured successfully to use secure
SSL connection.


STEP THIRTEEN: Configuring the Home page
administrator
B e fo re y o u b e g in
IBM® Connections administrators must be dedicated users. Their only purpose
should be application administration.

About this task
Only a Home page administrator can add, remove, enable, or disable widgets on
the Home page. For more information, see the Administering the Home page
from the user interface topic.

Note: You can also create global administrators for any of the applications, for
the purpose of managing content. For more information, see the Administering
application content topic.

To configure administrative access to the Home page application, complete the
following steps:


In your Browser log in to the Integrated Solutions Console with your IBM WebSphere
Application Server Administrator account and password.


Click “Applications” - “Application Types” - “WebSphere enterprise applications”.


Click the “Homepage” application.


In the “Detail Properties” section click the “Security roles to user/group mapping” link.


Select the “admin” role and click the “Map Users...” button.


Enter a name or part of a name in the “Search String” field and click the “Search” button.


Select one of the names in the “Available” view and click the button to add it to the
“Selected” view.


The user name is now in the “Selected” view. Click the “OK” button to continue.


The user is now listed in the “admin” role in the “Mapped Users” column. Click the “OK”
button to continue.


If you now login with this administrative user id to your connections server, you can see the
“Administration” link on the left side.


Here you can do some administrative configuration of the Homepage application.


STEP FOURTEEN: Configure services to start and
stop the server automatic

Summary

By default, the IBM WebSphere server installer configures a service in the
Windows OS only for the Deployment Manager. The Application Server
services nodeagent and the IBM Connections Application Server are not
configured as service. This step describes how to configure this additional
services and how to configure the dependencies.


By default only the Deployment Manager only is configured as a service.


We need the path to the Application Server profile. Open your File Explorer and navigate to
the directory “C:IBMWebSphereAppServerprofilesAppSrv01”. Then click into the URL
line and copy the path string into the clipboard with a “Ctrl-C”.


Open a CMD line window. Navigate to the WebSphere bin directory with the command “cd
C:IBMWebSphereAppServerbin”. Then enter the command “wasservice -add
connectionsNodeagent -serverName nodeagent -profilePath “ then copy in the clipboard
with the path. Then add “ -stopArgs “-username wasadmin -password passw0rd”
-encodeParams”.
When the command was running successfully you should see the message below.


Recall the command line and change just the 2 parameters to “connectionsServer” and
“connections_server”.


Two additional services are now created. Next step is to configure the dependencies.


Enter the command lines:
“sc config “IBMWAS70Service – connectionsServer” depend= “IBMWAS70Service –
connectionsNodeagent”

And
“sc config “IBMWAS70Service – connectionsNodeagent” depend=
“IBMWAS70Service – connectionsCellMnager01”


The nodeagent depends on the dmgr, and the connections server depends on the
nodeagent.


The last step is to set all services to “Automatic” and then the system should start up
completely and automatic after a OS restart.


STEP FIFTEEN: Install the CR1 Fixpack

General Information

Updates for IBM Connections 4.0 are delivered via interim fixes called "Cumulative
Refresh" (CR).

Cumulative Refreshes (CRs) consists of a set of cumulative fixes, one for each IBM
Connections application. The entire application is updated.

The CR includes multiple code changes, bundled into a single package and verified
together following IBM's interim fix delivery process.

We recommend customers to apply the latest set of CR fixes as it becomes available.
This ensures that all the applications in the IBM Connections environment are at the
latest version. This in turn prevents the occurrence of known issues in your environment,
increasing stability and minimizing downtime. It also helps expedite the resolution of
newly reported issues.


A list of the fixes included in the IBM Connections CR1 release can be found here:

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


Stop the IBM Connections Server and the nodeagent. The easiest way is to stop the
“nodeagent” service. Because of the dependencies configuration this will stop the
connections server as well. This can be done in the Services view.


Click the “Yes” button to continue.


The Connections Server and the Nodeagent have been stopped now.


Open your File Explorer and navigate to the directory “C:IBMConnections”. Rename the
directory “updateInstaller” to “updateInstaller_old”.


The directory is now renamed.


Open a second File Explorer and navigate to the directory “C:installIC4_Fixes”.


Copy the “updateInstaller” folder to the other File Explorer window into the directory
“C:IBMConnections”.


The updateInstaller directory is now copied to the right directory in your IBM Connections
installation.


In the last File Explorer window navigate to the directory
“C:IBMConnectionsupdateInstallerfixes”.


In the other File Explorer window mark all the .JAR files and copy them to the other explorer
window into the directory “C:IBMConnectionsupdateInstallerfixes”.


The CR1 Fixpack files are now copied successfully to the target directory.


Open a new CMD line window and enter the commands:
“cd IBMWebSphereAppServerbin”
“setupCmdLine”
“cd IBMConnectionsupdateInstaller”
“updateWizard.bat”


Deselect the Metrics fix and click the “Next” button to continue.


Enter the credentials of your IBM WebSphere Application Server administrator and click the


The Update Installer is installing the CR1 fixes. This step can take approximately 20 to 30
minutes.


The CR1 fixes are now installed successfully. Click the “Finish” button to continue.


Go into your Services window and start the “connectionsNodeagent” service only.


Check your Task Manager – Processes view and wait until the two “java.exe” processes do
not consume any CPU time. The system synchronizes the changed applications into the
application server. This can take up to 5 minutes.


Now you can start the “connectionsServer” service.


Congratulations, you have finished all required installation and configuration steps for
your first IBM Connections 4.0 installation.

You can publish the url of your server to the test or pilot users and see how the
content in your IBM Connections Server grows and it becomes alive.

As more people using the system and as more time they spend in initializing all the
applications and filling them with content, as faster the system will become
successful. A social software system is growing with the usage.

So the main messages here are:

- Use the system with as much people as possible.
- Use it for all tasks and services you can do.
- Spend time in the initialization.
- See how it succeeds.


Additional Steps after the installation:
Some additional Post Install Tasks can be done after all components are installed. You
should consult the IBM Connections Product Documentation in the Internet about this
steps here:

http://www-10.lotus.com/ldd/lcwiki.nsf/xpDocViewer.xsp?
lookupName=IBM+Connections+4.0+documentation#action=openDocument&res_title=
Optional_postinstallation_tasks_ic40&content=pdcontent


Connections 4.0 on Mobile devices
You can use the web browser on your mobile device to access the mobile version of IBM
Connections. The mobile version optimizes the applications for use from a mobile device.
It makes it easier for you to perform tasks with a minimal number of clicks.

Instead of using the web version from a mobile device, you can also install native
applications on the following devices:

Android devices
Apple iPhone
Apple iPad
Apple iPod Touch
BlackBerry OS6 devices

Search for the IBM Connections application from the Apple App Store, Android Market, or
BlackBerry App World.


How do I enable the mobile version?
Before you begin

Note: While it is possible to access IBM Connections by using the browser on your mobile
device, IBM recommends that you use the IBM Connections native app instead. The native
app is available for following mobile devices:

Android
Apple iOS
BlackBerry

Establish how mobile users will remotely and securely connect into your enterprise for IBM
Connections mobile access from a device.

If your enterprise requires the use of a VPN for mobile device remote access, Lotus Mobile
Connect is a recommended option.


If you use signer certificates that are not already trusted by the web browser, install the
SSL signer (trust) certificate on the mobile device. Standard certificate authorities, such as
VeriSign, for example, are trusted by most web browsers, so you would not need to
perform this step if you are using a certificate from a standard certificate authority. To
install the SSL signer certificate on the mobile device, complete the following step:

● Apple iOS:
Send an email to your users with the certificate provided as an attachment. Ask your
users to open the attachment from the device. When they do, the device recognizes
and installs the certificate.
● Devices that run on the Symbian operating system:

Refer to the documentation for the device to find out how to install certificates.

For example, to install a certificate on the Nokia S60 device, go to the Nokia website.

When you install IBM Connections, select the option to install Mobile.

Note: If you already installed IBM Connections, but did not select the Mobile application at
the time, you can rerun the installation wizard in Modify mode.


What to do next

Instruct your users that they can access the mobile version of IBM Connections by
completing the following steps:

1) Log in to your intranet from the mobile device.
2) Go to the following web address:

http://hostname/mobile
in this example we can use
“http://connections.renovations.com/mobile”

where hostname is the same server host name from which users access IBM Connections
in a standard web browser.


Installing plug-ins to use IBM Connections in other
applications
You can access your IBM Connections data from within other products by adding plug-ins
to those other products.

IBM Connections Desktop Plug-ins for Microsoft Windows
Use the plug-ins to share files and information between Microsoft™ Windows™
applications and IBM Connections.

IBM Connections Plug-in for Microsoft SharePoint
The IBM Connections Plug-in for Microsoft SharePoint brings IBM Connections
applications such as searching by tag, searching by profile, and viewing business cards,
into the SharePoint environment. Install the IBM Connections Widget for Microsoft
SharePoint so that Connections users can access documents from a SharePoint server.


IBM Connections Desktop Plug-ins for Microsoft
Windows
The IBM Connections Desktop Plug-ins Microsoft Windows supports:

● IBM Connections 4.0
● IBM Connections 3.0.1.1
● Microsoft Windows XP SP3 (32-bit)
● Windows Vista (32-bit)
● Windows 7 SP1 (32-bit, 64-bit)
● Microsoft Office 2007 Standard or higher (32-bit)2010 Standard or higher (32, 64-bit)
● Microsoft Outlook 2007 Standard or higher (32-bit), 2010 Standard or higher (32, 64-bit)


IBM Connections Desktop Plug-ins for Microsoft
Windows
The IBM Connections Desktop Plug-ins for Microsoft Windows provides the following
features from Microsoft Windows Explorer:

● Upload local files to IBM Connections from Windows Explorer or from your desktop
● Share uploaded files with people, communities, or folders in IBM Connections
● Work on files locally and publish them to IBM Connections
● View people's contact details and get in touch with them
● Pin, follow, or like IBM Connections files and folders
● View or contribute comments for a file
● Lock a file when you are editing it to prevent file conflicts
● View and restore files from IBM Connections Trash
● Share folders with IBM Connections Communities


Performing a user installation
Procedure

1) Download the plug-in from the IBM Connections catalog at the following web site:
https://greenhouse.lotus.com/catalog

2) Unzip the file.

3) Double-click “IBMConnectionsDesktop.exe” to launch the installation program.

4) Choose not to install the Microsoft Office or Microsoft Outlook plug-ins. In the Custom
Setup panel, click the icon next to Microsoft Office or Microsoft Outlook, and then click
“This feature will not be available” to not install those plug-ins. The Microsoft
Explorer plug in is always installed.

5) Click Finish to complete the installation.

6) If prompted, reboot your computer.


Legal Disclaimer

© IBM Corporation 2012. All Rights Reserved.
The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is
provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall
not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of,
creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.
References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this
presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way.
Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

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

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

IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, 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.


IBM Connections 4.0 Installation From Zero To Social Hero - 1.03 with AD LDAP

More Related Content

What's hot (19)

Similar to IBM Connections 4.0 Installation From Zero To Social Hero - 1.03 with AD LDAP (20)

Recently uploaded (20)

IBM Connections 4.0 Installation From Zero To Social Hero - 1.03 with AD LDAP