WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring a DB2 database on a z/OS system

You can configure an event database on a z/OS system using DB2 database software.

Before you begin

To configure the DB2 database from a remote client, you must have the DB2 Connect product installed with the latest fix packs.

Why and when to perform this task

Note: Follow this procedure only if you are configuring a DB2 event database on a z/OS system.
To configure the event database:

Steps for this task

  1. On the z/OS system, use the DB2 administration menu to create a new subsystem.
  2. Create a storage group. You will also need to specify the storage group name in the database response file; the default value is sysdeflt.
  3. Grant the necessary permissions to the user ID you want the WebSphere Process Server data source to use. This user ID must have rights to access the database and storage group you created; it must also have permission to create new tables, table spaces, and indexes for the database.
  4. Catalog the remote database. Use the following commands, either in a script or in a DB2 command-line window:
    catalog tcpip node zosnode remote hostname server IP_port system db_subsystem
    catalog database db_name as db_name at node zosnode authentication DCS

    For more information about how to catalog a nodes and databases, refer to the DB2 Connect documentation.

  5. Verify that you can establish a connection to the remote subsystem. You can check this by running the following command:
    db2 connect to subsystem user userid using password
  6. Bind to the host database. Use the following commands:
    db2 connect to db_name user userid using password
    db2 bind path/bnd/@ddcsmvs.lst blocking all sqlerror continue message 
         mvs.msg grant public
    db2 connect reset

    For more information about binding a client to a host database, refer to the DB2 Connect documentation.

  7. Go to the profile_path/event/dbconfig directory for the profile defining the WebSphere ESB run-time environment where you want to configure the database. (Replace profile_path with the path to the directory containing the WebSphere ESB profile.)
  8. Using an ASCII text editor, open the DB2ZOSResponseFile.txt sample database response file.
  9. Modify the database response file with the correct information for your environment. (See the comments in the sample response file for more information about the parameters, including complete syntax information.) Specify the following parameter values:
    DB_NAME
    The name of the z/OS database you created for the event database.
    JDBC_CLASSPATH
    The path to the DB2 JDBC driver.
    UNIVERSAL_JDBC_DRIVER_NATIVEPATH
    The path to the Universal JDBC native library path.
    UNIVERSAL_JDBC_CLASSPATH
    The path to the Universal JDBC driver.
  10. Run the database configuration script for your client operating system, specifying the name of the database response file as a parameter. Use one of the following commands:
    Windows systems
    config_event_database.bat response_file
    Linux and UNIX systems
    config_event_database.sh response_file

Result

The script configures the event database and creates two JDBC data sources: one for the event database and one for the event catalog. A message is displayed when database configuration is complete.
Note: If your database response file specifies EXECUTE_SCRIPTS=false, you must complete the database configuration by manually running the generated scripts. The default value in the sample database response file is EXECUTE_SCRIPTS=true.

What to do next

After you configure the event database, you must restart the application server.

Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\doc\tcei_install_configureDB2ZOS.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)