Install > Installing WebSphere Commerce > Prepare to install WebSphere Commerce > Prerequisites for installing WebSphere Commerce
Operating system prerequisites for installing WebSphere Commerce
AIX v6.1 64–bit
To install WebSphere Commerce ensure that the OS meets the following prerequisites:
- 64-bit AIX kernel is required
- Check the OS level by issuing the following command:
oslevel -sThis command should return the following value...
6100-0x
...where x indicates the maintenance level.
- Install fileset xlC.rte 6.0.0.0.
- Verify you have Mozilla Web browser and Adobe Acrobat Reader installed on the system.
- You have to 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
AIX v5.3 64–bit
To install WebSphere Commerce on AIX 5.3, ensure that the OS meets the following prerequisites:
- 64-bit AIX kernel is required
- Check the OS level by issuing the following command:
oslevel -sThis command should return 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 or higher, you are at the incorrect maintenance level for WebSphere Commerce.
Obtain the correct maintenance level.
- If you are planning to install IBM HTTP Server as the Web server, ensure that you have installed the xlC.rte file set.
To check if this fileset is installed on the machine, run the following command:
lslpp -l xlC.rte
- Software patches can always be found at IBM Support Fix Central for AIX 5.3.
- Verify 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...
ulimit -s 32768
- Verify that asynchronous I/O is enabled. This is especially important for logically partitioned (LPAR) systems where asynchronous I/O is enabled on the first LPAR but not on subsequent LPAR.
- Verify you have Mozilla Web browser and Adobe Acrobat Reader installed on the system.
- Synchronize the clocks of the servers if the database server and WebSphere Commerce server are in different machines. The time stamp for both the database server and the WAS should be the same. Server times which are synchronized with each other will prevent order subsystem issues.
IBM i v6.1
To install WebSphere Commerce ensure that the OS 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 i5/OS command line. (The QSERVER subsystem must be running on the iSeries system.)
- 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 v7 provided with WebSphere Commerce.
Update to v7.0.0.9 by downloading and applying WAS v7 Fix Pack 9 for IBM i platforms.
- Install the PTFs required by WAS and WebSphere Commerce products. At a minimum the following PTFs must be installed:
- A group PTF for the version of WAS (7.0.0.9 or later) installed on IBM i v6.1.
This group PTF includes database and Java group PTFs.
- Java SE 6 PTFs:
IBM i v7.1
To install WebSphere Commerce ensure that the OS 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 v7 (5733W70 option *BASE), optionally with Network Deployment (option 3). Update to v7.0.0.9 by downloading and applying WAS v7 Fix Pack 9 for IBM i platforms
- Install the PTFs required by WAS and WebSphere Commerce products. At a minimum the following PTFs must be installed:
- A group PTF for the version of WAS installed on IBM i v7.1.
This group PTF includes database and Java group PTFs.
- Java SE 6 PTFs:
Linux
Installation prerequisites...
- WAS installation prerequisites for Linux
- DB2 Installation Prerequisites for Linux
- DB2 Installation Prerequisites for Linux
- Oracle Installation Prerequisites for Linux
For DB2, all 32-bit compatibility libraries are required for 32-bit applications.
The OS installation might have installed a Web server by default.
Uninstall all Web servers other than IBM HTTP Server.
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 will not function correctly.
If the machine you are using to administer the WebSphere Commerce site is running the Windows OS, ensure that the Linux installation includes an X Server and that the X Server is running.
Verify that you have Mozilla Web browser installed.
The Mozilla Web browser is required to view the information available through the launch pad that displays before installing WebSphere Commerce.
Synchronize the clocks of the servers if the database server and WebSphere Commerce server are in different machines.
The time stamp for both the database server and the WAS should be the same. Server times which are synchronized with each other will prevent order subsystem issues.
Red Hat Enterprise Linux AS, v4.0 and SUSE LINUX Enterprise Server 9 Service Pack 4 WebSphere Commerce running on System z OSs has the following limitations:
- If WebSphere Commerce will use DB2, use a remote DB2 database.
Install the DB2 Runtime client first, and then on the same machine, use the Custom install option to install WebSphere Commerce. The WebSphere Commerce quick install option can not be used.
- When installing WebSphere Commerce, an "Installation prerequisite warnings" panel is shown.
A warning message indicating unsupported machine architecture can be ignored.
Solaris
Supported operating systems...
- Solaris 10 for SPARC The following patch clusters and patches are required:
- Recommend Patch Cluster dated 1/07/08 (or later)
- Required Patch: 127111-02 (obsoleted by 127127-11)
Check patch levels...
showrev -pIntel platform, x86, or x64/x86 editions of Solaris operating systems are not supported by WebSphere Commerce.
Set kernel parameters as documented in the Required Detail #1 section.
Verify 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... ulimit -s 32768
Install Mozilla Web browser and Adobe Acrobat Reader on the system.
If the database server and WebSphere Commerce server are in different machines, to avoid orderitems being treated as future orders, verify time stamps are synchronized.
MS Windows Server 2008 32 and 64–bit OS
Supported operating systems...
- Microsoft Windows Server 2008 Standard Edition
- Microsoft Windows Server 2008 Datacenter Edition
- Microsoft Windows Server 2008 Enterprise Edition
In addition to the required service pack levels, verify the system has all of the latest critical fixes.
If the database server and WebSphere Commerce server are in different machines, to avoid orderitems being treated as future orders, verify time stamps are synchronized.
Disable any virus scanning software active on the system.
Virus scanning software often interferes with the installation by causing problems when hanging DVDs during the installation. You can re-enable the virus scanning software immediately after completing the installation.
The paging file size should be double the size of the RAM. For example, 512 MB RAM should have a 1024 MB paging file. The paging file size is adjusted in the Virtual memory dialog box.
To access the Virtual memory dialog box:
Start | Control Panel | System | System Properties | Advanced tab | Performance | Settings | Advanced | Virtual memory | ChangeIf you have Terminal Services running in Application Server mode, activate install mode before installing WebSphere Commerce.
change user /install
MS Windows Server 2003
Supported operating systems...
- Microsoft Windows Server 2003 Standard Edition, Service Pack 2
- Microsoft Windows Server 2003 Enterprise Edition, Service Pack 2
Install latest service packs and critical fixes.
Disable any virus scanning software active on the system. Virus scanning software often interferes with the installation by causing problems when hanging DVDs during the installation.
You can re-enable the virus scanning software immediately after completing the installation.
The paging file size should be double the size of the RAM. For example, 512 MB RAM should have a 1024 MB paging file. The paging file size is adjusted in the Virtual memory dialog box.
To access the Virtual memory dialog box:
Start | Control Panel | System | System Properties | Advanced | Performance | Settings | Advanced | Virtual memory | ChangeIf you have Terminal Services running in Application Server mode, activate install mode before installing WebSphere Commerce.
change user /install
Requirements for IBM Sales Center for WebSphere Commerce
Windows XP Service Pack 3
- Install Microsoft Windows XP Service Pack 3.
- Verify the system has all of the latest critical fixes issued by Microsoft.
Windows Vista
- Install latest Windows Vista service pack.
- Install latest critical fixes issued by Microsoft.
Update Solaris OS kernel configuration parameters for DB2
If you are using DB2 with WebSphere Commerce, set the Solaris OS kernel parameters as described in the following chart. If you are using a multi-tier configuration, only the DB2 node must have these parameters set. If you do not set the parameters as specified, DB2 will not be able to create a DB2 instance ID. Once you have set the Solaris OS kernel file parameters, restart the machine so that the changes take effect. .
To set a kernel parameter:
- Log in as user ID root and use a text editor to add the following parameters to the Solaris OS kernel file, /etc/system.
- Add a line at the end of the /etc/system file using the following format:
set parameter-name=valueDo not leave any spaces at the end of any of the statements that you type into the kernel file.
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.
Restart the machine after updating the Solaris OS kernel parameters.
Refining Solaris kernel parameter settings after installation
After installing DB2 and WebSphere Commerce, and creating a WebSphere Commerce and, optionally, a WebSphere Commerce Payments instance, you can refine the kernel parameters using the db2osconf utility.
The db2osconf utility can be used to recommend more accurate kernel parameters based on the size and configuration of the 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...
/opt/IBM/db2/V9.5/bin
For more information about the db2osconf utility, see: