Home

Install Commerce v6.x

 

+

Search Tips   |   Advanced Search

 

Contents

  1. Pre-Install
  2. Install DB2 server
  3. Install DB2 client
  4. Install DB2 fixpacks
  5. Catalog database
  6. Configure Web servers
  7. Install the IHS Plug-in
  8. Apply IHS fixpacks
  9. Install ftp
  10. Install WAS ND and Commerce
  11. Apply Commerce fixpacks
  12. Make wasuser a member db2grp3
  13. Create a WebSphere Commerce instance
  14. Verify the instance creation
  15. Configure JVM
  16. Configure SSL
  17. Configure Plug-in
  18. Copy bundled static files to Web servers
  19. Copy custom static files to Web servers
  20. Change from temp DB to permanent DB
  21. Verify configuration
  22. Create clustered environment
  23. Publish a Consumer Direct store
  24. Verify store publish
  25. Create backups
  26. Configure automatic startup scripts
  27. Configure automatic shutdown scripts

See also

  1. mod_rewrite

 

Commerce Install Procedure

     

  1. Pre-Install

    2.  

  2. Configure the DB2 server

    3. See: Install and configure 64-bit DB2 Universal Database

     

  3. Install DB2 client

    4. We are installing the Application Development version of DB2 client, which includes the DBD-DB2-1.1 perl module, which is required for the eservice-driver to connect to the Ecard Database.

    If perl module is not loaded, you will get the following C header file errors...

    Constants.xs:16:20: sqlcli.h: No such file or directory
    Constants.xs:18:21: sqlcli1.h: No such file or directory
    Constants.xs:19:20: sqlext.h: No such file or directory

    1. Download the DB2 Enterprise Server Edition ESE binary...

      DB2 UDB Enterprise Server Edition V8.1 Linux for Intel 32-bit (C48THML)

      Run db2_install.

    2. In menu that comes up, choose...

      DB2.ADCL DB2 Application Development Client

    3. Create user wasuser

    4. Set up DB2 environment for wasuser

      cd /opt/IBM/db2/V8.1/instance
      ./db2icrt -s CLIENT wasuser

    5. Add the following to .bash_profile of user wasuser.

      LIBPATH=$LIBPATH:/opt/WAS/CommerceServer60/bin
      export LIBPATH
      . sqllib/db2profile
      umask 0027

    6. Verify current directory is in PATH of wasuser.

    7. Update DB2 client licenses.

      The license file is located in the download directory.

      db2licm -a db2ese.lic

     

  4. Install DB2 fixpacks

    1. Untar...

      • FP16_MI00207.tar - Regular fixpak
      • FP16_MI00207_ADCL.tar - Application Development Client

    2. Stop any websphere processes. We don't want any open transactions.

    3. As root, run...

      ./installFixPak -y
      cd adcl
      ./db2_install

    4. As root, run...

      . /home/db2inst3/sqllib/db2profile
      cd /opt/IBM/db2/V8.1/instance
      db2 get instance
      ./db2iupdt db2inst3

    5. Verify fixpack level

      # db2level
      DB21085I Instance "db2inst3" uses "32" bits and DB2 code release "SQL08029" with level identifier "030A0106".
      Informational tokens are "DB2 v8.1.2.144", "s080111", "MI00207", and FixPak "16".
      Product is installed at "/opt/IBM/db2/V8.1".

     

  5. Catalog Database

    6. For example, for STAGE environment...

      db2 catalog tcpip node SKYWAYN remote 10.1.70.52 server 60004
      db2 catalog db SKY_STG as SKYWAYSTG at node SKYWAYN
      db2 terminate
      db2 connect to SKYWAYSTG user wasuser using wasuser1
      db2 attach to SKYWAYN user wasuser using wasuser1
      db2 "list node directory"
      db2 get instance
      db2 list database directory
      db2 list tables for schema wasuser
      select tabname from syscat.tables

      db2 "quit"

     

  6. Configure the Web server

    7. These instructions detail how to install and configure the remote IBM HTTP Server with WebSphere Plug-in

    1. Review

    2. Log on as user root

    3. Uncompress and untar the WC_WAS_ND_xLinux_V6025.tar.gz installation images into /tmp

    4. cd /tmp/WAS6/disk1/IHS
      root> ./install

      Install into...

      /opt/ihs/ihs60

      Click Next.

    5. Select Custom installation and click Next.

    6. Perform a full installation by checking the HTTPServer Base and Security features.

      Click Next.

    7. Specify a HTTP Port and a HTTP Administration Port that are not in use and click Next. Figure 24 shows the ports selection.

    8. Select Launch the WebSphere Application Server - Plugin install and click Finish.

     

  7. Install the IBM HTTP Server Plug-in

    8.  

  8. Apply IBM HTTP server fixpacks

    1. Configure the WebSphere Application Server update installer.

      download.updii.61017.linux.ia32.zip

    2. Apply the latest refresh pack for the IBM HTTP server

      6.0-WS-WASIHS-LinuxX32-RP0000002.tar

      Apply the refresh pack to the Web server before applying latest fix pack level.

    3. Apply the latest IBM HTTP server fix pack.

      6.0.2-WS-WASIHS-LinuxX32-FP00000029.pak

    4. Apply the 6.0.2 refresh pack for the IBM HTTP server plug-in

      Apply the refresh pack to the Web server plug-in before it is updated to the latest fix pack level.

      The refresh pack will update the Web server plug-in to level 6.0.2.

      6.0-WS-WASPlugIn-LinuxX32-RP0000002.tar

    5. Update the Web server plug-in to the latest fix pack level.

      6.0.2-WS-WASPlugIn-LinuxX32-FP00000029.pak

     

  9. Install ftp

    1. up2date vsftpd
    2. Edit /etc/services and enable ftp port 21

     

  10. Install WebSphere Application Server and WebSphere Commerce

    1. Download installation images.

      • WebSphere Commerce Enterprise V6.0 Disk 1 and Disk 2 for Windows, linux, Solaris, iSeries, Linux on Intel, Linux on zSeries, Linux on iSeries and pSeries Multilingual

      • WebSphere Commerce - DB2 Universal Database Enterprise Server Edition and Administrative Client V8.2.3 for linux

      Local copies of...

        WC_DB2_ESE_and_Client_xLnx_26_V823.tar.gz WC_Enterprise_V60.zip WC_WAS_ND_xLinux_V6025.tar.gz

      ...can be found in...

      10.1.70.138:/software

      ...into /tmp.

      Review the WebSphere Commerce README file.

      The README file contains information about last-minute changes to the product. Last-minute changes can include additional fixes that must be installed before using WebSphere Commerce.

    2. Log on as user root.

      Set umask 002.

    3. Create non-root user: wasuser

      useradd wasuser

      Set the home directory. You might have to manually create this directory. If you create the directory manually, change the ownership to wasuser.

    4. Create a user group: wasgroup.

      groupadd wasgroup

      Add the wasuser to the new group, setting the new group as the Primary Group or Default Group.

      /usr/bin/gpasswd -a wasuser wasgroup
      su - wasuser
      newgrp wasgroup

      To confirm wasuser is a member of wasgroup...

      groups wasuser

    5. Edit the wasuser profile and verify the current working directory is part of the PATH variable.

      PATH=$PATH:.:
      export PATH

    6. Verify that the wasuser locale code is set properly.

      echo $LANG

      We want en_US

    7. Run Commerce installer... 

      root> cd /tmp/WC60/disk1
root> chmod u+x setup_linux
root> ./setup_linux

      If you get a message saying rpm-build is not installed, even though you have confirmed it is installed and current, ignore message and click next.

      Select Custom Installation because the database server and the Web server are on separate machines from the application server machine.

      Click Next.

    8. Specify the components to be installed. Deselect...

      • IBM DB2 Universal Database Enterprise Server Edition,
      • IBM HTTP Server
      • WebSphere Application Server Web server plug-ins

      These components are already installed on the remote Web server and remote database server.

      Click Next.

    9. Check Remote web server because the Web server is on a remote machine.

      Click Next.

    10. Specify the installation path for the WebSphere Application Server and the WebSphere Commerce installation directory.

      /opt/websphere/AppServer

      Click Next.

    11. Specify the IBM DB2 Universal Administration Client installation information.

      For example...

      DB userid db2inst1
      DB userpass ********
      Database user group wasgroup
      Database user home /home/wasuser

      Do NOT create this user. The install program will create this user.

      Click Next.

    12. Specify the user name and p for the Configuration Manager.

      Click Next.

    13. Specify the non-root information and click Next.

      For example...

      /home/wasuser

    14. If you wish, create a response file from your install.

      Click Next, then Finish, and wait for the installation to complete.

    15. Make non-root user (wasuser) a member of the database user group.

      /usr/bin/gpasswd -a wasuser db2grp3
      su - wasuser
      newgrp db2grp3

      To confirm wasuser is a member of db2grp3...

      groups wasuser

    16. Review WebSphere Commerce installation logs

      The following log files contain messages generated by the WebSphere Commerce installation wizard:

      • WC_installdir/logs/install.log

      • WC_installdir/logs/wctrace_date_time.log

        The wctrace_date_time.log file is intended for use by IBM support only. Examining this file might not provide you with any useful information.

      • WC_installdir/logs/wcnonroot.log

      • WC_installdir/logs/wcinstall.log

        The installation wizard will create the wcinstall.log file only if errors or warnings are encountered during the installation process.

      If the installation of WebSphere Commerce fails, these log files will be in /tmp.

      The WebSphere Commerce installation is complete if the following message appears in the install.log log file: WebSphere Commerce installation complete.

     

  11. Apply Commerce fixpacks

    12.  

  12. Set the wasuser user to be a member of the database user group, db2grp3.

    13. /usr/bin/gpasswd -a wasuser db2grp3

    To confirm that a wasuser is a member of db2grp3...

    groups wasuser

    Note that you will NOT be able to run WAS commands such as serverStatus.sh and wsadmin.sh until AFTER you have create a profile.

     

  13. Create a WebSphere Commerce instance

    14. See: Create a WebSphere Commerce instance

     

  14. Verify the instance creation

    15. Check the instance creation log files:

     

  15. Configure JVM

    16. For generic jvm arguments set...

    -Xk40000 -Xp10240k,1024k -DinvocationCacheSize=0

    Recommended heap settings are...

    Min Heap Size : 256
    Max Heap Size: 1280

     

  16. Configure SSL key stores and trust stores

    17. You can either use self-signed certs or verisign certs

    To generated self-signed certificates and key datbase, on the web server machine, use ikeyman or command-line utilities...

    mkdir /opt/ihs/ihs60/keys
    cd /opt/ihs/ihs60/keys
    ../bin/ikeyman

    Here are example values...

    gsk7cmd -keydb -create -db mykeydb.kdb -pw p -type cms -expire 360 -stash

    gsk7cmd -cert -create -db mykeydb.kdb -pw p -size 1024 -dn "CN=hostname,O=CoName,OU=IHS,ST=MO,C=US" -label IHS -default_cert yes -expire 360

    As wasuser, restart WebSphere Commerce

     

  17. Prepare IBM HTTP Server and Plug-in

    1. Edit IHS *.conf file and add required stanzas

      • httpd.conf
      • skyway.conf
      • clientx.conf

      See also: Manually editing the httpd.conf file for WebSphere Commerce instance

    2. In WAS ND console, expand...

      Servers | Web servers | remotewebserver

    3. Verify settings are correct...

    4. Click Generate Plug-in. A message displays with the path to the plug-in configuration file on the WebSphere Commerce server.

      Verify plugin has mappings to the WC_clientx application. If it does not, in the WAS console, go to...

      Enterprise Applications | WC_clientx | Map modules to servers

      ...and map your webserver to the modules.

    5. Copy the plugin-cfg.xml file from the WebSphere Commerce server to the remote Web server. Copy the plug-in file to the plugin directory specified in the httpd.conf file.

      For example, copy the file to...

      /ihs/ihs60/plugin/clientx/httpconf/plugin-cfg.xml

    6. Update the WebSpherePluginConfig directive in the httpd.conf file to point to the plugin-cfg.xml file copied in the previous step.

    7. Add virtual host aliases for clientx virtual hosts.

    8. In httpd.conf set...

      <IfModule worker.c>
      ThreadLimit 100
      ServerLimit 30
      StartServers 2
      MaxClients 3000
      MinSpareThreads 100
      MaxSpareThreads 750
      ThreadsPerChild 100
      MaxRequestsPerChild 0
      </IfModule>

     

  18. Copy bundled static files to Web servers

    1. Log on to Commerce appserver

    2. Run...

      cd /opt/websphere/AppServer/profiles/clientx/installedApps/WC_clientx_cell/WC_clientx.ear

      scp -r * root@webserver:/opt/ihs/ihs60/htdocs/en_US

    3. On webserver, go to...

      cd /opt/ihs/ihs60/htdocs

      ...and create file removeJSPJAR.pl... 

      use strict;
my $filter = $ARGV[0];
if ( !$filter )
{
print "Static file extensions were not specified.\n";
exit;
}
system("find en_US/ > t.out");
open F, "< t.out";
while ( my $file = <F> )
{
chomp( $file );
my @extensions = split( /\,/, $filter );
my $markForDelete = 1;
# Skip thread statements that do not match
foreach my $extension ( @extensions )
{
if ( $file =~ /\.$extension$/ )
{
$markForDelete = 0;
last;
}
}
unlink($file) if ( $markForDelete );
}
close F;
unlink("t.out");

    4. Execute removeJSPJAR.pl

      perl ./removeJSPJAR.pl html,css,js,gif,jpg,gif,bmp

     

  19. Copy custom static files to Web servers

    20. To deploy new custom web content from developers...

    1. Copy tarball from...

      foo5dc4sl43:/db2backup/ibm/nbaxa510/nbaxa510_static-*.tar.gz

      ...to...

      webserver:/opt/ihs/ihs60/htdocs/en_US

      You can also use static files on one of the production webservers

    2. Verify there is enough file system space to handle expanded file: df -k

    3. Verify contents of tar file before expanding. Change invalid paths. For example, change...

      /usr/clientx/htdocs/en_US/MyStore

      ...to...

      ./MyStore

    4. Unarchive tar file...

      cd /opt/ihs/ihs60/htdocs/en_US
      gunzip xvf nbaxa510-static*.tar.gz
      tar xvf nbaxa510-static*.tar

    5. Remove tar file when finished to free up disk space.

    6. Re-run procedure for copying bundled static content.

    7. Set owner and permissions:

        cd /opt/ihs/ihs60/htdocs/en_US find . -name \* -exec chown ihsadmin {} \;
        find . -name \* -exec chgrp ihsadmin {} \;
        find . -type d -exec cxxod 775 {} \;
        find . -type f -exec cxxod 664 {} \;

     

  20. Catalog Database

    21. For example, for STAGE environment...

      db2 catalog tcpip node SKYWAYN remote 10.1.70.52 server 60004
      db2 catalog db SKY_STG as SKYWAYSTG at node SKYWAYN
      db2 terminate
      db2 connect to SKYWAYSTG user wasuser using wasuser1
      db2 attach to SKYWAYN user wasuser using wasuser1
      db2 "list node directory"
      db2 get instance
      db2 list database directory
      db2 list tables for schema wasuser
      select tabname from syscat.tables

      db2 "quit"

     

  21. Change from temp DB to permanent DB

    22. If you had to configure the Commerce system against a temporary database, because the migrated DB had name longer than 7 characters, follow this procedure to point Commerce to the actual DB.

     

  22. Verify configuration

  23. In Web Container for each appserver, enable servlet caching.

     

  24. Create Clustered Environment

    • Create commerce instance clientx on a single application server which is selected as the first server with in the cell

    • Increase dmgr heap size and soap connection time out

    • Federate the first application server node

    • Perform federation of nodes

     

  25. Publish a Consumer Direct storefront asset store

    1. As wasuser, start the WebSphere Commerce server, if it has not already started.

    2. Open the WebSphere Commerce Administration console.

    3. Select the site and click OK.

    4. From the top menu, select Store Archives > Publish.


      This document contains screenshots for publishing an extended sites store model. Select Extended sites in the dropdown box, and then enable the ExtendedSitesOrganizationStructure.sar checkbox. Note that you can publish a different store model and use this section as a guide.

    5. Click Next.

    6. Ensure that all of the information in the Summary page is correct, and then click Finish to publish the store.

    7. An informational message states that the publish process has started.

    8. The Publish Status page automatically displays, and the ExtendedSitesOrganizationStructure.sar is given a status of "Publishing".

    9. After the sar is successfully published, the status changes to "Successful".

    10. Follow the above steps to publish the following additional sars:

      • ExtendedSitesHub.sar
      • ConsumerDirectStorefrontAssetStore.sar

      Even though you can publish the new sars after federating or clustering, we recommend publishing all the sars you need prior to federating or clustering. After all sars are published, the Publish Status page looks like...

     

  26. Verify the store publish

    1. Check the WebSphere Commerce Server status.

    2. If it has not started yet, start the WebSphere Commerce server.

    3. Check the SystemOut.log to confirm a clean start-up.

    4. Try accessing the storefront.

     

  27. Create backups

    1. Back up the WebSphere Application Server configuration.

    2. Back up the database.

     

  28. Configure automatic startup scripts

    29. To configure automatic startup of Clientx processes after a Linux reboot...

    1. On the WAS ND machine, create a master startup script to start deployment manager. Edit...

      /opt/WAS/dmgr/bin/WASstartupscript.sh

      ...and insert...

      /opt/websphere/profiles/Dmgr01/bin/startManager.sh

      Set ownership and perms of this script to wasuser and 775.

    2. On the WAS machines, create a master startup script to start application servers. Edit...

      /opt/WAS/AppServer/profiles/clientx/bin/WASstartupscript.sh

      and insert...

      /opt/websphere/AppServer/profiles/clientx/bin/startNode.sh
      /opt/websphere/AppServer/profiles/clientx/bin/startServer.sh ECard_xxx
      /opt/websphere/AppServer/profiles/clientx/bin/startServer.sh server1

      Set ownership and perms of this script to wasuser and 775.

    3. Edit /etc/rc.local on all machines, and call the startup script...

      su - wasuser -c ". /home/wasuser/.profile; /opt/WAS/dmgr/bin/WASstartupscript.sh"

     

  29. Configure automatic shutdown scripts

    1. On the WAS ND machine, create a master shutdown script to stop deployment manager. Edit...

      /opt/WAS/dmgr/bin/WASshutdown.sh

      ...and insert...

      /opt/websphere/profiles/Dmgr01/bin/stopManager.sh

      Set ownership and perms of this script to wasuser and 775.

    2. On the WAS machines, create a master shutdown script to stop application servers. Edit...

      /opt/WAS/AppServer/profiles/clientx/bin/WASshutdown.sh

      and insert...

      /opt/websphere/AppServer/profiles/clientx/bin/stopServer.sh server1
      /opt/websphere/AppServer/profiles/clientx/bin/stopServer.sh ECard_xxx
      /opt/websphere/AppServer/profiles/clientx/bin/stopNode.sh

      Set ownership and perms of this script to wasuser and 775.

    3. Edit /etc/rc.local on all machines, and call the shutdown script...

      su - wasuser -c ". /home/wasuser/.profile; /opt/WAS/dmgr/bin/WASshutdown.sh"

 

Author: Michael Pareene
michael.pareene@skyway.net
612.220.8724