Preparing to install maintenance

These steps prepare you to install WebSphere Commerce fix packs and mod packs. Review all of the following information before you continue with your WebSphere Commerce maintenance installation.


  1. Obtain the maintenance package that you want to install from IBM Fix Central.
  2. Apply any relevant fixes.
    WebSphere Commerce fix packs are tested with the WebSphere Application Server maintenance levels that are available when the WebSphere Commerce fix pack is released. You can install a WebSphere Commerce fix pack on these maintenance levels, or on later maintenance levels. Ensure that you applied the Required and recommended fixes for WebSphere Commerce.
  3. Ensure that you have sufficient disk space to install the maintenance package.
    It is recommended that the amount of free disk space is at least two times the size of your wc.ear file.
  4. Ensure that you are using the latest version of the WebSphere Commerce Update Installer.
  5. Ensure that the user that is running the Update Installer has the proper authority.
    • LinuxAIXThe user must be able to successfully execute chmod and su - non-root_user without any prompt for a password during a maintenance installation to a WebSphere Commerce instance.
    • For IBM i OS operating systemThe user must have *SECOFR authority.
  6. Disable your firewall, or allow access to the WebSphere Application Server administrative server.
    If you installed a firewall on your machine, the firewall can interfere with the application of the fix pack.
  7. Review firewall considerations for STMP servers.

    Some firewalls might be configured to introduce a delay after several NOOP messages are received to protect against Denial of Service attacks. You must either validate the firewall and SMTP configurations for NOOP messages, or set mail.smtp.userset to true.

    For more information, see Configuring validation for No Operation (NOOP) messages.

  8. Ensure that your custom assets are properly deployed. See Deploying.
  9. Back up your database. See your database vendor manual for information about how to back up your database.
  10. Back up your WebSphere Application Server configuration and EAR files.
  11. Back up the configuration of your node using the backupConfig command.
  12. Back up the following EAR files:
    • WebSphere Commerce: WC_profiledir\installedApps\cell_name\WC_instance_name.ear
    • WebSphere Commerce search: WC_profiledir\installedApps\cell_name_search_cell\Search_instance_name.ear\