Download In IBM Connections

Architecture & Deployment
IBM Connections 5.0 Workshop
Author: Paul Godby
IBM Ecosystem Development
Duration: 30 minutes
© 2014 IBM Corporation
Agenda




IBM Connections Applications
Prerequisite Software
Deployment Topologies
Installation
IBM Connections Applications
Activities
Home page
Blogs
Profiles
Bookmarks
Wikis
Communities
Mail
Files
Polls and Surveys
Forums
Social Analytics
Architecture

Required components






LDAP Directory
Tivoli Directory Integrator
Relational database (DB2 / Oracle / MS SQL)
WebSphere Application Server
IBM HTTP Server
Optional components

Metrics → IBM Cognos Business Intelligence

Mail → IBM Domino Server / Microsoft Exchange

Content Manager → FileNet

Surveys & Polls → IBM Forms

Presence, Chat, & Meetings → IBM Sametime
Agenda




IBM Connections Applications
Prerequisite Software
Deployment Topologies
Installation
Federated Repository


Allows users and groups from multiple repositories to appear as a single registry (called a
“realm”)
In WebSphere Application Server...



Used to manage and secure user and group identities
Used to assign users to various IBM Connections roles
In IBM Connections...



Used for authentication
IBM Connections will pull user profile data from the Profiles database (not LDAP)

User data will be synchronized to Profiles database using Tivoli Directory Integrator

Reduces load on the LDAP directory

Performance greatly enhanced by using relational database queries
To use the LDAP directory as the user profile store directly, you can disable the Profiles
extensions
Tivoli Directory Integrator

Used to populate the Profiles database with user information

Also used to populate photos and pronunciation files
Typically user information will come from the LDAP directory

You can create additional scripts to pull data from other user repositories
Information will sync down (from LDAP to Profiles)
In order to sync information up (from Profiles to LDAP), you must install and configure a
Directory Server Markup Language (DSML) service



WebSphere Application Server (WAS)

IBM WebSphere Application Server (WAS) provides the foundation to run many high-volume,
business-critical enterprise applications
Provides an environment to run J2EE applications

Delivers a Services Oriented Architecture hosting infrastructure
Middleware foundation for many IBM and 3rd party products






IBM WebSphere Portal
IBM Sametime
IBM Connections
And more!
Application (Blogs, Dogear, etc.)
Application Server (WAS)
Hardware, Operating System, Database,
Network, Storage…
WAS Terminology

Enterprise Application

An EAR and/or WAR file that implements some J2EE functionality
Application Server



Profile



Logical collection of server processes used to group application servers
Isolates solutions from each other (each profile has own unique configuration)
Node

An installation of WAS. Typically represents a physical machine
More than one node can be installed on a single physical machine

Collection of nodes managed by a single Integrated Solutions Console


A single JVM running one or more enterprise applications
Cell
WAS Topology
App
App
App
App Server
App
App Server
Profile
App
App
App Server
App
Application Server (server1)
Profile (AppSrv01)
Node (machine1)
App (i.e. Profiles)
Node (machine2)
Physical Machine (machine1)
Application Server
(i.e. server1)
Physical
Machine (machine2)
Profile (i.e. AppSrv01)
Node (i.e. machine3)
Cell (i.e. cell1)
Physical Machine (i.e. machine3)
WebSphere Application Server Network Deployment (WAS ND)

A network deployment:

Provides the administrator with a central management facility

Ensures users have constant access to data

Balances workload between servers

Improves server performance

Facilitates the maintenance of performance when user population increases
Additional WAS terms:

Deployment Manager (DM) = administers multiple nodes in a cell

Node Agent = works with the DM to perform administrative functions for the node

Cluster = group of application servers running the same applications
Integrated Solutions Console deployed to a single location (DM)




Changes can be synchronized to corresponding managed nodes
IBM Connections must be installed in a Network Deployment environment!
WAS ND Topology
App
App
App
Application Server
Application Server (server1)
App Server
App
App
App Server
Profile (AppServ01)
Node
Agent
Node
Agent
Profile (AppSrv01)
Managed Node (machine2)
Node
Agent
Profile (AppSrv01)
Managed Node (machine3)
Managed Node (machine1)
Physical Machine (machine1)
Physical Machine (machine2)
Physical Machine (machine3)
Cluster (i.e. cluster1)
App (admin console)
Application Server (dmgr)
Profile (DM Type)
Node (machine4)
Cell (i.e. cell1)
Physical Machine (machine4)
Central cell config
repository
Agenda




IBM Connections Applications
Prerequisite Software
Deployment Topologies
Installation
IBM Connections deployment options

Small deployment (for proof-of-concept or demo purposes only!)

Install all IBM Connections applications on a single node in a single cluster

Limited flexibility and does not allow individual applications to be scaled up

All the applications run within a single Java Virtual Machine (JVM)
Medium deployment

Install a subset of applications in separate clusters

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 Profiles and install it in its own
could be installed in a different cluster.
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
system resources.
IBM Connections: Small Deployment
IBM Connections: Medium Deployment
IBM Connections: Large Deployment
Agenda




IBM Connections Applications
Prerequisite Software
Deployment Topologies
Installation
IBM Connections 5.0 Installation Overview
Enhanced integration
solution:
- reduced steps: 13 to 9
- also reduced for fix pack:
11 to 7
CCM Extensions EAR
for audit compliance
Utilizes IBM
Installation
Manager
Installation
Manager to
deliver CRs
New
Improved
Cognos Wizard
Support for
clustered BI
server setup
Wizards
&
CCM
Upgrade
&
Migration
4.x to 5.0
Ready
Support for
BI server /
Transformer
separation
GUI
provided;
better
validation
Move from any GA or
CR release to IC 5.0
with updated migration
tool & database wizard
Simplified CCM
install process; no
separate fixpack
install required
FileNet fixpack
install scripts
provided
Added File sync /
push notification;
Highway; Concerto
library for SAML
setup;
Stellent libraries
updated
Updated ccmDomainTool:
- more robust
- post-install steps automated
- log generated
- more
Installation...In a nutshell

Install the following prerequisite software

LDAP

DB2

Tivoli Directory Integrator (TDI)

IBM Installation Manager (IM)

WebSphere Application Server Network Deployment (WASND)

IBM HTTP Server (IHS)
Create WASND Cell Profile
Configure WASND security and federated repository
Create IBM Connections databases
Use TDI to populate the Profiles database with user data and photos
Install IBM Connections
The process of actually installing IBM Connections
is only a small step. Most of your time will
Configure IHS and SSL
be spent installing and configuring the
prerequistie
applications / environment!
(Optional) Create server startup and shutdown scripts







Installation Enhancements

IBM Connections Installer


9 additional languages now supported
CCM unselected by default


Cognos




Selecting CCM will auto select Communities
Use a new wizard to install after installation of IBM Connections
Now supports BI and Transformer on same or different nodes
Installation Manager wizard now: applies fixpack, federates node, performs role
creates scheduled task to build PowerCube
External Collaboration

Enabled by default, but can be disabled by an administrator
Thanks!

Access FREE education on the IBM Collaboration Solutions portfolio of products today!
1. Visit the IBM Greenhouse and create a free account.
Link → http://greenhouse.lotus.com/
1. Visit the IBM Collaboration Solutions Ecosystem Development Community
Link → https://greenhouse.lotus.com/communities/community/icsecod
1. Learn new skills and share these links with your friends and colleagues!