Install the 3.0.1 fix pack to update Lotus
® Connections 3.0 to IBM
® Connections 3.0.1.
Before you begin
- Update your Lotus Connections 3.0 databases. For more information, see the Updating 3.0 databases topic.
- Ensure that you have downloaded and extracted the 3.0.1 fix pack. See the Downloading fixes topic for more information.
- If you installed IBM Connections 3.0 as a root user, you cannot install this fix pack as a non-root user.
- You have downloaded the IBM Connections 3.0.1 wizards. Search for the following part number on the Passport Advantage® website:
- AIX® or Linux®: CZVR1ML
- Windows®: CZVQ9ML
- If an error occurs during installation, IBM Installation Manager cancels the installation and rolls back the installation files. Installation errors are usually caused by environment problems such as insufficient disk space, privilege issues, or corruption of a WebSphere® profile. If your installation is cancelled, complete the following steps:
- Identify and resolve the error that caused the cancellation. After cancelling the installation, IBM Installation Manager displays an error message with an error code. You can look up the error code in the Installation error messages topic or check the log files.
- Start this task again.
About this task
You must use the same operating system user account to install this fix pack that was used to install Lotus
Connections 3.0. If that account is no longer available, recreate it with the same user name and password and use it to install the fix pack.
Run the wizard on the system where the Deployment Manager is installed. The update installer uses IBM
Installation Manager to install the fix pack.
To install the fix pack, complete the following steps:
- Stop all clusters in your deployment.
- From the IM_root directory, run the file to start the IBM Installation Manager:
From the IBM Installation Manager menu, click File -> Preferences.
In the left pane of the IBM Installation Manager, click Repositories -> Add Repository.
Enter the full path to the fix pack that you downloaded and extracted and then click OK. The IBM Installation Manager indicates if it can connect to the repository.
Click OK to save the new repository.
Select a package group, such as IBM Lotus Connections, for which to find an update.
Select the fix packs to install and click Next.
Review and accept the license agreement by clicking I accept terms in the license agreements and then click Next.
Ensure that all the applications are selected and click Next.
- AIX or Linux: ./launcher
64-bit, the launcher.exe
file is in the IM_root
- Windows 32-bit: launcher.exe
Server 2008, the launcher.exe
file is in the IM_root
Note: All of the installed applications are selected by default. The new Moderation application is also selected by default. If you add any of the unselected applications, those applications will be installed. If you clear any of the selected applications, those applications will be uninstalled.
Enter the administrative ID and password of the Deployment Manager.
Note: This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following J2EE roles: dsx-admin, widget-admin, and search-admin. It is also used to by the service integration bus. If you plan to use security management software such as Tivoli® Access Manager or SiteMinder, the ID that you specify here must exist in the LDAP directory so that it can be recognized by that software. For more information, see the Switching to unique administrator IDs for system level communication topic.
Configure your topology.
Enter the database information.
- This step applies only if you have selected new applications to install.
- The default cluster names in a Medium deployment have changed in version 3.0.1:
- The default cluster name for the Activities, Communities, Profiles, and Forums applications has changed from LCCluster1 to Cluster1.
- The default cluster name for the Blogs, Dogear, Files, Wikis applications has changed from LCCluster2 to Cluster2.
- The default cluster name for the Home page, Mobile, News, and Search applications has changed from LCInfraCluster to InfraCluster. This cluster also includes the Moderation application.
If you do not want to create new clusters, ensure that you install any new applications in the corresponding cluster from version 3.0.
- Select a topology solution. For more information about each option, see the Deployment options topic.
- Enter the application cluster name for each application.
Note: IBM Installation Manager creates servers and clusters when required.
- Accept the predefined node selection or select a different node.
Note: These nodes host application server instances that host IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.
- Enter the server member name for the selected node. Choose the default or enter a custom name.
Note: If you enter a custom server member name, the name must be unique across all nodes in your deployment.
Review the summary information. Click Back to change the information or click Update to install the selected fix packs.
Copy the lotus_connections_root/news/news/news/news.config/news directory to the profile_root/Dmgr01/config/cells/<cell name>/LotusConnections-config directory.
When the installation is complete, synchronize all the nodes and restart all the clusters.
The panel described in this step appears only if you selected new applications to install and if the new applications require database configuration.
- Specify whether the installed applications use the same database server or instance: Select Yes or No.
Note: If allowed by your database configuration, you can select multiple database instances as well as different database servers.
- Select a database type from one of the following options:
Enter the location of the JDBC driver library. For example:
- IBM DB2 Universal Database™
- Oracle Enterprise Edition
- Microsoft SQL Server Enterprise Edition
Ensure that the following JDBC driver libraries are present in the JDBC directory:
Enter the Host name of the database server. For example:appserver.enterprise.example.com
db2jcc.jar and db2jcc_license_cu.jarOracle
Download the SQL Server JDBC 2
driver from the Microsoft
website to a local directory and enter that directory name in the JDBC driver library
The directory must not contain the sqljdbc.jar
file, only the sqljdbc4.jar
file. Even though the datasource is configured to use the sqljdbc4.jar
file, an exception occurs if both files are present in the same directory.
recommends that you obtain this Microsoft hotfix for the JDBC 2 driver
for production deployments.
If your installed applications use different database servers, enter the database host name for each application.
Enter the Port of the database service. The default values are: 50000 for DB2, 1521 for Oracle, and 1433 for SQL Server.
If your installed applications use different database servers or instances, enter the database port for each application.
Enter the database user ID and password for each application.
If your database type is Oracle, you must connect to the database with the user ID that you used when you created the application databases.
Click Validate to verify your database settings. If the validation fails, check your database settings. When the validation succeeds, click Next.
IBM Installation Manager tests your database connection with the database values that you supplied. You can change the database configuration later in the WebSphere Application Server Integrated Solutions Console.
Connections deployment has been updated. To check the logs, go to the lotus_connections_root/logs
directory and open the <application>Update.log
file, where <application>
is the name of an IBM
Connections application. If you added new applications, check the @nowiki@20application>Install.log
file as well.
What to do next
Complete any relevant post-update tasks. For more information, see the Post-update tasks
Parent topic: Installing the 3.0.1 fix pack
Updating 3.0 databases
Installing the 3.0.1 fix pack in silent mode