Database Configurator README

IBM(R) Database Configurator version 1.4.1.0 for WebSphere(R) Commerce

Last Updated: July 15, 2002

Contents

Introduction

The purpose of this tool is to allow users to configure their WebSphere Commerce database environment to work with WebSphere Commerce.
You can create and tune your WebSphere Commerce database prior to the creation of an instance. Basic database configuration parameters can be easily configured with the use of a simple interface.
You can create users and tablespaces for use with WebSphere, WebSphere Commerce, and Payment Manager software. The Oracle database must exists on the system before running this tool.

This tool allows you to configure both local and remote databases.

What's in this README

This README contains basic information on how to configure your database to work with WebSphere Commerce. Updates to this README file are provided with every new release of this database configurator.

Installation

  1. Official support for languages other than English is not available. Ensure the system on which you install WebSphere Commerce, as well as your database are set to the English locale (en_US). Please note that this is the only supported English locale.
  2. To set the locale, use the Regional Settings tool in the Windows NT Control Panel or the Regional Options tool in the Windows 2000 Control Panel. After installation, the locale can be set back to the original one.
  3. Ensure that IBM SDK version 1.2.2 or later is installed on the system, and that the PATH variable is set to include the full path to where JDK is installed.
Installation Instructions

Installation of as Windows Executable (win-setup.exe):

  1. Download the win-dbconfig-setup.exe file, save it to a temporary directory.
  2. Navigate to the temporary directory, and run the win-dbconfig-setup.exe file.

Run as a Java Archive on AIX:

  1. Download the aix-dbconfig-setup.jar file, save it to local file system.
  2. Install a Java JDK for AIX ( JDK 1.2.2 and above, IBM JDK 1.3.0 recommended)
  3. Type the following command line to install it:

    "java -cp aix-dbconfig-setup.jar run"

Or
Run as an AIX native executable:

  1. Download and save the file locally: e.g. name is: aix-dbconfig-setup.jar
  2. change file permission to make it executable: chmod +x aix-dbconfig-setup.jar
  3. run the .jar file as an executable: ./aix-dbconfig-setup.jar

    This should start the installation launcher successfully as an AIX native code


Note: the installation as a Java .jar archive and the installation as a AIX native are equivalent. There is no need to run it twice.

Note: the aix-dbconfig-setup.jar file is actally not a java .jar archive, but a AIX native executable installer. The reason it is named as a jar file is because Windows IE browser will assume any file without extension a text file and append a .txt to it when saving to local file system, which brings confusion and inconvinence.

Run as a Java Archive on Solaris

  1. Download the sun-dbconfig-setup.jar file, save it to local file system.
  2. Install a Java JDK for Solaris ( JDK 1.2.2 and above, SUN JDK 1.3.0 recommended)
  3. Type the following command line to install it:

    "java -cp sun-dbconfig-setup.jar run"

Or

Run as an Solaris native executable:

  1. Download and save the file locally: e.g. name is: sun-dbconfig-setup.jar
  2. change file permission to make it executable: chmod +x sun-dbconfig-setup.jar
  3. run the .jar file as an executable: ./sun-dbconfig-setup.jar

    This should start the installation launcher successfully as an Solaris native code


Note: the installation as a Java .jar archive and the installation as a Solaris native are equivalent. There is no need to run it twice.

Note: the sun-dbconfig-setup.jar file is actally not a java .jar archive, but a Solaris native executable file. The reason it is named as a jar file is because Windows IE browser will assume any file without extension a text file and append a .txt to it when saving to local file system, which brings confusion and inconvinence.

Database Connections

  1. Make sure that your CLASSPATH variable contains the db2java.zip file, in order to allow DB Configurator to work properly.
  2. Make sure that your CLASSPATH variable contains the classes12.zip file, in order to allow DB Configurator to work properly.  Alternatively, ensure that the CLASSPATH variable contains the oracle.jdbc.driver.OracleDriver class loaded.

Running the Database Configurator

    From a command prompt, and navigate to the directory where the Database Configurator was installed, type
    java com.ibm.commerce.db.config.DbClient

    Note: This command must be issued from the Install Directory/bin location; otherwise, a FileNotFoundException will occur. Install Directory refers the the path where the database configurator is installed.

          Go to Start->Programs->IBM WebSphere Commerce->System Tools->Database Configurator, and launch Database Configurator
          Open a command-prompt and go to the DB Configurator Install Directory/bin. Then, execute the run-pd-<OS>.sh,
          where OS is the operating system name (i.e., aix, sun).

        Once the interface loads, follow these instructions:

  1. Fill in the mandatory values indicated in the interface, and then click on Run.
  2. A second window will open, displaying the composed database script. This script is based on the values entered on the previous screens.  At this point, the user may choose to save the script for later use, run the script to completion, or cancel and go back to the previous window.
  3. A log file called dbconfig.log is produced in the log directory that was specified at the time this product was installed. The user may examine this log to see the results of the run, and ensure that no errors where found.
  4. Click Exit.

Explanation of panels

Database
 This is the first panel in the Database Configurator. Note that ALL fields must be completed.

Product type
Select the WebSphere Commerce product name and version that you will be using.

Database type
From the drop-down list, select the name of the database management system you intend to use.

Remote
Click on ‘Remote’ if the database to be configured is on a remote system.

Hostname
Enter the hostname of the machine where your database is installed or accept the default.
Note: If the database is remote then you must use the fully qualified hostname.

Database name
According to the database type, this field will change its name to either Database Alias or OracleSID

Enter the name assigned to the database or accept the default.
For DB2, enter the name of your database. The name must be eight characters in length or less.
For Oracle, enter the WebSphere Commerce Global Database name that you entered during your Oracle installation (for example, o817 ).
 

Port#
Enter the port number associated with the remote database or accept the default.

Database User ID
Enter the user name of your database administrator. This is the user name that is used to perform the installation, unless you have defined
an alternate database administrator name.

If you have created a DB2 user for the database other than the database administrator, you can enter their user ID in this field. Otherwise, use the same user name as the database administrator.

Note that this user must have database administrative privileges in order to run this configuration tool.

For Oracle, use the Oracle user ID you created on Chapter 3, “Installing and configuring Oracle8i Database.”

Database user password
Enter the password associated with the database administrator’s user ID. This is the password of the user name that is used to perform the
installation, unless you have defined an alternate database administrator name.

DB Administrator Home Directory
Enter the the home directory of the Database Administrator. The default is /home/db2inst1.
Alternatively, you may use the home directory of the Database User. The default, too, is /home/db2inst1.


 

DB2 Settings

This panel is used to tune the DB2 parameters after the creation of the database.

Note: For more information on the following terms, see DB2 documentation.


 Default Application Heap (4KB)
Enter the application heap size or accept the default.

SQL Statement Heap (4KB)
Enter the SQL statement heap size or accept the default.

Max. Application Control Heap Size(4KB)
Enter the maximum application control heap size or accept the default.

Max. Storage for Lock List (4KB)
Enter the maximum storage for lock list value or accept the default.
 

WebSphere Commerce Panel

This panel is used to configure the tablespace and users that are needed by WebSphere Commerce upon instance creation.


 Full path to datafile
Enter the path to where the Oracle data file should be created upon creation of the WebSphere Commerce tablespace. 

For local database configuration, this field refers to a local path in the current database server where the Database Configurator is running.

For remote database configuration, note that this refers to a path in the remote database Server.  For instance, if the Database Configurator is running on a Windows client, and the database resides on a Unix Server, then the path to the datafile could be something like /usr/oracle/<tablespace_name>. Furthermore, this path does not necessarily have to be accessible from the client.  The information entered in this field is used by Oracle when attempting to create the tablespace(s) in the remote system.

Tablespace Name
Enter name of the WebSphere Commerce tablespace or accept the default.

Tablespace Size (MB)
Enter the initial tablespace size or accept the default.

User ID
Enter name of the user who will create the tablespace. Note that this user must have administrative privileges.

Password
Enter the password that is associated with the above user ID.

Temporary Tablespace
Enter the name of the temporary tablespace used by Oracle or accept the default.

 

Application Server Panel

This panel is used to configure the tablespace and users needed by WebSphere Application Server upon instance creation.

Note: The user may optionally choose to configure the WebSphere Application Server environment, for which a selection box is provided in the top left corner of the screen.


 Full path to datafile
Enter the path to where the Oracle data file should be created upon creation of the WebSphere Application Server tablespace. 

For local database configuration, this field refers to a local path in the current database server where the Database Configurator is running.

For remote database configuration, note that this refers to a path in the remote database Server.  For instance, if the Database Configurator is running on a Windows client, and the database resides on a Unix Server, then the path to the datafile could be something like /usr/oracle/<tablespace_name>. Furthermore, this path does not necessarily have to be accessible from the client.  The information entered in this field is used by Oracle when attempting to create the tablespace(s) in the remote system.


Tablespace Name
Enter name of the WebSphere Commerce tablespace or accept the default.

Tablespace Size (MB)
Enter the initial tablespace size or accept the default.

Ejs Admin User ID
Enter name of the ejs user who will create the tablespace. Note that this user must have administrative privileges.

Ejs Admin Password
Enter the password that is associated with the Ejs Admin ID.

Optional: Select this check box if you wish to create an EJB User for later use with WebSphere Application Server.  If selected, the following fields must be populated:

Ejb User ID
Enter name of the ejb user to create.

Ejb User Password
Enter the password that is associated with the above user ID.

 

Payment Manager Panel

This panel is used to configure the tablespace and users needed by WebSphere Commerce upon instance creation.


 Full path to datafile
Enter the path to where the Oracle data file should be created upon creation of the Payment Manager tablespace. 

For local database configuration, this field refers to a local path in the current database server where the Database Configurator is running.

For remote database configuration, note that this refers to a path in the remote database Server.  For instance, if the Database Configurator is running on a Windows client, and the database resides on a Unix Server, then the path to the datafile could be something like /usr/oracle/<tablespace_name>. Furthermore, this path does not necessarily have to be accessible from the client.  The information entered in this field is used by Oracle when attempting to create the tablespace(s) in the remote system.


Tablespace Name
Enter name of the WebSphere Commerce tablespace or accept the default.

Tablespace Size (MB)
Enter the initial tablespace size or accept the default.

Payment Manager User ID
Enter name of the user who will create the tablespace. Note that this user must have administrative privileges.

Password
Enter the password that is associated with the above user ID.

Temporary Tablespace
Enter the name of the temporary tablespace used by Oracle or accept the default.

Uninstalling Database Configurator

Uninstallation Instructions

Uninstalling on the Windows platforms:

  1. Select Start --> Program Files --> {IBM WebSphere Commerce Server Folder } --> System Tools --> Database Configurator
  2. Select Uninstall Database Configurator.
  3. Following the uninstall process to remove the program.
  1. From a command prompt, navigate to the directory where the Database Configurator is installed. For example, C:\Program Files\Database Configurator\_uninst\.
  2. Type the following command:
    java -jar uninstall.jar
  3. Remove the installation file structure, since there a few files left on the file system after the uninstall process. An example could be :

    cd C:\Program files\
    rm -r DatabaseConfigurator

Uninstalling on the AIX platform:

  1. Navigate to the installation directory:

    cd /opt/DatabaseConfigurator

  2. Type the following command to remove the files:

    cd _uninst
    ./uninstall-pd-aix.sh

  3. Follow the steps of the uninstall to remove the programs.

Uninstalling on the Solaris platform:

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

Any reference to an IBM licensed program in this publication is not intended to state or imply that only IBM’s licensed program may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM’s intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user’s responsibility.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504–1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION ″AS IS″.WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.  Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Canada Ltd.
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
Canada

Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer

Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

Credit card images, trademarks and trade names provided in this product should be used only by merchants authorized by the credit card mark’s owner to accept payment via that credit card.

Trademarks and Service Marks

The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both:

WebSphere                             DB2                     DB2 Extenders

DB2 Universal Database         VisualAge             IBM SecureWay

Domino is a trademark of Lotus Development Corporation.

Microsoft, IIS, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.

Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries.

Oracle is a registered trademark and Oracle8i is a trademark of Oracle Corporation.

Pentium is a trademark of Intel Corporation in the United States, other countries, or both.

JDK, JDBC, Java, HotJava and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a registered trademark of Linus Torvalds.

Other company, product or service names may be the trademarks or service marks of others.

 
**************************************************************************

** © COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001

** ALL RIGHTS RESERVED.

**************************************************************************

Note to US Government Users -- Documentation related to restricted rights -- Use, duplication, or disclosure is subject to restriction set forth in GSA ADP Schedule Contract with IBM Corp.

End of Database Configurator README File