For IBM i OS operating systemSolarisLinuxAIXWindows

Installing feature packs interactively on a WebSphere Commerce clustered environment

If you have a WebSphere Commerce clustered environment, you can install the required fix pack and feature pack using an interactive method, which uses a graphical install wizard.

Before you begin

To install the WebSphere Commerce feature pack, your system must meet the following prerequisites:

Ensure that you have the appropriate privileges:
  • AIXLinuxSolarisLog on:
    • As a root user
    • WebSphere Commerce Version 7.0.0.9 or laterFeature Pack 8Or as a non-root user that owns WC_installdir
  • WebSphere Commerce Version 7.0.0.9 or laterSolarisLinuxAIXFeature Pack 8If you want log on as a non-root user, ensure that the non-root user owns the appropriate .profile file and consider the following installation limitations.
    • Feature packs that are installed by a non-root user cannot be registered through native operating system mechanisms, such as the Red Hat Package Manager (RPM) on Linux. WebSphere software registers in the installation registry file and the vpd.properties file. All installed components are fully functional despite the lack of native registration.
    • Feature packs installed by the root user must be uninstalled by the root user only.
    If you accept the limitations, to change ownership, perform the following steps:
    1. Log on as the root user.
    2. If the directory /tmp/niflog/ exists, create a backup and then remove the directory.
    3. Change the ownership of /home/non-root_userdir/.profile to non-root user and the non-root user group. For example, change ownership of /home/wasuser/.profile to wasuser and wasgroup.
    4. Set the non-root user's umask to 0027.
  • For IBM i OS operating systemLog on with a user profile that has *SECOFR authority.
  • WindowsLog on to a user that has Windows Administrative user rights.
For IBM i OS operating system

About this task

If you are on IBM i, you cannot install WebSphere Commerce fix packs interactively. Instead, follow the steps for installing the fix pack silently.

Procedure