Before installing for migration

Prerequisites

• Check the Release notes for late-breaking issues.

• Install required fixes for WAS listed in the IBM Connections Software Requirements web page.

• If we previously installed Installation Manager (IIM), .

  Use the same user account to install Installation Manager and Connections.

• Choose type of deployment

• The installation process supports the creation of new server instances and clusters. Do not use existing clusters to deploy IBM Connections.

• We can install Connections with either root or non-root accounts on AIX and Linux, or administrator or non-administrator accounts on Windows.

• Complete the pre-installation tasks.

  For migrations from IBM Connections 4.5, complete only the following tasks:

  • Prepare to configure the LDAP directory
  • Install IBM WebSphere Application Server if we are installing on the same host as 4.5.
  • Set 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 dmgr is installed.

• Back up the profile_root/Dmgr01 directory.

• Configure WebSphere Application Server to communicate with the LDAP directory.

• Prepare directories to use as content stores. 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 dmgr.

• Set the system clocks on the dmgr 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 the database type to the dmgr and then from the dmgr to each node. Place the copied files in the same location on each node as their locations on the dmgr.

  If, for example, you copied the db2jcc4.jar file from /opt/IBM/sqllib on the dmgr, place the copy in the C:\IBM\SQLLIB directory on each node.

• If we are going to use a trusted SSL certificate, ensure available before you begin the installation.

• If we do not plan to deploy IBM Cognos Business Intelligence now to support metrics, we can still install the Metrics application along with the other 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.

• (Windows) We must use an administrator account to install Connections on Windows. If we are installing on Windows Server 2008, use a local administrator account. If we use a domain administrator account, the installation might fail.

• (Linux only) If we receive an error message after attempting to start Installation Manager, we might need to install additional 32-bit libraries. See: Unable to install Installation Manager on RHEL 6.0/6.1 (64-bit) webpage.

• (AIX and Linux) Ensure the directory paths entered contain no spaces.

• (AIX and Linux) Ensure the Open File Descriptor limit is 8192. See error code: CLFRP0042E.

• AIX: Installation Manager requires additional libraries for the AIX operating system.

• AIX: If Installation Manager hangs while being installed on the system, we might need to Installation Manager hangs on 64-bit AIX systems technote.update the version of the software.

• AIX:If we are downloading Installation Manager, the TAR program available by default with AIX does not handle path lengths longer than 100 characters. Use the GNU file archiving program, distributed through the AIX Toolbox for Linux Applications at the IBM AIX Toolbox website. Download and install the GNU-compatible TAR package. The RPM Package Manager is already installed as part of AIX.

  After installing the GNU-compatible compression program, change to the directory where you downloaded the 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 Installation Manager.

Tips:

• Establish naming conventions for nodes, servers, clusters, and web servers.

• Use a worksheet to record the user IDs, passwords, server names, and other information

• Install and configuring IBM Connections is a complex process; not only should you read the instructions but also pay attention to the Before you begin prerequisites in each topic.

• Install Linux libraries
  The complete list of Linux libraries required for deploying IBM Connections.

Parent topic:
Install Connections 5.0 for migration

Related:
Deployment options
Install as a non-root user
Install IBM WebSphere Application Server
Set up federated repositories
Worksheet for installing IBM Connections