U bekijkt help-inhoud voor de versie::
- 6.4
- 6.3
- 6.2
- Eerdere versies
The AEM generic solution provides methods of managing the commerce information held within the repository (as opposed to using an external ecommerce engine). This includes:
Opmerking:
The standard AEM installation includes the generic AEM (JCR) eCommerce implementation.
This is currently intended for demonstration purposes, or as the basic foundation for a custom implementation according to your requirements.
Opmerking:
The following procedures apply to both Products and Product Variations.
Before creating products you need to define a scaffold. This specifies the fields you need to define the products and how they are edited.
A scaffold is needed for each distinct product type. The appropriate scaffold is associated with the products by either:
- path
- the product can reference the scaffold
Opmerking:
The Geometrixx-Outdoors store has a single product type (and therefore a single scaffold):
/etc/scaffolding/geometrixx-outdoors
The Geometrixx-Outdoors product type is active on:
/etc/commerce/products/geometrixx-outdoors
You can create a new product definition anywhere under that without any additional setup.
-
Specify:
- Importer
The importer for the specific commerce provider, by default Geometrixx.
- Source
The file you want imported; you can use the browser to select a file.
- Incremental Import
Indicate whether this is an incremental import (as opposed to full).
Opmerking:
The incremental import (of the sample geometrixx-outdoor importer) operates at the product level.
A customized importer can be defined to operate as required.
- Importer
-
Opmerking:
The products will be imported to, or relative to, the current location.
Opmerking:
Repeatedly using Next and Back will repeatedly import the product definitions. However, as they have the same SKUs the information existing in the repository will simply be overwritten.
-
Specify:
- Store Name
Products will be imported to:
/etc/commerce/products/<store name>/ - Commerce Provider
The importer for your commerce provider; by default Geometrixx.
- Source File
The location in the repository of the file you want imported.
- Incremental Import
Indicate whether this is an incremental import (as opposed to full).
- Store Name
Opmerking:
The standard product management is basic, because the Geometrixx-Outdoors product set has been kept basic. The complexity is based on the product scaffolding, so with your own product scaffolding it is possible to achieve more sophisticated editing.
-
The wizard will open. Use the Basic and Product Tabs to enter the product attributes for the new product or product variant.
Opmerking:
Title and SKU are the minimum required to create a product or variant.
Opmerking:
Many products are offered in a range of colors and/or sizes. Information about the basic product and the related product variants can both be managed from the Products console.
Products and their variants are stored as a tree structure, the product information is at the top, with the variants underneath (this structure is enforced by the UI).
Opmerking:
Product images in geometrixx-outdoors are served from:
/etc/commerce/products/...
This means that, by default, they are blocked by the dispatcher, so configure as required.
-
The product attributes will be shown. Use Edit and Done to make any changes.
You can add multiple assets in the product component, then specify the asset that will appear on the product page.
Opmerking:
Everything related to multiple assets is done with the Touch-optimized UI.
-
Opmerking:
The assets you can select are from Assets.
Two assets are now stored in your product component. You can configure which one will appear on the product page. This works with a category system. First you need to add a category to the individual assets:
-
Tap/click Done icon. You now have to rollout your changes.
Now your assets in the product component have a category. You can configure which category will be displayed at three different levels:
Opmerking:
If you do not set categories, the first asset will be displayed on the product page.
The mechanism to select the image to be displayed is as follows:
- Verifiy if a category is set for the Product Page.
- If not, verifiy if a category is set for the Catalog.
- If not, verify if a category is set for the Products Console.
Opmerking:
For both the Catalog level and the Products Console level, you have to rollout your changes to apply the modifications and to see the difference on the product page.
-
Rollout your changes.
-
Rollout your changes.
Opmerking:
Often the product information is published through the pages that reference it. For instance, when publishing page X which references product Y, AEM will ask if you also want to publish product Y.
For special cases, AEM also supports publishing direct from the product data.
The Search&Promote integration allows you to:
- use the eCommerce API, independently of the underlying repository structure and commerce platform.
- leverage the Index Connector feature of Search&Promote to provide a product feed in XML format.
- leverage the Remote Control feature of Search&Promote to perform on-demand or scheduled requests of the product feed
- feed generation for different Search&Promote accounts, configured as cloud services configurations.
For more information, read Product Feed.
There is a Event Handler which logs an event when a product is added, modified or deleted and when a product page is added, modified or deleted. There are the following OSGi events:
- com/adobe/cq/commerce/pim/PRODUCT_ADDED
- com/adobe/cq/commerce/pim/PRODUCT_MODIFIED
- com/adobe/cq/commerce/pim/PRODUCT_DELETED
- com/adobe/cq/commerce/pim/PRODUCT_PAGE_ADDED
- com/adobe/cq/commerce/pim/PRODUCT_PAGE_MODIFIED
- com/adobe/cq/commerce/pim/PRODUCT_PAGE_DELETED
For the PRODUCT_* events, the path points to the base product in /etc/commerce/products. For the PRODUCT_PAGE_* events, the path points to the cq:Page node.
You can look at them in the Web Console in OSGI events (/system/console/events), for example:

Opmerking:
Read also Event handling in AEM.
The Image with Add to Cart Links component allows you to quickly add a product to the cart by creating a hotspot linked with a product on an image.
Clicking the hotspot opens a dialog which let you choose the size and quantity of the product.
-
Drag and drop an image in the component from the assets browser.
-
Clicking the browse icon opens the Asset Picker.
Opmerking:
Alternatively, you can type directly the product path which has to be at the product level, not the variant level.
-
Switch to preview mode.
Opmerking:
The catalog will reference your Product Data.
-
Open the Sites console (for example, http://localhost:4502/sites.html/content).
Opmerking:
The catalog will reference your Product Data.
Opmerking:
The following example deals with a promotion held directly in a campaign, this is used for vouchers.
A promotion can also be in an experience within a campaign.
For more information see Promotions and Vouchers.
-
Edit the Properties by either:
- opening the page, then clicking the Edit button to open the Properties dialog
- selecting the page in the Websites console, then using the context menu (usually the right mouse button) to select Properties... and open the properties dialog
Specify the Promotion Type, Discount Type, Discount Value and any other fields as required.
- opening the page, then clicking the Edit button to open the Properties dialog
In order to make a voucher unavailable to customers, you can either:
- Deactivate the voucher - it will remain available on the author environment so you can re-activate it at a later time.
- Delete it completely.
Both actions can be done from the Websites console.
To change the properties of a voucher or promotion, you can double-click on it on the Websites console and click Edit. After saving it, you should activate it so that the changes get pushed to the publish instance(s).
To allow users to add vouchers to their carts, you can use the built-in Vouchers component (Commerce category). You need to add this to the same page as where the cart is displayed (but is not mandatory). The vouchers component is merely a form in which the user can enter a voucher code, it is the shopping cart component that actually shows the list of applied vouchers and their discount.
In the demo site (Geometrixx Outdoors - English) you can see the voucher form on the cart page, under the actual shopping cart.
Opmerking:
It should be remembered that out-of-the-box AEM does not have actions required for standard functionality related to orders, such as returning merchandise, updating order status, doing fulfilment, generating packing slips. It is primarily intended as a technology preview.
The generic order management in AEM has been kept basic; the fields available in the wizard are dependent on the scaffold:
/etc/scaffolding/geometrixx-outdoors/order/jcr:content/cq:dialog
If you create a customized scaffold you can store more order information.
Opmerking:
The orders console exposes the vendor order information, which is never published.
The customer order information is held in their home directories and is exposed by the Order History for their Account. This information is published along with the rest of their home directory.
-
The wizard will open. Use the Basic, Content, Payment and Fulfilment tabs to enter the information about the new order.
-
The order information will be shown. Use Edit and Done to make any changes.