IBM(R) WebSphere Commerce Feature Pack 1, APAR IZ18527, README

This README file provides instructions for applying the interim fix IZ18527 on WebSphere Commerce Feature Pack 1.

Preparation

Software Versions

Download and install the WebSphere Commerce Update Installer. The directory to which you install the Update Installer will be called UPDI_installdir through the rest of this document.

Obtain the interim fix package (.pak file) for APAR IZ18527 and place it in a location accessible to the WebSphere Commerce Update Installer. For example UPDI_installdir/maintenance.

Installing WebSphere Commerce Feature Pack 1 Interim Fix IZ18527

Important:

  • You must apply all fix changes from the machine where you have created your WebSphere Commerce instances.
  • The WebSphere Commerce Help Server must be stopped when applying fixes.
  • The WebSphere Commerce Configuration Manager server must be stopped before applying the fixes.

Applying the WebSphere Commerce Feature Pack 1 fixes

Complete one of the following sections:

To uninstall the fixes, refer to Removing the WebSphere Commerce Feature Pack 1 fixes.

Special Install Instructions

Some of the fixes in this cumulative fix require additional steps.  Please see the details below.

 

JR27075 - Adds a fix that allows the Order Tag and Cart Tag to be populated with VAT (Value Added Tax) included in the prices, so these prices can be then sent to Coremetrics as opposed to prices without VAT.

1.      A new attribute named 'includeVATinUnitPrice' is added in the Cart Tag. So you have to set this attribute to true to include the tax part also with the unit price.

eg: <cm:cart databean="${orderBean}" includeVATinUnitPrice="true"/>

2.      Two new attributes named 'includeVATinUnitPrice' and 'includeVATinTotalPrice' is added to the Order Tag. includeVATinUnitPrice should be set to true to include tax in unit price of the ShopAction9 tag. includeVATinTotalPrice should be set to true to include tax in subtotal for ShopAction9 and Order tag

eg: <cm:order orderId="${WCParam.orderId}" includeVATinUnitPrice="true" includeVATinTotalPrice="true" />

LI73151 - Resolve the issue of sending the correct category to Coremetrics when a product exists under multiple categories in the same sales catalog.  The HttpSession is used to track the user's visits to categories and provide the correct category ID.

 

You must enable the session from the JSP. To do this, look for the <%@ page session="false"%> line in  JSTLEnvironmentSetup.jspf and change it to true. We are keeping track of the categoires visited by the user in the HttpSession object. So this is required for correctly attributing the category.

 

Applying the WebSphere Commerce Feature Pack 1 fixes using the graphical installer

Complete this section to install the WebSphere Commerce Feature Pack 1 interim fix. If you have already created a WebSphere Commerce instance, you must apply the interim fix to the WebSphere Commerce product installation directory first. After the interim fix is applied to the product, you must then apply it to your WebSphere Commerce instances.

Updating the WebSphere Commerce installation directory

  1. Using the command line, navigate to the UPDI_installdir directory and type the following command based on your operating system:
    • AIX | Linux | Solaris : ./update.sh
    • Windows : update.bat
  2. On the Welcome panel, review the information and click Next to continue.
  3. Specify the WebSphere Commerce installation directory.
  4. Ensure the correct directory is listed for the WebSphere Commerce product. Enter the correct directory and click Next.
  5. When prompted, select Product Only from the drop down list.

Note:

This selection will only be shown if you have configured WebSphere Commerce instances on the system.

  1. Select Install maintenance package. Click Next.
  2. Select the appropriate .pak file from UPDI_installdir/maintenance directory and click Next.
  3. On the summary page, review the information and click Next to begin the installation.

Note:

If you have a WebSphere Commerce instance created, you must first update the WebSphere Commerce product, then relaunch the installer.

  1. Ensure that the installer displays the message Success:The following maintenance package was installed. If you do not see this message the installer will indicate which log files to check. Click Finish.

Updating your WebSphere Commerce instance

Complete this procedure only if Coremetrics enhanced Web analytics has already been enabled. If you have not yet enabled Coremetrics enhanced Web analytics, you do not need to manually apply this Coremetrics fix on the WebSphere Commerce instance. This is because the Coremetrics fix will be automatically applied to the instance when you run the enablement script.

To update the tag library, you need to manually copy the files to the WebSphere Commerce enterprise application directory under the WebSphere Application Server directory. If it is clustered, you must perform this on all nodes that have cluster members that run the WebSphere Commerce application.

1.      Backup the file: WAS_deploydir/Stores.war/WEB-INF/lib/coremetrics.jar.  The backup will be required if you ever need to uninstall IZ18527.

2.      Copy WCD_installdir /components/Coremetrics/wc.ear/Stores.war/WEB-INF/lib/coremetrics.jar to WAS_deploydir/Stores.war/WEB-INF/lib/coremetrics.jar.

Applying the WebSphere Commerce Feature Pack 1 fixes using the silent installer

Complete this section to silently install the WebSphere Commerce Feature Pack 1 interim fix. If you have already created a WebSphere Commerce instance, you must apply the interim fix to the WebSphere Commerce product first. After the interim fix is applied to the product, you must then apply it to your instances.

Updating the WebSphere Commerce installation directory

This section updates the WebSphere Commerce product.

  1. i5/OS : Enter the QShell by typing QSH at the i5/OS command prompt.
  2. Navigate to the UPDI_installdir/responsefiles directory and open the install.txt file in a text editor.
  3. Edit the install.txt file, ensuring the following sections are edited appropriately:
    • The -W maintenance.package contains the full path name for the interim fix. For example:
      • AIX : -W maintenance.package="/usr/IBM/WebSphere/UpdateInstaller/V61/UPDI/maintenance/APAR1.pak"
      • i5/OS : -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/APAR1.pak"
      • Linux | Solaris : -W maintenance.package="/opt/IBM/WebSphere/UpdateInstaller/V61/UPDI/maintenance/APAR1.pak"
      • Windows : -W maintenance.package="C:\Program Files\IBM\WebSphere\UpdateInstaller\V61\UPDI\maintenance\APAR1.pak"
    • The -W product.location contains the full path name of the WebSphere Commerce installation directory. For example:
      • AIX : -W product.location="/usr/IBM/WebSphere/CommerceServer60"
      • i5/OS : -W product.location="/QIBM/ProdData/CommerceServer60"
      • Linux | Solaris : -W product.location="/opt/IBM/WebSphere/CommerceServer60"
      • Windows : -W product.location="C:\Program Files\IBM\WebSphere\CommerceServer60"

Verify that the -W update.instancename and -W update.db entries do not exist or are commented out. Save the file and exit.

Note:

If you have an WebSphere Commerce instance created, you must first update your WebSphere Commerce product. After you have update the product, you must re-edit the response file, and run the Update installer again.

  1. Run the following command from the UPDI_installdir:
    • AIX | Linux | Solaris :   ./update.sh -silent -options UPDI_installdir/responsefiles/install.txt
    • i5/OS : update -options UPDI_installdir/responsefiles/install.txt
    • Windows : update.bat -silent -options UPDI_installdir/responsefiles/install.txt
  2. Refer to the log files in the following directory to verify that your install was successful:
    • WC_installdir/logs/update 

Updating your WebSphere Commerce instance

Complete this procedure only if Coremetrics enhanced Web analytics has already been enabled. If you have not yet enabled Coremetrics enhanced Web analytics, you do not need to manually apply this Coremetrics fix on the WebSphere Commerce instance. This is because the Coremetrics fix will be automatically applied to the instance when you run the enablement script.

To update the tag library, you need to manually copy the files to the WebSphere Commerce enterprise application directory under the WebSphere Application Server directory. If it is clustered, you must perform this on all nodes that have cluster members that run the WebSphere Commerce application.

1.      Backup the file: WAS_deploydir/Stores.war/WEB-INF/lib/coremetrics.jar.  The backup will be required if you ever need to uninstall IZ18527.

2.      Copy WCD_installdir /components/Coremetrics/wc.ear/Stores.war/WEB-INF/lib/coremetrics.jar to WAS_deploydir/Stores.war/WEB-INF/lib/coremetrics.jar.

Removing the WebSphere Commerce Feature Pack 1 fixes

Important

  1. AIX | Linux | Solaris : Ensure that you are logged in as the root user for WebSphere Commerce.
  2. i5/OS : Ensure that you are logged in as a user that has QSECOFR authority.
  3. Windows : Ensure that you are logged in with a Windows user ID that is a member of the Administrator group.
  4. Complete one of the following steps:
    • To remove the fix from the WebSphere Commerce product:
      • Stop the following servers:
        • WebSphere Commerce Help server.
        • WebSphere Commerce Configuration Manager server.
    • To remove the fix from the WebSphere Commerce instance only:
      • Start the following servers:
        • WebSphere Commerce Application Server. For example, server1 or DMGR.
        • WebSphere Commerce database server.
        • If you have a federated environment, ensure that the WebSphere Application Server nodeagents are started.

Complete one of the following sections:

Uninstalling the WebSphere Commerce Feature Pack 1 fixes using the graphical installer

Complete this section to uninstall the WebSphere Commerce Feature Pack 1 fix. If you have applied the fix to your WebSphere Commerce instance, you must uninstall the fix from that instance before uninstalling the fix from the WebSphere Commerce product.

Removing the fix from the WebSphere Commerce instance

To restore the WebSphere Commerce Instance to its pre IZ18527 state:

1.      Locate the backup of WAS_deploydir/Stores.war/WEB-INF/lib/coremetrics.jar that was manually made during installation.

2.      Replace the file WAS_deploydir/Stores.war/WEB-INF/lib/coremetrics.jar with the backup from step 1.

Removing the interim fix from the WebSphere Commerce installation directory

  1. Using the command line, navigate to the UPDI_installdir directory and type the following command based on your operating system:
    • AIX | Linux | Solaris : ./update.sh
    • Windows : update.bat
  2. On the Welcome panel, review the information and click Next to continue.
  3. On the Product Selection panel ensure that the directory name is correct. This is the WebSphere Commerce installation directory.
  4. Click Next to accept the WebSphere Commerce product found on your computer.
  5. When prompted, specify the Product Only.
  6. Select Uninstall Maintenance package. Click Next.
  7. Select the appropriate .pak file and click Next.
  8. Ensure that the installer displays the message Success:The following maintenance package was uninstalled.. If you do not see this message the installer will indicate which log files to check. Review the information and click Relaunch to start the Update Install wizard again or Finish to close the Update Installer.
  9. On the Summary page, review the information and click Next to begin the uninstall process.
  10. Refer to the log files in the following directory to verify that your uninstall was successful:
    • WC_installdir/logs/update 

Uninstalling the WebSphere Commerce Feature Pack 1 fixes using the silent installer

Complete this section to uninstall the WebSphere Commerce Feature Pack 1 interim fix. If you have applied the fix to your WebSphere Commerce instance, you must uninstall the fix from that instance before uninstalling the fix from the WebSphere Commerce product.

Removing the interim fix from the WebSphere Commerce instance

To restore the WebSphere Commerce Instance to its pre IZ18527 state:

  1. Locate the backup of WAS_deploydir/Stores.war/WEB-INF/lib/coremetrics.jar that was manually made during installation.
  2. Replace the file WAS_deploydir/Stores.war/WEB-INF/lib/coremetrics.jar with the backup from step 1.

Removing the interim fix from the WebSphere Commerce installation directory

Note:

If you have applied the fix to a WebSphere Commerce instance, you must remove the fix from that instance before removing it from the WebSphere Commerce product directory.

  1. i5/OS : Enter the QShell by typing QSH at the i5/OS command prompt.
  2. Navigate to the UPDI_installdir/responsefiles directory and open the uninstall.txt file in a text editor.
  3. To remove the fix from the WebSphere Commerce product:

a.  Update the -W backup.package entry with the name of the maintenance package that you want to uninstall.

b.  Note: If the -W backup.package is not specified, the most recently installed fix is uninstalled.

c.  Update the -W product.location with the location of the WebSphere Commerce install.

d.  Ensure that the following line does not exist or is commented out of the uninstall.txt file: 

e.                      -W update.instancename="instance_name"
1.                              Where instance_name is the name of your WebSphere Commerce instance.
  1. Run the following command:
    1. AIX | Linux | Solaris : ./update.sh -silent -options UPDI_installdir/responsefiles/uninstall.txt
    2. i5/OS : update -options UPDI_installdir/responsefiles/uninstall.txt
    3. Windows : update.bat -silent -options UPDI_installdir/responsefiles/uninstall.txt
  1. Refer to the log files in the following directory to verify that your uninstall was successful:
    1. WC_installdir/logs/update 

Trademarks and service marks

The following are trademarks or registered trademarks of IBM Corporation in the United States and other countries:

IBM      WebSphere

Windows and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

**************************************************************************
 
** © COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2006
 
** ALL RIGHTS RESERVED.
 
**************************************************************************

Note to US Government Users -- Documentation related to restricted rights -- Use, duplication, or disclosure is subject to restriction set forth in GSA ADP Schedule Contract with IBM Corp.

End of README File