The default installation of the runtime product creates
a stand-alone application server, and a Derby database for use by
the Message Logger mediation primitive. If you want to deploy mediation
modules that use this primitive, you might prefer to make use of the
reliability of a remote DB2® database
on a z/OS® system.
About this task
You can use coreDBUtility to create
the WebSphere® ESB message
logging database on a remote z/OS system.
You can run this utility after profile creation for any profile type.
The utility generates scripts that can then be used by a z/OS administrator on the z/OS system.
For a full list of the parameters
you can use with coreDBUtility, see coreDBUtility parameters.
The coreDBUtility utility
is located in install_root/bin.
The commands used in the example procedures are for a profile called default,
and a DB2 for z/OS v8 database
named ESBDB. The utility also supports DB2 for z/OS v9 databases.
Procedure
- Use coreDBUtility to create a database. For example:
coreDBUtility createDB -DprofilePath=install_root\profiles\default
-DdbType=DB2UDBOS390_V8_1 -DdbName=ESBDB
A script called createDB_DB2.sql is
generated. You can then run this script on the remote z/OS system to create the database.
- Create the table in the database.
- You can use coreDBUtility to generate the
script for creating the database table. For example, for a table in
the database storage group named ESBDBSTO, with a
schema called ESBLOG:
coreDBUtility createTable -DprofilePath=install_root\profiles\default
-DdbType=DB2UDBOS390_V8_1 -DdbName=ESBDB -DsqlScriptPath.default=install_root
\util\EsbLoggerMediation\DB2UDBOS390_V8_1\Table_esb_DB2UDBOS390_V8_1.ddl
-DdbStorageGroup=ESBDBSTO -DdbSchemaName=ESBLOG -DdbDefineSQL false
This
command generates a script called Table_esb_DB2UDBOS390_V8_1.ddl in install_root/profiles/default/databases/ESBDB,
which you can run on the remote z/OS system
to create the table. To view an example of this script, see Example of Table_esb_DB2UDBOS390_V8_1.ddl.
- You can also choose to generate and remotely execute the script
in one command. For example:
coreDBUtility createTable -DprofilePath=install_root\profiles\default
-DdbType=DB2UDBOS390_V8_1 -DdbName=ESBDB -DsqlScriptPath.default=install_root
\util\EsbLoggerMediation\DB2UDBOS390_V8_1\Table_esb_DB2UDBOS390_V8_1.ddl
-DdbStorageGroup=ESBDBSTO -DdbSchemaName=ESBLOG -DdbHostName hostname
-DdbServerPort server_port -DdbJDBCClasspath=JDBC_classpath
-DdbUserId=username -DdbPassword=password
-DdbConnectionLocation=connection_location
This
runs the script on the remote z/OS system
using the connection parameters you set in the command.
- Create the JDBC provider for the required database type. You can use coreDBUtility to connect to the WebSphere configuration and
create the JDBC definitions. For example, for a cell named defaultCell and
a node named defaultNode:
coreDBUtility createJDBCProvider -DprofilePath=install_root\profiles\default
-DdbType=DB2UDBOS390_V8_1 -DscopeLevel=node -DcellName=defaultCell
-DnodeName=defaultNode -DdbJDBCClasspath=JDBC_classpath
- Create the data source. You can use coreDBUtility to
connect to the WebSphere configuration
and create the data source to be used. For example:
coreDBUtility createDataSource -DjndiName=jdbc/ESBDB
-DprofilePath=install_root\profiles\default -DprofileName=default
-DdbType=DB2UDBOS390_V8_1 -DdbName=ESBDB -DdbHostName hostname
-DdbServerPort server_port -DdbUserId=username -DdbPassword=password
-DdbConnectionLocation=connection_location -DdbStorageGroup=ESBDBSTO
-DscopeLevel=node -DcellName=defaultCell -DnodeName=defaultNode
-DdbJDBCClasspath=JDBC_classpath