Architecture & Deployment · PDF fileIBM Connections Applications Activities Blogs Bookmarks...

© 2014 IBM Corporation

Architecture & DeploymentIBM Connections 5.0 Workshop

Author: Paul GodbyIBM Ecosystem DevelopmentDuration: 30 minutes

Agenda

● IBM Connections Applications● Prerequisite Software● Deployment Topologies● Installation

IBM Connections Applications

Activities

Blogs

Bookmarks

Communities

Files

Forums

Home page

Profiles

Wikis

Mail

Polls and Surveys

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


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 directory service 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!

Hardware, Operating System, Database, Network, Storage…

Application Server (WAS)

Application (Blogs, Dogear, etc.)

WAS Terminology

● Enterprise Application● An EAR and/or WAR file that implements some J2EE functionality

● Application Server● A single JVM running one or more enterprise applications

● 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

● Cell● Collection of nodes managed by a single Integrated Solutions Console

WAS Topology

Physical Machine (machine1)

Node (machine1)


Node (machine2)

Profile (AppSrv01)

Application Server (server1)

App

Cell (i.e. cell1)

Profile

Physical Machine (i.e. machine3)

Node (i.e. machine3)

Profile (i.e. AppSrv01)

Application Server (i.e. server1)

App (i.e. Profiles)

App

App App

App

App Server

App Server

App App

App Server

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

Cell (i.e. cell1)


Managed Node (machine3)

Profile (AppSrv01)

Application Server (server1)

App



Profile (AppSrv01)

Application Server

App



App

App Server

App App

App Server

NodeAgent

NodeAgent

NodeAgent


Node (machine4)

Profile (DM Type)

Application Server (dmgr)

App (admin console)

Central cell configrepository

Profile (AppServ01)

Cluster (i.e. cluster1)

Agenda


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

cluster, while other applications 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

options but also requires more system resources.

IBM Connections: Small Deployment

IBM Connections: Medium Deployment

IBM Connections: Large Deployment

Agenda


IBM Connections 5.0 Installation Overview

Cognos WizardCognos Wizard

UpgradeUpgrade&&

MigrationMigration4.x to 5.04.x to 5.0

WizardsWizards&&

CCMCCM

NewNew

Move from any GA orCR release to IC 5.0with updated migration tool & database wizard

ReadyReady

ImprovedImproved

Support for clustered BI server setup

Utilizes IBM Installation Manager

Support for BI server / Transformer separation Updated ccmDomainTool:

- more robust- post-install steps automated- log generated- more

Simplified CCM install process; no separate fixpack install required

Added File sync / push notification; Highway; Concerto library for SAML setup;Stellent libraries updated

GUI provided; better validation

Installation Manager to deliver CRs

Enhanced integration solution:- reduced steps: 13 to 9- also reduced for fix pack: 11 to 7

FileNet fixpack install scripts provided

CCM Extensions EAR for audit compliance

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● Configure IHS and SSL● (Optional) Create server startup and shutdown scripts

The process of actually installing IBM Connectionsis only a small step. Most of your time will

be spent installing and configuring the prerequistie applications / environment!

Installation Enhancements

● IBM Connections Installer● 9 additional languages now supported● CCM unselected by default

– Selecting CCM will auto select Communities

● Cognos● 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

mappings, configures LDAP, 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/

2. Visit the IBM Collaboration Solutions Ecosystem Development Community

Link → https://greenhouse.lotus.com/communities/community/icsecod

3. Learn new skills and share these links with your friends and colleagues!

http://greenhouse.lotus.com/

https://greenhouse.lotus.com/communities/community/icsecod

Architecture & Deployment · PDF fileIBM Connections Applications Activities Blogs Bookmarks...

Documents

Transcript of Architecture & Deployment · PDF fileIBM Connections Applications Activities Blogs Bookmarks...