Installing a fix pack in interactive mode 

---

Install a fix pack to update IBM® Connections.

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 latest fix pack. See the Downloading fixes topic for more information.
• (AIX® or Linux™) If you installed Lotus Connections 3.0 as a root user, you cannot install this fix pack as a non-root user.
• 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:
1. 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.
2. Start this task again.
   
• You must run IBM Installation Manager on the system where the Deployment Manager is installed.
• User account:
• AIX or Linux: 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.
• Windows™: Use an operating system user account that is in the same Administrators group as the account that was used to install Lotus Connections 3.0.
  
  

About this task

To install the fix pack, complete the following steps:

Procedure

1. Stop all clusters in your deployment. Leave the Deployment Manager and node agents running during the fix pack installation.
2. From the IM_root directory, run the file to start the IBM Installation Manager:
• AIX or Linux: ./launcher
• Windows 32-bit: launcher.exe
Note: On Windows Server 2008, the launcher.exe file is in the IM_root\eclipse directory.

3. From the IBM Installation Manager menu, click File -> Preferences.
4. In the left pane of the IBM Installation Manager, click Repositories -> Add Repository.
5. Enter the full path to the fix pack that you downloaded and then click OK.
   
For example, C:\IBM\LotusConnections\update\fixes\LC3011_Fixpack.zip

The IBM Installation Manager indicates if it can connect to the repository.

6. Click OK to save the new repository.
7. Click Update.
8. The package group panel appears. Click Next to continue.
9. Select the fix packs to install and click Next.
10. Review and accept the license agreement by clicking I accept terms in the license agreements and then click Next.
11. Ensure that all the applications are selected and click Next.
    
Note: All of the installed applications are 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.

12. 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.

13. Configure your topology:
    
Note: The panel described in this step appears only if you selected new applications to install.

1. Select a topology solution. For more information about each option, see the Deployment options topic.
   
2. Enter the application cluster name for each application.
   
Note: IBM Installation Manager creates servers and clusters when required.

3. 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.

4. 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.

14. Enter the database information.
    
Note: The panel described in this step appears only if you selected new applications to install and if the new applications require database configuration.

1. 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.

2. Select a database type from one of the following options:
   
• IBM DB2 Universal Database™
• Oracle Enterprise Edition
• Microsoft SQL Server Enterprise Edition
  
  
3. Enter the location of the JDBC driver library. For example:
   
• AIX:
/usr/IBM/WebSphere/AppServer/lib

• Linux:
/opt/IBM/WebSphere/AppServer/lib

• Windows:
C:\IBM\WebSphere\Appserver\lib

4. Ensure that the following JDBC driver libraries are present in the JDBC directory:
   
DB2®
db2jcc.jar and db2jcc_license_cu.jar
Oracle
ojdbc6.jar
SQL Server
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 field.

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.

IBM recommends that you obtain this Microsoft hotfix for the JDBC 2 driver for production deployments.

5. Enter the Host name of the database server. For example:appserver.enterprise.example.com
   
If your installed applications use different database servers, enter the database host name for each application.

6. 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.

7. 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.

8. 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.

15. Review the summary information. Click Back to change the information or click Update to install the selected fix packs.
16. When the installation is complete, synchronize all the nodes and restart all the clusters.
    

Results

Your IBM 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 <application>Install.log file as well.

Parent topic: Installing fix packs

Related concepts
Updating 3.0 databases

Related tasks
Installing a fix pack in silent mode
Downloading fixes

Related reference
Installation error messages