Before installing for 4.0 migrationAdded by IBM on February 11, 2013 | Version 1 (Original)
|Verify that all necessary prerequisite conditions are complete before installing IBM® Connections.
Parent topic: Installing IBM Connections 4.0 for migration
Installing as a non-root user
Installing IBM WebSphere Application Server
Setting up federated repositories
Worksheet for installing IBM Connections
- Check the Release notes for late-breaking issues.
- Install all the required fixes for WebSphere® Application Server that are listed in the IBM Connections 4.0 Software Requirements webpage. In particular, ensure that PM65486 is installed because it prevents a problem with using IBM Installation Manager.
- If you previously installed IBM Installation Manager, update it to V1.4.4 or higher. For more information, go to the IBM Installation Manager updates webpage.
Note: Use the same user account to install IBM Installation Manager and IBM Connections.
- IBM Installation Manager presents three options for the type of deployment that you can install. For more information about these options, see the Deployment options topic.
- The IBM Connections installation process supports the creation of new server instances and clusters. Do not use existing clusters to deploy IBM Connections.
- You can install IBM Connections with either root or non-root accounts on AIX® and Linux™, or administrator or non-administrator accounts on Microsoft™ Windows™. For more information, see the Installing as a non-root user topic.
- Complete the Pre-installation tasks.
If you are migrating from IBM
Connections 3.0.1, you need to complete only the following tasks:
- Preparing to configure the LDAP directory
- Installing IBM WebSphere Application Server if you are installing on the same host as 3.0.1.
- Setting up federated repositories
- Do not complete the Pre-installation tasks for creating databases or populating the Profiles database. The migration process handles those tasks separately.
- Install IBM WebSphere Application Server Network Deployment (Application Server option) on each node. IBM Connections is installed on the system where WebSphere Application Server Deployment Manager is installed. For more information, see the Installing IBM WebSphere Application Server topic.
- Back up the profile_root/Dmgr01 directory.
- Configure WebSphere Application Server to communicate with the LDAP directory. For more information, see the Setting up federated repositories topic.
- Prepare directories to use as content stores. You need to provide shared content stores on network share devices and local content stores on each node. Both shared and local content stores must be accessible using the same path from all nodes and from the Deployment Manager.
- Set the system clocks on the Deployment Manager and the nodes to within 1 minute of each other. If these system clocks are further than 1 minute apart, you might experience synchronization errors.
- Copy the JDBC files for your database type to the Deployment Manager (DM) and then from the DM to each node. Place the copied files in the same location on each node as their locations on the DM. If, for example, you copied the db2jcc.jar file from the C:\IBM\SQLLIB directory on the DM, place the copy in the C:\IBM\SQLLIB directory on each node. See the following table to determine which files to copy:
Table 1. JDBC files
|Database type||JDBC files|
Note: Ensure that you are using the latest version of the ojdbc6.jar file.
- If you are going to use a trusted SSL certificate, ensure that is available before you begin the installation.
- If you do not plan to deploy IBM Cognos® Business Intelligence now to support metrics, you can still install the Metrics application along with the other IBM Connections applications. This enables Connections to begin collecting event data immediately and store it in the Metrics database for use when Cognos is available to provide reports.
- (Microsoft Windows) You must use an administrator account to install IBM Connections on Windows. If you are installing on Windows Server 2008, you must use a local administrator account. If you use a domain administrator account, the installation might fail.
- (Linux only) If you receive an error message after attempting to start IBM Installation Manager, you might need to install additional 32-bit libraries. For more information about required Linux libraries, see the Linux libraries topic. For more information about IBM Installation Manager errors, go to the Unable to install Installation Manager on RHEL 6.0/6.1 (64-bit) webpage.
- (AIX and Linux) Ensure that the directory paths that you enter contain no spaces.
- (AIX and Linux) Ensure that the Open File Descriptor limit is 8192. For information about setting the file limit, go to the Installation error messages topic and search for error code CLFRP0042E.
- (AIX only) IBM Installation Manager requires additional libraries for the AIX operating system. For more information, go to the Required filesets on AIX for Installation Manager webpage.
- (AIX only) If IBM Installation Manager hangs while being installed on your system, you might need to update your version of the software. For more information, read the IBM Installation Manager hangs on 64-bit AIX systems technote.
- (AIX only) If you are downloading IBM Installation Manager, the TAR program available by default with AIX does not handle path lengths longer than 100 characters. To overcome this restriction, use the GNU file archiving program instead. This program is an open source package that IBM distributes through the AIX Toolbox for Linux Applications at the IBM AIX Toolbox website. Download and install the GNU-compatible TAR package. You do not need to install the RPM Package Manager because it is provided with AIX.
After installing the GNU-compatible compression program, change to the directory where you downloaded the IBM Connections tar file. Enter the following command to extract the files from the file:
gtar -xvf Lotus_Connections_wizard_aix.tar
This command creates a directory named after IBM Installation Manager.