Use the configEventServiceDerbyDB command
to configure the Common Event Infrastructure using a Derby database.
Purpose
The
configEventServiceDerbyDB 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 Derby on a
server or cluster. For more information about the AdminTask object,
see the
WebSphere® Application Server
Network Deployment, version 6.1 documentation.
Note: The product uses a Jython version that does not support Microsoft® Windows® 2003 or Windows Vista operating systems.
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.
- - dbHostName
- The host name of the network Derby database. To create the Derby
network data source, specify this parameter and the dbPort parameter.
To create the Derby local data source, do not specify this parameter
and the dbPort parameter.
- - dbPort
- The port number of the network Derby database. To create the Derby
network data source, specify this parameter and the dbHostName parameter.
To create the Derby local data source, do not specify this parameter
and the dbHostName parameter.
- - dbName
- The database name to be created. The default value is event if
not specified.
- - dbUser
- The user ID used by the data source for the Derby database authentication.
This parameter is optional when the WebSphere domain security is disabled.
If you specify this parameter, you also must specify the dbPassword parameter.
This parameter is required when the WebSphere domain security is enabled.
- - dbPassword
- The password used by the data source for the Derby database authentication.
This parameter is optional when the WebSphere domain security is disabled.
If you specify this parameter, you also must specify the dbUser parameter.
This parameter is required when the WebSphere domain security is enabled.
- - 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/derby
if this parameter is not specified.
Sample
Batch mode example usage:
Using Jacl:
$AdminTask configEventServiceDerbyDB {-createDB true -overrideDataSource true
-nodeName nodename -serverName servername}
Using Jython string:
AdminTask.configEventServiceDerbyDB( '[-createDB true -overrideDataSource true
-nodeName nodename -serverName servername]')
Using Jython list:
AdminTask.configEventServiceDerbyDB(['-createDB', 'true', '-overrideDataSource',
'true', '-nodeName', 'nodename', '-serverName', 'servername'])
Interactive mode example usage:
Using Jacl:
$AdminTask configEventServiceDerbyDB -interactive
Using Jython string:
AdminTask.configEventServiceDerbyDB('[-interactive]')
Using Jython list:
AdminTask.configEventServiceDerbyDB(['-interactive'])