WebSphere Commerce V5.4 Handbook: Architecture and Integration Guide

464 WebSphere Commerce V5.4 Handbook, Architecture and Integration Guide

3. We recommend updating the default application heap size for the WebSphere

Application Server repository database from 128 to 512 pages (256 in

minimum required):

$ db2 update db cfg for was40 using applheapsz 512

4. To ensure that this new setting takes effect, stop and restart DB2:

$ db2stop

$ db2start

The installation and base configuration of the DB2 Server is now complete.

13.3 DB2 Client installation

This section describes the procedures needed to install and configure the DB2

client in preparation for use with WebSphere Commerce. The section is

organized as follows:

 DB2 Client installation and configuration overview

 Install DB2 V7.2 Client

 Install DB2 V7 FixPak 6 (7.1.0.60)

 Configure DB2 client .profile

 Configure and verify DB2 client/server connectivity

13.3.1 DB2 Client installation and configuration overview

Each WebSphere Commerce machine will connect to the DB2 UDB server via a

DB2 client. The client code must match the DB2 V7.2 FixPak 6 (7.1.0.60), which

was installed on the server machine in 13.2, “DB2 Server installation” on

page 458. A DB2 instance needs to be created on each client machine, using the

same DB2 instance owner ID and password as on the server.

The DB2 client requires the same updates to the JDBC drivers to enable JDBC2,

and the update for extended shared memory.

The DB2 program files and executables will be installed to the /usr file system,

specifically, the /usr/lpp/db2_07_01 directory. A minimum of 70 MB of free disk

space will be required there, for the client code.

In addition, at least 10 MB are needed in the home directory for each DB2

instance owner (for example, /home/db2inst1), for DB2 log files and for softlinks

to the DB2 program files in /usr.

Chapter 13. AIX three-tier runtime with DB2 and IBM HTTP Server 465

13.3.2 Install DB2 V7.2 Client

To install the DB2 V7.2 UDB client, you should use the DB2 V7.2 UDB CD

provided in the WebSphere Commerce product package. This CD includes and

automatically installs the FixPak 5 (level 7.1.0.55). Full instructions can be found

in the

Installation Guide, IBM WebSphere Commerce V5.4 Professional and

Business Edition for AIX

.

The high-level steps to install DB2 client on the Commerce Application Server

node are as follows:

1. Run ./db2setup from the IBM DB2 UDB CD.

2. Select the

DB2 Administration Client and DB2 Application Development

Client

components.

3. Create a DB2 instance for WebSphere Commerce. For example, we created

a DB2 instance named db2inst2, owned by the user db2inst2 (member of

group db2iadm2), with home directory /home/db2inst2. Use the same

password for this user as on the server.

13.3.3 Install DB2 V7 FixPak 6 (7.1.0.60)

For details, refer to 13.2.3, “Install DB2 V7.2 FixPak 6 (7.1.0.60)” on page 459.

13.3.4 Configure DB2 client .profile

Enable JDBC2

For details, refer to “Enable JDBC2” on page 460.

Update .profile to use extended shared memory

For details refer to“Update .profile to use extended shared memory” on

page 461.

13.3.5 Configure and verify DB2 client/server connectivity

Before installing the WebSphere Application Server and WebSphere Commerce,

it is necessary to ensure that the DB2 client can successfully connect to

databases on the DB2 server machine.

Note: The DB2 Application Development Client is required by DB2 V7.x

when loading stored procedures needed by WebSphere Commerce. The

DB2 installer will also install a number of Java.rte.* filesets (at the 1.1.8.6

level) to the /usr/jdk_base directory.