The extent and nature of the customization of the starter store will affect your deployment strategy. The following table describes a typical deployment scenario.
Machine |
Task |
Development machine |
|
Staging server and production server |
- Prepare the store's catalog in CSV or XML format to load into the database.
- Install and configure your WebSphere Commerce instance including, if necessary, payments configuration.
|
Staging server |
- Publish the starter store.
- Remove unused languages and currencies from the store.
- Set exchange rates.
- Use the WebSphere Commerce Accelerator to configure the store. For example, change the store logo, shopping flow, text on store pages, and default text in e-mail messages.
- Load the catalog data from XML or CSV files.
- Use the WebSphere Commerce Accelerator to set up taxes, shipping, and discounts.
- Deploy JSP, XML, Java code, and EJB assets developed on the development system.
- Use the staging tools to move database from staging server to the production server.
- Copy store file assets. For a list of the file assets that you need to copy refer to Starter store conventions. If you have changed the MemberRegistrationAttributes.xml file, you will also need to copy this file to the production server.
|
Related concepts
Related tasks
(C) Copyright IBM Corporation 1996, 2005. All Rights Reserved.