Creating a DB2 UDB for z/OS database for Business Process Choreographer

Use this task to create a DB2® UDB for z/OS® database for Business Process Choreographer.

Why and when to perform this task

This topic describes how to create a DB2 UDB for z/OS database and how to verify that it is reachable from the server that hosts the application server.

Steps for this task

  1. You must have already installed WebSphere® Process Server on a UNIX®, Linux®, or Windows® server.
  2. On the z/OS server that hosts the database:
    1. Log on the native z/OS environment.
    2. If multiple DB2 systems are installed, decide which subsystem you want to use.
    3. Make a note of the IP port to which the DB2 subsystem is listening.
    4. Using the DB2 administration menu, create a new database, for example, named BPEDB. Note the name of the database.
    5. Create a storage group and note the name.
    6. Decide which user ID is used to connect to the database from the remote server running WebSphere Process Server. Normally, for security reasons, this user ID is not the one that you used to create the database.
    7. Grant the user ID the rights to access the database and storage group. The user ID must also have permission to create new tables for the database.
    8. Decide if you want to create the tables and views in the schema of the connected user ID or if you want to customize the schema qualifier (_SQLID). If a single user ID accesses multiple databases with tables of the same name, you must use different schema qualifiers to avoid name collisions.
  3. On the server that hosts the Process Server:
    1. Make sure that you have DB2 Connect™ Gateway installed. DB2 Connect™ Gateway is part of the DB2 UDB ESE package, but you can also install it separately.
    2. Catalog the remote database using the following commands in a DB2 command line window:
      catalog tcpip node zosnode remote host_name server IP_port ostype mvs
      catalog database subsystem as subsystem at node zosnode authentication dcs
      catalog dcs database subsystem as subsystem parms ',,INTERRUPT_ENABLED'
    3. Make sure that the sync point manager instance name is specified. Enter the following commands:
      db2 update dbm cfg using SPM_NAME host_name
      db2 update dbm cfg using SPM_LOG_FILE_SZ log_file_size
    4. Take note of the following information:

      An important difference exists between DB2 UDB and DB2 UDB for z/OS. DB2 UDB does not have the concept of a subsystem, but DB2 UDB for z/OS does. To avoid confusion between database name and subsystem name, it is important to understand that because DB2 UDB for z/OS runs in a subsystem, the catalog node and catalog database commands must identify the appropriate subsystem. On DB2 UDB, the subsystem name is not a known concept, so the database name that the catalog command makes a link to is really the name of the DB2 UDB for z/OS subsystem.

    5. Verify that you can establish a connection to the remote subsystem by entering the following command: db2 connect to subsystem user userid using password
    6. Change to the ProcessChoreographer subdirectory in the installation root directory of the application server.
    7. Edit the createTablespaceDb2zOSv8.ddl script. Replace @STOGRP@ with the storage group name and replace @DBNAME@ with the database name (not the subsystem name).
    8. Run your customized version of the createTablespaceDb2zOSv8.ddl script, as described in the header of the script. If you want to drop the table space, use the dropTablespaceDb2zOSv8.ddl script.
    9. Edit the createSchemaDb2zOSv8.ddl script.
      1. Replace @STOGRP@ with the storage group name.
      2. Replace @DBNAME@ with the database name (not the subsystem name).
      3. Replace @_SQLID@ with the schema qualifier or remove @_SQLID@ (including the following dot) from the script. A custom schema qualifier can only be used with the DB2 Universal JDBC driver and requires that the configuration customSQLID property is set to the appropriate value.
    10. Run your customized version of the createSchemaDb2zOSv8.ddl script, as described in the header of the script. If this script does not work, or if you want to remove the tables and views, use the dropSchemaDb2zOSv8.ddl script to drop the schema, but replace @_SQLID@ before running the script.

Result

The DB2 UDB for z/OS database for Business Process Choreographer exists.

What to do next

Continue configuring in the parent topic at step 2.

Terms of use |

Last updated: Thu Apr 27 14:54:57 2006

(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)