Deploy a starter store
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
- Publish the starter store with a sample data set to learn about the catalog structure.
- Create, modify, and test JSP pages, Java code, and EJB beans according to your business requirements.
- Create access control and registration scripts for any development assets.
These scripts will be needed to quickly register your new views and commands when you move your development assets to another machine. Creating scripts to register new commands and views is described in Set access control for the page.
- Use the WebSphere Commerce Accelerator to learn about styles, options, and other features.
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 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