Filter
Top Products
6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm
168 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
19.A window confirming that WebSphere Commerce V5.6 has been installed is
shown. Click Next.
20.The Installation Wizard prompts for restarting the system. Ensure that
Restart now is selected and click Finish.
21.After the system has restarted, the DB2 Universal Database V8.1 and
WebSphere Commerce V5.6 First Steps wizards will appear. Close the DB2
Universal Database V8.1 First Steps wizard.
22.If the DB2 Universal Database V8.1 CD you supplied in step 16 on page 167
is not refreshed to fixpack 5 as mentioned previously, you must now apply
DB2 Universal Database V8.1 fixpack 5.
9.2.2 Configuring IBM HTTP Server
In order to finish the installation, the IBM HTTP Server should be configured to
use SSL and to improve performance, the Adaptive Fast Path Architecture
(AFPA) Cache Accelerator should be enabled.
Enabling for SSL
In order for WebSphere Commerce V5.6 tools and for customer sites to work
SSL has to enabled. SSL certificates can either be self-signed or trusted (issued
by a Certification Authority, CA). In our example we had a trusted SSL certificate,
issued by VeriSign, which we copied from WebSphere Commerce Suite V5.1
and configured IBM HTTP Server to enable it. Please refer to WebSphere
Commerce Developer Edition information center to see how SSL is enabled.
Enabling Cache accelerator
If you are using IBM HTTP Server v1.3.26.2 for WebSphere Commerce V5.6,
you should enable the AFPA Cache Accelerator to improve performance for
serving static content.
To enable AFPA, ensure that the following lines in the IBM HTTP Server
<ihs_home>\conf\httpd.conf are activated, either by adding them or removing
any line comment (#) in front of these lines:
Note: During the installation of WebSphere Application Server V5.0.2
fixes, the installation progress bar may stay at 95% for a very long time.
This is normal behavior. The progress of the fixpack installation can be
followed by monitoring the contents of the <was_home>\logs\update
directory and the file <was_home>\logs\WASFixPack.log, where
<was_home> is the installation directory for WebSphere Application
Server.