Install interim fixes in interactive mode

Install interim fixes with the update wizard in interactive mode.

For information about prerequisites, see the Installing interim fixes topic.

An interim fix is a noncumulative fix that resolves a single issue. This topic describes the steps to install an interim fix only; it does not include information about how to prepare the production environment before installing the fix.

By using the update wizard, we can interact with each step in the procedure.

We can install multiple fixes in this procedure, by copying all fixes to a single location. .

To install an interim fix in interactive mode:

A WAS admin user and password with a word space is not supported. Use a WAS admin user and password without a word space to install fixes.

1. Stop all the clusters that host Connections applications.

2. Configure the command line:
   cd WebSphere/AppServer/bin
   . setupCmdLine.sh

3. When updating to Connections 5.0, replace updateInstaller by running chmod for the new UpdateInstaller. For example:
   cd /opt/IBM/Connections/updateInstaller
   ./ chmod ugo+x *

Start the installation wizard from the updateInstaller in the connections_root directory, and run the following script:

cd /opt/IBM/Connections/updateInstaller
./updateWizard.sh

On the Welcome page, click Next to continue.

Enter the location of the fixes in the Fix location field, or click Browse to navigate to the location of the fixes and then click Next.

The update wizard scans the location for fixes.

Select the check boxes of the fixes to install and then click Next.

Confirm whether you backed up any customizations made to the Connections interface.

This input does not validate any such backup; it is just a reminder to consider backing up any customizations because updates to the deployment could overwrite the customizations.

Enter the WAS dmgr administrator ID and password for each application, and then click Next.

Review the information entered. To edit the input, click Back. To start the update, click Next.

The installation process can take up to 10 minutes to complete.

Review the result of the update. Click Finish to exit the wizard.

Remove temporary WebSphere Application Server directories such as...

app_server_root/profiles/AppSrv01/temp

Perform a full synchronization to push the update to all nodes.

Results

The log files created by the wizard are located under the directory...

connections_root/version/log

Check the <timestamp>_<fix name>_<feature name>_install.log to find the Build Successful message near the end of the file. If this exists, you have installed fixes successfully. Otherwise, uninstall the fix and then install again.

What to do next

Your IBM Connections deployment was updated. To check the logs, go to the IM_root directory, and open the applicationUpdate.log file, where application is the name of a Connections application.

If we receive an installation failed message for any of the components in the summary screen, check the installation logs. If we see the error: Failure could be caused by OSGI cache issue, refer to the instructions in this technote. Next, perform a resynchronization of the nodes, and then rerun the updateInstaller wizard. The components previously marked as failed now should be eligible for upgrade. Processing this upgrade for the components should succeed on the second attempt. If it fails a second time, contact the IBM vendor.

Parent topic:
Install interim fixes