|Lesson 9 of a 10 part tutorial that walks through a single node installation of IBM Connections on a Red Hat Enterprise Linux 6.3 64 bit system. In this lesson, you will install IBM Connections 4.0 . At the end of this lesson, you will be able to install and configure IBM Connections in order to create a single node IBM Connections 4.0 environment running on a Red Hat Enterprise Linux 6.3 64 bit system.
ShowTable of Contents
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.
Lesson 1: Preparing your system
Lesson 2: Installing 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)
In this lesson, you will install IBM Connections V4.0 for Linux to complete the configuration of IBM Connections.
At the end of this lesson, you will be able to install IBM connections and verify a successful configuration. 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:
- Install Connections
- Verify Configuration
A RHEL 6.3 64-bit machine with a minimum of 8G memory and 100G of disk space is required.
Task 1: Install Connections
In this task, we will verify that the deployment Manager is started and we will install IBM Connections.
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
Part Number: CIA3EML
Description: IBM Connections V4.0 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
Login as root
and start the Deployment Manager (DMGR) server (if not already running).
[root@connections4 bin]# /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/bin/startManager.sh
ADMU0116I: Tool information is being logged in file
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
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 if not, copy it to this location
- Unpack the install pack (CIA3HML)
- Change to the newly created Connections/IBM_Connections_Install directory
- Run ./launchpad.sh
[root@connections4 ~]# cd opt/install/Connections
[root@connections4 Connections]# ls IBM_Connection40_Wzd_LNXAIX_CIA3HML.tar
[root@connections4 Connections]# tar xvf IBM_Connection40_Wzd_LNXAIX_CIA3HML.tar
[root@connections4 Connections]# cd IBM_Connections_Install
[root@connections4 IBM_Connections_Install]# ./launchpad.sh
If you are using a supported browser (see here
) then the launchpad should start successfully. There is a known issue with newer versions of Firefox where the launchpad with not start and may instead give you the following error:
An error occurred while starting the launchpad. This error typically occurs when the launchpad is unable to find a supported browser. Check your product's documentation for a list of supported browsers.
If this occurs, you have two options.
1. Uninstall the Firefox browser and also the xulrunner-17 package and it's dependant packages (should I list these ?
), then install a supported Firefox browser and xulrunner-10. Once this is done, you should be able to start the launchpad and begin the Connections installation.
2. Start the installer manually by doing the following steps:
a. Open a command prompt
b. Change to the IBM_Connections_install/IM/OS
directory, where OS
is your operating system
c. Enter ./install.sh
[root@connections4 ~]# cd /opt/install/Connections/IBM_Connections_Install/IM/linux
[root@connections4 linux]# ./install.sh
At the initial Installation Manager (IM)
dialogue, leave the options selected and click Next
Accept the license agreement and click Next
|For the location of the Installation Manager Directory, leave the default. Click Next.|
For the location of the Shared Resources Directory
, leave the default. Click Next.
|Leave the option select for Create a new package group. For the Installation Directory, leave the default set to /opt/IBM/Connections. Click Next.|
|For the feature to install, keep them all selected. Click Next.|
|At the Common Configuration dialogue, use the browse button to navigate to the path to the AppServer directory. Input the correct values for the additional fields and click Validate. After a few minutes, you should see a Validation Successful message. Click OK to return you to the Common Configurations screen. Click Next.|
Note: If you receive an error on the validate indicating "Application security is not enabled on the deployment Manager profile", it could be that global application security was not enabled. Please see Appendix A: Troubleshooting below.
|For the topology deployment type, choose Small. Enter C4Cluster as the Cluster Name. Check off the box next to the node and leave the default server name.|
For the Database Location
, enter the appropriate values and click Validate
. After a few minutes, you should get a dialogue showing that the validation was successful. Click OK
to continue. Click Next
The applications are on the same database instance: Yes
Database Type: DB2 Universal Database
DB server host name: <your host>
JDBC driver location: <Browse to the path where both of these files are located - db2jcc.jar and db2jcc_license_cu.jar>
Check box "Use the same password for all applications"
Enter the User ID and password that you created the databases with in Lesson 8, task 2.
In our case it is LCUSER. The password entered in the first field will propagate to all others.
|For the Cognos configuration, enter cogadmin for the Administration user ID and enter the password. This user was created in Lesson 7, step 3. Click Load node info. The other fields should be pre-filled. Click Validate then Next.|
For Content Store, accept the defaults and click Validate then Next.
|For Notification, select Enable Notification Only and WebSphere Java Mail Session. For the SMTP Server Information, enter the hostname of the Domino LDAP server created in Lesson 7, Task 2, Step 9. Enter port 25. Leave the other fields blank.|
On the install summary
, review and click Install
. This could take up to an hour.
When completed, click Finish
to exit the IBM Installation Manager
Note: The logs from the install are located in /opt/IBM/Connections/logs.
|Result: You have successfully installed and configured IBM Connections.|
For a deployment scenario showing the configuration details for a two-node cluster on RHEL 6.3, see here.
Task 2: Verify Configuration
In this task, we will verify the successful configuration and operation of IBM Connections.
Appendix A: Troubleshooting
You receive an error similar to the following:
CLFRP0007E: Application security is not enabled on the deployment Manager profile.
Be sure application security
in the Global Security panel. (The default is disabled.)
Check the following:
1. Click Servers > Server Types > WebSphere application servers > server_name.
2. Click Security > Security domain.
Security settings for this server override cell settings
Specifies that the settings on this panel override the settings on the Security > Global Security panel.
Enable application security
If necessary, see here
for more details.