Use the configEventServiceDB2ZOSDB command
to configure the Common Event Infrastructure using a DB2® for z/OS® database.
Purpose
The configEventServiceDB2ZOSDB command
is a Common Event Infrastructure administrative
command is available for the AdminTask object. Use this command to
create the event service database and data sources for DB2 z/OS on
a server or cluster. For more information about the AdminTask object,
see the WebSphere® Application Server
Network Deployment, version 6.1 documentation.
Parameters
- - createDB
- The command generates the DDL database scripts and creates the
database when this parameter is set to true. The
command only generates the DDL database scripts when this parameter
is set to false. To create the database, the current
server must be already configured to run the database commands. The
default value is false if not specified.
- - overrideDataSource
- When this parameter is set to true, the command
removes any existing event service data source at the specified scope
before creating a new one. When this parameter is set to false,
the command does not create an event service data source at the specified
scope if another event service data source is found at the same scope.
The default value is false if not specified.
- - nodeName
- The name of the node that contains the server where the event
service data source should be created. If this parameter is specified,
then the serverName parameter must be set. You
must not specify this parameter if the clusterName parameter
is specified.
- - serverName
- The name of the server where the event service data source should
be created. If this parameters is specified without the nodeName parameter,
the command will use the node name of the current WebSphere profile. You must not specify
this parameter if the clusterName parameter is
specified.
- - clusterName
- The name of the cluster where the event service data source should
be created. If this parameter is specified, then the serverName and nodeName parameters
must not be set. You must not specify this parameter if the serverName and nodeName parameters
are specified.
- - jdbcClassPath
- The path to the JDBC driver. Specify only the path to the driver
file; do not include the file name in the path. This parameter is
required.
- - dbHostName
- The host name of the server where the database is installed. This
parameter is required.
- - dbPort
- DB2 for z/OS instance port. The default value is 5027
if not specified.
- - dbName
- The DB2 database name. On
the DB2 client, this is the
name of the catalogued database. On the native z/OS server, it is the name of the database
subsystem. The default value is event if not specified.
- - dbDiskSizeInMB
- Specify the disk size in MB for the event service database. This
value must be at least 10 MB. The default value is 100 MB if not specified.
- - dbUser
- DB2 user ID that has privileges
to create and drop the databases. This parameter is required.
- - dbPassword
- Password of the database user ID. This parameter is required.
- - storageGroup
- The storage group for the event database and the event catalog
database. The storage group must already be created and active.
- - bufferPool4K
- The name of the 4K buffer pool. This buffer pool must be active
before the database DDL scripts can be run.
- - bufferPool8K
- The name of the 8K buffer pool. This buffer pool must be active
before the dabase DDL scripts can be run.
- - bufferPool16K
- The name of the 16K buffer pool. This buffer pool must be active
before the database DDL scripts can be run.
- - outputScriptDir
- Optional database script output directory. When this parameter
is specified, the command generates the event service database scripts
in the specified directory. If the specified directory does not contain
a full path, the command creates the specified directory in profile_root/bin.
The default database script output directory is profile_root/databases/event/node/server/dbscripts/db2zos
if this parameter is not specified.
Sample
Batch mode example usage:
Using Jacl:
$AdminTask configEventServiceDB2ZOSDB {-createDB true -overrideDataSource true
-nodeName nodename -serverName servername -jdbcClassPath c:\sqllib\java
-dbUser db2user -dbPassword dbpassword -dbHostName host_name -dbPort 5027
-storageGroup sysdeflt -bufferPool4K BP9 -bufferPool8K BP8K9
-bufferPool16K BP16K9}
Using Jython string:
AdminTask.configEventServiceDB2ZOSDB('[-createDB true -overrideDataSource true
-nodeName nodename -serverName servername -jdbcClassPath c:\sqllib\java
-dbUser db2user -dbPassword dbpassword -dbHostName host_name -dbPort 5027
-storageGroup sysdeflt -bufferPool4K BP9 -bufferPool8K BP8K9
-bufferPool16K BP16K9]')
Using Jython list:
AdminTask.configEventServiceDB2ZOSDB(['-createDB', 'true', '-overrideDataSource',
'true', '-nodeName', 'nodename', '-serverName', 'servername', '-jdbcClassPath',
'c:\sqllib\java', '-dbUser', 'db2user', '-dbPassword', 'dbpassword',
'-dbHostName', 'host_name', '-dbPort', '5027', '-storageGroup', 'sysdeflt',
'-bufferPool4K', 'BP9', '-bufferPool8K', 'BP8K9', '-bufferPool16K', 'BP16K9'])
Interactive mode example usage:
Using Jacl:
$AdminTask configEventServiceDB2ZOSDB -interactive
Using Jython string:
AdminTask.configEventServiceDB2ZOSDB('[-interactive]')
Using Jython list:
AdminTask.configEventServiceDB2ZOSDB ['-interactive'])