This article describes how to do the following:
was
, which is used by WebSphere Application Serverwas
databaseThe procedures in this article assume that DB2 is installed in the default location /opt/IBMdb2/V7.1 and that any required FixPak is installed.
db2adm
as the group for db2inst1. For
the steps in this section, use a password such as ibmdb2. Note that DB2
requires a password of 8 or fewer characters. Specify a home directory of, for
example, /home/db2inst1.# /opt/IBMdb2/V7.1/instance/db2icrt -u db2inst1 db2inst1
# /opt/IBMdb2/V7.1/cfg/db2ln
db2inst1
, then run:
# /opt/IBMdb2/V7.1/samples/db2sampl
. /opt/IBMdb2/V7.1/sqllib/db2profile
For csh, add the following line to the .cshrc of the instance owner:
source /opt/IBMdb2/V7.1/sqllib/db2cshrc
. /opt/IBMdb2/V7.1/sqllib/db2profile
Because this is the first installation, create a database to store the
configuration. The was database will be defined by its
JDBC URL as jdbc:db2:was
. Create the was database
and set its DB2 application heap size by entering the command:
$ db2 create database was
When the database is created, enter the command below to set the application heap size:
$ db2 update db config for WAS using applheapsz 256
If an application heap size of 256 doesn't work for your system, increase the size to, for example, 512.
To verify the connection to the was database, log in as db2inst1.
If DB2 is not already running, enter the command db2start
. Then,
when DB2 is running, enter the command:
$ db2 connect to was