Install > Installing WebSphere Commerce > Installing WebSphere Commerce using the custom installation > Prepare for a custom installation > Preparing database servers to use with WebSphere Commerce > Use DB2 Database


Use an existing DB2 Database installation


Overview

You can use an existing DB2 installation if you are doing a custom installation of WebSphere Commerce.

Existing database must be...

To check the version...

db2level

For DB2 Client, we need IBM Data Server Client. The IBM Data Server Runtime Client and DB2 Connect will not work.

To determine what version of DB2 Client you have, run db2ls -p -q. For example, the following is the wrong client... 

$ cd /opt/isv/db2/db2_97_03/install
$ ./db2ls -p -q

Install Path : /opt/isv/db2/db2_97_03

Product Response File ID         Level   Fix Pack   Product Description
-------------------------------------------------------------------------
CONNECT_SERVER                  9.7.0.3          3   DB2 Connect Server

Here is where you can download correct DB2 client

https://www-304.ibm.com/support/docview.wss?uid=swg24028306

Go to AIX 64-bit, then select IBM Data Server Client.


Procedure

  1. Ensure that the DB2 Application Development Tools are installed on the database server.

  2. On appserver, create user IDs required by Commerce

  3. Ensure that you set the passwords for the database user ID, since it can be possible to create the user ID without a password. If this database user ID does not have a password associated with it, Commerce might not function correctly.

  4. For AIX and Linux, on appserver, add the DB2 Fenced user group to the list of groups associated with the non-root user.

    For example, if you are using non-root user as the non-root user ID, add that user to the db2fgrp1 group.

  5. For AIX, Linux and Solaris, on appserver, add the DB2 Fenced user group to the list of groups associated with the DB2 user ID.

    For example, if you used default values during the DB2 installation, add db2inst1 as a user in the db2fgrp1 group. If you are planning to use a multiple node topology, only do this on the database server node.

  6. If you are logged in as the database user ID or the Commerce non-root user, log off so that these changes can take effect.

  7. For remote database servers, manually update the DB2 profile registries on the database server...

    db2set DB2_WORKLOAD=WC
    db2set DB2BIDI=yes

  8. Restart DB2 Database.

  9. Add the following to .bash_profile of user non-root user.

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

  10. Verify current directory is in PATH of non-root user.

  11. Update DB2 client licenses.

    The license file is located in the download directory.

    db2licm -a db2ese.lic


+

Search Tips   |   Advanced Search