Example: parameters file for publishing the Aurora starter store

When you publish the Aurora starter store by using the publishstore utility, you can specify a custom parameters file. The utility uses the file to set certain store publish parameters, such as the store type, directory, and the extended site details if you are publishing a storefront asset store.

When you run the publishstore utility from the command line, you must specify the path to your custom parameters file in the -paramfile parameter. The parameters file is optional; if you do not provide a parameters file, the default store publish parameters are used.

You can publish the Aurora starter store as any of the following store types:

Storefront asset store for the extended sites business model (either B2C or B2B direct)

Storefront asset store: parameters

Typically, you publish a storefront asset store during the advanced method for publishing an extended site. This method requires you to publish a number of other store archives and create organizations to own the stores. To understand where the step to publish a storefront asset store falls within the overall steps, see Publishing an extended site: advanced method.

To publish the Aurora starter store as a storefront asset store for a B2C or B2B direct store, include the following eight parameters in your custom parameters file:

STORE_DIR

A name for the directory in which the publishstore utility will place the storefront assets, such as JSP files and images. Example: MyAuroraSAS

STORE_IDENTIFIER

A name to uniquely identify the published store. Example: MyAuroraSAS

ORGANIZATION_DN

The distinguished name for the organization or organizational unit that owns this storefront asset store. Example: ou=aurorastorefrontassetstore,o=extended sites organization,o=root organization

Tip: Use the following SQL statement to find the distinguished name:

select dn from orgentity where orgentity_id in (select member_id from storeent where identifier='store_identifier');

Where store_identifier is the identifier for the storefront asset store, for example, AuroraStorefrontAssetStore.

STORE_TYPE

The type of store to publish. Valid values:

MPS (for a B2C storefront asset store)
BMP (for a B2B direct storefront asset store)

INV_CHOICE

The inventory model to use in the store. Valid values:

Non-ATP: Non-ATP inventory system.
ATP: ATP inventory system.
NoInv: No inventory system.
ExtInv: External inventory system.
DOMInv: Distributed Order Management inventory system.

STORE_IDENTIFIER_CPS

The name of the store that contains the shared catalog data in the extended site. Example: Extended Sites Catalog Asset Store

ORGANIZATION_DN_PROFILE

The distinguished name for the organization or organizational unit that owns the associated catalog asset store.Example: ou=asset store organization,o=extended sites organization,o=root organization

Tip: Use the following SQL statement to find the distinguished name:

select dn from orgentity where orgentity_id in (select member_id from storeent where identifier='store_identifier');

Where store_identifier is the identifier for the catalog asset store, for example, Extended Sites Catalog Asset Store.

STORE_DIR_CPS

The name of the directory that contains the shared catalog data in the extended site. Example: ExtendedSitesCatalogAssetStore

Storefront asset store: example

The following example parameters file sets store publish parameters for a B2C storefront asset store:

STORE_DIR=MyAuroraSAS
STORE_IDENTIFIER=MyAuroraSAS
ORGANIZATION_DN=ou=aurorastorefrontassetstore,o=extended sites organization,o=root organization
STORE_TYPE=MPS
INV_CHOICE=Non-ATP
STORE_IDENTIFIER_CPS=Extended Sites Catalog Asset Store
ORGANIZATION_DN_PROFILE=ou=asset store organization,o=extended sites organization,o=root organization
STORE_DIR_CPS=ExtendedSitesCatalogAssetStore