The Aurora starter store can be used only as a storefront asset store in the
Extended Sites business model. It is not possible to deploy Aurora as a stand-alone B2B or B2C
store. The Aurora.sar archive contains the organization structure, predefined
user roles, and access control policies necessary to create either a B2C storefront asset store or a
B2B storefront asset store.
Follow this procedure
to publish the Aurora starter store as a storefront asset store in an existing Extended Sites
organization. If you are working on a
clean environment that does not have an Extended Sites organization
(ExtendedSitesOrganizationStructure.sar or
ExtendedSites.sar) published, then complete the procedure in the following
topic to successfully publish the Aurora starter store: Publishing an extended site: advanced method.
The storefront includes
Web 2.0 capabilities with Asynchronous JavaScript and XML (Ajax) and Dojo technologies to create a
feature-rich working store. Use the Publish wizard in the Administration Console to publish this
store archive.
Procedure
-
Open the
Administration Console.
-
Select the Site option.
-
From the Store Archives menu, select
Publish. The Store Archives page lists the store
archives available for publish. By default, the page displays composite store archives.
-
In the View, select Extended Sites.
-
Select Aurora.sar.
-
Click Next. The Parameters page
opens.
From the Store type list, select the business model for
your store:
Option | Description |
---|
Consumer direct storefront asset store (MPS) |
Select this option to publish a B2C storefront asset store. |
B2B direct storefront asset store (BMP) |
Select this option to publish a B2B storefront asset store. |
-
Complete the Publish wizard parameters that apply to the business model you
selected:
- Store directory
- The name of the directory that you want to contain the storefront assets (such as JSP files and
images).
- The default value is Aurora. If you are publishing more than one type of
store from the Aurora.sar store archive, consider changing to a more meaningful
name, for example, Aurora_B2C.
- Store identifier
- The name that uniquely identifies the published store.
- The default value is Aurora. If you are publishing more than one type of
store from the Aurora.sar store archive, consider changing to a more meaningful
name, for example, Aurora_B2C.
Organization
- The organization to which you want to publish the store archive.
- The default value for B2C is Seller Organization (Root
Organization).
- The default value for B2B is Extended Sites Seller Organization (Root
Organization).
Catalog asset store
- The catalog that you want to use. Select the name of the store that contains the shared catalog
data that you want to use.
- Example: Extended Sites Catalog Asset Store
- Inventory Model
- The choice of inventory model to be used in the store: ATP (available to
promise), Non-ATP, External inventory, No
inventory, or DOM inventory.
- The default value is ATP.
-
Click Next. The Summary page
displays, listing the store archive and parameters that are selected, and the location to which the
store archive is published.
-
After you review the summary information, click Finish.
A confirmation dialog displays with the number of the publishing job. Note the job number for future
reference.
-
To check the publishing status, click Refresh.
-
When the Publish Status column displays
Successful, select the corresponding job number and click
Details.
-
Set up WebSphere Commerce Search and build the search index.
-
Set up the
search index


You must complete this step every time you publish a store.
Complete this step if workspaces is enabled. Otherwise, you
do not have to complete this step.
-
Preprocess the
search index data


You must complete this step every time you publish a store.
Complete this step if workspaces is enabled. Otherwise, you
do not have to complete this step.
-
Build the
WebSphere Commerce Search index.


You must complete this step every time you publish a store.
Complete this step if workspaces is enabled. Otherwise, you
do not have to complete this step.
-
Restart the server.