Use this task to create a DB2® for z/OS® database for Business Process Choreographer.
Why and when to perform this task
This topic describes how to create a DB2 for z/OS database and how to verify that it
is reachable from the server that hosts the application server.
Steps for this task
- You must have already installed WebSphere® Process Server on a UNIX®, Linux®, or Windows® server.
- On the z/OS server that hosts the database:
- Log on the native z/OS environment.
- If multiple DB2 systems are installed, decide which subsystem you
want to use.
- Make a note of the IP port to which the DB2 subsystem is listening.
- Using the DB2 administration menu, create a new database, for example,
named BPEDB. Note the name of the database.
- Create a storage group and note the name.
- 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.
- 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.
- 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.
- On the server that hosts the WebSphere Process Server:
- 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.
- 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'
- 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
- Take note of the following information:
An important
difference exists between DB2 for z/OS and DB2 for Linux, UNIX, and Windows. DB2 for Linux,
UNIX, and Windows does not have the concept of a subsystem, but DB2 for z/OS does.
To avoid confusion between database name and subsystem name, it is important
to understand that because DB2 for z/OS runs in a subsystem, the catalog
node and catalog database commands must identify
the appropriate subsystem. On DB2 for Linux, UNIX, and Windows, 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 for z/OS subsystem.
- Verify that you can establish a connection to the remote subsystem by
entering the following command: db2 connect to subsystem user userid using password
- On the server that hosts your application server, change to
the directory where the Business Process Choreographer configuration scripts
for your database system are located:
- On Windows systems, depending on your DB2 version, enter
one of the following commands:
cd install_root\dbscripts\ProcessChoreographer\DB2zOSV7
cd install_root\dbscripts\ProcessChoreographer\DB2zOSV8
- On UNIX and Linux systems,
depending on your DB2 version, enter one of the following commands:
cd install_root/dbscripts/ProcessChoreographer/DB2zOSV7
cd install_root/dbscripts/ProcessChoreographer/DB2zOSV8
- Edit the createTablespace.sql script. Replace @STOGRP@ with
the storage group name and replace @DBNAME@ with the database name
(not the subsystem name).
- Run your customized version of the createTablespace.sql script,
as described in the header of the script. If you want to drop the
table space, use the dropTablespace.sql script.
- Edit the createSchema.sql script.
- Replace @STOGRP@ with the storage group name.
- Replace @DBNAME@ with the database name (not the subsystem
name).
- 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.
- Run your customized version of the createSchema.sql 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 dropSchema.sql script
to drop the schema, but replace @_SQLID@ before running the
script.
Result
The database for Business Process Choreographer exists.
What to do next
Continue configuring in the parent topic at step 2.