Installing interim fixes in silent mode

Install interim fixes with the update wizard in silent mode.

1. Stop all the clusters that host IBM® Connections applications.
2. From the updateInstaller directory under the connections_root directory open a command prompt and enter the following commands (without the carriage returns):
   • AIX:

     chmod +x updateSilent.sh
     ./updateSilent.sh -fix -installDir connections_root
     -fixDir fix_file_location -install 
     -fixes APAR_number_of_fix 
     -wasUserId AdminUserID 
     -wasPassword AdminPasswordAdminPassword 
     -featureCustomizationBackedUp backup_status

   • Linux:

     chmod +x updateSilent.sh
     ./updateSilent.sh -fix -installDir connections_root
     -fixDir fix_file_location -install 
     -fixes APAR_number_of_fix 
     -wasUserId AdminUserID 
     -wasPassword AdminPasswordAdminPassword 
     -featureCustomizationBackedUp backup_status

   • Windows:

     updateSilent.bat -fix 
     -installDir connections_root
     -fixDir fix_file_location -install 
     -fixes APAR_number_of_fix 
     -wasUserId AdminUserID 
     -wasPassword AdminPasswordAdminPassword 
     -featureCustomizationBackedUp backup_status

   • IBM i:
     Note: For IBM i, you must comment out the export QIBM_JAVA_STDIO_CONVERT=Y property of the ConfigEngine.sh script typically located in the /QIBM/ProdData/IBM/Connections/ConfigEngine directory.

     updateSilent_OS400.sh -fix 
     -installDir connections_root
     -fixDir fix_file_location -install 
     -fixes APAR_number_of_fix 
     -wasUserId AdminUserID 
     -wasPassword AdminPasswordAdminPassword 
     -featureCustomizationBackedUp backup_status

   where

   • fix_file_location is the directory containing the downloaded fixes
   • APAR_number_of_fix is the APAR number of the fix (such as LO36338)
   • AdminUserId is the administrative user name for WebSphere® Application Server Deployment Manager. A space in the WAS admin user and password is not supported. You need to use a WAS admin user and password without space to install fixes.
   • AdminPwd is the password for that user
   • backup_status confirms whether you backed up any customizations that you made to the IBM Connections interface. The possible values are yes|no. This parameter does not validate any such backup; it is just a reminder to consider backing up any customizations because updates to your deployment could overwrite your customizations.
   • homepageDBSchemaUpdatesHaveBeenCompleted is for acknowledgement that the schema must be updated as part of CR2 upgrade and is required. The possible values are yes|no. The database schema update can be performed at any time during the CR2 upgrade maintenance window. The database must be upgraded prior to restarting the server with CR2 applied. For more information about updating the Homepage Database schema, refer to this technote.

   Note:

   If you do not know the APAR number of the fix, the fix JAR filename contains it. It is the string starting with "LO" and followed by 5 digits. Example: For fix JAR 4.0.0.0-IC-News-IFLO12345.jar, the APAR is LO12345.

   For example:./updateSilent.sh -installDir /opt/IBM/Connections -fix -fixDir /opt/IBM/Connections/update/fixes -install -fixes LO36338 LO34499 LO34327 LO35077 LO34966 -wasUserId wasadmin -wasPassword wasadmin -featureCustomizationBackedUp yes

   Note: For IBM i, if you want to install the fix for Wikis (LO75060-IC4500-CR01-Wikis.jar) shipped in the CR package, use the following example as a guide:

   updateSilent_OS400.sh -installDir /QIBM/ProdData/IBM/connections -fix -fixDir /QIBM/ProdData/IBM/connections/updateinstaller/fixes -install -fixes LO75060-IC4500-CR01-Wikis -wasUserId wasadmin -wasPassword password -featureCustomizationBackedUp yes

3. Remove the content of temporary WebSphere Application Server directories such as the app_server_root/profiles/AppSrv01/temp directory.
4. After installing the fixes, perform a full synchronization to push the updates to all nodes.