Operating system prerequisites for installing WebSphere Commerce

Before you install WebSphere Commerce, ensure that your operating system meets all listed requirements.

Notes: Ensure that your system clock is set accurately and consistently for all server tiers (web, application, and database).

WebSphere Commerce Version 7.0.0.2 or laterAIX Version 7.1 (64-bit)

To install WebSphere Commerce, ensure that the operating system meets the following prerequisites:
  • 64-bit AIX kernel is required
  • Check your operating system level by issuing the following command:
    oslevel -s 
    This command returns the following value, or higher: 7100-00-01-xxxx. For example, 7100-00-01-1037 meets the minimum requirement. If the output from the command does not end in -01-xxxx or higher, you are at the incorrect maintenance level for WebSphere Commerce. Obtain the correct maintenance level: IBM Fix Central
  • Ensure file set xlC.rte 11.1.0.1 or higher is installed.
    • Log on as root and run the following command: lslpp -l | grep xlC.rte
  • Ensure that a Mozilla web browser is installed on your system.
    Note: WebSphere Commerce launchpad supports Mozilla Firefox 10 or earlier web browsers.
  • You must take care of the time stamp, if the database server and WebSphere Commerce server are in different machines. The time stamp for both database server and WebSphere Commerce should be same. If you synchronize the server times, you can avoid an issue that causes available order items to be treated as future orders.
  • Ensure that the file size limit is set to unlimited. To check the current limit, type the following in a command window: ulimit -a

    If the value returned for the file size is not set to unlimited, change the limit by running the following command: ulimit -f unlimited​

    For guidelines on setting ulimit values, see Guidelines for setting ulimits
  • Ensure that you increase the default limit of the open files parameter. Change the limit by running the following command: ulimit -n 8192

WebSphere Commerce Version 7.0.0.2 or laterAIX Version 6.1 (64-bit)

To install WebSphere Commerce, ensure that the operating system meets the following prerequisites:
  • 64-bit AIX kernel is required
  • Check your operating system level by issuing the following command:
    oslevel -s 
    This command returns the following value: 6100-0 x, where x indicates the maintenance level
  • Ensure file set xlC.rte 6.0.0.0 is installed.
  • Ensure that the Mozilla web browser and Adobe Acrobat Reader are installed on your system.
    Note: WebSphere Commerce launchpad supports Mozilla Firefox 10 or earlier web browsers.
  • You must take care of the time stamp, if the database server and WebSphere Commerce server are in different machines. The time stamp for both database server and WebSphere Commerce should be same. If you synchronize the server times, you can avoid an issue that causes available order items to be treated as future orders.
  • Ensure that the file size limit is set to unlimited. To check the current limit, type the following in a command window: ulimit -a

    If the value returned for the file size is not set to unlimited, change the limit by running the following command: ulimit -f unlimited​

    For guidelines on setting ulimit values, see Guidelines for setting ulimits
  • Ensure that you increase the default limit of the open files parameter. Change the limit by running the following command: ulimit -n 8192
AIX Version 5.3 (64-bit) To install WebSphere Commerce on AIX 5.3, ensure that the operating system meets the following prerequisites:
  • 64-bit AIX kernel is required
  • Check your operating system level by issuing the following command:
    oslevel -s
    This command returns the following value or higher: 5300-07-01. For example: 5300-07-01-0748 meets the minimum requirement. If the output from the command does not end in -01-xxxx or higher, you are at the incorrect maintenance level for WebSphere Commerce. Obtain the correct maintenance level from IBM Fix Central
  • If you are planning to install IBM HTTP Server as your web server, ensure that you installed the xlC.rte file set. To check whether this file set is installed on your machine, run the following command:
     lslpp -l xlC.rte
  • Software patches can always be found at IBM Support Fix Central for AIX 5.3, IBM Fix Central
  • Ensure that the stack quota limit is at least 32768. To check the current limit, type the following command in a command window: ulimit -a

    If the value returned for the stack is less than 32768, increase it to this level by running the following command: ulimit -s 32768

  • Ensure that the file size limit is set to unlimited. To check the current limit, type the following in a command window: ulimit -a

    If the value returned for the file size is not set to unlimited, change the limit by running the following command: ulimit -f unlimited​

    For guidelines on setting ulimit values, see Guidelines for setting ulimits
  • Ensure that you increase the default limit of the open files parameter. Change the limit by running the following command: ulimit -n 8192
  • Ensure that asynchronous I/O is enabled. This requirement is especially important for logically partitioned (LPAR) systems where asynchronous I/O is enabled on the first LPAR but not on subsequent LPAR.
  • Ensure that the Mozilla web browser and Adobe Acrobat Reader are installed on your system.
    Note: WebSphere Commerce launchpad supports Mozilla Firefox 10 or earlier web browsers.
  • You must take care of the time stamp, if the database server and WebSphere Commerce server are in different machines. The time stamp for both database server and WebSphere Commerce should be same. If you synchronize the server times, you can avoid an issue that causes available order items to be treated as future orders.
IBM i Version 6.1

IBM i Version 6.1 is supported for WebSphere Commerce Feature Pack 5 and later.

To install WebSphere Commerce, ensure that the operating system meets the following prerequisites:
  • IBM i 6.1 Operating System (5761SS1 which includes DB2) with the following options:
    • Extended Base Directory Support (5761SS1 option 3)
    • Host Servers (5761SS1 option 12). You can start the host servers by using the Start Host Server (STRHOSTSVR) command by typing STRHOSTSVR *ALL on the command line. (The QSERVER subsystem must be running.)
    • Qshell (5761SS1 option 30)
    • Portable App Solutions Environment (5761SS1 option 33)
    • Digital Certificate Manager (5761SS1 option 34)
    • CCA Cryptographic Service Provider (5761SS1 option 35)
    • International Components for Unicode (5761SS1 option 39)
  • IBM HTTP Server for IBM i (5761DG1 option *BASE)
  • IBM Developer Kit for Java (5761JV1 option *BASE) and one or both of the following options
    • Java SE 6 32-bit (5761JV1 option 11)
    • Java SE 6 64-bit (5761JV1 option 12)
  • IBM Toolbox for Java (5761JC1 option *BASE)
  • IBM TCP/IP Connectivity Utilities for IBM i (5761TC1 option *BASE)
  • IBM WebSphere Application Server Version 7 (5733W70 option *BASE), optionally with Network Deployment (option 3). Update to the recommended version of WebSphere Application Server.
  • Install the PTFs required by WebSphere Application Server and WebSphere Commerce products. At a minimum the following PTFs must be installed:
  • Configure permissions as described in the following technote: manageprofiles script might fail with ClassNotFoundException
IBM i Version 7.1

IBM i Version 7.1 is supported for WebSphere Commerce Feature Pack 5 and later.

To install WebSphere Commerce, ensure that the operating system meets the following prerequisites:
  • IBM i 7.1 Operating System (5770SS1 which includes DB2) with the following options:
    • Extended Base Directory Support (5770SS1 option 3)
    • Host Servers (5770SS1 option 12). You can start the host servers by using the Start Host Server (STRHOSTSVR) command by typing STRHOSTSVR *ALL on the IBM i command line. (The QSERVER subsystem must be running on the IBM i system.)
    • Qshell (5770SS1 option 30)
    • Portable App Solutions Environment (5770SS1 option 33)
    • Digital Certificate Manager (5770SS1 option 34)
    • CCA Cryptographic Service Provider (5770SS1 option 35)
    • International Components for Unicode (5770SS1 option 39)
  • IBM HTTP Server for IBM i (5770DG1 option *BASE)
  • IBM Developer Kit for Java (5761JV1 option *BASE) and one or both of the following options
    • Java SE 6 32-bit (5761JV1 option 11)
    • Java SE 6 64-bit (5761JV1 option 12)
  • IBM TCP/IP Connectivity Utilities for IBM i (5770TC1 option *BASE)
  • IBM WebSphere Application Server Version 7 (5733W70 option *BASE), optionally with Network Deployment (option 3). Update to the recommended version of WebSphere Application Server.
  • Install the PTFs required by WebSphere Application Server and WebSphere Commerce products. At a minimum the following PTFs must be installed:
  • Configure permissions as described in the following technote: manageprofiles script might fail with ClassNotFoundException
Linux
WebSphere Commerce customers that run on a Linux operating system must meet all installation prerequisites for both WebSphere Application Server, and their database product:
Important:
  • DB2For DB2, all 32-bit compatibility libraries are required for 32-bit applications.
  • Your operating system installation might have installed a web server by default. Ensure that all web servers other than IBM HTTP Server are uninstalled. If a web server other than IBM HTTP Server is installed before you start the WebSphere Commerce installation wizard, the resulting installation of WebSphere Commerce does not function correctly.
  • If the machine you are using to administer your WebSphere Commerce site is running the Windows operating system, ensure that the Linux installation includes an X Server and that the X Server is running.
  • Ensure that you have Mozilla web browser installed. The Mozilla web browser is required to view the information available through the launchpad that displays before you install WebSphere Commerce.
    Note: WebSphere Commerce launchpad supports Mozilla Firefox 10 or earlier web browsers.
  • You must take care of the time stamp, if the database server and WebSphere Commerce server are in different machines. The time stamp for both database server and WebSphere Commerce should be same. If you synchronize the server times, you can avoid an issue that causes available order items to be treated as future orders.
  • Ensure that you have the compat-libstdc++ library.
  • Ensure that the file size limit is set to unlimited. To check the current limit, type the following in a command window: ulimit -a

    If the value returned for the file size is not set to unlimited, change the limit by running the following command: ulimit -f unlimited​

    For guidelines on setting ulimit values, see Guidelines for setting ulimits
  • Ensure that you increase the default limit of the open files parameter. Change the limit by running the following command: ulimit -n 8192
Note: Red Hat Enterprise Linux AS, Version 4.0 and SUSE Linux Enterprise Server 9 Service Pack 4 WebSphere Commerce running on System z Operating Systems has the following limitations:
  • If WebSphere Commerce will use DB2, you must use a remote DB2 database. Install the DB2 Data Server Client first, and then on the same machine, use the Custom installation option to install WebSphere Commerce. The WebSphere Commerce quick installation option cannot be used.
  • When you install WebSphere Commerce, an "Installation prerequisite warnings" panel is shown. A warning message that indicates unsupported machine architecture can be ignored.
Solaris Ensure that you have one of the following Sun operating systems installed:
  • Solaris 10 for SPARC The following patch clusters and patches are required:
    • Recommended Patch Cluster dated 1/07/08 (or later)
    • Required Patch: 127111-02 (obsoleted by 127127-11)
Notes:
  • You can check patch levels by using the showrev -p command. For information about using the showrev -p command, see your Solaris documentation.
  • Intel platform, x86, or x64/x86 editions of Solaris operating systems are not supported by WebSphere Commerce.
  • Ensure that you set the kernel parameters as documented in the Required Detail #1 section.
  • Ensure that the stack quota limit is at least 32768. To check the current limit, type the following in a command window: ulimit -a

    If the value returned for the stack is less than 32768, increase it to this level by running the following command: ulimit -s 32768

  • Ensure that the file size limit is set to unlimited. To check the current limit, type the following in a command window: ulimit -a

    If the value returned for the file size is not set to unlimited, change the limit by running the following command: ulimit -f unlimited​

  • Ensure that you increase the default limit of the open files parameter. Change the limit by running the following command: ulimit -n 8192
  • Ensure that the Mozilla web browser and Adobe Acrobat Reader are installed on your system.
    Note: WebSphere Commerce launchpad supports Mozilla Firefox 10 or earlier web browsers.
  • You must take care of the time stamp, if the database server and WebSphere Commerce server are in different machines. The time stamp for both database server and WebSphere Commerce should be same. If you synchronize the server times, you can avoid an issue that causes available order items to be treated as future orders.
WebSphere Commerce Version 7.0.0.8 or laterMicrosoft Windows Server 2012 (64-bit) Ensure that you the following supported Microsoft Windows operating systems installed:
  • Microsoft Windows Server 2012 Standard Edition
  • Microsoft Windows Server 2012 Datacenter Edition
Notes:
  • In addition to the required service pack levels, ensure that your system has all of the latest critical fixes that are issued by Microsoft. To obtain the latest service packs and critical fixes, see the Microsoft Windows Update website: Windows Update.
  • You must take care of the time stamp, if the database server and WebSphere Commerce server are in different machines. The time stamp for both database server and WebSphere Commerce should be same. If you synchronize the server times, you can avoid an issue that causes available order items to be treated as future orders.
  • Ensure that you disable any virus scan software that is active on the system. Virus scan software often interferes with the installation by causing the DVDs to hang during installation. You can re-enable the virus scan software immediately after you complete the installation.
  • Specify a paging file size that is double the size of the RAM. For example, if there is 512 MB RAM, specify a value of 1024 MB for the paging file. The paging file size is adjusted in the Virtual memory dialog box.
    • To access the Virtual memory dialog box:
      1. Select Start > Control Panel > System.
      2. In System Properties, select the Advanced tab.
      3. Click Settings in the Performance section.
      4. In Performance Options, select the Advanced tab.
      5. Under Virtual memory, click Change.
Microsoft Windows Server 2008 (32 and 64-bit operating system) Ensure that you have one of the following Microsoft Windows operating systems installed:
  • Microsoft Windows Server 2008 Standard Edition
  • Microsoft Windows Server 2008 Datacenter Edition
  • Microsoft Windows Server 2008 Enterprise Edition
  • Microsoft Windows Server 2008 Enterprise Edition R2 (64-bit only)
Notes:
  • In addition to the required service pack levels, you ensure that your system has all of the latest critical fixes that are issued by Microsoft. To obtain the latest service packs and critical fixes, see the Microsoft Windows Update website: Windows Update.
  • You must take care of the time stamp, if the database server and WebSphere Commerce server are in different machines. The time stamp for both database server and WebSphere Commerce should be same. If you synchronize the server times, you can avoid an issue that causes available order items to be treated as future orders.
  • Ensure that you disable any virus scan software active on the system. Virus scan software often interferes with the installation by causing the DVDs to hang during installation. You can re-enable the virus scan software immediately after you complete the installation.
  • Specify a paging file size that is double the size of the RAM. For example, if there is 512-MB RAM, specify a value of 1024-MB for the paging file. The paging file size is adjusted in the Virtual memory dialog box.
    • To access the Virtual memory dialog box:
      1. Select Start > Control Panel > System.
      2. In System Properties, select the Advanced tab.
      3. Click Settings in the Performance section.
      4. In Performance Options, select the Advanced tab.
      5. Under Virtual memory, click Change.
  • If you have Terminal Services running in Application Server mode, you must activate installation mode before you install WebSphere Commerce. To activate installation mode, issue the following command from a command prompt session: change user /install. For more information, review the following Microsoft Knowledge Base article: Installing and Using Programs in Windows 2000 Terminal Services
Microsoft Windows Server 2003 (32 and 64-bit operating system)
  • Ensure that you have one of the following Microsoft Windows operating systems installed:
    • Microsoft Windows Server 2003 Standard Edition, Service Pack 2
    • Microsoft Windows Server 2003 Enterprise Edition, Service Pack 2
Notes:
  • In addition to the required service pack levels, ensure that your system has all of the latest critical fixes that are issued by Microsoft. To obtain the latest service packs and critical fixes, see the Microsoft Windows Update website: Windows Update.
  • You must take care of the time stamp, if the database server and WebSphere Commerce server are in different machines. The time stamp for both database server and WebSphere Commerce should be same. If you synchronize the server times, you can avoid an issue that causes available order items to be treated as future orders.
  • Ensure that you disable any virus scan software that is active on the system. Virus scan software often interferes with the installation by causing the DVDs to hang during installation. You can re-enable the virus scan software immediately after you complete the installation.
  • Specify a paging file size that is double the size of the RAM. For example, if there is 512 MB RAM, specify a value of 1024 MB for the paging file. The paging file size is adjusted in the Virtual memory dialog box.
    • To access the Virtual memory dialog box:
      1. Select Start > Control Panel > System.
      2. In System Properties, select the Advanced tab.
      3. Click Settings in the Performance section.
      4. In Performance Options, select the Advanced tab.
      5. Under Virtual memory, click Change.

Operating system requirements for IBM Sales Center for WebSphere Commerce

Windows XP
  • Ensure that you have the latest Windows XP service pack installed.
  • Ensure that your system has all of the latest critical fixes that are issued by Microsoft. To obtain the latest service packs and critical fixes, see the Microsoft Windows Update website: Windows Update
Windows Vista
  • Ensure that you have the latest Windows Vista service pack installed.
  • Ensure that your system has all the latest critical fixes that are issued by Microsoft. To obtain the latest service packs and critical fixes, see the Microsoft Windows Update website: Windows Update
Windows 7
  • Ensure that you have the latest Windows 7 service pack installed.
  • Ensure that your system has all the latest critical fixes that are issued by Microsoft. To obtain the latest service packs and critical fixes, see the Microsoft Windows Update website: Windows Update
Solaris

Related information and required details

Updating Solaris operating system kernel configuration parameters for DB2

If you are using DB2 with WebSphere Commerce, you must set the Solaris operating system kernel parameters as described in the following chart. If you are using a multitier configuration, only the DB2 node must have these parameters set. If you do not set the parameters as specified, DB2 is not able to create a DB2 instance ID. After you set the Solaris operating system kernel file parameters, you must restart your machine so that the changes take effect.

To set a kernel parameter:
  1. Log in as user ID root and use a text editor to add the following parameters to the Solaris operating system kernel file, /etc/system.
  2. Add a line at the end of the /etc/system file with the following format:
      set parameter-name=value
    Do not leave any spaces at the end of any of the statements that you type into the kernel file.
Select the values for the following parameters, which are based on the configuration that applies to your system.
Solaris operating system Kernel Configuration Parameters (Minimum required values)
Kernel Configuration Parameter Physical Memory
up to 2 GB 2 GB - 4 GB 4 GB - 16 GB over 16 GB
msgsys:msginfo_msgmax 65535 65535 65535 65535
msgsys:msginfo_msgmnb 65535 65535 65535 65535
msgsys:msginfo_msgssz 32 32 32 32
msgsys:msginfo_msgseg 32767 32767 32767 32767
msgsys:msginfo_msgmap 1794 2562 3586 3586
msgsys:msginfo_msgmni 1792 2560 3584 3584
msgsys:msginfo_msgtql 1792 2560 3584 3584
semsys:seminfo_semmap 2050 3074 4098 4098
semsys:seminfo_semmni 2048 3072 4096 4096
semsys:seminfo_semmns 4300 6452 8602 8602
semsys:seminfo_semmnu 2048 3072 4096 4096
semsys:seminfo_semume 240 240 240 240
shmsys:shminfo_shmmax 966367641 2899102923 3865470566 15461882265
shmsys:shminfo_shmmni 2048 3072 4096 4096
shmsys:shminfo_shmseg 240 240 240 240
Queue managers are generally independent of each other. Therefore, system kernel parameters, for example shmmni, semmni, semmns, and semmnu need to allow for the number of queue managers in the system.
Note: You must restart the machine after you update the Solaris operating system kernel parameters.
SolarisDB2

Refine Solaris kernel parameter settings after installation

After you install DB2 and WebSphere Commerce, and after you create a WebSphere Commerce instance and, optionally, a WebSphere Commerce Payments instance, you can refine the kernel parameters using the db2osconf utility. The db2osconf utility can be used to determine more accurate kernel parameters that are based on the size and configuration of your system. The db2osconf utility does not change the /etc/system file and the system must be restarted in order for any changes to the /etc/system file to take place. The db2osconf utility can be found under the /DB2_installdir/bin directory.

For more information about the db2osconf utility, see: