Installing the fix pack

Install the fix pack, by completing the steps that are listed here.

To install the fix pack, complete the following steps:

1. Copy the env_settings.ini file to the extracted folder and overwrite the existing file.
   Note: The existing env_settings.ini file of the InfoSphere® MDM Collaboration Server - Collaborative Edition 11.4 version was copied in the Extracting the fix pack files.
2. Remove the following properties from the common.properties file:
   • db_userName
   • db_password
   • db_url
   • db_class_name
3. Run $TOP/setup.sh script.
4. Run $TOP/bin/configureEnv.sh script.
   Important: If the value of the encrypt_password=yes in the [db] section of the env_settings.ini file to avoid password prompt, specify dbpassword argument while starting the configureEnv.sh script.
   $TOP/bin/configureEnv.sh -dbpassword=database_password
   Note:

   • 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 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 backup copy has the same file name.
5. Verify that the db.xml file is created in the $TOP/etc/default directory.
6. Recompile the solution Java™ code by using the latest product .jar files that are included in this patch.
7. Redeploy InfoSphere MDM Collaboration Server - Collaborative Edition to the application server.
   WebSphere Application Server® - The application server shell script, install_war.sh, installs InfoSphere MDM Collaboration Server - Collaborative Edition into the WebSphere®.

   1. Ensure that the default WebSphere Application Server (server1) is installed and running. You also need to verify that you can log in to the server. For more information about the default WebSphere Application Server, see the administration information in the WebSphere Application Server IBM Knowledge Center.
   2. Run install_war.sh script that is located in the $TOP/bin/websphere/ directory, with optional parameters:

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

      The install_war.sh script installs the WAR file for each app server that is defined in the[services] section in the env_settings.ini file.
   3. If WebSphere Application Server security is enabled,
      1. Add the wsadminUsername and wsadminPwd arguments to the install_war.sh script.
      2. 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>

   Optional

   GDS

   If you want to install the GDS feature along with InfoSphere MDM Collaboration Server - Collaborative Edition, you need to run the application server shell script for GDS, install_gds_war.sh, which is located in the $TOP/bin/websphere/ directory:

   install_gds_war.sh

   You need to configure GDS feature before starting the service. See Enabling the Global Data Synchronization (GDS) for details.

   Script Workbench

   If you are using the Script workbench for InfoSphere MDM Collaboration Server - Collaborative Edition, when you install this fix pack, the Script workbench communication .jsp and .jar files are removed from your server configuration.