Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Connections On-Premise Wiki
  • THIS WIKI IS READ-ONLY.
  • HCL Forums and Blogs
  • Home
  • API Documentation
Search
Community Articles > Deployment Scenarios > IBM Connections 4.0 Deployment Scenario - Red Hat upgrade for DB2
  • Share Show Menu▼

Recent articles by this author

How to set up embedded Connections Content Manager with Connections 4.5
This procedure describes how to set up Connections Content Manager (CCM) with Connections by using the Embedded installation path.

How to set up Cognos and metrics for Connections 4.5
This document assumes that you do not have Connections 4.5 installed. It describes the procedure to install Cognos and the Cognos fix packs correctly and the Connections installation steps that deal with Cognos integration to get metrics to work against Connections 4.5.

IBM Connections 4.5: How to Deploy a Two Node Cluster of Connections V4.5 on a RedHat (RHEL) Server V6.4 (x86-64bit)
Contents 1. Deployment topology 2. Connections system requirements 3. Middleware installation and configuration 3.1 Install Installation Manager 1.5.3 3.2 Install WAS V8 Deployment Manager (DM) 3.3 Install WAS V8 Applications Server on Node1 and Node2 3.4 Install HTTP Server (IHS) ...

IBM Connections V4.5: How to configure Tivoli Access Manager (TAM) V6.1.1.
Configuring TAM

IBM Connections V4.5: How to configure SPNEGO
Configure IBM® Connections to use SPNEGO for single sign-on (SSO). This configuration permits users to sign in to the Windows desktop and automatically authenticate with Connections.
Community articleIBM Connections 4.0 Deployment Scenario - Red Hat upgrade for DB2
Added by ~Manny Ekwegenettu | Edited by ~Manny Ekwegenettu on January 9, 2013 | Version 2
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
The objective of this document is to detail the experiences of the System Verification Test (SVT) team Upgrading Connections 4.0 in-place upgrade with SPNEGO. The goal of testing was to ensure that data that was migrated from Connection 3.0.1.x to Connections 4.0 performed as expected when integrated with SPNEGO.
Tags: spnego, dbs, red hat, 4.0_deployment
ShowTable of Contents
HideTable of Contents
  • 1 Overview
  • 2 About the author

Overview


A .pdf version of this document may be downloaded from the Attachments section below.

The components that are required to install and configure in this scenario are Lotus Connections 3.0.x Medium deployment, SPNEGO Domain. All Domains are configured to share LDAP and SPNEGO Domain, and SSO is implemented with a common LTPA token. The operating system used this environment is RHEL 6.2 on a VM.

The environment includes the following assumptions to migrate for the in-place upgrade:
  • Lotus Connections 3.0.x Medium Cluster deployment
  • LDAP server: Microsoft Active Directory 2008
  • Domain: SPNEGO
  • Database: DB2 9.7

About the author


Srinivas Allampally is a software engineer for IBM Collaboration Solutions.

  • Actions Show Menu▼


expanded Attachments (1)
collapsed Attachments (1)
Edit the article to add or modify attachments.
File TypeSizeFile NameCreated OnDelete file
application/pdf 7,061 KB IC4PD107.pdf 1/2/13, 3:15 AM
expanded Versions (2)
collapsed Versions (2)
Version Comparison     
VersionDateChanged by              Summary of changes
2Jan 9, 2013, 2:05:49 AM~Manny Ekwegenettu  
This version (2)Jan 9, 2013, 2:05:49 AM~Manny Ekwegenettu  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility