Perform this task if you want to use DB2 for z/OS as the database
store for your UDDI registry data.
Before you begin
To connect from a machine that runs a distributed
operating system to a remote DB2 database on the z/OS operating system, you
must have DB2 Version 8.2 or later. You must also have a DB2 Connect license
(see the DB2 documentation for more information).
If you want to create a remote
database, refer first to the database product documentation about the relevant
capabilities of the product.
About this task
You need to perform this task only once
for each UDDI registry, as part of setting up and deploying a UDDI registry.
There
are some known restrictions with DB2 for zSeries Version 7:
- Publish and inquiry strings are limited to 255 characters. For more information,
see UDDI registry Application
Programming Interface.
- When a UDDI inquiry request uses a discoveryURL that contains complex
Unicode characters, the request might fail to return expected entities. Avoid
using Unicode characters in discoveryURL elements if you are using this version
of DB2.
Procedure
- Copy the createddl.sh script that is supplied in the directory app_server_root/UDDIReg/rexx
to a temporary directory of your choice.
- Using the UNIX System Services (USS) command prompt, edit the copy
of the createddl.sh script, as follows:
- Search for the text 'Define some constants'.
- If WebSphere Application Server is not installed in the default
location, update the root_dir constant to reflect this. The UDDIReg directory
must remain at the end of the path.
- If you do not want to use the default temporary directory, update
the temp_dir constant to specify the temporary directory that you require.
- Using the USS command prompt, run the copy of the createddl.sh
script by entering the following command:
createddl.sh database_name tablespace_name hlq
where
the parameters are as follows:
- database_name
- The name that is used when defining the required DB2 tables and other
components. The default is UDDI30.
- tablespace_name
- The tablespace in which the database tables are defined. The default
is UDDI30TS.
- hlq
- The high-level qualifier under which the SQL and JCL partitioned datasets
(PDS) are created. The default is IBMUSER.
The script generates the hlq.UDDI.SQL
and hlq.UDDI.JCL partitioned data sets, which contain members
that are required for subsequent steps. If the script is run successfully
using the default parameters, the result is the following output:
database.tablespace = UDDI30.UDDI30TS
HLQ = IBMUSER
( 14) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_10_prereq_db2.sql
( 436) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_20_tables_generic.sql
( 136) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_25_tables_db2udb.sql
( 452) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_30_constraints_generic.sql
( 14) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_35_constraints_db2udb.sql
( 559) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_40_views_generic.sql
( 94) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_45_views_db2udb.sql
( 329) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_50_triggers_db2udb.sql
( 16) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_60_insert_initial_static_
data.sql
( 39) /WebSphere/V6R0M0/AppServer/UDDIReg/databaseScripts/uddi30crt_70_insert_default_database_
indicator.sql
Conversion complete
/tmp/udditmp/makedb71.jcl ===> IBMUSER.UDDI.JCL(MAKEDB71)
/tmp/udditmp/makedb81.jcl ===> IBMUSER.UDDI.JCL(MAKEDB81)
/tmp/udditmp/table.sql ===> IBMUSER.UDDI.SQL(TABLE)
/tmp/udditmp/table7.sql ===> IBMUSER.UDDI.SQL(TABLE7)
/tmp/udditmp/index.sql ===> IBMUSER.UDDI.SQL(INDEX)
/tmp/udditmp/view.sql ===> IBMUSER.UDDI.SQL(VIEW)
/tmp/udditmp/trigger.sql ===> IBMUSER.UDDI.SQL(TRIGGER)
/tmp/udditmp/alter.sql ===> IBMUSER.UDDI.SQL(ALTER)
/tmp/udditmp/initial.sql ===> IBMUSER.UDDI.SQL(INITIAL)
/tmp/udditmp/insert.sql ===> IBMUSER.UDDI.SQL(INSERT)
- There are two sample jobs in the JCL library for creating the DB2
database, one for DB2 version 7 and one for DB2 version 8. The JCL for these
jobs can be found in members MAKEDB71 and MAKEDB81 respectively, in the hlq.UDDI.JCL
PDS. These JCL scripts are templates; modify the template in the appropriate
MAKEDB member according to your DB2 setup and whether you want a default or
a customized UDDI node:
- Add or modify the JOB accounting information, if required.
- If you used a different high level qualifier from the default when running
the script in step one, ensure that all occurrences of IBMUSER are changed
to the qualifier that you specified.
- If you do not want your database to be used as a default UDDI node, comment
out the line of the job which specifies the INSERT member of the SQL PDS;
this should be the last line in the job.
- Ensure that all occurrences of the LIB parameter correctly reflect the
directory into which you installed DB2.
- Use TSO to submit the job that you modified in the previous step.
The job will create the DB2 database.
What to do next
Continue with setting up and deploying your UDDI registry node.