Operating system prerequisites for a WebSphere Commerce installation

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

Important: WebSphere Commerce is expected to function as designed using a hypervisor with a supported operating system. Due to the large number of hypervisors available, and the complexity of emulation, no guarantee can be made that your environments will work as expected. Therefore, only combinations which are known by HCL to be problematic will be listed here.

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


AIX 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` 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`
IBM i Version 7.3 (64-bit) Version 7.1, Version 7.2 (64-bit)	To install WebSphere Commerce, ensure that the operating system meets the following prerequisites: IBM i 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) Java for IBM i Version 7.1 IBM Developer Kit for Java (5761JV1 option BASE) Java SE 7 64 bit (5761JV1 option 15) Java for IBM i Version 7.2: IBM Developer Kit for Java (5770JV1 option BASE) Java SE 7 64 bit (5770JV1 option 15) IBM TCP/IP Connectivity Utilities for IBM i (5770TC1 option BASE) WebSphere Application Server IBM WebSphere Application Server Base Version 8.5.5 (5733W85 option BASE WebSphere Application Server V85 for IBM i). Or, you can choose Network Deployment (5733W85 option 3) WebSphere Application Server V85 Plugins (5733W85 Option 7) Update to the recommended version of WebSphere Application Server. The minimum version is Version 8.5.5.7. For IBM i Version 7.1, install the PTFs that are required by WebSphere Application Server and WebSphere Commerce products. At a minimum the following PTFs must be installed. A group PTF for your version of WebSphere Application Server installed on IBM i Version 7.1. IBM HTTP Server for i PTF number, SF99368 WebSphere App Server V8.5 PFT number, SF99381 Java PTF number, SF99572 Note: For more information about downloading or ordering the PTF, you can search by PTF number at the following URL, Preventive Service Planning - PSP. For IBM i Version 7.2, install the PTFs that are required by WebSphere Application Server and WebSphere Commerce products. At a minimum the following PTFs must be installed. A group PTF for your version of WebSphere Application Server installed on IBM i Version 7.2. IBM HTTP Server for i PTF number SF99713 WebSphere App Server V8.5 PFT number, SF99481 Java PTF, SF99716 Note: For more information about downloading or ordering the PTF, you can search by PTF number at the following URL, Preventive Service Planning - PSP. Configure permissions as described in the following technote: manageprofiles script might fail with ClassNotFoundException
Red Hat Enterprise Linux Red Hat Enterprise Linux version 8.4 or higher Red Hat Enterprise Linux Version 7.8, 7.9 Red Hat Enterprise Linux Version 7.1, 7.2, 7.3, 7.4, 7.5	WebSphere Commerce customers that run on a Red Hat Enterprise Linux operating system must meet all installation prerequisites for both WebSphere Application Server, and their database product: Preparing Linux systems for installation DB2 Version 10.5 Installation Prerequisites for Linux Oracle Database Preinstallation Tasks
Linux (generic)	WebSphere Commerce customers that run on a Linux operating system must meet all installation prerequisites for both WebSphere Application Server, and their database product: Preparing Linux systems for installation DB2 Version 10.5 Installation Prerequisites for Linux Oracle Database Preinstallation Tasks Important: 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. 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. For more information, see Installing and verifying Linux packages Ensure that the following packages or later versions are installed. For each package that is listed, both the 32-bit and 64-bit packages are required. libXau-1.0.5-1 libxcb-1.5-1 libX11-1.3-2 libXext-1.1-3 libXp-1.0.0-15.1 libICE-1.0.6-1 libuuid-2.17.2-12 libSM-1.1.0-7.1 libXt-1.0.7-1 libXmu-1.0.5-1 libXi-1.3-3 libXtst-1.0.99.2-3 libXrender-0.9.5-1 freetype-2.3.11-6 expat-2.0.1-9.1 fontconfig-2.8.0-3 ksh-20100621-2 libXft-2.1.13-4.1 rpm-build-4.8.0-12 compat-db-4.6.21-15 elfutils-0.148-1 elfutils-libs-0.148-1 Ensure that the following 32-bit packages are installed libgcc_s.so.1 libgtk-x11-2.0.so.0 libpk-gtk-module.so libcanberra-gtk-module.so 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`
Microsoft Windows Server 2012 (64-bit)	Ensure that the following supported Microsoft Windows operating system is installed: Microsoft Windows Server 2012 Standard Edition R2 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: Select Start > Control Panel > System. In System Properties, select the Advanced tab. Click Settings in the Performance section. In Performance Options, select the Advanced tab. Under Virtual memory, click Change.