

Configuring the development environment to use an Oracle database
The initial installation of WebSphere Commerce Developer provides WebSphere Commerce Developer with the Apache Derby database. You can reconfigure your environment to use an Oracle database.
Before you begin
Ensure that you completed the following tasks:
- Installed an Oracle database on a local or remote Windows machine. See the following table for a
list of components required for a local or remote installation of the Oracle database.
Local Oracle database Remote Oracle database - Oracle Net Services
- Oracle Net Protocol Support
- SQL*Plus
- Oracle JDBC/Thin Interfaces
- Oracle JDBC/OCI Interfaces
- Database server machine
-
- Oracle Net Services
- Oracle JDBC/Thin Interfaces
- Oracle JDBC/OCI Interfaces
- WebSphere Commerce development machine
-
- Oracle Enterprise Client
- SQL*Plus
- Oracle JDBC/Thin Interfaces
- Oracle JDBC/OCI Interfaces
- Oracle Network Utilities
- Oracle Database Utilities
- Created a new Oracle user ID and an empty schema. Ensure that the database uses the UTF-8 character set and that the Oracle user ID has access to the new database. The Oracle user ID must not be a reserved user ID like SYSTEM or SYS.
- Set the Oracle
open_cursors
configuration parameter to 1000 or higher. You must restart Oracle after changing theopen_cursors
value.The installation default value of
open_cursors
is 300. If you do not set theopen_cursors
value higher, you might receive error messages. - Record the following information about the Oracle database:
Local Oracle database Remote Oracle database - The root directory of the Oracle database.
For example,
C:\ORACLE\ORA
- The name of the database
- The database administrator ID
- The database administrator password
- The database user ID
- The database user password
- The root directory of the Oracle database client
For example,
C:\ORACLE\ORA
- The name of the remote database
- The name of the local net service for the remote database
- The database administrator ID
- The database administrator password
- The database user ID
- The database user password
- The fully qualified host name of the database server
- The port number on the database server used for remote connections
- The root directory of the Oracle database.
- Back up your existing development database.
About this task
Procedure
- Stop the Rational Application Developer server.
- Start a Windows command prompt and go to the WCDE_installdir/bin directory.
-
Restore the database to the default Apache Derby database if you are not currently using the
default database.
-
Issue one of the following commands, depending on your needs.
Option Description You are configuring the development environment to use a newly created Oracle database. Issue the following command:
where:setdbtype oracle ORACLE_HOME dbName dbAdminID dbAdminPassword dbUserID dbUserPassword [dbHost dbServerPort] createdb
- ORACLE_HOME
- The root directory of Oracle or the database client, depending on if you have a local or a
remote database.
For example,
C:\ORACLE\ORA12
. - dbName
- The name of the database to use with WebSphere Commerce developer. If you are using a remote database, this is the name of the database on the remote database server.
- dbAdminID
- The database administrator ID.
- dbAdminPassword
- The database administrator password.
- dbUserID
- The new Oracle user ID created as part of the prerequisites. Important: Do not specify a reserved Oracle ID user ID. Examples of reserved Oracle IDs include SYSTEM and SYS.
- dbUserPassword
- The database user password.
- dbHost
- For remote database only The fully qualified host name of the database server.
- dbServerPort
- For remote database only The port number on the database server used for remote connections.
You are configuring the development environment to use an existing Oracle development database. Issue the following command:
where:setdbtype oracle ORACLE_HOME dbName dbAdminID dbAdminPassword dbUserID dbUserPassword [dbHost dbServerPort]
- ORACLE_HOME
- The root directory of Oracle or the database client, depending on if you have a local or a
remote database.
For example,
C:\ORACLE\ORA12
. - dbName
- The name of the database to use with WebSphere Commerce developer.
If you are using a remote database, this is the name of the database on the remote database server.
- dbAdminID
- The database administrator ID.
- dbAdminPassword
- The database administrator password.
- dbUserID
- The database user ID. Important: Do not specify a reserved Oracle ID user ID. Examples of reserved Oracle IDs include SYSTEM and SYS.
- dbUserPassword
- The database user password.
- dbHost
- For remote database only The fully qualified host name of the database server.
- dbServerPort
- For remote database only The port number on the database server used for remote connections.
- Restart the WebSphere Commerce Test server.
-
To reset the Stores project or before you publish a new starter store, run the command:
- WCDE_installdir/bin/resetstores.bat
Note: If you run this command, you cannot use the existing stores if you decide to switch back to the Apache Derby database later.
Results
The WebSphere Commerce development environment is now configured to use
a DB2 database. All data in the Apache Derby database remains unchanged until you return to using
Apache Derby as the development database. Your Apache Derby database is reset and cleaned when you
run any of the following commands:
- Run the resetdb.bat command
- Run the resetstores.bat command
- Run the setdbtype command, specifying Apache Derby and by using the
createdb
flag.