IBM Connections 4.5 CR2 Installation - From Zero To Social Hero - 2.02 - with Domino LDAP

© 2009 IBM Corporation
IBM Collaboration Solutions
IBM Connections 4.5 &
CR2 Installation
”From Zero to Social Hero”
Frank Altenburg | SME for IBM Social Collaboration Software
IBM Collaboration Solutions
mailto:frank.altenburg@de.ibm.com
Version 2.03, released Oct 11. 2013
For Domino LDAP

2 © 2013 IBM CorporationSocial Business
About the Author
Frank Altenburg is a Certified Senior Field Support Engineer and
Subject Matter Expert for IBM Social Collaboration Software in the
Accelerated Value Program (AVP) organization in Germany, which
delivers a proactive, cost-reducing, and productivity enhancing advisory
service. Frank has more then 15 years experience supporting Lotus
products predominately on customer sites. For over 10 years Frank has
specialized his skills in the IBM Sametime Product family. As a leader
of the European IBM Sametime and IBM Connections Communities,
Frank is an evangelist for the IBM Social Collaboration business and is
a regular presenter at Lotusphere since 2008. He has presented at
many events all around the world. Frank is the author of the "From Zero
To Hero" document series for IBM Sametime and IBM Connections.
Frank can be found on Facebook, Twitter or his blog.

Agenda
● Introduction
● Requirements for a IBM Connections 4.5 installation
● Architecture of a IBM Connections 4.5 Server deployment
● The 33 steps to a IBM Connections 4.5 Server deployment

Introduction
This document
● Describes how to implement, in a very fast way, the infrastructure for a small
deployment of a IBM Connections 4.5 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. All instructions in this
document are based on the official documentation wiki.
● 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.

What's new in IBM Connections 4.5
What's new for administrators in Version 4.5?
Installation
● The installation of IBM Connections Content Manager for the Libraries application on
AIX®, Linux, and Windows.
● The installation now supports IBM i platform 6.1/7.1 for all applications other than
Libraries.
● The installation wizard is based on IBM Installation Manager 1.5.3.
Administration
IBM Connections:
● You can lock the default frequency with which email digests from IBM
Connections applications are sent to your users by configuring the
frequencyLocked property in the notification-config.xml file. For more
information, see Setting the default frequency of email digests.

What's new in IBM Connections 4.5 (cont.)
Activities:
● The EventLogPurgeJob task deletes old entries from the Activities events log. This task
helps maintain performance and keeps the log from becoming too large. By default, it
runs daily at 2 AM. You can specify the time that the log is purged and set the properties
that define which entries can be deleted.
Communities:
● You can increase the maximum number of communities that can be displayed in the
Communities user views by adding a configuration setting to the LotusConnections-
config.xml file.
● If the Communities catalog index becomes corrupted or is not being refreshed properly,
you can restore the index by deleting the existing index data and waiting for the next
scheduled crawl. For more information, see the Restoring the Communities catalog index
topic.
● By adding search to the list of modes in the Linked Library widget definition, you can
enable search for content in linked libraries. For more information, see Enabling search
for linked libraries.

Libraries:
Libraries provide community members document management capabilities to upload,
manage, organize, and collaborate on community files. A community can contain
multiple libraries.
Attention: When the IBM® Connections Content Manager add-on is deployed,
community owners can create libraries directly from a community using the Library
widget. Community owners can also link to existing libraries using the Linked Library
widget available in IBM Connections 3.0.1 and later. In this documentation, the libraries
created directly from a community using the Library widget are referred to as
community libraries. The libraries connected to a community using the Linked Library
widget are referred to as linked libraries. Community libraries are currently only
supported in IBM FileNet® Content Manager deployments. Linked libraries are
supported by IBM FileNet Content Manager and IBM Content Manager.

Community libraries provide owners and members with the following content management
capabilities and enhanced social features:
● Checkin and checkout. Members can check out files and edit them using private drafts.
Checked out files are locked to prevent other users from making updates at the same
time.
● Version control. Members can see who has updated content at a glance and roll back to
previous file versions if there is a need to recover older content.
● File organization. Members can copy, move, and delete files, and use Trash view
functionality to manage deleted content.
● Draft review. Members can collaborate on shared files and send them through an
established review cycle to obtain the approval of selected members of the community.
● Sharing. Community owners can set file-level access to the library, giving them tighter
control over who can edit content.
● Social content management. Members can interact with content in the community
library in a social and dynamic way. For example, they can use tags to categorize
content and improve file retrieval, and like files to recommend them to fellow members.
Members can also track file updates in the community activity stream, follow files,
comment on files, and see who has downloaded files.
● Document types and properties. Community owners can set the default document type
for a library, allowing them to specify a defined set of information and properties for
library files.

Existing linked libraries from earlier versions of IBM Connections can also leverage many of
the content management capabilities and enhanced social features provided by community
libraries, depending on the deployment specification. Where there are limitations for specific
linked library deployments, these are noted in this help.
Notes:
● Access to linked libraries is managed on the Enterprise Content Management (ECM)
server unlike community libraries, where the access is managed from the community.
Access to a linked library does not include the community owners and members groups,
so having access to a community does not necessarily mean that you have access to its
linked libraries. You can see the Linked Library widget but unless you have access to
the linked library, you cannot see any content in the library.
● If you remove the Linked Library widget from your community, the linked library content
is not deleted from the ECM server. You can access the content by adding the Linked
Library widget to your community again and recreating the connection with the ECM
server. If you remove the Library widget from your community, the associated library
content is permanently removed from your community and cannot be retrieved.
● You can search for files in community libraries, however, searching in linked libraries is
disabled by default. If search is enabled for linked libraries, a Linked Libraries tab is
available in your Communities search results. Linked library search results display all
matching files in the library. The search results do not include any social features, such
as tagging, or document type information. When you click a search result, you are taken
to a generic landing page that is outside the scope of a community. When a linked
library is connected to a subfolder of a library, the search results are scoped to the
library rather than to the folder.

Wikis:
● The Wikis administrator can delete draft wiki pages that were created by other users. This
capability is useful after a user leaves the organization.
● Create your own message for users by customizing the Wikis welcome page.
Files:
● You can now use a Files administrative command to obtain the ID of a community library
using its community uuid value. The format of the command is:
FilesLibraryService.getByExternalContainerId(string community_id)

Profiles:
● You can now exclude nicknames when adding or updating user profiles by specifying a
new name.expansion property in the tdi-profiles-config.xml file.
● You can use the new mapToNameTable property in the profiles-types.xml file to specify
an additional givenname or surname value for use with Profiles directory search.
● You can integrate the Profiles business card with your web application by mapping an
LDAP distinguished name, using the DN parameter; in addition to the previously available
user ID and email mapping options.
● The hashEmail extended attribute can be added to the
map_dbrepos_from_source.properties file or profileExtension table in the tdi-profiles-
config.xml file to support Profiles users in conjunction with the Microsoft Outlook Social
Connector. For related information topics in the Using the IBM Connections Desktop
Plug-ins for Microsoft Windows section of the IBM Connections wiki.

News:
● Use the NewsActivityStreamService.updateApplicationRegistrationForEmailDigest
command to update a registered third-party application to enable it for email digest
functionality. For more information about this command, see Registering third-party
applications.
● Use the NewsEmailDigestService.refreshDefaultEmailPrefsFromConfig()command to
refresh updates to the default email preferences specified in the notification-config.xml file
without the need for a server restart.

Search:
● Use the new, optional parameter for the SearchService.startBackgroundIndex command
to run social analytics indexing jobs at the end of the background indexing operation.
● You can configure post-filtering for the ECM service by enabling or disabling a property in
the Search configuration file. Post-filtering is enabled by default.
● Use the SearchService.startBackgroundSandIndex command to create a background
index for the social analytics service. Use this command to run background indexing for
social analytics without having to run a full index crawl.
● By adding search to the list of modes in the Linked Library widget definition, you can
enable search for content in linked libraries using FileNet P8 5.2. For more information,
see Enabling search for linked libraries.

Administrators: Deploying the preview guide to your users
The IBM® Connections 4.5 preview guide is available for you to distribute to your users for
new installations and upgrades to IBM Connections 4.5. 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. http://www-10.lotus.com/ldd/lcwiki.nsf
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.
● Install and configure Cognos Business Intelligence and Cognos Transformer

Agenda
● Introduction

Detailed system requirements for IBM Connections
You can find the official IBM Connections 4.5 System Requirements here:
Detailed system requirements for IBM Connections (#7012786)

IBM Connections 4.5 Server Prerequisites
For this pilot deployment you need
● a supported LDAP directory server (see system requirements)
In this example we use Domino LDAP
● two Windows Server 2008 64Bit boxes for the installation
● Network and DNS configuration
● to download the required installation files from Passport Advantage and Fix
Central
● several administrative user accounts
● a trusted certificate (optional)
● A IBM Lotus Domino 8.5.3 FP3 Server for Domino Mail integration (optional)
● A IBM Sametime Proxy Server 8.5.2 IFR1 for the Sametime awareness and BIZ-
Card integration (optional)

● 1 Server that will host the following applications:
● IBM DB2 Database Server
● IBM Tivoli Directory Integrator
● IBM Connections Content Manager
● IBM Connections 4.5 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 address and a DNS Alias entry.
● 1 Server that will host the following applications:
● IBM DB2 Database Client
● IBM Cognos Server
Dual CPU, 8GB RAM or more, 30GB disk space or more, 64 Bit OS
1 GBit Network Interface with 1 IP address and a DNS Alias entry.
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 4.5 Server components.
Hardware required for this Pilot Example Deployment

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 machines have 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 machines with only 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“.

For a Windows installation you need to download these files from Passport Advantage:
CIG8XML IBM FileNet Content Platform Engine V5.2 Windows Multilingual
CIG9FEN IBM FileNet Content Platform Engine Client V5.2 Windows English
CIG7ZML IBM FileNet Collaboration Services V2.0 Windows Multilingual
CI5VMML IBM Cognos Business Intelligence Server 64-bit 10.1.1 Windows Multilingual
CI2Q1ML IBM Cognos Business Intelligence Transformer 10.1.1 Windows Multilingual
CI6NDML IBM DB2 10.1 Enterprise Server Edition - Authorized User Single Install Option
Quick Start and Activation Multiplatform Multilingual
CZ9MKML IBM Tivoli Directory Integrator Identity Edition V7.1 for Windows x86-64
CZM9KML IBM WebSphere Application Server Network Deployment V8.0 (1 of 4)
CZM9LML IBM WebSphere Application Server Network Deployment V8.0 (2 of 4)
CZM9MML IBM WebSphere Application Server Network Deployment V8.0 (3 of 4)
CZVG4ML IBM WebSphere Application Server Network Deployment V8.0 (4 of 4)
CZM91ML IBM WebSphere Application Server V8.0 Supplements (1 of 4)
CZXR9ML IBM WebSphere Application Server V8.0 Supplements (4 of 4)
CIHC5ML IBM Connections V4.5 for Windows Multilingual
CIHC8ML IBM Connections V4.5 Wizard for Windows Multilingual
Required files for a deployment on Windows

To update the WebSphere system to the required level you need to download these files
from Fix Central:
DB2-ntx64-universal_fixpack-10.1.200.238-FP002
7.1.0-TIV-TDI-FP0006
Cognos Business Intelligence 10.1.1 Fix Pack 1
IBM Installation Manager 1.5.3 Install Kit for Windows
IBM WebSphere Application Server Fix Pack 8.0.0.5 for distributed platforms part1
IBM WebSphere Application Server Fix Pack 8.0.0.5 for distributed platforms part2
8.0.0-WS-WASSupplements-FP0000005-part1 for distributed platforms
8.0.0-WS-WASSupplements-FP0000005-part2 for distributed platforms
WebSphere Customization Toolbox Fix Pack 8.0.0.5 for distributed platforms
8.0.0.5-WS-WASND-IFPM62615
8.0.0.5-WS-WAS-IFPM76920
8.0.0.5-WS-WAS-IFPM85834
Required files for a deployment on Windows (cont.)

For the Domino Social Mail integration you need to download this file from Greenhouse:
ICM1.3_iFix1_allplattform_install.zip
This download can be found here. Log in with your Greenhouse ID and password. If you dont
have a Greenhouse ID you can join Greenhouse for free.
https://greenhouse.lotus.com/plugins/plugincatalog.nsf/assetDetails.xsp?
action=editDocument&documentId=2118E657CE35A81F85257B2C0083B92D

If you have downloaded all files into a single directory then this directory should look like
this screen shot:

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:InstallCCM” contains the 3 executable files from the 3 CCM packages:

The Directory “C:InstallDB2” contains the subdirectories “UNIVERSAL” for the DB2 10.1
FP2 installer and “License” for the license files.

The Directory “C:InstallTDI” contains the subdirectories “TDI_7.1.0” for the TDI installer
and “7.1.0-TIV-TDI-FP0006” for the Fixpack 6 files.

The Directory “C:InstallWAS_ND_8.0” contains the subdirectories “IM” for the IBM
Installation Manager, “WAS” for the WebSphere 8.0 Installation Files, “WAS_FP5” for the
WAS 8.0 FP5 files, “..SUP..” for the WAS Supplements and Supplements FP5 files and the
“..WCT..” for the WebSphere Configuration Tools FP5 files and the 5 additional fixes.

On the Cognos Box, the Directory “C:Install” contains the subdirectories “Cognos” for the
Cognos files, “UNIVERSAL” for the DB2 client installer and “WAS_ND_8.0” for the
WebSphere installation files.

The Directory “C:InstallCognos” contains the subdirectories “bisrvr” for the Cognos
Business Intelligence Server install files, “bitrsfrm” for the Cognos Transformer installation
files and “CBI_10.1.1_Win64_FP001” for the FP1 installation files.

The Directory “C:InstallWAS_ND_8.0” contains the subdirectories “IM” for the IBM
Installation Manager, “WAS” for the WebSphere 8.0 Installation Files, “WAS_FP5” for the
WAS 8.0 FP5 files and the 5 additional fixes.

Required technical users for IBM Connections 4.5
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.

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

Cognos Admin
This user is required to administer the Cognos Business Intelligence
and Transformer components in your Connections installation. This
user must be created in your LDAP directory and the password should
never expire as all technical user accounts. Take note of the
shortname of this user. This shortname is required later in the post
install tasks for Cognos.
Connections Content Manager (CCM) Administrator
This user is required for CCM to communicate with the WebSphere
Application Server part. If you use an existing FileNet deployment then
this user should be an LDAP user that has admin rights to your
WebSphere deployment. If you install a new FileNet deployment – this
is what we are doing here with this document – it is easiest to use the
existing “wasadmin” user.

Anonymous User for Filenet
IBM FileNet Collaboration Services implements anonymous access
with a designated user that is used only for this purpose. The user
should be a system-type user that is not used by a real person. The
user ID does not need, and should not have, any particular privileges
on the object store beyond what is given by the installation guide. This
user's access control records will determine what level of access is
given to anonymous users. Consequently, choose a functional ID that
is reserved for this purpose and that does not have special access.
Configuring an anonymous user is required if users will be accessing
Connections communities anonymously. In some cases, such as when
desktop single-sign is enabled, or when roles in the communities
application have been restricted to limit access to authenticated users,
setting up anonymous access for FileNet is optional. Refer to Roles for
information on restricting access to anonymous users in communities.
Create a user with the name “Anonymous User” in your Domino
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.5 Server deployment
As you could see in the previous slides, you can install IBM 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.
Everything between one box and many boxes is possible. For your production
environment a detailed architecture design and sizing is urgently recommended.
In this pilot we use one box for the IBM Connections Server and an other box for the
Cognos Business Intelligence and Transformer services. We assume you have a
already existing Domino LDAP with user data.
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. On the second box we will install the DB2 client, the
WebSphere Server platform and the Cognos Server components.

IBM Connections 4.5 architecture for this document
Existing components New components to be installed
IBM DB2
Database
Server
IBM
Connections
Server
Cognos
BI Server
IBM HTTP
Server
IBM Lotus
Domino LDAP
Server
IBM DB2
Database
Client
IBM Tivoli
Directory
Integrator
IBM
Connections
Content
Manager

Agenda
● Introduction

The 33 steps to a IBM Connections 4.5 Pilot deployment
Pre Installation tasks
1.Prepare your machines and the network 54
2.Prepare your LDAP 57
3.Install the IBM DB2 Server, add the license and create users 61
4.Run the Database Creation Wizard 102
5.Install IBM Tivoli Directory Integrator and update to FP6 117
6.Run the Population Wizard 141
7.Install IBM WebSphere Application Server 8.0 and the FP5 159
8.Create the required Manager and AppServer profiles 187
9.Update WebSphere with 5 required fixes 196
10.Install IBM IHS, Plugin and FP5 213
11.Setup LDAP with Federated Repositories in WAS 239
12.Create the Cognos administrator account 281

13.Install the DB2 Database Client for Cognos 282
14.Install IBM WebSphere Application Server for Cognos 299
15.Create the required AppServer profile 327
16.Update the WebSphere Server with 5 required fixes 336
17.Install the Cognos Business Intelligence and Transformer Server 354
18.Federate Cognos 373
19.Validate Cognos 388
Installation
20.Install the IBM Connections Server 393
Post Installation tasks
21.Reviewing the JVM heap size 450

22.Configure the IBM HTTP Server IHS 460
23.Configuring the Home page administrator 566
24.Configure File Downloads through the HTTP server 579
25.Install the Cognos FP1 Fixpack 603
26.Granting access to Global Metrics and Community Metrics 631
27.Configuring the IBMConnectionsMetricsAdmin role on Cognos 649
28.Configure Cognos to use the HTTP Server and SSL 685
29.Configure the Job Scheduler 707
30.Configure IBM Connections Content Manager for Libraries 731
31.Configure services to start and stop the server automatic 788
32.Update IBM Connections to the Cumulative Refresh 1 level 805
33.Update IBM Connections to the Cumulative Refresh 2 level 943
Attachment:
● Worksheet for Connections 1088

On the second document “IBM Connections 4.5 Integration – From Zero
To Social Hero” you can find this topics:
● IBM Connections 4.5 on Mobile devices
● IBM Connections Desktop Plug-ins for Microsoft Windows
● IBM Connections 4.5 Plug-ins for IBM Lotus Notes
● Configure IBM Lotus Domino Social Mail integration
● An easy way to import some user photos
● Adding Sametime awareness through the IBM Sametime Proxy
Server
● Configure IBM Sametime Proxy to use the IBM Connections
business card in place of the Sametime business card
● Installing the IBM Connections Portlets for WebSphere Portal
● Integrating Sametime Advanced with IBM Connections

STEP ONE: Prepare your machines and the network
Summary
Before you can install your IBM Connections Server environment, some things needs to
be checked and prepared.

The machines that you run the IBM Connections 4.5 Server, the Cognos Server and the
DB2 Database Server can be virtual machines or a hardware boxes. 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.5+documentation#action=openD
ocument&content=catcontent&ct=prodDoc
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 external link 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 user:

A LDAPSEARCH response for a group:

STEP THREE: Install the IBM DB2 Server, add the
license and create users
Summary
This step installs the IBM DB2 Database Server release 10.1 with the FP2
update, installs the license key into the server and then creates 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 then 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:InstallDB2UNIVERSAL”. 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 Version
10.1 Fix Pack 2” section. Do not select the first option (Advanced Enterprise Server)
because the License file does not fit.

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.

Remove the “Program Files” part again in the path and select “Do not autostart the
IBM SSH server” option. Then click the “Next” button to continue.

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.

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

Click the “Next” button to continue.

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.

Click the “Finish” button to end the DB2 Setup.

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

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 Window - Administrator”.

Enter the command “db2licm -l”. you will see that the license is not registered.
Do not copy and paste any commands from this document into your CMD line. This does not
work because this would copy some special characters.

Enter the command
“db2licm -a C:installDB2licenseese_udb2licensedb2ese_u.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”
“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 this step 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

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 to 15 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 13 databases
and the wizard has set this parameter to 15. 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:InstallTDITDI_7.1.0” 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
InstallTDI7.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.

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 profiles (PEOPLEDB) database.
STEP SIX: Run the Population Wizard

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.

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. Then click the “Next” button to continue.

In most LDAP servers you have not filled the country code field. Then you should select
“null” in the “countryCode” attribute. 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 Log shows the progress of the population work.

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

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
STEP SEVEN: Install IBM WebSphere Application
Server 8.0 and the FP5 update

Starting with WebSphere 8.0 the System is installed using the IBM Installation Manager.
For IBM Connections 4.5 we use the IBM Installation Manager release 1.5.3. Navigate to
the directory “C:InstallWAS_ND_8.0IM”. Then right click the file “install.exe” and select
“Run as Administrator”.

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

Remove the “Program Files/” part in the path. Then click the “Next” button to
continue.

The IBM Installation Manager is installing. This step takes approximately 60 to 90 seconds.

The IBM Installation Manager is installed. Click the “Restart Installation Manager”
button.

First you need to add the repositories. Click “File” and then “Preferences...”.

First uncheck the “Search service repositories during installation and updates”
checkbox. If this is checked and you have access to the internet, the installer searches
for updates and newer fixpacks. This can cause the connections system to fail after the
installation. Click the “Add Repository...” button.

Click the “Browse...” button.

Navigate to the directory “C:InstallWAS_ND_8.0WAS” and select the
“repository.config” file. Then click the “Open” button.

Click again the “Add Repository...” button.

Navigate to the directory “C:InstallWAS_ND_8.0WAS_FP5” and select the

Now click on “Install”.

Check both check boxes. Then click the “Next” button to continue.

continue.

Remove the “Program Files/” part in the path. Then click the “Next” button to continue.

Again remove the “Program Files” part in the path. Then click the “Next” button to
continue.

Then click the “Install” button to start the installation.

The installation takes approximately 5 to 8 minutes.

Click the “Finish” button now. The “Profile Management Tool” will start automatically.

This step creates the required profiles for the Deployment Manager and the
Application Server. It automatically creates the dmgr server and a default server
in the Application Profile. This server will be deleted later because it is not
required.
STEP EIGHT: Create the required Deployment
Manager and Application Server profiles

Click the “Create...” button to start the profiles creation wizzard.

Select “Cell (deployment manager and a federated application server)”. Then click the

Enter the WebSphere Administrators user name and password. Be sure this user does not
exist in your LDAP directory. Do not use special characters like $ or % or others in the
password. Then click the “Next” button to continue.

Then click the “Create” button to continue.

This step takes approximately 4 to 5 minutes.

Un-check the “Launch the First steps console”. Then click the “Finish” button to continue.

Close the WebSphere Customization Toolbox now.

This step updates your WebSphere Application Server and installs 5 fixes
required for IBM Connections 4.5.
STEP NINE: Update the WebSphere Server with 5
required Fixes.

Click “File” and then “Preferences...”.

Un-check the WAS and WAS_FP5 repositories. Then click the “Add Repository...”
button.

Navigate to the directory “C:InstallWAS_ND_8.0” and select the “8.0.0-ws-wasnd-
ifpm71430.zip” file. Then click the “Open” button.

Click again the “Add Repositories...” button.

Navigate to the directory “C:InstallWAS_ND_8.0” and select the “8.0.0.5-ws-was-
ifpm76920.zip” file. Then click the “Open” button. Repeat this steps (page 202 to 206
) for the files “8.0.0.5-ws-was-ifpm85834.zip”, “8.0.0.5-ws-wasnd-ifpm62615.zip”
nd “8.0.0.5-ws-wasnd-ifpm83196.zip”

Click “Update” to start the Fixes installation

Select all 5 fixes. Then click the “Next” button to continue.

Then click the “Update” button to continue.

The installation of the fixes takes only some seconds.

Click the “Finish” button to close the installer.

Summary
In this step you install the IBM HTTP Server and IBM HTTP Server Plugin. Then
you will update them to the required fix and patch level for IBM Connections 4.5.
STEP TEN: Install IBM HTTP Server and the IHS
Plugin. Then update both to the required level

Un-check the 5 fixes repositories. Then click the “Add Repository...” button.

Navigate to the directory “C:InstallWAS_ND_8.0WAS_SUP” and select the

Navigate to the directory “C:InstallWAS_ND_8.0WAS_SUP_FP5” and select the

Navigate to the directory “C:InstallWAS_ND_8.0WAS_WCT_FP5” and select the

Now click the “OK.” button.

Click “Install” to start the installation.

Select the “IBM HTTP Server for WebSphere Application Server” and the “FP 8.0.0.5”,
the “Web Server Plug-ins for IBM WebSphere Application Server” and the “FP 8.0.0.5”,
and the “WebSphere Customization Toolbox” and the “FP 8.0.0.5”. Then click the “Next”
button to continue.

continue.

Select the “IBM HTTP Server” and remove the “Program Files” part in the path.

Select the “Web Server Plugins for IBM HTTP Server” and remove the “Program Files”
part in the path.

Select the “WebSphere Customization Toolbox” and remove the “Program Files” part in
the path. Then click the “Next” button to continue.

Click the “Install” button to continue.

This installation takes approximately 3 to 5 minutes.

We dont want to run the tool now. Select the “None” checkbox on the right sind. Then
click the “Finish” button.

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 Domino LDAP. If you plan to use Microsoft Active
Directory LDAP then consult the AD LDAP version of this document.
STEP ELEVEN: Setup LDAP with Federated
Repositories in IBM WebSphere Application
Server

The IBM WebSphere Application Server Deployment Manager “dmgr” needs to be started
first. In the “Start” menue click on “All Programs” - “IBM WebSphere” - “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.

Select “LDAP repository”.

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” 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 ...”. Enter here just “root” if you use Domino LDAP and have flat group names in the
directory. Leave the second field blank if you use Domino 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.

Now click “Web and SIP security” and then on “Single sign-on (SSO)”.

Enter your domain in the Domain Name field. Check the “Interoperability Mode” box and
enter “LtpaToken” in the LTPA V1 cookie name field. Enter “LtpaToken2” in the LTPA V2
cookie name field. Un check the “Set security cookies to HTTPOnly to help prevent
cross-site scripting attacks” box. This is required if you plan to implement the IBM
Domino Social Mail feature or the Sametime integration. Then click the “OK” button to
continue.

Click the “Apply” button.

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”.

Aaaaah – the Domino Users are listed.......

To check the groups click on “Manage Groups”.

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

Attention: The Cognos administrator account must reside in the same LDAP
directory used by IBM Connections.
If you will use an existing LDAP account, take note of the user name and
password. For example, if your organization already has a Cognos
deployment, you might choose to use the same administrator account with
Connections.
If an acceptable account does not exist already, create it now; again, note
the credentials for use later. The short name of this user needs to be used
during the Cognos installation.
STEP TWELFE: Create the Cognos Administrator
Account

B e fore you be g in
This step installs the DB2 Database client to the Cognos Server box. This
client is required for the Cognos Transformer component to connect to the
Cognos and Metrics Databases on your DB2 Server.
STEP THIRTEEN: Install the DB2 Database Client on
the Cognos Server box

Switch to the Cognos Box and navigate to the directory “C:InstallUNIVERSAL”. Then right
click the “setup.exe”. Then select “Run as Administrator”

In the navigator click “Install a Product”.

Scroll down until you can see the “IBM Data Server Client Version 10.1 Fix Pack 2”. here
click the “Install New” button.

Select “I accept both the IBM and the non-IBM terms”. Then click the “Next” button to
continue.

Select “Install IBM Data Server Client on this computer”. Then click the “Next” button to
continue.

Remove the “Program Files” part in the path. Then click the “Next” button to continue.

The DB2 client is now installing. This installation takes approximately 3 to 5 minutes.

The installation has finished. Click the “Next” button to continue.

Click the “Finish” button to end and close the installer.

Close the “Welcome” screen.

Next step is to configure the connectivity to the DB2 Server. For this configuration we need
a DB2 command window. Click “Run” - “All Programs” - “IBM DB2” - “DB2COPY1” -
“Command Window - Administrator”.

In the Command Window enter the 3 commands:
“db2 catalog tcpip node db2node remote connections.renovations.com server 50000”
“db2 catalog database COGNOS as COGNOS at node db2node”
“db2 catalog database METRICS as METRICS at node db2node”
Be sure all 3 commands completing successfully.

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
STEP FOURTEEN: Install IBM WebSphere Application
Server 8.0 and the FP5 update

Starting with WebSphere 8.0 the System is installed using the IBM Installation Manager.
For IBM Connections 4.5 we use the IBM Installation Manager release 1.5.3. Navigate to
the directory “C:InstallWAS_ND_8.0IM”. Then right click the file “install.exe” and select
“Run as Administrator”.

continue.

Remove the “Program Files/” part in the path. Then click the “Next” button to
continue.

The IBM Installation Manager is installing. This step takes approximately 60 to 90 seconds.

The IBM Installation Manager is installed. Click the “Restart Installation Manager”
button.

First you need to add the repositories. Click “File” and then “Preferences...”.

Uncheck the “Search service repositories during installation and updates” check
box. Then click the “Add Repository...” button.

Navigate to the directory “C:InstallWAS_ND_8.0WAS” and select the

Click again the “Add Repository...” button.

Navigate to the directory “C:InstallWAS_ND_8.0WAS_FP5” and select the

Now click on “Install”.

Check both check boxes. Then click the “Next” button to continue.

continue.

Remove the “Program Files/” part in the path. Then click the “Next” button to continue.

Again remove the “Program Files” part in the path. Then click the “Next” button to
continue.

Then click the “Install” button to start the installation.

The installation takes approximately 5 to 8 minutes.

Click the “Finish” button now. The “Profile Management Tool” will start automatically.

This step creates the required profiles for the Application Server. It automatically
creates a default server in the Application Profile. This server will be deleted later
because it is not required.
STEP FIFTEEN: Create the required AppServer
profile for Cognos

Click the “Create...” button to start the profiles creation wizzard.

Select “Application Server”. Then click the “Next” button to continue.

Enter the WebSphere Administrators user name and password. Be sure this user does not
exist in your LDAP directory. Then click the “Next” button to continue.

Then click the “Create” button to continue.

This step takes approximately 4 to 5 minutes.

Un-check the “Launch the First steps console”. Then click the “Finish” button to continue.

Close the WebSphere Customization Toolbox now.

This step updates your WebSphere Application Server and installs 5 fixes
required for IBM Connections 4.5.
STEP SIXTEEN: Update the WebSphere Server with
5 required Fixes.

Un-check the WAS and WAS_FP5 repositories. Then click the “Add Repository...”
button.

Navigate to the directory “C:InstallWAS_ND_8.0” and select the “8.0.0-ws-wasnd-
ifpm71430.zip” file. Then click the “Open” button.

Navigate to the directory “C:InstallWAS_ND_8.0” and select the “8.0.0.5-ws-was-
ifpm76920.zip” file. Then click the “Open” button. Repeat this steps (page 342 to 346
) for the files “8.0.0.5-ws-was-ifpm85834.zip”, “8.0.0.5-ws-wasnd-ifpm62615.zip”
nd “8.0.0.5-ws-wasnd-ifpm83196.zip”

Click “Update” to start the Fixes installation

Select all 5 fixes. Then click the “Next” button to continue.

Then click the “Update” button to continue.

The installation of the fixes takes only some seconds.

Click the “Finish” button to close the installer.

Close the IBM Installation Manager.

B e fore you be g in
The following conditions must be satisfied to ensure that the Cognos
Business Intelligence components installs correctly:
●
The Cognos Content Store database must have been created on the
database server, and that database server must be running (see
Creating databases)
●
The current server must reside within the same domain as the IBM
Connections servers so you can enable SSO (Single Sign-On) as
required for generating reports.
●
The user running the Cognos installation script must have permissions
to use the database client.
STEP SEVENTEEN: Install the Cognos Business
Intelligence and Transformer Server

Open your file explorer and navigate to the directory
“C:InstallIBM_Connections_InstallCognos”. There you can find the file
“CognosConfig.zip”. Copy this file to your Cognos Server to the directory “C:Install”.

On the Cognos Server navigate to the “C:Install” directory and then right click the file
“CognosConfig.zip” and select “Extract All...” in the menu.

Edit the path to “C:InstallCognosConfig”.

Then click the “Extract” button.

The ZIP file is now extracted.

Now change to the directory “C:IBMSQLLIBJAVA” and mark the two files “db2jcc.jar”
and “db2jcc_license_cu.jar”. Click “Ctrl-C” to copy the files into your dashboard.

Open a second file explorer window and navigate to the directory
“C:InstallCognosConfigBI-CustomizationJDBC”. Then click “Ctrl-V” to copy the 2 files
into the directory.

Go back to the “C:InstallCognosConfig” directory and open the file “cognos-
setup.properties” with your Editor. You can use Notepad or Wordpad.

You need to fill this lines with relevant data:
was.install.path “C:IBMWebSphereAppServer”
was.profile.name “AppSrv01”
was.local.admin.username “wasadmin”
was.local.admin.password “passw0rd”
was.fqdn.hostname “cognos.renovations.com”
cognos.was.node.name “cognosNode01”

IBM Connections 4.5 CR2 Installation - From Zero To Social Hero - 2.02 - with Domino LDAP

IBM Connections 4.5 CR2 Installation - From Zero To Social Hero - 2.02 - with Domino LDAP

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (20)

Ähnlich wie IBM Connections 4.5 CR2 Installation - From Zero To Social Hero - 2.02 - with Domino LDAP

Ähnlich wie IBM Connections 4.5 CR2 Installation - From Zero To Social Hero - 2.02 - with Domino LDAP (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

IBM Connections 4.5 CR2 Installation - From Zero To Social Hero - 2.02 - with Domino LDAP