wsc developer install

WebSphere Commerce Developer Enterprise Commerce Developer Professional

Version 6.0

Installation Guide

GC10-4255-06

WebSphere Commerce Developer Enterprise Commerce Developer Professional

Version 6.0

Installation Guide

GC10-4255-06

Note: Before using this information and the product it supports, be sure to read the general information under Notices on page 55.

Edition Notice This edition applies to Version 6.0 of the following editions of WebSphere Commerce Developer and to all subsequent releases and modifications until otherwise indicated in new editions: v IBM WebSphere Commerce Developer Enterprise (product number 5724i39) v IBM WebSphere Commerce Developer Professional (product number 5724i41) Ensure that you are using the correct edition for the level of the product. Order publications through your IBM representative or the IBM branch office serving your locality. IBM welcomes your comments. You can send your comments by using the online IBM WebSphere Commerce documentation feedback form. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1996, 2007. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

ContentsPreface . . . . . . . . . . . . . . . vAbout this book . . . . . . . . . . . . . v Document description . . . . . . . . . . v Updates to this book . . . . . . . . . . v Conventions and terminology used in this book vi Path variables . . . . . . . . . . . . vii Knowledge requirements . . . . . . . . . vii Obtaining WebSphere Commerce software. . . . viii Configuring the development environment to DB2 Universal Database . . . . . . . Configuring the development environment to DB2 Universal Database for iSeries . . . Configuring the development environment to Oracle Database . . . . . . . . . . Configuring the development environment to Cloudscape . . . . . . . . . . . use . . use . . use . . use . . . 26 . 30 . 32 . 36

|

Part 1. Welcome to WebSphere Commerce Developer . . . . . . . . 1Products included with WebSphere Commerce Developer . . . . . . . . . 3

Configuring additional WebSphere Commerce software for WebSphere Commerce Developer . . . . . . . . 37WebSphere Commerce business integration . . . . WebSphere MQ . . . . . . . . . . . . IBM WebSphere InterChange Server . . . . . Adding IBM Sales Center development environment to an existing WebSphere Commerce Developer . . Installing the IBM Gift Center for WebSphere Commerce . . . . . . . . . . . . . . . 37 37 38 39 39

Part 2. Planning your WebSphere Commerce Developer installation . . 5About WebSphere Commerce Developer 7 Migrating previous versions of WebSphere Commerce Developer

| |

Part 5. Uninstalling WebSphere Commerce Developer . . . . . . . 41Uninstalling the WebSphere Commerce toolkit . . . . . . . . . . . . . . . 43 Uninstalling Rational Application Developer . . . . . . . . . . . . . 45

. . . 9

Coexistence with previous versions of WebSphere Commerce Developer . . . 11 Pre-installation requirements . . . . . 13Prerequisite hardware . . . . . . Prerequisite software . . . . . . Network configuration requirements . . . . . . . . . . . . . . 13 . 13 . 13

Part 6. Appendixes. . . . . . . . . 47Appendix A. Troubleshooting your installation . . . . . . . . . . . . . 49Error message in the setup.log . . . . . . . Problems starting the WebSphere Commerce test server . . . . . . . . . . . . . . . WebSphere Commerce test server does not appear to start . . . . . . . . . . . . . . . The WebSphere Commerce development environment does not start . . . . . . . . . 49 . 49 . 49 . 49

Part 3. Installing WebSphere Commerce Developer . . . . . . . 15Applying fixes to Rational Application Developer . . . . . . . . . . . . . 17 Applying fixes to the WebSphere Application Server Test Environment. . 19 Installing the WebSphere Commerce toolkit . . . . . . . . . . . . . . . 21

Appendix B. WebSphere Commerce development environment tasks . . . . 51Starting WebSphere Commerce Developer . . Starting multiple instances of WebSphere Commerce Developer . . . . . . . . Starting IBM Sales Center development environment for WebSphere Commerce . . Starting and stopping WebSphere Commerce . Starting the WebSphere Commerce information center . . . . . . . . . . . . . . . . . . . . 51 . 51 . 51 . 51 . 52

Part 4. Configuring WebSphere Commerce Developer . . . . . . . 23Changing the development databaseDatabases supported by the test environment . .

25. 25

Copyright IBM Corp. 1996, 2007

iii

Enabling help access from the WebSphere Commerce tools in the development environment 52 Starting the WebSphere Application Server Administrative Console in the WebSphere Commerce development environment . . . . . 52

Notices . . . . . . . . . . . . . . 55 Trademarks. . . . . . . . . . . . . 59

iv

WebSphere Commerce Developer Installation Guide

PrefaceAbout this book Document descriptionThis installation guide describes how to install and configure the following products: v IBM WebSphere Commerce Developer Enterprise v IBM WebSphere Commerce Developer Professional It is intended for developers or system administrators who are using WebSphere Commerce Developer to develop store-front assets and back-office business logic to run with the following products: v WebSphere Commerce Enterprise v WebSphere Commerce Professional When developing for an edition of WebSphere Commerce, you must use the matching edition of WebSphere Commerce Developer. For example, when developing for WebSphere Commerce Professional, you must use WebSphere Commerce Developer Professional.

Updates to this bookUpdated versions of this book are available as PDF files from the IBM publications Web site.

Update historyThis section provides an outline of the history of changes to this book:Edition First edition, Fifth Revision First edition, Fourth Revision First edition, Third Revision First edition, Second Revision First edition, First Revision First edition Publication number GC10-4255-05 GC10-4255-04 Updates v Updates for WebSphere Commerce fix pack 3. v Added information on obtaining software. v Updates for WebSphere Commerce fix pack 2. GC10-4255-03 GC10-4255-02 v Minor updates to the Installing WebSphere Commerce Developer section. v Minor updates.

GC10-4255-01 GC10-4255-00

v Minor updates. v Original publication of this book.


v

Conventions and terminology used in this bookThis book uses the following highlighting conventions:Boldface type Monospace type Italic type host_name Indicates commands or graphical user interface (GUI) controls such as names of fields, icons, or menu choices. Indicates examples of text you enter exactly as shown, file names, and directory paths and names. Used to emphasize words. Italics also indicate names for which you must substitute the appropriate values for your system. 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.Indicates information specific to WebSphere Commerce Developer Enterprise Indicates information specific to WebSphere Commerce Developer Professional Indicates information specific to IBM Cloudscape database. 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

2000 Enterprise

Professional 2000

Cloudscape

2000 DB2

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


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 variablesThis 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 C:\WCToolkitPro60

Professional 2000

| | |

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 Files\IBM\Rational\Application 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 requirementsThis 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 IBM DB2 Universal Database, IBM DB2 Universal Database for iSeries , or Oracle database v Cloudscape Database v Basic SQL commands v2000 EnterpriseProfessional 2000

This knowledge should include how to complete administration and configuration tasks for the operating system and database server.

Preface

vii

| | | | | |

Obtaining WebSphere Commerce softwareWebSphere 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


Part 1. Welcome to WebSphere Commerce DeveloperThis book describes how to install and configure WebSphere Commerce Developer. It is intended for developers or system administrators who are using the WebSphere Commerce Developer to develop stores and WebSphere Commerce application code. If you are using WebSphere Commerce Developer Enterprise to create customized Java code, it can only be deployed to a WebSphere Commerce Enterprise application.2000 Enterprise

If you are using WebSphere Commerce Developer Professional to create customized Java code, it can only be deployed to a WebSphere Commerce Professional application.Professional 2000

For instructions on the installation and configuration of WebSphere Commerce, refer to WebSphere Commerce Installation Guide. WebSphere Commerce Developer should be installed on a separate machine from a WebSphere Commerce production or staging environment.


1

2


Products included with WebSphere Commerce DeveloperThe following products and components are packaged with WebSphere Commerce Developer: v Rational Application Developer Note: The WebSphere Commerce Developer package does not contain the full version of Rational Application Developer. The only options available are Rational Application Developer 6.0 WebSphere Application Server 6.0 Integrated Test Environments Remote Agent v WebSphere Commerce Version 6.0 toolkit v WebSphere Commerce, Version 6.0 WebSphere Commerce for Windows is included with WebSphere Commerce Developer for testing purposes. If you want to put your site into production using WebSphere Commerce, you must purchase a licensed copy of WebSphere Commerce. For a list of products and components provided with WebSphere Commerce, refer to WebSphere Commerce Installation Guide.


3

4


Part 2. Planning your WebSphere Commerce Developer installationThis section contains information on planning your installation of WebSphere Commerce Developer, including the prerequisites for WebSphere Commerce Developer.


5

6


About WebSphere Commerce DeveloperWebSphere Commerce Developer is the combination of Rational Application Developer and the WebSphere Commerce toolkit. The WebSphere Commerce toolkit provides a test environment, a workspace, and published starter stores in Rational Application Developer. The test environment and workspace are customized for WebSphere Commerce development. If you are developing assets for more than one target application, you might need to configure multiple WebSphere Commerce workspaces. To obtain multiple WebSphere Commerce workspaces, install the WebSphere Commerce toolkit multiple times.


7

8


Migrating previous versions of WebSphere Commerce DeveloperMigration to WebSphere Commerce Developer, Version 6.0 from the following versions of WebSphere Commerce Developer is supported: v WebSphere Commerce Developer Version 5.6.1 v WebSphere Commerce Developer Version 5.6 v WebSphere Commerce Studio Version 5.5 Migration from other versions of WebSphere Commerce Studio is not supported. For information on how to migrate to WebSphere Commerce Developer, Version 6.0 from previous versions of WebSphere Commerce, refer to the WebSphere Commerce Developer Migration Guide. The Migration Guides are available from the WebSphere Commerce technical library.


9

10


Coexistence with previous versions of WebSphere Commerce DeveloperWebSphere Commerce Developer, Version 6.0 can coexist on the same machine with the following previous versions of WebSphere Commerce Developer: v WebSphere Commerce Developer Version 5.6.1 v WebSphere Commerce Developer Version 5.6 v WebSphere Commerce Studio Version 5.5 Coexistence with other versions of WebSphere Commerce Studio is not supported. When installing WebSphere Commerce Developer, Version 6.0 in a coexistence environment, no additional steps are required to prepare for or complete an installation of WebSphere Commerce. Follow the instructions for installing WebSphere Commerce Developer, Version 6.0 in this book.


11

12


Pre-installation requirementsBefore installing WebSphere Commerce Developer, ensure that your machine meets the following hardware and software prerequisites.

Prerequisite hardwareEnsure that the machine on which you want to install WebSphere Commerce Developer meets the requirements listed in the IBM WebSphere Commerce Developer Version 6.0 Hardware prerequisites Technote #7007490.

Prerequisite softwareEnsure that the machine on which you want to install WebSphere Commerce Developer meets the requirements listed in IBM WebSphere Commerce Developer Version 6.0 Software prerequisites Technote #7007488.

Network configuration requirementsEnsure that the machine on which you want to install WebSphere Commerce Developer meets the requirements listed in IBM WebSphere Commerce Developer Version 6.0 Networking prerequisites Technote #7007489.


13

14


Part 3. Installing WebSphere Commerce DeveloperInstalling WebSphere Commerce Developer is a six-step process: Step 1. Ensure that your are logged on as user with Administrator privileges Step 2. Install Rational Application Developer. For instructions, refer to the Rational Application Developer 6.0 documentation.

Important installation instructions When installing Rational Application Developer 6.0 ensure that you do the following tasks: v Ensure that you are logged on as a user with Administrator privileges. v Do not accept the default installation path for Rational Application Developer 6.0. Specify a short directory name such as C:\RAD601. The default installation path is too long for configuration with the WebSphere Commerce toolkit. Also, avoid using periods (.), spaces, or dollar signs ($) in the directory names. v When prompted to select the features to install, ensure that you select WebSphere Application Server 6.0 Integrated Test Environments. v During the installation process you will see options to install software that does not ship with WebSphere Commerce Developer. WebSphere Commerce Developer does not ship a full set of Rational Application Developer CD images. The only options that are available for installation are: Rational Application Developer 6.0 WebSphere Application Server 6.0 Integrated Test Environments Remote Agent Step 3. Apply IBM Rational Application Developer 6.0.1.1 fixes. For instructions, refer to Applying fixes to Rational Application Developer on page 17. Step 4. If you plan to use the WebSphere Commerce development environment, you must apply WebSphere Application Server fixes to the WebSphere Application Server Test Environment in Rational Application Developer. For instruction, refer to Applying fixes to the WebSphere Application Server Test Environment on page 19. Step 5. If you plan to use the IBM Sales Center development environment, you must preinstall IBM Sales Center for WebSphere Commerce client. To install the IBM Sales Center client refer to the Installing IBM Sales Center for WebSphere Commerce topic in the WebSphere Commerce Information Center. Step 6. Install the WebSphere Commerce toolkit. For instructions, refer to Installing the WebSphere Commerce toolkit on page 21. Copyright IBM Corp. 1996, 2007

| | | | | | | |

| | | | |

15

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


Applying fixes to Rational Application DeveloperUpdate Rational Application Developer to the 6.0.1.1 level. To apply Rational Application Developer fixes complete the following steps: 1. Open the Rational Product Updater by selecting Start > Programs > IBM Rational > Rational Product Updater. 2. Select IBM Rational Application Developer and click Find Updates. 3. The updater detects all of the applicable fixes. Click Select All and click Install Updates. Note: If you have chosen to install the Remote Agent Controller, ensure that you apply the latest fixes that are available for the that component. 4. Accept the license agreement and click Finish. 5. Follow the prompts to install all of the updates. Note: Incremental updates might be required. To apply these updates the Rational Product Updater must be run multiple times.


17

18


Applying fixes to the WebSphere Application Server Test EnvironmentPrerequisites v The machine on which you are installing meets all prerequisites outlined in Pre-installation requirements on page 13. v You have installed IBM Rational Application Developer 6.0.1.1 with the WebSphere Application Server Version 6.0 Test Environment on the machine. v You have stopped any applications running on your machine. v You are logged on as a user with Administrator privileges. Procedure To apply WebSphere Application Server fixes to the WebSphere Application Server Version 6.0 Test Environment in Rational Application Developer, do the following: 1. Depending on the location of your WebSphere Application Server CD image, complete one of the following: v Insert the WebSphere Application Server CD Disk 2 from the WebSphere Commerce package provided with WebSphere Commerce Developer, into the CD-ROM drive of the machine where you have Rational Application Developer installed. v Navigate to the location of the WebSphere Application Server CD Disk 2 image on the machine where you have Rational Application Developer installed. 2. Prepare the update installation wizard as follows: a. Start a command prompt session. b. Do the following in the command prompt session: 1) Change directories to the \WAS\ directory on the CD image. 2) Issue the following command:install.exe

You can close the command prompt session at this point. c. Select the WebSphere Application Server that is used by Rational Application Developer. d. When prompted by the install wizard, select Apply maintenance and add features. e. Ensure that the following directory is selected to update:RAD_installdir/runtimes/base_v6

Click Next. 3. When the update installation wizard completes, click Finish. For the most current list of required maintenance, see the WebSphere Commerce Developer required maintenance Technote #1236356.


19

20


Installing the WebSphere Commerce toolkitPrerequisites v The machine on which you are installing meets all prerequisites outlined in Pre-installation requirements on page 13. v You have installed IBM Rational Application Developer 6.0.1.1 with the IBM WebSphere Application Server, Version 6.0.2.5 Test Environment on the machine. v You have stopped any applications running on your machine. v Disable any Web server that you have configured on your machine. v You are logged on as a user with Administrator privileges. v If you plan to use the IBM Sales Center development environment, you must preinstall IBM Sales Center client. Procedure To install the WebSphere Commerce toolkit, do the one of the following: v Complete a GUI installation of the WebSphere Commerce toolkit on page 21. v Complete a silent installation of the WebSphere Commerce toolkit on page 22. Complete a GUI installation of the WebSphere Commerce toolkit v To complete a GUI 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. If the WebSphere Commerce toolkit installation does not start automatically, run setup.exe on the root of the WebSphere Commerce Developer CD. Navigate to the location of the WebSphere Commerce Developer CD image on the machine where you have Rational Application Developer installed. From the root directory of the WebSphere Commerce Developer CD image, run the following command:setup.exe

| |

| | |

2. Follow the instructions on the panels and complete your installation. Important: Long installation paths can cause errors with some WebSphere Commerce additional software. You should use a short directory name such as C:\WCToolkit60. 3. Ensure that the install was successful by doing the following: Examine the contents of WCDE_installdir/logs/setup.log. If setup.log is empty or has errors, try running WCDE_installdir/bin/setup.bat from the command line. If you have installed the IBM Sales Center development environment component examine the contents of the WCDE_installdir/logs/ setupmsc.log for errors. Copyright IBM Corp. 1996, 2007

21

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 Settings\Administrator\Local Settings\Temp\ 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


Part 4. Configuring WebSphere Commerce DeveloperThe chapters in this section describe how to perform any of the optional configurations for WebSphere Commerce Developer beyond the initial configuration when you install WebSphere Commerce Developer. Topics covered in this section include: v Changing the development database on page 25 v Configuring additional WebSphere Commerce software for WebSphere Commerce Developer on page 37


23

24


Changing the development databaseThe initial configuration of the WebSphere Commerce development environment uses Cloudscape as the development database. However, you can switch to using DB2 Universal Database, DB2 Universal Database for iSeries, or Oracle Database as the development database. Consider the following guidelines when switching between database types: v If you are developing session beans or custom entity bean finders that have database-specific SQL statements, you should consider moving to using DB2 Universal Database, DB2 Universal Database for iSeries, or Oracle Database, as appropriate. The alternative is to code your session beans and custom finders to examine the useCloudscape, useDB2, useDB2_400, and useOracle methods of the BaseJDBCHelper class and then generate the database specific SQL statements. v The effort of maintaining code that will work with Cloudscape and your target database, must be weighed against the additional setup and configuration effort required in setting up development environments that works directly against the target database.

Important As you create a new database or switch your database using the setdbtype command, keep in mind that the Stores Web project assets can be impacted by this change. The Stores Web project contains a Struts configuration file which ties the store_id in the database to the JSP pages of your store. If your existing database does not have the same stores with the same store_id it is recommended that you make a copy of the WCDE_installdir/workspace/ Stores directory and save it with a reminder of which database it is assigned to. If required, restore this directory anytime that you switch the databases. If you are starting from a clean database and would like a clean Stores Web project, you can run the resetstores command. If this step is omitted, it might result in a incorrect Struts configuration file, causing routing errors while you navigate the store pages.

Databases supported by the test environmentFor more information on the databases supported by the WebSphere Commerce test environment, see Databases supported by the test environment Technote #7007559


25

Configuring the development environment to use DB2 Universal DatabaseImportant 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. v2000 Professional You have one of the following versions of DB2 Universal 2000 Enterprise 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


v You have the following information gathered about your database server:Local DB2 Universal Database v The root directory of DB2 Universal Database For example, C:\SQLLIB v The database administrator ID v The database administrator password v The database user password Remote DB2 Universal Database v The root directory of the DB2 Universal Database client For example, C:\SQLLIB v The database administrator ID v The database administrator 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

v The database user ID (schema owner ID) v The database user ID (schema owner ID)

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

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


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.

+ +


29

Configuring the development environment to use DB2 Universal Database for iSeriesThe 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 English French German Italian CCSID 37 297 273 280 LangID ENU FRA DEU ITA CountryID US FR DE IT

30


Table 1. Localized settings for iSeries user profiles (continued) Language Spanish CCSID 284 LangID ESP PTB JPN KOR CHT CHS CountryID ES BR JP KR TW CN

Brazilian Portuguese 37 Japanese Korean Traditional Chinese Simplified Chinese 5035 933 937 935

2. 3. 4. 5.

Important: Using localized settings for an iSeries user profile other than those defined above might work, but has not been tested. Ensure that Rational Application Developer is not running. Start a Windows command prompt session. Switch directories to the WCDE_installdir/bin directory. 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.


31

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 DatabaseThe 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


Local Oracle Database v Oracle Database v Oracle Net Services v Oracle Net Protocol Support v SQL*Plus v Oracle JDBC/OCI Interfaces

Remote Oracle Database Database server machine v Oracle Database v Oracle Net Services 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 v The root directory of Oracle Database For example, C:\ORACLE\ORA v The name of the database v The database administrator ID v The database administrator password v The database user ID v The database user password Remote Oracle Database v The root directory of Oracle Database client For example, C:\ORACLE\ORA v The name of the remote database v The name of the local net service for the remote database v The database administrator ID 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

ProcedureChanging the development database

33

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:\ORACLE\ORA92. 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


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:\ORACLE\ORA92. 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 thatChanging the development database

35

+ + +

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 CloudscapeIf 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. 2. 3. 4. Ensure that Rational Application Developer is not running. Start a Windows command prompt session. Switch directories to the WCDE_installdir/bin directory. 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


Configuring additional WebSphere Commerce software for WebSphere Commerce DeveloperWebSphere Commerce provides additional software packages that you might want to use in the WebSphere Commerce test environment. For more information on the additional software packages provided with WebSphere Commerce, refer to theWebSphere Commerce Additional Software Guide for the edition of WebSphere Commerce you have. Use the information in this section, along with the WebSphere Commerce Additional Software Guide for the appropriate edition of WebSphere Commerce, to install and configure the additional software packages for use with WebSphere Commerce Developer. In the following sections, refer to the Edition notice to see if the software discussed is supported by your edition of WebSphere Commerce Developer.

WebSphere Commerce business integrationThe business integration software packages, WebSphere MQ and IBM WebSphere InterChange Server, are not provided with either WebSphere Commerce or WebSphere Commerce Developer. They must be purchased separately.

WebSphere MQPrerequisites: v You have installed the WebSphere Commerce development environment. Procedure: To use WebSphere MQ (formerly MQSeries) with WebSphere Commerce Developer, do the following: 1. Follow the instructions found in WebSphere Commerce Additional Software Guide with the following changes: v For WebSphere MQ Version 5.3 If plan to use Client mode connections to your messaging server, ensure that you apply the fixes listed on the WebSphere MQ support Web site. Embedded messaging client Obtain and install the fixes found under WebSphere embedded messaging interim fixes for WebSphere Application Server V6.0. WebSphere MQ client Ensure that you are at CSD08 or later. You will need an IBM ID and password to access the fixes. If you do not have an IBM ID or password, click My IBM registration to obtain an ID and password. v 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. Copyright IBM Corp. 1996, 2007

37

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 Server2000 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


| |

Adding IBM Sales Center development environment to an existing WebSphere Commerce DeveloperIf 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 CommerceEdition 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

40


Part 5. Uninstalling WebSphere Commerce Developer


41

42


Uninstalling the WebSphere Commerce toolkitNote: Uninstallation of specific components of the WebSphere Commerce toolkit is not supported. The WebSphere Commerce toolkit uninstall will remove everything that is installed under the WebSphere Commerce toolkit installation directory. To uninstall the WebSphere Commerce toolkit, do the following: 1. Stop the WebSphere Commerce server. For instructions on stopping the WebSphere Commerce server, refer to Starting and stopping WebSphere Commerce on page 51. 2. Select Start > Settings > Control Panel > Add/Remove Programs 3. Click Change or Remove Programs. 4. Select one of the following, depending on the edition you have installed:2000 Enterprise

IBM WebSphere Commerce Developer Enterprise 6.0 IBM WebSphere Commerce Developer Professional 6.0

Professional 2000

5. Click Remove. The uninstall wizard starts. 6. Complete the uninstall wizard by following the prompts. The uninstall will only remove files that were originally installed. Files that were created or modified after the installation will not be removed. You must delete the WCDE_installdir directory once you have determined that you do not need any of the remaining files.

Uninstalling multiple toolkit installations When you have multiple WebSphere Commerce toolkit installations on the same machine, the entry in the Windows Add/Remove Programs panel only uninstalls the most recent WebSphere Commerce toolkit installation. To uninstall a specific WebSphere Commerce toolkit installation, you must issue the following command:WCDE_installdir/_uninst/uninstall

WCDE_installdir will be unique for each installation of the WebSphere Commerce toolkit on a machine.


43

44


Uninstalling Rational Application DeveloperBefore uninstalling Rational Application Developer, uninstall the WebSphere Commerce toolkit by following the instructions in Uninstalling the WebSphere Commerce toolkit on page 43. To uninstall Rational Application Developer, complete the following steps: 1. While logged on with a Windows user ID with Administrator authority, select Start > Settings > Control Panel > Add/Remove Programs. 2. Click Change or Remove Programs, select Rational Application Developer and click Change/Remove. The uninstall wizard starts. 3. Complete the uninstall wizard by following the prompts. 4. When the uninstall is complete, restart your machine. 5. Delete the following directories: v RAD_installdir where the default value for RAD_installdir is listed in Path variables on page vii.


45

46


Part 6. Appendixes


47

48


Appendix A. Troubleshooting your installationUse the information in this section to troubleshoot your installation of WebSphere Commerce Developer

Error message in the setup.logAfter the installation has completed, an error appears in the setup.log. For example:[addApplication] Application successfully added to the server, attempting to stop the server.

This error occurs when the installer has detect that the publish application process has taken too much time. This might not be an error. In order to verify if this is actually an error, you will need to examine the trace.log file in the WCDE_installdir/wasprofile/logs/server1 directory. If this file does not contain errors then this situation might be corrected by manually publishing the application through the Rational Application Developer. If there are errors in the trace.log file, then they must first be addressed before a publish can occur.

Problems starting the WebSphere Commerce test serverWhen starting the WebSphere Commerce test server, the console output does not appear. This is normal Rational Application Developer behavior. Rational Application Developer does not log any messages on the console until after the server has completed initialization. To follow the startup progress of the test server, examine the WCDE_installdir/wasprofile/logs/server1/trace.log file.

WebSphere Commerce test server does not appear to startThe WebSphere Commerce Test Server displays a status of starting... even though the WCDE_installdir/wasprofile/logs/server1/trace.log file stated that the server has started properly. There are some instances where the network configuration of a machine causes some problems in the RMI communication between Rational Application Developer and WebSphere Application Server. When this happens, Rational Application Developer might not be able to retrieve the proper status from the WebSphere Application Server test server. In order to fix this problem, you should change the communication protocol between the products from RMI to SOAP. This can be done in the WebSphere Commerce Test Server configuration editor.

The WebSphere Commerce development environment does not startIf the WebSphere Commerce development environment does not start, ensure that you have Rational Application Developer installed and that the RAD_HOME variable in the setenv.bat file is set to the full path to the Rational Application Developer. To correct the value for RAD_HOME, do the following: 1. Open the following the file in a text editor: Copyright IBM Corp. 1996, 2007

49

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


Appendix B. WebSphere Commerce development environment tasksStarting WebSphere Commerce DeveloperTo start the WebSphere Commerce development environment, do one of the following, depending on your edition of WebSphere Commerce Developer:2000 Enterprise

Select Start > Programs > IBM WebSphere Commerce Developer Enterprise 6.0 > WebSphere Commerce development environment Select Start > Programs > IBM WebSphere Commerce Developer Professional 6.0 > WebSphere Commerce development environment

Professional 2000

Starting multiple instances of WebSphere Commerce DeveloperIf you have the WebSphere Commerce toolkit installed multiple times, the entry in the Windows Start menu starts the most recent installation of the WebSphere Commerce toolkit. To start other installations of the WebSphere Commerce toolkit, issue the following command:WCDE_installdir/bin/startWCToolkit

WCDE_installdir will be unique for each installation of the WebSphere Commerce toolkit on a machine.

Starting IBM Sales Center development environment for WebSphere CommerceTo start the IBM Sales Center development environment, do one of the following: v To start the IBM Sales Center development environment, do one of the following, depending on your edition of WebSphere Commerce Developer2000 Enterprise

Select Start > Programs > IBM WebSphere Commerce Developer Enterprise 6.0 > IBM Sales Center development environment Select Start > Programs > IBM WebSphere Commerce Developer Professional 6.0 > IBM Sales Center development environment

Professional 2000

v Run the following command from a command line:WCDE_installdir/bin/startMSCToolkit.bat

Starting and stopping WebSphere CommercePrerequisites v The WebSphere Commerce development environment is running. For instructions on starting the WebSphere Commerce development environment, refer to Starting WebSphere Commerce Developer. Procedure


51

To start WebSphere Commerce within the WebSphere Commerce development environment, do the following: v In the Servers view, right-click one of the following, depending on the test environment you want to start: WebSphere Commerce Test Server v Select Start or Stop from the pop-up menu. v The WebSphere Commerce is started successfully if there are no errors in the Console view and the following message appears in the Console view:Server server1 open for e-business

Before accessing any of the WebSphere Commerce tools, ensure that you start the WebSphere Commerce help system by following the instructions in Starting the WebSphere Commerce information center.

Starting the WebSphere Commerce information centerThe help system starts automatically in the development environment. By default Rational Application Developer runs the Help Server on a random port. To start the help system in the WebSphere Commerce development environment, do the following: 1. Ensure that the WebSphere Commerce tools in the development environment can access the help system. For instruction on enabling help access from the WebSphere Commerce tools in the development environment, refer to Enabling help access from the WebSphere Commerce tools in the development environment. 2. Start the WebSphere Commerce development environment. For instructions on starting the WebSphere Commerce development environment, refer to Starting WebSphere Commerce Developer on page 51. 3. Start the help system by selecting Help > Help Contents in the WebSphere Commerce development environment.

Enabling help access from the WebSphere Commerce tools in the development environmentTo enable help to be accessed from the WebSphere Commerce Accelerator, Organization Administration Console, or the Administration Console, you must set the port that the help server uses to 8001, by doing the following: 1. Select Window > Preferences > Help > Help Server. 2. In the Port for the server to listen on field, type 8001. 3. Click Apply. 4. Restart Rational Application Developer. 5. Start the help system by selecting Help > Help Contents in the WebSphere Commerce development environment.

Starting the WebSphere Application Server Administrative Console in the WebSphere Commerce development environmentPrerequisites v The WebSphere Commerce development environment is running.

52


For instructions on starting the WebSphere Commerce development environment, refer to Starting WebSphere Commerce Developer on page 51. v The test environment is available. Procedure To start the WebSphere Application Server Administrative Console in the WebSphere Commerce development environment, do the following: 1. Start the WebSphere Commerce Test Server. Refer to Starting and stopping WebSphere Commerce on page 51. 2. In the Servers view, right-click on WebSphere Commerce Test Server and select Run Administrative console. The WebSphere Application Server Administrative Console will appear in the Admin Console view.

Appendix B. WebSphere Commerce development environment tasks

53

54


NoticesThis 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 users 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 IBMs licensed program may be used. Any functionally equivalent product, program, or service that does not infringe any of IBMs 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 users 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 105041785 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


55

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 want 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 IBMs 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

56


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 marks owner to accept payment via that credit card.

Notices

57

58


TrademarksThe IBM logo and the following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries or both: v v v v v v v Cloudscape CrossWorlds DB2 DB2 Universal Database i5/OS IBM iSeries

v MQSeries v QuickPlace v WebSphere Intel and Pentium is a registered trademark of Intel Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft and Windows are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others.


59

60


Printed in USA

GC10-4255-06

wsc developer install

Documents

websphere commerce toolkit

websphere commerce tools

websphere commerce test

websphere commercestarting

rational application

copyright ibm

ibm representative

ibm gift center