Installing the fix pack

After you download the fix pack, complete the steps that are listed here.

To extract the downloaded file, complete the following steps:

1. Change the directory to $TOP (or the current working directory) and verify that the correct permissions exist for unpacking the files by running the following command.

   cd $TOP | chmod –R 755 $TOP

2. Unpack the files by using the GNU Tar utility, so extract the TGZ file to the same folder where Product Master 12.0 version is installed by using the following command.

   gtar zxvf $TOP/<fix pack tar file name>

   Important: The Product Master files are packed by using the GNU gtar utility. Use the GNU Tar utility to unpack the archive file for best results, especially on computers that run on the AIX® operating system. If you use the AIX version of the tar command, you might not be able to unpack correctly all files in the archive. One indication of incorrect unpacking of the archive is the presence of the @LongLink file in the directory in which you unpack the archive.
3. Overwrite the existing env_settings.ini file in the extracted folder with your backup file.
4. Run the setup.sh script located in the $TOP folder.
5. Run the configureEnv.sh script located in the $TOP/bin folder to regenerate the compat.sh file.
   Note:

   • If the value of the encrypt_password=yes in the [db] section of the env_settings.ini file, you can avoid the password prompt by specifying dbpassword argument when you run the configureEnv.sh script.

     $TOP/bin/configureEnv.sh -dbpassword=database_password

   • If you customize the content of some configuration files (except common.properties) and you choose to overwrite such files when running the configureEnv.sh script, you need to manually restore customized values by using the backup copy. The file name of the backup copy is the name of the corresponding configuration file with the BAK suffix.
   • If you run the configureEnv.sh script two or more times, you can lose the original customized configuration files because every time the configureEnv.sh script is run, the generated backup copy has the same file name.
6. Run the compat.sh file to set most commonly used environment variables.
7. Verify that the db.xml file is created in the $TOP/etc/default folder.
8. Recompile the solution Java™ code by using the latest product JAR file that are included with the fix pack.
9. Redeploy the IBM® Product Master to the application server.
   Note: If you are using the Script workbench, when you install this fix pack the Script workbench communication .jsp and .jar files are removed from your server configuration.
10. Integrate the IBM Product Master and the WebSphere Application Server.
     Admin UI 
    1. Run the install_war.sh script in the $TOP/bin/websphere folder, with the following optional parameters.

       install_war.sh [ --wsadminUsername=WAS admin user name --wsadminPwd=password for WAS admin user] 

       The script installs the WAR file for each app server that is defined in the [services] section in the env_settings.ini file.
    2. If the WebSphere Application Server security is enabled, add the wsadminUsername and wsadminPwd arguments to the install_war.sh script.
       Note: Following arguments are no longer required in the $TOP/bin/start_local.sh, $TOP/bin/start_rmi_appsrv.sh, $TOP/bin/stop_local.sh, and $TOP/bin/rmi_status.sh commands.

       wsadminUsername=<WAS admin user name> --wsadminPwd=<password for WAS admin user> 

     Persona-based UI 
    1. Run the installAll.sh script in the $TOP/mdmui/bin folder, with parameters for update installation.

       installAll.sh

       The installAll.sh script installs the mdm-rest.war and mdm_ui.war WAR files. The script also configures features like dashboard, FTS, DAM, machine learning, and starts services based on the configuration.
       Note: If the Admin UI services are already started, then the script restarts it and starts the Persona-based UI services.
11.  GDS  If you want to install the GDS feature, run the install_gds_war.sh file in the $TOP/bin/websphere folder.
    Note: You need to configure GDS feature before you start the service. For more information, see Configuring GDS feature.