IBM Business Process Manager, V8.0.1, All platforms > Reference > Commands and scripts > Commands (wsadmin scripting)

configEventServiceOracleDB command

Use the configEventServiceOraclesDB command to configure the Common Event Infrastructure using an Oracle database.

Purpose

The configEventServiceOracleDB command is a Common Event Infrastructure administrative command is available for the AdminTask object. Use this command to create the event service tables and data sources for Oracle on a server or cluster. The command does not create the database; the Oracle SID must already exist. For more information about the AdminTask object, see the WebSphere Application Server documentation.

The product uses a Jython version that does not support Microsoft Windows 2003, Windows Vista, or Windows 7 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

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.

- oracleHome

The ORACLE_HOME directory. This parameter must be set when the parameter createDB is set to true.

- dbHostName

The host name of the server where the Oracle database is installed. The default value is localhost if not specified.

- dbPort

Oracle instance port. The default value is 1521 if not specified.

- dbName

The Oracle system identifier (SID). The SID must already exist and must be available for the event service command to create the tables and populate the tables with data. The default value is orcl if not specified.

- dbUser

The Oracle schema user ID that will own the event service Oracle tables. The user ID will be created during the database creation; the WebSphere data source uses this user ID to authenticate the Oracle database connection. The default value is ceiuser if not specified.

- dbPassword

The password of the schema user ID. The password will be created during the database creation; the WebSphere data source uses this password to authenticate the Oracle database connection. This parameter is required.

- sysUser

Oracle sys user ID. This must be a user that has SYSDBA privileges. The default value is sys if not specified.

- sysPassword

The password for the user specified by the sysUser parameter. The default value is an empty string if not specified.

- ceiInstancePrefix

The command uses the event service instance name to group the database files in a directory with unique names. The default value is ceiinst1 if not specified.

- 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/oracle if this parameter is not specified.

Sample

Batch mode example usage:

• Use Jacl:

  $AdminTask configEventServiceOracleDB {-createDB true
   -overrideDataSource true
   -nodeName nodename
   -serverName servername
   -jdbcClassPath c:\oracle\ora92\jdbc\lib
   -oracleHome c:\oracle\ora92
   -dbUser ceiuser
   -dbPassword ceipassword
   -dbHostName host_name
   -dbPort 1521
   -sysUser sys
   -sysPassword syspassword}
  

• Use Jython string:

  AdminTask.configEventServiceOracleDB( '[-createDB true
   -overrideDataSource true
   -nodeName nodename
   -serverName servername
   -jdbcClassPath c:\oracle\ora92\jdbc\lib
   -oracleHome c:\oracle\ora92
   -dbUser ceiuser
   -dbPassword ceipassword
   -dbHostName host_name
   -dbPort 1521
   -sysUser sys
   -sysPassword syspassword]' )
  

• Use Jython list:

  AdminTask.configEventServiceOracleDB(['-createDB', 'true',  '-overrideDataSource', 'true',  '-nodeName', 'nodename',  '-serverName', 'servername',  '-jdbcClassPath', 'c:\oracle\ora92\jdbc\lib',  '-oracleHome', 'c:\oracle\ora92',  '-dbUser', 'ceiuser',  '-dbPassword', 'ceipassword',  '-dbHostName', 'host_name',  '-dbPort', '1521',  '-sysUser', 'sys',  '-sysPassword', 'syspassword'])
  

Interactive mode example usage:

• Use Jacl:

  $AdminTask configEventServiceOracleDB -interactive
  

• Use Jython string:

  AdminTask.configEventServiceOracleDB('[-interactive]')
  

• Use Jython list:

  AdminTask.configEventServiceOracleDB(['-interactive'])
  

Parent topic: Commands (wsadmin scripting)

Related information:

Obtaining online help using wsadmin scripting
Administrative command invocation syntax using wsadmin scripting
Use the wsadmin scripting tool
Jython script library