Upgrading

When IBM® releases a fix pack for the IBM Product Master, you can upgrade the fix pack and upgrade.

Before you begin

Ensure that you have installed and configured the base version of IBM Product Master 12.0.
- For applying any interim fix, ensure that you have installed and configured full build of IBM Product Master 12.0.
  Example
  To apply IBM Product Master Fix Pack 1 Interim Fix 1, proceed as follows:
  IBM Product Master 12.0 GA > IBM Product Master 12.0 Fix Pack 1 > IBM Product Master 12.0 Fix Pack 1 Interim Fix 1
Download the fix pack from Fix Central to a user or temporary directory and extract the fix pack artifacts. For more information, see Extracting and installing the fix pack.
Review the lists of known issues and issues that are fixed in the latest release. These lists are available on the IBM Support website.
To see the detailed system requirements from Software Product Compatibility Reports (SPCR), search IBM Product Master in the following link.
Software Product Compatibility Reports
Password encryption utility Run the following command to generate an encrypted password that can then be pasted in the respective properties file.
```
$JAVA_RT com.ibm.ccd.common.generate.config.DBEncryptionUtils -encrypt --password=password 
```
Copy the existing env_settings.ini file at the $TOP/bin/conf/ having all important configuration to some other folder.
Avoid incompatibilities and issues in using the user interface, by cleaning your browser cache so that the latest JavaScript files are loaded and used by the user interface.
Stop the Product Master application on the local server.
- Check the scheduler to make sure that no critical jobs are running or need to complete.
- Stop the scheduler manually by running the following shell script, if the scheduler queue is clear:
  $TOP/bin/go/svc_control.sh --action=stop --svc_name=scheduler
- Check the workflow engine to make sure that no critical workflow events are running or need to complete by running the following shell script:
  $TOP/bin/go/svc_control.sh --action=short_status --svc_name=workflowengine
- Check the scheduler status to make sure that no critical jobs are running or need to complete by running the following shell script:
  $TOP/bin/go/svc_control.sh --action=short_status --svc_name=scheduler
- Shut down the workflow engine manually by running the following shell script, if no critical workflow events are running:
  $TOP/bin/go/svc_control.sh --action=stop --svc_name=workflowengine
- Stop all remaining Product Master services by running the following script, for all applications deployed in a cluster environment:
  $TOP/bin/go/abort_local.sh
  
  Note: Running the abort_local.sh shell script does not affect any of the other JVM services.
- Ensure that all processes are stopped by using the ps command.
- If the GDS feature is enabled,
  - Ensure that you stop the GDS message listener by running the following script:
    $TOP/bin/gdsmsg.sh stop
  - Allow the GDS message listener to finish processing the messages already picked up, and then run this script:
    $TOP/bin/gdsmsg.sh abort
Back up your system. The installation overwrites your current files with updated versions from the fix pack. If any issues occur when you install the fix pack, you can use this backup copy to roll back the installation.
- Create a full backup of all of your Product Master directories, especially where the following directories where the configuration files, common.properties, admin_properties.xml, and env_settings.ini are stored:
  - $TOP/etc/default
  - $TOP/bin/conf
- Back up the following GDS messaging files and restore them after the installation is completed:
  - $TOP/etc/default/gds.properties
  - $TOP/etc/default/.bindings
- Create a full backup of your database.