Configuring and testing DB2 UDB 6.1

Before you can run WebSphere Application Server, you must create a DB2 UDB instance and the database named was, which WebSphere Application Server uses.

Creating a database instance

  1. Ensure that you are logged into the machine with superuser (root) privileges.
  2. Navigate to the directory containing the DB2 Installer by entering the following command: # cd /usr/lpp/db2_06_01/install
  3. Start the DB2 Installer by entering the following command: # ./db2setup
  4. On the DB2 Installer screen, highlight the Create button beside the option labeled To create a DB2 Instance, or the Administration Server, select Create and press Return.
  5. On the Create DB2 Services screen, highlight the Create the Administration Server option and press Return.
  6. On the Administration Server screen, perform the following steps, noting the values that you enter or accept for future reference:
    1. Enter a user name or accept the default value for the User Name option.
    2. Enter a user ID or accept the default user ID by ensuring that the Use default UID option has an asterisk (*) beside it.
    3. Enter a group name or accept the default value for the Group Name option.
    4. Enter a group ID or accept the default group ID by ensuring that the Use default GID option has an asterisk (*) beside it.
    5. Enter a home directory or accept the default value for the Home Directory option. (It is recommended that you create the home directory that you specify on your system before trying to create the Administration Server.)
    6. Type a password for the user in the Password and Verify Password options. DB2 requires a password of 8 or fewer characters.
    7. Highlight OK and press Return.
  7. A Notice screen informs you of the value being created for the DB2SYSTEM environment variable. Ensure that OK is highlighted and press Return.
  8. On the Create DB2 Services screen, highlight the Create a DB2 Instance option and press Return.
  9. On the DB2 Instance screen, perform the following steps, noting the values that you enter or accept for future reference:
    1. Enter a user name or accept the default value for the User Name option.
    2. Enter a user ID or accept the default user ID by ensuring that the Use default UID option has an asterisk (*) beside it. The user ID is the DB2 instance owner and is needed for installing WebSphere Application Server.
    3. Enter a group name or accept the default value for the Group Name option.
    4. Enter a group ID or accept the default group ID by ensuring that the Use default GID option has an asterisk (*) beside it.
    5. Enter a home directory or accept the default value for the Home Directory option. (It is recommended that you create the home directory that you specify on your system before trying to create the Instance.)
    6. Type a password for the user in the Password and Verify Password options. DB2 requires a password of 8 or fewer characters.
    7. Highlight OK and press Return.
  10. On the Fenced User screen, perform the following steps, noting the values that you enter or accept for future reference:
    1. Enter a user name or accept the default value for the User Name option.
    2. Enter a user ID or accept the default user ID by ensuring that the Use default UID option has an asterisk (*) beside it.
    3. Enter a group name or accept the default value for the Group Name option.
    4. Enter a group ID or accept the default group ID by ensuring that the Use default GID option has an asterisk (*) beside it.
    5. Enter a home directory or accept the default value for the Home Directory option. (It is recommended that you create the home directory that you specify on your system before trying to create the Fenced User.)
    6. Type a password for the user in the Password and Verify Password options.
    7. Highlight OK and press Return.
  11. On the Create DB2 Services screen, highlight OK and press Return. The Summary Report screen is displayed, summarizing all of the choices you have made so far.
  12. Verify the information on the Summary Report screen. When you have determined that it is correct, ensure that Continue is highlighted and press Return. A Warning screen is displayed, giving you the option of canceling the processes.
  13. On the Warning screen, ensure that OK is highlighted and press Return.
  14. A Notice screen informs you when the processes have completed. Ensure that OK is highlighted and press Return.
  15. The Status Report screen informs you of process successes and failures. View the Log File for information on how to correct particular failures. To exit this screen, ensure that OK is highlighted and press Return.
  16. On the DB2 Installer screen, highlight Close and press Return.
  17. On the Notice screen, ensure that OK is highlighted and press Return.
  18. Make root a member of the administrative group that you accepted or designated for the Group Name option during the creation of the Administrative Server in Step 6.
  19. Create symbolic links by entering the following command: # /usr/lpp/db2_06_01/cfg/db2ln
  20. Configure the instance owner (the value that you specified for the User Name option in Step 9) to run db2profile on startup, by doing one of the following:
  21. Configure root to run db2profile on startup. This is required to install and run WebSphere Application Server.

Creating and configuring a database for WebSphere Application Server

Create a database named was and set its DB2 application heap size by performing the following steps:

  1. Log in as the DB2 instance owner (the value that you specified for the User Name option in Step 9 in "Creating a database instance"). Note that when you log in as the instance owner, the command prompt appears as $, rather than #, to indicate your login identity.
  2. Enter the following command to start DB2: $ db2start
  3. Enter the following command to create a database named was. This process can take several minutes to complete. $ db2 create database was
  4. Enter the following command to set the application heap size: $ db2 update db config for WAS using applheapsz 256
  5. Stop and start the database for your changes to take effect. If an application heap size of 256 does not work for your system, increase it to 512.

It is recommended that you set up the database manager to use TCP/IP to remotely connect to WebSphere. Note that if you are using a local DB2 database with WebSphere Application Server (for example, both DB2 and WebSphere Application Server are installed on the same machine) all of the steps in the following procedure will be performed on the same machine:

  1. On the server machine, log in as the DB2 instance owner. (Note that, in these steps, the server and client may be the same machine.) Then, do the following:
    1. Set DB2COMM to TCP/IP using a command such as the following: db2set DB2COMM=tcpip
    2. Open an editor on the /etc/services file. If it does not specify DB2 connection and interrupt service ports, then add lines such as the following to specify the ports: server1 50000/tcp # DB2 connection service port server1i 50001/tcp # DB2 interrupt connection service port
    3. Update the database manager configuration:
      db2 update dbm cfg using svcename <DB2_connection_service_port>

      For DB2_connection_service_port, specify the name used in the /etc/services file (for example, server1).

  2. On the client machine:
    1. Catalog the node using a command such as the following:
      db2 catalog tcpip node node1 remote <hostname> server \
      <DB2_connection_service_port>
    2. Catalog the database:
      db2 catalog database was as wasAlias at node node1
  3. Stop and start DB2.

Verifying installation of DB2 UDB V6.1

To demonstrate that DB2 is functioning correctly, create a sample database and then compile and execute a Java application that accesses this database. The steps below establish that the correct environment is available for DB2 and the IBM Java Development Kit (JDK) and that the Java Database Connectivity (JDBC) driver is accessible from a Java application. Perform the following steps to create the sample database and compile and run the Java application:

  1. Log in as the DB2 instance owner (the value that you specified for the User Name option in Step 9 in "Creating a database instance"). Note that when you log in as the instance owner, the command prompt appears as $, rather than #, to indicate your login identity.
  2. To ensure that the DB2 profile has been set correctly, search the environment for the value of DB2INSTANCE by entering the following command. The value returned must be the instance owner name (the value that you specified for the User Name option in Step 9 in "Creating a database instance"): $ env | grep DB2INSTANCE
  3. Enter the following command to create the sample database. This process can take several minutes to complete. $ db2sampl
  4. Compile an example Java application, placing the resulting class file in the local directory, by entering the following command: $ javac -d . sqllib/samples/java/DB2Appl.java
  5. Start DB2 by entering the following command: $ db2start
  6. Execute the sample by entering the following command: $ java DB2Appl

    Your output appears like the following:

    Retrieve some data from the database... Received results: empno= 000010 firstname= CHRISTINE empno= 000020 firstname= MICHAEL empno= 000030 firstname= SALLY . . . Update the database... Changed 1 row.
  7. To log out, enter control-D (^D) at the command prompt.

Verifying connection to the was database

To verify connection to the was database, perform the following steps:

  1. Log in as the DB2 instance owner (the value that you specified for the User Name option in Step 9 in "Creating a database instance"). Note that when you log in as the instance owner, the command prompt appears as $, rather than #, to indicate your login identity.
  2. Enter the command: $ db2 connect to was

    Your output appears like the following (assuming an instance name of db2inst1):

    Database Connection Information
    
         Database server        = DB2/6000 6.1.0  
         SQL authorization ID   = DB2INST1
         Local database alias   = WAS
  3. To log out, enter control-D (^D) at the command prompt.