You can configure an event database on a z/OS® system using DB2® database
software.
Before you begin
To configure the DB2 database
from a remote client, you must have the DB2 Connect™ product installed with the
latest fix packs.
About this task
To configure the event database:
Procedure
- On the WebSphere® system,
start the wsadmin tool.
- Use the AdminTask object to run the configEventServiceDB2ZOSDB administrative
command in batch or interactive mode. The minimum required
parameters of the configEventServiceDB2ZOSDB command are as
follows:
- createDB
If
this parameter is set to false, or if you are running
the command on the z/OS system,
the scripts are created but are not run. You must then run the database
configuration scripts to complete the database configuration.
- nodeName
- The name of the node that contains the server where the event
service data source should be created. If you specify a node name,
you must also specify a server name. You must specify one of the following:
- Node name and server name
- Cluster name
- serverName
- The name of the server where the event service data source should
be created.
- clusterName
- The name of the cluster where the event service data source should
be created. If you specify a cluster name, do not specify node and
server names.
- jdbcClassPath
- The path to the JDBC driver. Specify only the path to the driver
file; do not specify the file name.
- dbHostName
- The host name of the server where the database is installed.
- dbUser
- The DB2 user ID to use when
creating the event database. The specified user ID must have sufficient
privileges to create and drop databases.
- dbPassword
- The DB2 password to use.
Other parameters might be required for your environment.
For a complete list of parameters and usage information, refer to
the help for the configEventServiceDB2ZOSDB administrative
command.
Results
The administrative command creates the required data source
at the specified scope; if you are running the command on a Linux®, UNIX®, or Windows® DB2 client and you specified true for
the createDB parameter, the command also runs the generated database
configuration script to create the database. On a z/OS system, you must use the SQL Processor
Using File Input (SPUFI) facility to run the generated DDL files.
The DDL files are stored in the profile_root/databases/event/node/server/db2zos/ddl
directory.
The generated database configuration scripts are
stored by default in the profile_root/databases/event/node/server/dbscripts/db2zos
directory. (In a Network Deployment environment, these scripts are
stored under the deployment manager profile directory.) If you specified
a value for the optional outputScriptDir parameter, the scripts are
stored in that location instead. You can use these scripts to manually
configure the event database at any time.
What to do next
After you have finished configuring the database, you can
use the server administrative console to test the database configuration.
To do this, navigate to the appropriate JDBC data source and select
the
Test Connection option.