configEventServiceDB2DB command

Use the configEventServiceDB2DB command to configure the Common Event Infrastructure using a DB2® database.

Purpose

The configEventServiceDB2DB 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 on a server or cluster. For more information about the AdminTask object, see the WebSphere Application Server 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: 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/dbtype if this parameter is 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.
- dbNodeName: The DB2 node name (this must be 8 characters or less). This node must be already catalogued and configured to communicate with the DB2 server. This parameter must be set if the current server is configured as a DB2 client and the parameter createDB is set to true.
- dbHostName: The host name of the server where the database server is installed. This parameter is required.
- dbPort: DB2 instance port. The default value is 50 000 if not specified.
- dbName: The database name to be created. The default value is event if not specified.
- dbUser: DB2 user ID that has privileges to create and drop the databases. The default value is db2inst1 if not specified.
- dbPassword: DB2 password. This parameter is required.
- 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/db2 if this parameter is not specified.

Sample

Batch mode example usage:

Using Jacl:

$AdminTask configEventServiceDB2DB {-createDB true
 -overrideDataSource true 
 -nodeName nodename
 -serverName servername
 -jdbcClassPath c:\sqllib\java 
 -dbUser db2inst1
 -dbPassword dbpassword
 -dbHostName host_name
 -dbPort 50000 }

Using Jython string:

AdminTask.configEventServiceDB2DB('[-createDB true 
 -overrideDataSource true
 -nodeName nodename
 -serverName servername
 -jdbcClassPath c:\sqllib\java
 -dbUser db2inst1
 -dbPassword dbpassword
 -dbHostName host_name
 -dbPort 50000 ]')

Using Jython list:

AdminTask.configEventServiceDB2DB(['-createDB', 'true',
 '-overrideDataSource',  'true',
 '-nodeName', 'nodename',
 '-serverName', 'servername',
 '-jdbcClassPath', 'c:\sqllib\java',
 '-dbUser', 'db2inst1',
 '-dbPassword', 'dbpassword ',
 '-dbHostName', 'host_name',
 '-dbPort', '50000 '])

Interactive mode example usage

Using Jacl:

$AdminTask configEventServiceDB2DB -interactive

Using Jython string:
Note: The product uses a Jython version that does not support Microsoft Windows 2003, Windows Vista, or Windows 7 operating systems.
```
AdminTask.configEventServiceDB2DB('[-interactive]')
```

Using Jython list:

AdminTask.configEventServiceDB2DB(['-interactive'])