You can install your fix pack using
an interactive method which uses a graphical install wizard. After
navigating through the install panels, your fix pack is installed.
Before you begin
- Download and extract the WebSphere Commerce V7.0.0.x installation
package to a temporary location. For example:where x is the fix pack level.
About this task
Complete this section to install the WebSphere Commerce fix
pack. If you have already created a WebSphere Commerce or WebSphere Commerce Payments instance,
you must apply the fix pack to the WebSphere Commerce product
installation directory first. After the fix pack is applied to the
product, you must then apply it to your WebSphere Commerce or WebSphere Commerce Payments instances.
To
minimize downtime, apply the fix pack at a time that will least impact
the operation of your business.
Procedure
- Download the required WebSphere Commerce fix
pack.
- Save the fix pack to
directory:
- UPDI_installdir/maintenance
Notes: - Ensure that the fix pack maintains the proper file extension. The file must be named
7.0.0-WS-WCServer-FP00X.pak where X is the number of the fix
pack that you plan to install.
- Do not put any other maintenance files in the UPDI_installdir/maintenance directory.
-
Before you apply the fix pack to your machine, back up the following objects:
- WC_profiledir directory
- See Backing up and recovering the application server environment.
- Database
- The database updates that are included in this fix pack cannot be undone. If you want to undo
the database update after you apply the WebSphere Commerce fix pack, you must
restore your database backup. See your database documentation for information about backing up your
database.
- JSP files
- A fix pack overwrites certain JSP files that are related to the WebSphere Commerce tools pages. See
the text file
7.0.0.x files changes
for a list of the files that are overwritten
during the installation of the fix pack. A link to this text file is found on each WebSphere Commerce fix pack download
page. The Fix packs for WebSphere Commerce technote
provides links to the fix pack download pages.
- If you use a staging server, you must
ensure that your production server and staging server stay synchronized.
-
Review the following information about WebSphere Commerce instances:
Option | Description |
---|
Existing WebSphere Commerce instancesImportant: If you customized your
WebSphere Commerce instance,
ensure that you followed the documented deployment procedure in the IBM Knowledge Center, otherwise
your customizations are removed when the fix pack is installed. For more information about
customized code, see Customized
code deployment. |
- You must apply the fix pack to the WebSphere Commerce product
installation directory first. After the fix pack is applied to the product, you must then apply it
to your WebSphere Commerce or
WebSphere Commerce Payments
instances.
- If any new components are installed from the WebSphere Commerce base (7.0) DVD images,
you must reinstall the fix pack in order to upgrade that component to the current fix pack level.
For example, if you installed the WebSphere Commerce remote management
utilities on a separate node from your WebSphere Commerce Server, install the
fix pack on that node as well. If you do not install the fix pack on that node, you are not able to
use the Configuration Manager client.
- Delete all the old disk cache files before you install a fix pack.
- Stop the WebSphere Application Server V70-WC_instance_Name.
- Delete the contents of the disk offload cache that can be found in one of these directories:
- Default location
- WC_profiledir/temp/node_name/server1/_dynacache
- Offload location
- This directory is set in the WebSphere Application Server Administration Console. Click . Cancel the enable disk offload.
- Start the application server.
- Correct data in the MSGTYPES table, if necessary.
If you created your own table that
references the MSGTYPES table by using MSGTYPE_ID as foreign key, and if there are records in the
table with MSGTYPE_ID = 1002, 1003, or 1004, you must take steps to ensure that the
fix pack installation succeeds.
- Back up the records in your table with
MSGTYPE_ID = 1002, 1003, 1004, then
delete them from your original table.
- After you apply Fix Pack 1 to the WebSphere Commerce Version 7.0 instance, reinsert the backup
records into the table, but change the
MSGTYPE_ID values to 620, 621, 622.
|
New WebSphere Commerce instances |
Each new WebSphere Commerce or WebSphere Commerce Payments instance that you
create after you applied the fix pack to your WebSphere Commerce product installation directory, is
created at that specific fix pack level. You are not required to update the WebSphere Commerce or WebSphere Commerce Payments instance to the
fix pack level. |
What to do next
Note: If you encounter an error that says
Unhandled
exception, Type=Segmentation error
while running installing
the fix pack, you might need to install one of the following:
- DB2 V9.5 Fix pack 6a, or higher
- DB2 V9.7 Fix pack 3a, or higher
See
Troubleshooting: Massload error when using DB2 for details.