HCL Connections On-Premise Wiki: Education: start Tutorial - Installing Connections 4.0 on a Linux RHEL 6.3 64-bit System: LESSON 8: Intermediate Steps

start Tutorial - Installing Connections 4.0 on a Linux RHEL 6.3 64-bit System: LESSON 8: Intermediate Steps

Added by ~Kelly Rekromarobu | Edited by ~Kelly Rekromarobu on April 11, 2013 | Version 19

Actions ▼

Lesson 8 of a 10 part tutorial that walks through a single node installation of Connections on a Red Hat Enterprise Linux 6.3 64 bit system. In this lesson, you will install Connections 4.0 . At the end of this lesson, you will be able to Configure WAS to work with Domino LDAP, create a dedicated DB2 user and database required for Connections, and populate the Profiles database.

Tags: connections4 installation rhel63

ShowTable of Contents

HideTable of Contents

1 Overview
2 Task 1: Configure WAS to Work with Domino LDAP
3 Task 2: Create a Dedicated DB2 User for use with Connections
4 Task 3: Create a Database
5 Task 4: Populate the Profiles Database
6 Appendix A: Troubleshooting

Overview

This tutorial walks through a single-node installation of IBM Connections on a Red Hat Enterprise Linux 6.3 64-bit system . The first eight lessons are required to configure a working environment.

Introduction
Lesson 1: Preparing your system
Lesson 2: starting WebSphere Application Server (WAS)
Lesson 3: Installing IBM HTTP Server and Plugin
Lesson 4: Installing WAS Fix Packs
Lesson 5: Installing DB2
Lesson 6: Installing Tivoli Directory Integrator
Lesson 7: Installing a Domino LDAP Directory
Lesson 8: Intermediate Steps
Lesson 9: Installing IBM Connections 4.0
Lesson 10: Installing Cognos (optional - requires another VM with 4G RAM and 100G disk space)

Lesson objectives

In this lesson, you will do a few intermediate steps required before installing and verifying Connections 4.0.

At the end of this lesson, you will be able to complete the final requirements of configuring WAS to work with you Domino LDAP server. After creating a user and DB2 database dedicated for use with Connections, you will populate the database with users from your Domino LDAP server. At the end of this tutorial, you will be able to configure and test a single-node IBM Connections 4.0 environment running on a Red Hat Enterprise Linux 6.3 64-bit system.

After completing this lesson, you will be able to do the following:

Configure WAS to Work with Domino LDAP
Create a Dedicated DB2 User for use with Connections
Create a DB2 Database
Populate the Profiles Database

System requirements

A RHEL 6.3 64-bit machine with a minimum of 8G memory and 100G of disk space is required.

Resources

IBM Connections 4.0 Documentation

IBM Connections 4.0 on Linux

Task 1: Configure WAS to Work with Domino LDAP

In this task, we will modify settings in WAS so it is properly configured to work with a Domino LDAP server.
Note: Before beginning this task, be sure the Domino server is running LDAP. For details on how to start the server, see Lesson 7, task 2, step 13.

Step	Action
1	Check status of the Deployment Manager (DMGR) server. [root@connections4 bin]# cd /opt/IBM/WebSphere/AppServerDemo/bin/ [root@connections4 bin]# ./serverStatus.sh -all -user wasadmin -password *<YourPassword>* If it is not running, start it : [root@connections4 bin]# /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/bin/startManager.sh ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/logs/dmgr/startServer.log ADMU0128I: Starting tool with the Dmgr01 profile ADMU3100I: Reading configuration for server: dmgr ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server dmgr open for e-business; process id is 10687
2	Make a backup copy of your existing wimconfig.xml file. This will help you recover if you make a mistake. [root@connections4 bin]# cd /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/config/cells/connections4Cell02/wim/config [root@connections4 bin]# cp wimconfig.xml wimconfig.xml.bak
3	Open web browser and go to http://connections4.yourtestdomain.net:9060/admin In my case, I'm using a test machine and have multiple instances installed, so my listening port is 9061 instead of the standard 9060. So I will access http://connections4.xxx.yyy.yourco.com:9061/admin
4	Clicking Administrative Console should start the browser. You will receive a dialogue stating that the connection is untrusted. Expand I Understand the Risks then click Add Exception. Clicking Administrative Console should start the browser. You will receive a dialogue stating that the connection is untrusted. Expand I Understand the Risks then click Add Exception.
5	A subsequent confirmation dialogue will display. Click Confirm Security Exception.
6	At the Integrated Solutions Console (ISC), enter wasadmin and the password for credentials. Click Log in.
7	Once logged in to the ISC, click *Security* - *Global security. Scroll down to the User account repository* section and next to the Available Realm Definitions Federated repository field, click Configure.
8	Under *General Properties, in the section Repositories in the realm* click Add Base entry to Realm.
9	Click Add Repository.
10	Input the following values: Field Name Value Repository identifier -> MyLDAPRepository Directory type -> IBM Lotus Domino Primary host name of your Domino server -> yourhost.xxx.yyy.yourco.com Login properties -> uid;mail (this allows users to login with either their Domino shortname [uid] or email [mail] address) Click OK
11	In the field Distinguished name of a base entry that uniquely identifies this set of entries in the realm, type o=C4Tut. Click Apply and then *Save* directly to the master configuration.
12	Your are returned back to the Federated Repositories Page. Scroll down to the Repositories in the realm section. Under the Repository Identifier column, click MyLDAPRepository.
13	Now on Global Security -> Federated repositories -> My LDAPRepository, scroll down to the Additional Properties. Click LDAP entity types. Under Entity Type, click Group. Change the object classes mapping from groupOfNames to dominoGroup. Click Apply and then *Save* directly to the master configuration.
14	Click the PersonAccount entity type and modify the object class mapping from inetOrgPerson to dominoPerson. Click Apply and then *Save* directly to the master configuration.
15	Within the navigation options, click MyLDAPRepository. Scroll down. Under Additional Properties click Group attribute definition and then click Member attributes. Click member. Change the Object class from groupOfNames to dominoGroup. For Scope select Direct. Click Apply and then *Save* directly to the master configuration.
16	Set the MyLDAPRepository repository as the current repository. Click *Global Security* in the navigation trail at the top of the page. Scroll down. Select *Federated Repositories* from the Available realm definitions field, and then click Set as current.
17	Enable login security on WebSphere Application Server. Select the Enable Administrative Security and Enable Application Security check boxes. Click Apply and then *Save* directly to the master configuration.
18	Logout of the ISC.
19	Restart the server. [root@connections4 ~]# /opt/IBM/WebSphere/AppServerDemo/bin/stopManager.sh -user wasadmin -password <yourPassword> ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/logs/dmgr/stopServer.log ADMU0128I: Starting tool with the Dmgr01 profile ADMU3100I: Reading configuration for server: dmgr ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server dmgr stop completed. [root@connections4 config]# /opt/IBM/WebSphere/AppServerDemo/bin/startManager.sh ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/logs/dmgr/startServer.log ADMU0128I: Starting tool with the Dmgr01 profile ADMU3100I: Reading configuration for server: dmgr ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server dmgr open for e-business; process id is 21785
20	To configure Single Sign-On (SSO), use a browser to login to the server: http://connections4.xxx.yyy.yourco.com:9061/admin
21	Once logged in to the ISC, click *Security - Global security. In the Authentication* section, expand Web and SIP security and click Single sign-on (SSO)
22	Select the following options: Enabled Interoperability Mode Web inbound security attribute propagation. Also enter *.yourdomain.com* (NOTE: this value starts with a dot) Click Apply and then *Save* directly to the master configuration.
23	You should be returned to the Global security page. Expand Web and SIP security and click General settings.
24	Select Use available authentication data when an unprotected URI is accessed. Click Apply and then *Save* directly to the master configuration.
25	Result: You have successfully configured WAS to work with a Domino LDAP directory.

Task 2: Create a Dedicated DB2 User for use with Connections

In this task, we will create a DB2 database user called lcuser with a limited set of privileges. The scripts that are provided with IBM Connections grant the appropriate rights to lcuser and are written with the assumption that the user name is lcuser. Always use lower case characters for this user name.

Step	Action
1	Log into the DB2 server as the root user. Type the command below to create a new user named lcuser: [root@connections 4 ~]# useradd -u 1004 -g db2iadm1 -m -d /home/lcuser lcuser -p *password*
2	Reset the user's password to make sure it's set properly: [root@connections 4 ~]# passwd lcuser Changing password for user lcuser. You can now choose the new password. A valid password should be a mix of upper and lower case letters, digits, and other characters. You can use an 8 character long password with characters from at least 2 of these 4 classes. An upper case letter that begins the password and a digit that ends it do not count towards the number of character classes used, unless disable_firstupper_lastdigit_check option is enabled. Enter new password: Re-type new password: passwd: all authentication tokens updated successfully.
3	Result: You have successfully created a DB2 user for use with Connections.

Task 3: Create a Database

In this task, we will create a DB2 database required for Connections.

Step	Action
1	Locate the Connections file shown below that was downloaded and extracted in Lesson 1, Task 10 . It should be in the directory /opt/install/Connections. IBM_Connection40_Wzd_LNXAIX_CIA3HML.tar Part Number: CIA3HML Description: IBM Connections V4.0 Wizard for Linux, AIX Multilingual Note: If you do not have the file and need to download, go to XL Software Downloads or IBM Passport Advantage On-line Web site.
2	Login as user root. Complete the following steps: Type xhost + to grant display authority to other users. [root@connections4 ~]# xhost + access control disabled, clients can connect from any host Type echo $DISPLAY to echo the value of DISPLAY under the root user. Ensure that the current user is qualified or switch to a qualified user (e.g. su - db2inst1). Note: db1inst1 is the DB2 Admin created in Lesson 5, task 1, step 14. [root@connections4 ~]# echo $DISPLAY :1.0 [root@connections4 ~]# su - db2inst1 Type *export DISPLAY=<hostname:displaynumber.screennumber* where represents the client system, monitor number, and window number. Note: Enter the value you got from the previous echo $DISPLAY step. [db2inst1@connections4 ~]$ export DISPLAY=:1.0 Start the DB2 database instance by entering db2start. [db2inst1@connections4 ~]$ cd /home/db2inst1/sqllib [db2inst1@connections4 sqllib]$ . ./db2profile [db2inst1@connections4 sqllib]$ db2start** 02/27/2013 12:44:55 0 0 SQL1026N The database manager is already active. SQL1026N The database manager is already active.
3	Use the Database Wizard to create the Connections databases. Be sure to do all of these steps in the same terminal window. Login as root. Switch to the /opt/install/Connections directory and verify that the file IBM_Connection40_Wzd_LNXAIX_CIA3HML.tar exists. Move the file to the /opt/install directory. Unzip the install pack. Change ownership of the newly created Wizards directory so user db2inst1 is owner. Exit as root. (Should now be logged in as user db2inst1) Switch to the /opt/install/Wizards directory. Run ./dbWizard [db2inst1@database4 ~]$ su - [root@connections4 ~]# cd opt/install/Connections [root@connections4 Connections]# ls IBM_Connection40_Wzd_LNXAIX_CIA3HML.tar [root@connections4 Connections]# cd .. [root@connections4 install]# mv /Connections/IBM_Connection40_Wzd_LNXAIX_CIA3HML.tar . [root@connections4 install]# tar xvf IBM_Connection40_Wzd_LNXAIX_CIA3HML.tar ... [root@connections4 install]# chown -R db2inst1 Wizards [root@connections4 install]# exit [db2inst1@connections4 ~]# cd /opt/install/Wizards [db2inst1@connections4 Wizards]# ./dbWizard.sh
4	At the initial welcome screen, click Next.
5	At the Database task selection, select Create. Click Next.
6	At the Database selection, select DB2 Universal Database. Input your Database install location and the name of your database instance. Click Next.
7	For the application selection, select them all. Click Next.
8	At the Pre-configuration task summary, click Create.
9	At the Database creation detailed command, click Execute.
10	The database creation task will take approximately 15 minutes to complete.
11	The required database has been created and the LCUSER account has been given access. Click Finish.
12	Result: You have successfully created a database for use with IBM Connections.

Task 4: Populate the Profiles Database

In this task, we will copy users from the Domino LDAP server to the DB2 People Database.

Step	Action
1	Logout as db2inst1. As root user, start the Profiles Population Wizard. [db2inst1@connections 4 Wizards]$ exit logout [root@connections 4 ~]# cd /opt/install/Wizards [root@connections 4 Wizards]# ./populationWizard.sh
2	At the Welcome screen, click Next.
3	For profiles database type, click Next.
4	For the Profiles database properties, the values shown below. Click Next.
5	For the LDAP server connection, enter the name of the machine running LDAP. Note: The Domino LDAP server must be started before completing this step.
6	For the LDAP authentication properties, enter the fully distinguished name of the LDAP administrator user. For help, see Lesson 7, task 3 'Prepare for use with LDAP'.
7	For the Base distinguished name and filter for searches, enter the organization name that you created when configuring the Domino LDAP server in Lesson 7, task 2, step 5. Click Next.
8	For Profiles database mapping, leave the defaults. Click Next.
9	For Optional database tasks, leave the defaults. Click Next.
10	Review the Profiles population configuration summary and click Next.
11	It will execute the population the database with the few users previously created in the Domino LDAP server lesson.
12	When complete, you can review the results or open the log. Click Finish.
13	OPTIONAL: [db2inst1@connections4 Wizards]$ whoami db2inst1 [db2inst1@connections4 Wizards]$ db2 (c) Copyright IBM Corporation 1993,2007 Command Line Processor for DB2 Client 9.7.5 You can issue database manager commands and SQL statements from the command prompt. For example: db2 => connect to sample db2 => bind sample.bnd For general help, type: ?. For command help, type: ? command, where command can be the first few keywords of a database manager command. For example: ? CATALOG DATABASE for help on the CATALOG DATABASE command ? CATALOG for help on all of the CATALOG commands. To exit db2 interactive mode, type QUIT at the command prompt. Outside interactive mode, all commands must be prefixed with 'db2'. To list the current command option settings, type LIST COMMAND OPTIONS. For more detailed help, refer to the Online Reference Manual. db2 => connect to peopledb Database Connection Information Database server = DB2/LINUXX8664 9.7.5 SQL authorization ID = DB2INST1 Local database alias = PEOPLEDB db2 => connect to peopledb Database Connection Information Database server = DB2/LINUXX8664 9.7.5 SQL authorization ID = DB2INST1 Local database alias = PEOPLEDB db2 => describe table empinst.employee Data type Column Column name schema Data type name Length Scale Nulls PROF_KEY SYSIBM VARCHAR 36 0 No PROF_UID SYSIBM VARCHAR 256 0 No PROF_UID_LOWER SYSIBM VARCHAR 256 0 No PROF_LAST_UPDATE SYSIBM TIMESTAMP 10 6 No PROF_MAIL SYSIBM VARCHAR 256 0 Yes PROF_MAIL_LOWER SYSIBM VARCHAR 256 0 Yes PROF_GUID SYSIBM VARCHAR 256 0 No PROF_SOURCE_UID SYSIBM VARCHAR 256 0 No PROF_DISPLAY_NAME SYSIBM VARCHAR 256 0 Yes PROF_LOGIN SYSIBM VARCHAR 256 0 Yes PROF_LOGIN_LOWER SYSIBM VARCHAR 256 0 Yes PROF_GIVEN_NAME SYSIBM VARCHAR 128 0 Yes PROF_SURNAME SYSIBM VARCHAR 128 0 Yes PROF_ALTERNATE_LAST_NAME SYSIBM VARCHAR 64 0 Yes PROF_PREFERRED_FIRST_NAME SYSIBM VARCHAR 32 0 Yes PROF_PREFERRED_LAST_NAME SYSIBM VARCHAR 64 0 Yes PROF_TYPE SYSIBM VARCHAR 64 0 Yes PROF_MANAGER_UID SYSIBM VARCHAR 256 0 Yes PROF_MANAGER_UID_LOWER SYSIBM VARCHAR 256 0 Yes PROF_SECRETARY_UID SYSIBM VARCHAR 256 0 Yes PROF_IS_MANAGER SYSIBM CHARACTER 1 0 Yes PROF_GROUPWARE_EMAIL SYSIBM VARCHAR 128 0 Yes PROF_GW_EMAIL_LOWER SYSIBM VARCHAR 128 0 Yes PROF_JOB_RESPONSIBILITIES SYSIBM VARCHAR 128 0 Yes PROF_ORGANIZATION_IDENTIFIER SYSIBM VARCHAR 64 0 Yes PROF_ISO_COUNTRY_CODE SYSIBM VARCHAR 3 0 Yes PROF_FAX_TELEPHONE_NUMBER SYSIBM VARCHAR 32 0 Yes PROF_IP_TELEPHONE_NUMBER SYSIBM VARCHAR 32 0 Yes PROF_MOBILE SYSIBM VARCHAR 32 0 Yes PROF_PAGER SYSIBM VARCHAR 32 0 Yes PROF_TELEPHONE_NUMBER SYSIBM VARCHAR 32 0 Yes PROF_WORK_LOCATION SYSIBM VARCHAR 32 0 Yes PROF_BUILDING_IDENTIFIER SYSIBM VARCHAR 64 0 Yes PROF_DEPARTMENT_NUMBER SYSIBM VARCHAR 24 0 Yes PROF_EMPLOYEE_TYPE SYSIBM VARCHAR 256 0 Yes PROF_FLOOR SYSIBM VARCHAR 16 0 Yes PROF_EMPLOYEE_NUMBER SYSIBM VARCHAR 16 0 Yes PROF_PAGER_TYPE SYSIBM VARCHAR 16 0 Yes PROF_PAGER_ID SYSIBM VARCHAR 32 0 Yes PROF_PAGER_SERVICE_PROVIDER SYSIBM VARCHAR 50 0 Yes PROF_PHYSICAL_DELIVERY_OFFICE SYSIBM VARCHAR 32 0 Yes PROF_PREFERRED_LANGUAGE SYSIBM VARCHAR 100 0 Yes PROF_SHIFT SYSIBM VARCHAR 4 0 Yes PROF_TITLE SYSIBM VARCHAR 256 0 Yes PROF_COURTESY_TITLE SYSIBM VARCHAR 64 0 Yes PROF_TIMEZONE SYSIBM VARCHAR 64 0 Yes PROF_NATIVE_LAST_NAME SYSIBM VARCHAR 256 0 Yes PROF_NATIVE_FIRST_NAME SYSIBM VARCHAR 256 0 Yes PROF_BLOG_URL SYSIBM VARCHAR 256 0 Yes PROF_FREEBUSY_URL SYSIBM VARCHAR 256 0 Yes PROF_CALENDAR_URL SYSIBM VARCHAR 256 0 Yes PROF_DESCRIPTION SYSIBM CLOB 1048576 0 Yes PROF_EXPERIENCE SYSIBM CLOB 1048576 0 Yes PROF_SOURCE_URL SYSIBM VARCHAR 256 0 Yes PROF_SRC_UID_LOWER SYSIBM VARCHAR 256 0 No TENANT_KEY SYSIBM VARCHAR 36 0 No PROF_STATE SYSIBM INTEGER 4 0 No 57 record(s) selected. db2 => quit DB20000I The QUIT command completed successfully.
14	As user root, restart the server. [root@connections4 ~]# /opt/IBM/WebSphere/AppServerDemo/bin/stopManager.sh -user wasadmin -password <yourPassword> ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/logs/dmgr/stopServer.log ADMU0128I: Starting tool with the Dmgr01 profile ADMU3100I: Reading configuration for server: dmgr ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server dmgr stop completed. [root@connections4 config]# /opt/IBM/WebSphere/AppServerDemo/bin/startManager.sh ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/logs/dmgr/startServer.log ADMU0128I: Starting tool with the Dmgr01 profile ADMU3100I: Reading configuration for server: dmgr ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server dmgr open for e-business; process id is 21785
15	Result: You have successfully populated the DB2 PEOPLE database with a few users from the Domino LDAP server. In the real world, before doing this, you would plan your installation more carefully. The following are a few steps to consider: - Plan 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. - Pre-populate Profiles photos. - Plan for business card use and for Sametime presence awareness. - Ensure that TDI is properly configured. - Consider using TDI to populate the LDAP directory server prior to populating the Profiles database.

Next is Lesson 9: Installing IBM Connections!

Appendix A: Troubleshooting

Problem

You receive a segmentation fault similar to the following:

[db2inst1@connections4 Wizards]$ ./dbWizard.sh
No protocol specified
Exception in thread "main" org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
on17 Wizat org.eclipse.swt.SWT.error(SWT.java:4308)    at org.eclipse.swt.widgets.Display.createDisplay(Display.java:909)
ccon17 Wat org.eclipse.swt.widgets.Display.create(Display.java:897)    at org.eclipse.swt.graphics.Device.(Device.java:157)
    at org.eclipse.swt.widgets.Display.(Display.java:500)
    at org.eclipse.swt.widgets.Display.(Display.java:491)
    at org.eclipse.swt.widgets.Display.getDefault(Display.java:1681)
    at com.ibm.lconn.wizard.common.ui.ResourcePool.getDisplay(Unknown Source)
    at com.ibm.lconn.wizard.launcher.DBWizardLauncher.main(Unknown Source)
./dbWizard.sh: line 63: 28308 Segmentation fault      (core dumped) ${BIN_PATH}/javaw ${LOGLEVEL} -Djava.library.path=lib/linkfile com.ibm.lconn.wizard.launcher.DBWizardLauncher $1

Suggestion

Check the following:

If you got this crash on Task 3, step 3 above, be sure you ran all of the steps within the same terminal window. If the user running the shell script does not have access to the directory, it can crash like this. If unsure, repeat the steps and be sure to begin by running xhost +.

If you follow the steps correctly and continue to get a crash, verify that all of the correct libraries (packages) are installed. If not, apply the correct ones and retry.

Actions ▼

Attachments (0)

Versions (1)

Comments (0)

Copy and paste this wiki markup to link to this article from another article in this wiki.

Link:

Recent articles by this author

Using @mentions in Connections 4

Tutorial - Installing Connections 4.0 on a Linux RHEL 6.3 64-bit System: LESSON 9: Installing Connections 4.0