Installing Update Packages for HCL Commerce Developer (silent method)

You can use a silent method to install an Update Package on a HCL Commerce Developer environment.To install silently, IBM Installation Manager requires a response file to provide the input. A response file is generated by installing the Update Package on a machine by using the interactive method. The options that you choose in the GUI are recorded in a file. Then, you can use the response file on other machines to install the Update Package silently.

Before you begin

Installing or updating the product to a later version is a processor and memory intensive operation. Your machine can become unresponsive for extended periods of time, during which you may observe applyUpdate.bat consuming large amounts of system resources.
Note: Allow sufficient time for the install or update process to complete as the applyUpdate.bat progress indicator can remain at 99% for up to two hours on less powerful machines.
Stop any Java applications that are running on your machine.
Ensure that Rational Application Developer is not running.
Disable any Web server that you configured on your machine.
Log in to Windows as a user with Administrator privileges.
Backup your system before you create the response file. Creating a response file might create conflicting files on your system. These conflicting files can cause issues when you use the response file to install the Update Package.
If you do not have the Update Package, download and extract the Update Package that you want to install.
1. Log in to HCL License and Delivery portal.
2. Search for the Update Package by part number. For information about available part numbers, see HCL Commerce releases.
  Note: The Update Package can update to the target version from any previous version. For example, if you are on 9.0.0.0 and want to update to 9.0.0.2, you only need to download the 9.0.0.2 Update Package.
3. Download and extract the package.
Back up your database. The database updates that are included in this update cannot be undone. If you want to undo the database update, you must restore your database from a back up. For more information about how to back up, see BACKUP DATABASE COMMAND.

Procedure

Create a response file.
If you already have a response file, skip to Step 2.
1. In a command prompt, go to the eclipse subdirectory in the directory where you installed IBM Installation Manager.
  For example, drive:\Program Files\IBM\Installation Manager.
2. Run the IBM Installation Manager by using the following commands to create a response file:
  Important: Ensure that you enter a file path that exists. Installation Manager does not create directories for the response file and the log file.
  - To create the response file and install the product:
```
IBMIM –record response_file_path
```
    For example, IBMIM –record C:\WCDE_v9\installresponse.txt.
  The Installation Manager starts.
3. Complete the steps in the Installation Manager to install the Update Package by using the interactive method.
  The options that you choose while you use the interactive method are recorded in the response file. For more information about using the interactive method, see Installing Update Packages (interactive method).
  Remember: Ensure that you set the repository preferences to the location of the HCL Commerce Developer installation image during the recording of the response file.
4. Click Finish, then close Installation Manager to save and finalize the response file.
  
  Note: The response file is generated only after you click Finish and exit Installation Manager.
5. Revert your system back to the state it was in before you created the response file.
Copy the response file, response_file_path, to the machines that intend to use the file for a silent installation.
Open the target response file in a text editor.
Modify the entries in the response file to match the installation options that you want.
- Remove any unnecessary repositories that are in the response file.
- Update any entries as needed to match the machine that will be using the response file.
On the command line, start the silent installation process:
1. Go to the eclipse/tools subdirectory of Installation Manager.
2. Run the following command.
```
imcl.exe -input response_file_path -log log_file_path -acceptLicense
```
  Note: Add the -sP parameter to obtain more installation progress information.
Where
- response_file_path is the full path of the response file
- log_file_path is the full path of log file, for example c:\logs\maintenance_install.log. The full path must exist, for example, c:\logs\.
Check for any issues in the WCDE_installdir\UpdateDelta\9.0.x.y\applyUpdate.log file.
- The x and y values represent the Update Package level.
Merge files as needed.
If any files were added, updated or removed by the developer since the last installation, and also added, updated or removed by the update, these files are recorded during the process.
1. Check for any issues in the WCDE_installdir\UpdateDelta\9.0.x.y\backup\merges.log file.
  Note:
  - All files that overlap with changes in the Update Package are backed up to the WCDE_installdir\UpdateDelta\9.0.x.y\backup directory before making any changes to your workspace. However, only the files that require review after installation are recorded in the merges.log.
  - It is possible that some files that are updated might have paths or information that is specific to your environment after installation. In these cases, the replacement file will contain an updated template version of the file, before any variables are replaced. You must manually merge these files, replacing the variables in the updated file with the values from the backup version of the file to ensure that your environment continues to function correctly.
2. For each pair of files in merges.log, compare the original version with the updated version using a text file comparison tool.
3. For each file that was described as deleted by the update process, review the original version to determine if it is still needed and make appropriate changes.
4. If you deleted a compressed archive (ZIP, JAR, WAR) and the update process modifies that archive, the archive is recreated by the update process, but will only contain the changed files in the archive so it will be incomplete. In this case a warning is written to merges.log, recommending to rollback, restore the original archives, and reapply the update. For this reason, it is recommended that you do not delete any compressed archives, even if they are not used.
Update the database to the latest HCL Commerce database schema.
1. Back up the database.
  You need to back up because if you ever uninstall an update, you need to also restore the database to the earlier version. For more information about how to back up, see BACKUP DATABASE COMMAND.
2. Update the wcs.9.0.0.2.bootstrap.xml file.
  HCL is aware of an issue with an XML file in the Version 9.0.0.2 Update Package that causes the updatedb utility to fail. The fix will be resolved in the next update. Complete the following steps to immediately fix the issue and finish the update to Version 9.0.0.2.
  1. Open the WCDE_installdir/schema/data/xml/9.0.0/wcs.9.0.0.2.bootstrap.xml file for editing.
  2. Wrap the contents of the file with <import> </import>.
  3. Save the file.
3. Run the updatedb utility to update your database.

What to do next

Verify your search index data.
Refresh the workspace and republish the application after the update is completed.
1. Open HCL Commerce Developer and switch to the Enterprise Explorer view.
2. In the Explorer view, select all projects and select File > Refresh (or the F5 keyboard shortcut) to refresh the projects in the workspace.
3. (Optional) If you enabled workspaces in HCL Commerce Developer Version 9.0.0.0 and you just installed Version 9.0.0.1, complete the following steps for workspaces to function in 9.0.0.1.
  1. Open the Administration console, and go to Application Server > server > Process definition > Java Virtual Machine. server is the name of your server, and the default value is server1.
  2. In the Generic JVM argument field of the Configuration tab, add the following string.
```
-DWorkspaceTaskListEnabled=true
```
  3. Save your changes to the master configuration.
4. Start or restart the test server
5. Right-click the test server in the Servers view and select Publish.
6. Wait for the application to finish publishing and to restart.