Use the Database page of the Configuration Manager to configure WebSphere Commerce to work with your database.
In the WebSphere Commerce instance creation wizard, the fields described here appear on the Database and Schema panels. Note: The Database panel does not apply to i5/OS users and is not displayed for the Instance Creation wizard on i5/OS.
The fields displayed on the Database page differ significantly when running Configuration Manager on different operating systems. To move quickly to the section of this page applicable to your operating system, click one of the following links:
AIX, Solaris OS, Linux and Windows users
To move quickly to the panel for which you want help, click one of the following links:
Complete the fields in the Database panel as follows:
- Database
- This is only available in the Instance Creation wizard.
Select one of the options available here as follows:If you want to create the WebSphere Commerce database and populate the database, select Create a new DB2 database or Oracle tablespace.
If you want to create and populate a tablespace in the WebSphere Commerce database, select Create a new DB2 database or Oracle tablespace.
The Oracle database must have been created before installing WebSphere Commerce by following the instructions in WebSphere Commerce Installation Guide.
- If you want to use an existing WebSphere Commerce database or tablespace, select Use an existing DB2 database or Oracle tablespace.
When using an existing WebSphere Commerce database, ensure that the database name in the Database name field on Schema panel of the Instance Creation wizard matches the name of the existing WebSphere Commerce database.
Notes on using an existing database:
Ensure that the schema user exists on the database machine.
- Ensure that the existing database is empty. If the tables in the existing database contain any data, instance creation will fail.
- The existing WebSphere Commerce database or tablespace must be a database or tablespace for WebSphere Commerce 5.7. Databases or tablespaces for WebSphere Commerce Version 5.6 and lower must be migrated before they can be used as a WebSphere Commerce 5.7 database or tablespace. Migration instructions are provided in WebSphere Commerce Migration Guide.
- You cannot use an existing WebSphere Commerce Payments database as the WebSphere Commerce database. WebSphere Commerce and WebSphere Commerce Payments must use different databases or tablespaces. If WebSphere Commerce and WebSphere Commerce Payments share the same database or tablespace, WebSphere Commerce Payments will not start.
- Database administrator name
Enter the local operating system user ID for your database administrator.
Enter the Oracle ID for the database administrator. You cannot use the Oracle ID SYS as the database administrator name.
- Database administrator password
- Enter the password of the database administrator.
Database administrator home directory
- Enter the home directory of the database administrator ID. The home directory is used to locate the profile of the database administrator when setting up the environment for instance creation.
This field is not displayed if you chose to use Oracle database.
- Database name
- Enter the name of the database to create for this instance, or enter the name of an existing database that you want to associate with the instance that you are creating.
The database name must contain 8 characters or fewer. On AIX and Solaris Operating Environment, this database will be cataloged remotely at a node named after your WebSphere Commerce machine's host name as the following:
rdatabase_name
- Database type
- Select the product you will be using as your database management system.
Selecting Oracle as your database type enables the following fields:
- Oracle SID
- The Oracle database SID. The Service Name field is only available if you have selected Oracle in the Database Type field.
- Database server port
- Enter the port number on which your remote database server is running. The default port is 1521.
- Full path to datafile
- Enter the full path to the WebSphere Commerce datafile (.DBF file) on the Oracle server. The default path is the following:
Oracle_installdir/database/wcs.dbf
- Tablespace Name
- Enter the name of the tablespace that Configuration Manager will create and populate in the Oracle database you created for use by WebSphere Commerce server in WebSphere Commerce Installation Guide
- Temporary Tablespace
- Enter the name of the temporary tablespace that Configuration Manager will create in the WebSphere Commerce database you created for use by WebSphere Commerce Server in WebSphere Commerce Installation Guide
- Remote
- Select this check box if your database server software is on a different machine than your WebSphere Commerce Server.
Note: If you have installed your database server on a different node than WebSphere Commerce (for example, if you are configuring a three-node environment), you must select this check box.
Selecting this check box enables the following fields:
- Database server host name
- Enter the fully qualified host name of the machine that hosts your database software.
Database server port
- Enter the port number on which your remote database server is running.
The default port is 50000. Database node name
- Enter the node name that you used when cataloging the node for your remote database. If you have not already cataloged a node for your remote database, Configuration Manager will catalog a node for you.
Do not use db2 anywhere in the node name. A node name containing db2 will cause instance creation to fail.
The node name must contain 8 characters or less.
- Advanced Options
- The Advanced Options check box is available in the Instance Creation wizard.
Select Advanced Options to set the advanced settings when creating and populating the WebSphere Commerce database during instance creations.
If you selected DB2 as the database type, the following fields are available:
- Default application heap (4KB)
- Enter the number of 4KB blocks you would like the default application heap to use for the WebSphere Commerce database.
- SQL statement heap (4KB)
- Enter the number of 4KB blocks you would like the SQL statement heap to use for the WebSphere Commerce database.
- Max. appl. control heap size (4KB)
- Enter the number of 4KB blocks you would like the maximum application control heap size to be for the WebSphere Commerce database.
- Max storage for lock list (4KB)
- Enter the number of 4KB blocks you would like the maximum storage for the lock list to be for the WebSphere Commerce database.
If you selected Oracle as the database type, the following fields are available:
- Tablespace Size (MB)
- Enter the tablespace size (in MB) you would like defined when Configuration Manager creates and populates the WebSphere Commerce database.
- Generate properties file only
- This check box only displays in the Instance Creation wizard.
Select this check box if you do not want to create an instance but you want to populate a properties file. The properties file can be used with the CreateInstance Ant target to create a WebSphere Commerce instance.
The properties file is found in WC_installdir/instances/instance_name/properties/createInstance.properties.
Complete the fields in the Schema panel as follows:
- Schema
- This is only available in the Instance Creation wizard if you chose to use an existing database.
Select one of the options available here as follows:- If you want to create the WebSphere Commerce schema in the database, select Create WebSphere Commerce schema.
- If you want to use an existing WebSphere schema, select Use existing WebSphere Commerce schema.
Only tables, views and indexes can exist in the schema at the time of instance creation. If there are constraints, stored procedures, or the database has been previously populated, instance creation will fail.
Oracle instance userid
- Enter the Oracle user ID of the user who issues Oracle commands.
- Database user name
Enter an existing operating system user ID to use for this database. The user ID must be defined on the system on which DB2 Universal Database is installed.
The user ID must be able to access the database and have the following DB2 Universal Database permissions:
- createtab
- binadd
- connect
The user ID must also have permissions to create tables in the target tablespaces.
Enter the Oracle user ID for this database that the Instance Creation wizard will create. Do not enter an existing Oracle user ID.
Important: The WebSphere Commerce database user ID must be different from the WebSphere Commerce Payments database user ID. Using the same user ID for the WebSphere Commerce and WebSphere Commerce Payments databases will cause connection pool problems, causing WebSphere Commerce Payments to functions incorrectly. Using the same user ID may also prevent the WebSphere Commerce Payments instance from being created correctly.
- Database user password
- Enter the password associated with the user name for this database.
- Confirm Database user password
- Confirm the password to be used for the database user ID that the Instance Creation wizard will create.
Database user home directory
- Enter the home directory of the database user ID. The home directory is used to locate the profile of the database user when setting up the environment for instance creation.
- Set as active database
- Select this check box if this database is the database you want to use with your WebSphere Commerce instance. After you have created your instance you can create additional databases and select the one that you want to use for your instance.
This check box is selected by default.
- Generate properties file only
- This check box only displays in the Instance Creation wizard.
Select this check box if you do not want to create an instance but you want to populate a properties file. The properties file can be used with the CreateInstance Ant target to create a WebSphere Commerce instance.
The properties file is found in WC_installdir/instances/instance_name/properties/createInstance.properties.
i5/OS users
- Relational Database Name
- Select the name of the database to use for WebSphere Commerce. The Relational Database Names can be checked by issuing the WRKRDBDIRE command from an i5/OS command line.
- Instance Logon password
- Enter the password for the new instance user profile that will be created. The password must be 10 characters or less.
- Confirm password
- Re-enter the instance logon password.
- Use staging server
- Select this check box if you want to use this database for your staging server.
- Remote
- This check box will be selected if you selected a remote database in the Relational Database Name.
If this check box is selected, the following fields display:
- Database server host name
- This field displays the host name of the node where the select database exists.
- Generate properties file only
- This check box only displays in the Instance Creation wizard.
Select this check box if you do not want to create an instance but you want to populate a properties file. The properties file can be used with the CreateInstance Ant target to create a WebSphere Commerce instance.
The properties file is found in WC_installdir/instances/instance_name/properties/createInstance.properties.