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.
Before you begin
The following steps use a number of variables. Before you
start, decide appropriate values to use for these variables. The variables,
and suggested values, are:
- DataBaseName
- The name of the UDDI registry database. A suggested value is UDDI30.
The UDDI information uses the suggested name of UDDI30, so if you
use a different name, remember to substitute it when you see UDDI30
in the UDDI information.
- DB2UserID
- A DB2 user ID with administrative privileges.
- DB2Password
- The password for the DB2 user ID.
- BufferPoolName
- The name of a buffer pool for the UDDI registry database to use.
A suggested name is uddibp, but you can use any name because the buffer
pool is created as part of this task.
- TableSpaceName
- The name of a table space. A suggested value is uddits, but you
can use any name.
- TempTableSpaceName
- The name of a temporary table space. A suggested value is udditstemp,
but you can use any name because the temporary table space is created
as part of this task.
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 perform this task only once
for each UDDI registry, as part of setting up and deploying a UDDI
registry.
Procedure
- Change directory to app_server_root/UDDIReg/databaseScripts.
- Start the DB2® Command Line Processor.
For all operating systems except Windows®,
enter the following command at the command prompt:
db2
![[Windows]](../../windows.gif)
For
the Windows operating system, enter the following
command at the command prompt:
db2cmd
Then
enter the following command in the new DB2 window:
db2
- Set up the DB2 environment variables. Enter
the following command:
set DB2CODEPAGE=1208
- Create the DB2 database. Enter the
following command:
create database DataBaseName using codeset UTF-8 territory en
- Configure the DB2 database. Enter
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. Enter
the following commands:
connect to DataBaseName user DB2UserID using DB2Password
connect reset
terminate
force application all
terminate
stop
start
- Create further database structures. Enter 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
- Define the database structures that are needed to store
the UDDI data. For all operating systems except Windows, exit the DB2 Command
Line Processor and enter the following commands exactly as shown.
For the Windows operating system, enter
the following commands exactly as shown from the db2cmd window. Note
that one step uses -vf rather than -tvf.
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
- Optional: To use the database as a default
UDDI node, enter the following command:
db2 -tvf uddi30crt_70_insert_default_database_indicator.sql
What to do next
![[Version 6.0]](../../v60.gif)
To ensure that the following tModel entities are present,
you must run an additional script against the database:
- uddi-org:wsdl:types
- uddi-org:derivedFrom
- uddi-org:validatedBy
- uddi-org:owningBusiness_v3
- uddi-org:relationships
- uddi-org:xml:localName
- uddi-org:xml:namespace
For details, see the UDDI registry troubleshooting topic.
Continue
with setting up and deploying your UDDI registry node.