8. Conventions and terminology used in this book
This book uses the following highlighting conventions:
Boldface type Indicates commands or graphical user interface (GUI) controls
such as names of fields, icons, or menu choices.
Monospace type Indicates examples of text you enter exactly as shown, file names,
and directory paths and names.
Italic type Used to emphasize words. Italics also indicate names for which
you must substitute the appropriate values for your system.
host_name The fully qualified host name of the WebSphere Commerce
development environmentsystem (for example,
server1.torolab.ibm.com is fully qualified).
This icon marks a Tip - additional information that can help you
complete a task.
Important
These sections highlight especially important information.
Attention
These sections highlight information intended to protect your data.
2000
Enterprise Indicates information specific to WebSphere Commerce Developer Enterprise
2000
Professional Indicates information specific to WebSphere Commerce Developer Professional
Cloudscape Indicates information specific to IBM Cloudscape database.
2000
DB2 All references to DB2 Universal Database™ in this book refer to the edition of DB2
Universal Database supported by the edition of WebSphere Commerce Developer
you are using.
If you are using WebSphere Commerce Developer Enterprise or Profession
edition, DB2 Universal Database Enterprise Server Edition is supported.
Oracle
2000 Indicates information specific to Oracle9i Database.
Indicates information specific to Oracle10g Database
This book uses the following terms:
back-office business logic
The part of your store that customers do not see. Back-office business logic
includes WebSphere Commerce commands, data beans, enterprise beans
development machine
The machine onto which you install WebSphere Commerce Developer to
develop store-front assets or back-office business logic for WebSphere
Commerce.
vi WebSphere Commerce Developer Installation Guide
9. store-front assets
The part of your store with which your customers interact. Store-front
assets include HTML pages, JSP files, style sheets, images, graphics, and
other multimedia file types that define the layout and content of your Web
pages.
Path variables
This guide uses the following variables to represent directory paths:
WCDE_installdir
This is the installation directory for the WebSphere Commerce toolkit. The
default installation directory for the WebSphere Commerce toolkit, depends
on your edition of WebSphere Commerce Developer:
2000
Enterprise C:WCToolkitEE60
2000
Professional C:WCToolkitPro60
| Important: Long installation paths can cause errors with some WebSphere
| Commerce additional software. You should use a short directory name
| such as C:WCToolkit60.
RAD_installdir
This is the installation directory for Rational® Application Developer. The
default installation directory for Rational Application Developer is
C:Program FilesIBMRationalApplication Developer.
| Important: This default installation path is too long for configuration with
| some WebSphere Commerce additional software. You should use a short
| directory name such as C:RAD601.
Knowledge requirements
This book should be read by developers or system administrators who are
installing WebSphere Commerce Developer to develop store-front assets and
back-office business logic to run with WebSphere Commerce.
Developers or system administrators who are installing and configuring
WebSphere Commerce Developer should have knowledge in the following areas:
v Knowledge of one of the following operating systems:
– Microsoft® Windows® 2000 Professional Edition
– Microsoft Windows 2000 Server Edition
– Microsoft Windows 2000 Advanced Server Edition
– Microsoft Windows XP Professional
v 2000
Enterprise IBM DB2® Universal Database, IBM DB2 Universal Database
2000
Professional
®
for iSeries , or Oracle database
v Cloudscape Database
v Basic SQL commands
This knowledge should include how to complete administration and configuration
tasks for the operating system and database server.
Preface vii
10. | Obtaining WebSphere Commerce software
| WebSphere Commerce software media is obtained through the IBM Passport
| Advantage® Web site. Through this Web site, you can either download media
| images or order physical media (CDs).
| For instruction on obtaining WebSphere Commerce software, refer to Downloading
| WebSphere Commerce media images.
viii WebSphere Commerce Developer Installation Guide
26. Step 7. Obtain and apply the most recent WebSphere Commerce Developer fix
pack.
Important
Ensure that WebSphere Commerce Developer and WebSphere
Commerce are at the same fix pack level. If you apply a fix pack to
WebSphere Commerce Developer, apply the same fix pack level to
WebSphere Commerce. For example, if you apply WebSphere
Commerce Developer fix pack 6.0.1 to WebSphere Commerce
Developer, you must apply WebSphere Commerce fix pack 6.0.1 to
WebSphere Commerce.
WebSphere Commerce Developer fix packs are available from
theWebSphere Commerce Developer support Web site.
Instructions for applying the fix pack are provided with the fix pack at the
WebSphere Commerce Developer support Web site.
16 WebSphere Commerce Developer Installation Guide
32. – If errors appear in the log, examine the WCDE_installdir/bin/setenv.bat
file. Ensure that the RAD_HOME environment variable points to the
correct Rational Application Developer installation location, and that the
WED_HOME environment variable points to the correct IBM Sales Center
for WebSphere Commerce location.
– Check that the install was able to properly detect Rational Application
Developer on your system by ensuring that WCDE_installdir/bin/
setenv.bat sets the RAD_HOME environment variable to RAD_installdir
correctly.
Complete a Silent installation of the WebSphere Commerce toolkit
v To complete a silent installation of the WebSphere Commerce toolkit, complete
the following steps:
1. Depending on the location of your WebSphere Application Server CD image,
complete one of the following:
– Insert WebSphere Commerce Developer CD in the CD-ROM of the
Rational Application Developer machine.
The WebSphere Commerce toolkit installation wizard should start
automatically. Exit the installation and copy the responsefile.txt of the CD
to a temporary directory.
Navigate to the location of the WebSphere Commerce Developer response
file.
– Navigate to the location of the WebSphere Commerce Developer response
file on the machine where you have Rational Application Developer
installed.
2. Open the responsefile.txt file in a text editor.
3. Modify the entries in the responsefile.txt to match the desired installation
options.
4. Run the following command from the location of the CD image to start the
silent installation process:
silentsetup.exe -silent -options temp_dir/responsefile.txt
5. Ensure that the install was successful by doing the following:
– Examine the contents of WCDE_installdir/logs/wc_toolkit.log. Ensure
that the CWXAI7782S: WebSphere Commerce Developer edition
installation complete message appears at the end of the wc_toolkit.log.
Note: If wc_toolkit.log is not located in the WCDE_installdir/logs
directory, the file found can be found in the user temp location. For
example:
C:Documents and SettingsAdministratorLocal SettingsTemp
wc_toolkit.log
– If you have installed the IBM Sales Center development environment
component examine the contents of the WCDE_installdir/logs/
setupmsc.log for errors.
– If errors appear in the log, examine the WCDE_installdir/bin/setenv.bat
file. Ensure that the RAD_HOME environment variable points to the
correct Rational Application Developer installation location, and that the
WED_HOME environment variable points to the correct IBM Sales Center
for WebSphere Commerce location.
You now have a fully functioning WebSphere Commerce development
environment installed.
22 WebSphere Commerce Developer Installation Guide
36. Configuring the development environment to use DB2 Universal
Database
Important
The instructions in this section do not apply to using DB2 Universal Database
for iSeries as the development database.
If you want to configure the development environment to use DB2 Universal
Database for iSeries, refer to “Configuring the development environment to
use DB2 Universal Database for iSeries” on page 30.
The initial installation of WebSphere Commerce Developer provides a WebSphere
Commerce development environment that uses IBM Cloudscape as the WebSphere
Commerce database.
You should reconfigure the development environment to use DB2 Universal
Database if any of the following statements apply to your development needs:
v You are developing enterprise beans that require you to write database specific
SQL.
v You are making significant changes to the database schema
You can use either local or remote DB2 Universal Database.
Prerequisites
v You have installed Rational Application Developer with the IBM WebSphere
Application Server, Version 6.0.2.5 Test Environment.
v You have applied the required fixes to Rational Application Developer as
documented in “Applying fixes to Rational Application Developer” on page 17
v You have applied the required fixes to IBM WebSphere Application Server,
Version 6.0.2.5 Test Environment as documented in “Applying fixes to the
WebSphere Application Server Test Environment” on page 19.
v 2000
Enterprise Professional You have one of the following versions of DB2 Universal
2000
Database installed or a local or remote Windows machine:
– IBM DB2 Universal Database Enterprise Server Edition Version 8.1.5
– IBM DB2 Universal Database Enterprise Server Edition Version 8.2.3
Ensure the Application Development Tools component is installed.
v If you are using a remote DB2 Universal Database database server, you have
installed the DB2 Universal Database Administration Client on the WebSphere
Commerce development environment machine.
26 WebSphere Commerce Developer Installation Guide
37. v You have the following information gathered about your database server:
Local DB2 Universal Database Remote DB2 Universal Database
v The root directory of DB2 Universal v The root directory of the DB2 Universal
Database Database client
For example, C:SQLLIB For example, C:SQLLIB
v The database administrator ID v The database administrator ID
v The database administrator password v The database administrator password
v The database user ID (schema owner ID) v The database user ID (schema owner ID)
v The database user password v The database user password
v The fully qualified host name of the
database server
v The port number on the database server
used for remote connections
v The node name of the remote database
Procedure
To configure the development environment to use DB2 Universal Database, do the
following:
1. Ensure that IBM Rational Application Developer 6.0.1.1 is not running.
2. If you are using a remote a WebSphere Commerce, Version 6.0 development
database, complete one of the following steps:
v If you are creating a new remote WebSphere Commerce, Version 6.0
development database, the database is catalogued for you automatically.
v If you have an existing, remote WebSphere Commerce, Version 6.0
development database that you want to use, do the following on your
WebSphere Commerce Developer machine the first time you switch to the
existing database:
a. Catalog the remote database node.
b. Catalog the remote database.
For information on how to catalog a remote database node and how to
catalog a remote database, refer to the “Catalog Database command” help
file in the DB2 Information Center.
Once a remote database node and a remote database are cataloged on
machine, they will not have to be cataloged again. You can switch to the
cataloged remote database without repeating this step.
3. Start a Windows command prompt session.
4. Switch directories to the WCDE_installdir/bin directory.
5. Do one of the following steps:
If this is the first time you are configuring the development environment to
use DB2 Universal Database and you are not using an existing WebSphere
Commerce, Version 6.0 development database:
Issue the following command:
setdbtype db2 DB2_HOME dbName dbAdminID dbAdminPassword dbUserID
dbUserPassword [dbHost dbServerPort dbNode] [createdb]
where the command parameters are defined as follows:
Changing the development database 27
38. DB2_HOME
The root directory of DB2 Universal Database or the DB2
Universal Database client, depending on if you are using a local
or remote database.
For example, C:SQLLIB.
dbName
The name of the database you want to use with WebSphere
Commerce Developer.
If this is the first time you are switching database, this is the
name you want to give the database that will be created in the
next step.
dbAdminID
The database administrator ID.
dbAdminPassword
The database administrator password.
dbUserID
The database user ID (schema owner).
dbUserPassword
The database user password.
dbHost Remote database only The fully qualified host name of the
database server.
dbServerPort
Remote database only The port number on the database server
used for remote connections. The default port is 50000.
dbNode
Remote database only The node name of the remote database.
This command creates and populates the DB2 Universal Database
development database and switches the development database to this
new database.
If you want to switch to an existing, DB2 Universal Database development
database:
Issue the following command:
setdbtype db2 DB2_HOME dbName dbAdminID dbAdminPassword dbUserID
dbUserPassword [dbHost dbServerPort dbNode]
where the command parameters are defined as follows:
DB2_HOME
The root directory of DB2 Universal Database or the DB2
Universal Database client, depending on if you are using a local
or remote database.
For example, C:SQLLIB.
dbName
The name of the database you want to use with WebSphere
Commerce Developer.
If this is the first time you are switching database, this is the
name you want to give the database that will be created in the
next step.
28 WebSphere Commerce Developer Installation Guide
39. dbAdminID
The database administrator ID.
dbAdminPassword
The database administrator password.
dbUserID
The database user ID (schema owner).
dbUserPassword
The database user password.
dbHost Remote database only The fully qualified host name of the
database server.
dbServerPort
Remote database only The port number on the database server
used for remote connections.
dbNode
Remote database only The node name of the remote database.
This command switches the development database to the existing
development database.
6. Restart your WebSphere Commerce server. To restart the WebSphere Commerce
server, refer to “Starting and stopping WebSphere Commerce” on page 51.
7. Run the following commands from your WCDE_home/bin if you want to reset the
Stores project:
resetstores.bat
Note: If you run these commands you will not be able to properly use the
existing stores if you decide to switch back to the Cloudscape database.
The WebSphere Commerce development environment is now configured to use
DB2 Universal Database as its database.
All data in the Cloudscape database remains unchanged until you return to using
Cloudscape as the development database unless you run the resetdb.bat or
resetstores.bat commands. If you run these commands your Cloudscape
database is reset and cleaned.
+ Note: If you run the resetdb.bat command after you have applied a WebSphere
+ Commerce fix pack, you must run the updatedb.bat command to bring that
+ database back to the appropriate level. For instructions on running the
+ updatedb.bat command refer to the appropriate WebSphere Commerce fix
+ pack installation guide.
Notes:
1. The DB2 Universal Database development database does not come with all
starter stores published, unless you are connecting to an existing DB2 Universal
Database development database. You must run the resetstores.bat file before
publishing any of the starter stores. You must publish any starter stores you
want to work using the WebSphere Commerce Administration Console. For
more information on publishing starter stores, refer to the WebSphere
Commerce Information Center.
+ 2. If you had enabled any WebSphere Commerce features on your previous
+ database, you need to enable the features again. Refer to enabling features.
Changing the development database 29
40. Configuring the development environment to use DB2 Universal
Database for iSeries
The initial installation of WebSphere Commerce Developer provides a WebSphere
Commerce development environment that uses IBM Cloudscape as the WebSphere
Commerce database.
You should reconfigure the development environment to use DB2 Universal
Database for iSeries if any of the following statements apply to your development
needs:
v You want to run your development database on an iSeries machine.
v You are developing enterprise beans that require you to write database specific
SQL.
v You are making significant changes to the database schema
DB2 Universal Database for iSeries will be running on a machine remote from your
WebSphere Commerce development environment machine.
Prerequisites
v You have installed Rational Application Developer with the IBM WebSphere
Application Server, Version 6.0.2.5 Test Environment.
v You have applied the required fixes to Rational Application Developer as
documented in “Applying fixes to Rational Application Developer” on page 17
v You have applied the required fixes to IBM WebSphere Application Server,
Version 6.0.2.5 Test Environment as documented in “Applying fixes to the
WebSphere Application Server Test Environment” on page 19.
v Your iSeries machine is running one of the following database management
systems:
– DB2 Universal Database for iSeries V5R3 (provided with i5/OS® V5R3)
– DB2 Universal Database for iSeries V5R4 (provided with i5/OS V5R4)
v You have the following information gathered about your database server:
– The relational database name in which the WebSphere Commerce
development environment database tables should be created
– The database user profile used to access the database
– The password for the user profile
– The fully qualified host name of the database server
Procedure
To configure the development environment to use DB2 Universal Database for
iSeries, do the following:
1. Ensure that the iSeries user profile uses the localized settings for a language as
listed in the table below.
Table 1. Localized settings for iSeries user profiles
Language CCSID LangID CountryID
English 37 ENU US
French 297 FRA FR
German 273 DEU DE
Italian 280 ITA IT
30 WebSphere Commerce Developer Installation Guide
41. Table 1. Localized settings for iSeries user profiles (continued)
Language CCSID LangID CountryID
Spanish 284 ESP ES
Brazilian Portuguese 37 PTB BR
Japanese 5035 JPN JP
Korean 933 KOR KR
Traditional Chinese 937 CHT TW
Simplified Chinese 935 CHS CN
Important: Using localized settings for an iSeries user profile other than those
defined above might work, but has not been tested.
2. Ensure that Rational Application Developer is not running.
3. Start a Windows command prompt session.
4. Switch directories to the WCDE_installdir/bin directory.
5. Do one of the following steps:
If this is the first time you are configuring the development environment to
use DB2 Universal Database for iSeries and you are not using an existing
WebSphere Commerce, Version 6.0 development database
Issue the following command:
setdbtype iseries dbName dbHost dbUserID dbUserPassword createdb
where the command parameters are defined as follows:
dbName
The name of the relational database you want to use with
WebSphere Commerce Developer.
dbHost The fully qualified host name of the remote iSeries database
server.
dbUserID
The database user profile used to access the database.
dbUserPassword
The password for the user profile.
This command creates and populates the DB2 Universal Database for
iSeries development database and switches the development database
to this new database.
If you want to switch to an existing, DB2 Universal Database for iSeries
development database
Issue the following command:
setdbtype iseries dbName dbHost dbUserID dbUserPassword
where the command parameters are defined as follows:
dbName
The name of the database you want to use with WebSphere
Commerce Developer.
dbHost The fully qualified host name of the remote iSeries database
server.
Changing the development database 31
42. dbUserID
The database user profile used to access the database.
dbUserPassword
The password for the user profile.
This command switches the development database to the existing
development database.
6. Restart your WebSphere Commerce server. To restart the WebSphere Commerce
server, refer to “Starting and stopping WebSphere Commerce” on page 51.
7. Run the following commands from your WCDE_home/bin if you want to reset the
Stores project:
resetstores.bat
Note: If you run these commands you will not be able to properly use the
existing stores if you decide to switch back to the Cloudscape database.
The WebSphere Commerce development environment is now configured to use
DB2 Universal Database for iSeries as its database.
Notes:
1. The new DB2 Universal Database for iSeries development database does not
come with all starter stores published. You must run the resetstores.bat file
before publishing any of the starter stores. You must publish any starter stores
you want to work using the WebSphere Commerce Administration Console. For
more information on publishing starter stores, refer to the WebSphere
Commerce Information Center.
+ 2. If you had enabled any WebSphere Commerce features on your previous
+ database, you need to enable the features again. Refer to enabling features.
Configuring the development environment to use Oracle Database
The initial installation of WebSphere Commerce Developer provides a WebSphere
Commerce development environment that uses IBM Cloudscape as the WebSphere
Commerce database.
You should reconfigure the development environment to use Oracle Database if
any of the following statements apply to your development needs:
v You are developing enterprise beans that require you to write database specific
SQL.
v You are making significant changes to the database schema
Prerequisites
v You have installed Rational Application Developer with the IBM WebSphere
Application Server, Version 6.0.2.5 Test Environment.
v If you plan to use the full WebSphere Commerce test environment, you have
applied the required fixes to Rational Application Developer as documented in
“Applying fixes to the WebSphere Application Server Test Environment” on
page 19.
v You have installed the WebSphere Commerce toolkit and have a test
environment.
v You have installed Oracle Database on a local or remote Windows machine. The
following table lists the components you should install for a local and a remote
Windows machine:
32 WebSphere Commerce Developer Installation Guide
43. Local Oracle Database Remote Oracle Database
v Oracle Database Database server machine
v Oracle Net Services v Oracle Database
v Oracle Net Protocol Support v Oracle Net Services
v SQL*Plus v Oracle JDBC/OCI Interfaces
v Oracle JDBC/OCI Interfaces
WebSphere Commerce Developer
machine
v Oracle Enterprise Client
v SQL*Plus
v Oracle JDBC/Thin Interfaces
v Oracle JDBC/OCI Interfaces
v Oracle Network Utilities
v Oracle Database Utilities
Ensure that the Oracle client and server are
configured to communicate correctly
according to instructions found in the
Oracle Database Database documentation.
For instructions on installing these components, refer to your Oracle Database
documentation.
v You have created a new Oracle user ID and an empty database. Ensure that the
database uses the UTF-8 character set and that the Oracle user ID has access to
the new database.
For instructions on creating a database, refer to your Oracle Database
documentation.
The Oracle user ID must not be a reserved user ID like SYSTEM or SYS.
v You have set the Oracle open_cursors configuration parameter to 1000 or higher.
The installation default value of open_cursors is 300. If you do not set the
open_cursors value to 1000 or higher, you might receive error messages.
You must restart Oracle after changing the open_cursors value.
v You have gathered the following information about Oracle Database:
Local Oracle Database Remote Oracle Database
v The root directory of Oracle Database v The root directory of Oracle Database
For example, C:ORACLEORA client
v The name of the database For example, C:ORACLEORA
v The database administrator ID v The name of the remote database
v The database administrator password v The name of the local net service for the
remote database
v The database user ID
v The database administrator ID
v The database user password
v The database administrator password
v The database user ID
v The database user password
v The fully qualified host name of the
database server
v The port number on the database server
used for remote connections
Procedure
Changing the development database 33
44. To configure the development environment to use Oracle Database, do the
following:
1. Ensure that Rational Application Developer is not running.
2. Start a Windows command prompt session.
3. Switch directories to the WCDE_installdir/bin directory.
4. Do one of the following steps:
If this is the first time you are configuring the development environment to
use Oracle Database and you are not using an existing WebSphere
Commerce, Version 6.0 development database
Issue the following command:
setdbtype oracle ORACLE_HOME dbName dbAdminID dbAdminPassword dbUserID
dbUserPassword [dbHost dbServerPort] createdb
where the command parameters are defined as follows:
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:ORACLEORA92.
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 used ID or this
command will fail. Examples of reserved Oracle IDs
include SYSTEM and SYS.
dbUserPassword
The database user password.
dbHost Remote database only The fully qualified host name of the
database server.
dbServerPort
Remote database only The port number on the database server
used for remote connections.
This command connects to your Oracle development database and
creates and populates a WebSphere Commerce schema. It then
configures the development environment to use this new schema.
If you want to switch to an existing Oracle development schema
Issue the following command:
setdbtype oracle ORACLE_HOME dbName dbAdminID dbAdminPassword dbUserID
dbUserPassword [dbHost dbServerPort]
34 WebSphere Commerce Developer Installation Guide
45. where the command parameters are defined as follows:
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:ORACLEORA92.
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 used ID or this
command will fail. Examples of reserved Oracle IDs
include SYSTEM and SYS.
dbUserPassword
The database user password.
dbHost Remote database only The fully qualified host name of the
database server.
dbServerPort
Remote database only The port number on the database server
used for remote connections.
This command configures the development environment to use the
existing development WebSphere Commerce schema.
5. Restart your WebSphere Commerce server. To restart the WebSphere Commerce
server, refer to “Starting and stopping WebSphere Commerce” on page 51.
6. Run the following command from your WCDE_home/bin if you want to reset the
Stores project:
resetstores.bat
Note: If you run these commands you will not be able to properly use the
existing stores if you decide to switch back to the Cloudscape database.
The WebSphere Commerce development environment is now configured to use
Oracle Database as its database.
All data in the Cloudscape database remains unchanged until you return to using
Cloudscape as the development database unless you run the resetdb.bat or
resetstores.bat commands. If you run these commands your Cloudscape
database is reset and cleaned.
Notes:
+ 1. If you run the resetdb.bat command after you have applied a WebSphere
+ Commerce fix pack, you must run the updatedb.bat command to bring that
Changing the development database 35
46. + database back to the appropriate level. For instructions on running the
+ updatedb.bat command refer to the appropriate WebSphere Commerce fix pack
+ installation guide.
2. The new Oracle Database development database does not come with all starter
stores published. You must run the resetstores.bat file before publishing any of
the starter stores. You must publish any starter stores you want to work using
the WebSphere Commerce Administration Console. For more information on
publishing starter stores, refer to the WebSphere Commerce Information Center.
+ 3. If you had enabled any WebSphere Commerce features on your previous
+ database, you need to enable the features again. Refer to enabling features.
Configuring the development environment to use Cloudscape
If you are using DB2 Universal Database, DB2 Universal Database for iSeries, or
Oracle Database you can return to using Cloudscape as the development database.
Prerequisites
v The WebSphere Commerce development environment uses DB2 Universal
Database, DB2 Universal Database for iSeries, or Oracle Database for the
development database.
Procedure
To configure the development environment to use Cloudscape, do the following:
1. Ensure that Rational Application Developer is not running.
2. Start a Windows command prompt session.
3. Switch directories to the WCDE_installdir/bin directory.
4. Issue the following command:
setdbtype cloudscape
5. Restart your WebSphere Commerce server. To restart the WebSphere Commerce
server, refer to “Starting and stopping WebSphere Commerce” on page 51.
The WebSphere Commerce development environment is now configured to use
IBM Cloudscape as its database.
All data in the DB2 Universal Database, DB2 Universal Database for iSeries, or
Oracle Database database remains unchanged until you return to using the DB2
Universal Database, DB2 Universal Database for iSeries, or Oracle Database
database as the development database.
36 WebSphere Commerce Developer Installation Guide
48. v Scope changes to the WebSphere Commerce application server by selecting
Server from list of available scopes.
You cannot scope any changes to the WebSphere Commerce application
server by entering the name of the WebSphere Commerce application server
in the Server field as this field is unavailable when the WebSphere
Application Server Administrative Console runs in the WebSphere Commerce
test environment.
v Update the listener for WebSphere MQ server. To update the listener,
complete the following steps:
a. Open the WebSphere Commerce configuration file in a text editor. For
example:
WCDE_installdir/xml/config/wc-server.xml
b. Search for “Listener for WebSphere MQ”.
c. Update the Enable field from false to true.
d. Save the file and exit.
IBM WebSphere InterChange Server
2000
Enterprise
Prerequisites:
v You have installed the WebSphere Commerce development environment.
Procedure:
To use IBM WebSphere InterChange Server (formerly IBM CrossWorlds) with
WebSphere Commerce Developer, do the following:
v Follow the instructions found in WebSphere Commerce Additional Software Guide
with the following changes:
– Replace all occurrences of WC_installdir with WCDE_installdir.
– When tasks refer to the WebSphere Commerce machine, use the WebSphere
Commerce Developer machine.
– Launch the administration console from within WebSphere Commerce
Developer by following the instructions in “Starting the WebSphere
Application Server Administrative Console in the WebSphere Commerce
development environment” on page 52 instead of opening the WebSphere
Application Server Administrative Console.
– Complete the following steps:
1. Open the WebSphere Commerce configuration file in a text editor. For
example:
WCDE_installdir/xml/config/wc-server.xml
2. Search for CWSAI.
3. Complete the fields as described in the WebSphere Commerce Additional
Software Guide.
– Scope changes to the WebSphere Commerce application server by selecting
Server from list of available scopes.
You cannot scope any changes to the WebSphere Commerce application
server by entering the name of the WebSphere Commerce application server
in the Server field as this field is unavailable when the WebSphere
Application Server Administrative Console runs in the WebSphere Commerce
test environment.
38 WebSphere Commerce Developer Installation Guide
49. | Adding IBM Sales Center development environment to an existing
| WebSphere Commerce Developer
If you plan to add the IBM Sales Center development environment to an existing
copy of WebSphere Commerce Developer, complete the following steps:
| 1. You must preinstall IBM Sales Center for WebSphere Commerce. For more
| information refer to:
| Installing IBM Sales Center for WebSphere Commerce
| 2. Run the WebSphere Commerce Developer installation wizard, and select to
| install the IBM Sales Center development environment as described in
| “Installing the WebSphere Commerce toolkit” on page 21.
3. Open the following file in a text editor:
WCDE_installdir/bin/setenv.bat
4. Ensure that the RAD_HOME environment variable points to the correct
Rational Application Developer installation location
5. Ensure that the WED_HOME environment variable points to the correct IBM
Sales Center for WebSphere Commerce location.
6. Save the file and exit.
For information on launching the IBM Sales Center development environment,
refer to the Launching the IBM Sales Center development environment topic in the
WebSphere Commerce Information Center.
Installing the IBM Gift Center for WebSphere Commerce
Edition notice
The IBM Gift Center for WebSphere Commerce is supported by WebSphere
Commerce Developer Enterprise, and WebSphere Commerce Developer
Professional.
For instructions on how to enable the IBM Gift Center for WebSphere Commerce
on your WebSphere Commerce Developer Enterprise system, refer to the WebSphere
Commerce Additional Software Guide.
Configuring additional WebSphere Commerce software for WebSphere Commerce Developer 39
60. WCDE_installdir/bin/setenv.bat
2. Locate the line containing RAD_HOME and ensure that it points to the full path of
the Rational Application Developer (RAD_installdir).
3. Save any changes and exit the text editor
50 WebSphere Commerce Developer Installation Guide