Configuration Manager - Payments - Database

Use the Database page of the Configuration Manager to configure WebSphere Commerce Payments to work with your database. Complete the fields as follows:

WebSphere Commerce Payments Database - Create a new database or tablespace
To have Configuration Manager create the new database or tablespace, select this radio button. If the database or tablespace was already created for you by a database administrator (and you do not need Configuration Manager to create it), select the radio button for using an existing database or tablespace.

Important: You cannot use an existing WebSphere Commerce database as the WebSphere Commerce Payments database. WebSphere Commerce and WebSphere Commerce Payments must use different databases. If WebSphere Commerce and WebSphere Commerce Payments share the same database, WebSphere Commerce Payments will not start.

AIXLinuxSun Solaris Operating EnvironmentWindows  Database administrator name
DB2 Enter the local operating system user ID for your database administrator.
Oracle Enter the Oracle ID for the database administrator. You cannot use the Oracle ID SYS as the database administrator name.
AIXLinuxSun Solaris Operating EnvironmentWindows  Database administrator password
Enter the password of the database administrator.
AIXSun Solaris Operating Environment  Database administrator home directory
Enter the home directory of the database administrator ID.
AIXLinuxSun Solaris Operating EnvironmentWindows  Database name
Enter the name of the database that you want 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. If you are using Oracle as your database management system, enter the ODBC datasource that you defined in the odbc.ini file.

DB2 The database name must contain 20 characters or fewer. On AIX and Solaris Operating Environment, this database will be cataloged remotely at a node named after your WebSphere Commerce's machine's host name as the following:

rdatabase_name


AIXLinuxSun Solaris Operating EnvironmentWindows  Database type
Select the product you will be using as your database management system.

Selecting Oracle as your database type enables the following fields:

AIXLinuxSun Solaris Operating EnvironmentWindows Oracle SID
The Oracle database SID. The Service Name field is only available if you have selected Oracle in the Database type field.
AIXSun Solaris Operating Environment Oracle instance userid
Enter the Oracle user ID of the user who issues Oracle commands.
AIXLinuxSun Solaris Operating EnvironmentWindows 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/wpm.dbf
If there is a separate .DBF file for WebSphere Commerce Payments, be sure to specify the Payments .DBF file name.
AIXLinuxSun Solaris Operating EnvironmentWindows  Tablespace name
Enter the name of the tablespace that Configuration Manager will create and populate in the Oracle database you created.
AIXLinuxSun Solaris Operating EnvironmentWindows  Temporary tablespace
Enter the name of the temporary tablespace that Configuration Manager will create in the WebSphere Commerce Payments database you created for use by WebSphere Commerce Payments.


Remote
Select this check box if your database server software is on a different machine than your WebSphere Commerce Payments Server.

Note: If you have installed your database server on a different node than WebSphere Commerce Payments (for example, you are configuring a three-node environment), you must select this check box.

Selecting this check box enables the following fields:

Database server hostname
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.
DB2  The default port is 50000.
Oracle  The default port is 1521.
DB2  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, the Configuration Manager will catalog a node for you.