Create a DB2 distributed database for the UDDI registry
Perform this task if you want to use DB2 on the Windows, Linux or UNIX operating systems, as the database store for your UDDI registry data. The steps below use a number of variables for which enter appropriate values. You should decide the values that you will use before you start. The variables used, and suggested values are:
- <DataBaseName>
- is the name of the UDDI registry database. A recommended value is UDDI30, and this name is assumed throughout the UDDI documentation. If you use some other name, then you should substitute that name whenever you see 'UDDI30' in other sections of the documentation.
- <DB2UserID>
- is a DB2 userid with administrative privileges.
- <DB2Password>
- is the password for the DB2 userid.
- <BufferPoolName>
- is the name of a buffer pool to be used by the UDDI registry database. A suggested name is uddibp, but any name can be used, as the buffer pool is created as part of this task.
- <TableSpaceName>
- is the name of a table space. A suggested value is uddits, but any name can be used.
- <TempTableSpaceName>
- is the name of a temporary table space. A suggested value is udditstemp, but any name can be used, as the temporary table space is created as part of this task.
Overview
You only need to perform this task once for each UDDI registry, as part of setting up and deploying a UDDI registry.
If you are creating a remote database, use the database product documentation to familiarize yourself with the relevant capabilities of the product before proceeding with this task.
Procedure
- Change directory to app_server_root/UDDIReg/databaseScripts.
- Start the DB2 Command Line Processor by entering db2 at the command prompt.
For Windows platforms, enter db2cmd and then enter db2 in the new DB2 window.
- Run the following command to setup the DB2 environment variables:
set DB2CODEPAGE=1208
- Create the DB2 database by entering the following command:
create database <DataBaseName> using codeset UTF-8 territory enwhere <DataBaseName> is the name of the database being created.
- Configure the DB2 database by entering the following commands:
- connect to <DataBaseName> user <DB2UserID> using <DB2Password>
- update db cfg for <DataBaseName> using applheapsz 2048
- update db cfg for <DataBaseName> using logfilsiz 8192
- connect reset
- terminate
- Create additional database structures by entering the following commands:
- connect to <DataBaseName> user <DB2UserID> using <DB2Password>
- create bufferpool <BufferPoolName> size 250 pagesize 32K
- connect reset
- terminate
- force application all
- terminate
- stop
- start
- Create further database structures by entering the following commands:
- connect to <DataBaseName> user <DB2UserID> using <DB2Password>
- create regular tablespace uddits pagesize 32K managed by system using ('<TableSpaceName>') extentsize 64 prefetchsize 32 bufferpool <BufferPoolName>
- create system temporary tablespace <TempTableSpacename> pagesize 32K managed by system using ('<TempTableSpacename>') extentsize 32 overhead 14.06 prefetchsize 32 transferrate 0.33 bufferpool <BufferPoolName>
- Exit the DB2 Command Line Processor and enter the following commands exactly as shown, noting that one step uses -vf rather than -tvf (on Windows platforms, run the commands from the db2cmd window). These commands define the database structures needed to store the UDDI data:
- db2 -tvf uddi30crt_10_prereq_db2.sql
- db2 -tvf uddi30crt_20_tables_generic.sql
- db2 -tvf uddi30crt_25_tables_db2udb.sql
- db2 -tvf uddi30crt_30_constraints_generic.sql
- db2 -tvf uddi30crt_35_constraints_db2udb.sql
- db2 -tvf uddi30crt_40_views_generic.sql
- db2 -tvf uddi30crt_45_views_db2udb.sql
- db2 -vf uddi30crt_50_triggers_db2udb.sql
- db2 -tvf uddi30crt_60_insert_initial_static_data.sql
- Run this step only if you want your database to be used as a default UDDI node. Enter the following command:
db2 -tvf uddi30crt_70_insert_default_database_indicator.sql
What to do next
Continue with setting up and deploying your UDDI registry node.
Related tasks
Setting up a default UDDI node
Setting up a customized UDDI node