This guide describes how to import product and catalog data from INTERSHOP into AEM.
The content of the present document is valid for the following combinations of software versions:
Intershop | Intershop Commerce Pro for Adobe | Adobe Experience Manager |
---|---|---|
7.5.1 | 2.0 | 6.0.1 |
Term / Abbrevation | Description |
---|---|
AEM | Adobe Experience Manager (Version 6.0.1) |
Tags | The AEM uses tags to annotate and organize the objects in its content repository. In this case tags are used to specify the category to products assignments. |
Section | An AEM term. In this case a section represents a catalog category. |
Cookbook - AEM Catalog and Product Import
Note
The Geometrixx demo scenario is already set up with the installation of the content packages. You only need to run the steps below if data has changed on IS7 side that should be imported into the AEM.
There are pre-configured data feeds on the IS7 side to export the product and catalog data into files. These data feeds will later be imported into the AEM.
Wait until the data feed has finished and download the data file. Press refresh to reload the contents of the page with the current feed status.
If the installation is on your local computer: The data files are generated at: <IS_HOME>\share\sites\Geometrixx-GeometrixxOutdoors-Site\units\Geometrixx-GeometrixxOutdoors\syndication\export.
These data feeds have been created via dbinit steps in the adobe_init cartridge. Specific configuration of these feeds has to be done via dbinit configuration files if necessary. See the according subsections of the data feeds for more detailed information.
The product data feed exports basic product data that is needed in the AEM. The pre-configured data feed transfers:
as AEM tags and no additional custom attributes as it is currently configured. In order to export additional custom attributes of the selected products, the data feed needs to be configured via dbinit when it is created. See the Recipe: Configure the Product Data Feed Properties to Export Additional Custom Attributes for details. The following list shows the properties that can be applied to configure the feed.
Property | Default Value | Description |
---|---|---|
localeID | en_US | The locale for localizable data of the product, e.g., the product name and the product attribute values to the feed |
imageTypeID | default:3XL | The image view (optional) ID and the image type ID that is used to create an image reference for the product |
imageTargetBasePath | /content/dam/geometrixx-outdoors/products/import | The image target path determines the location where images are stored in the AEM. |
customAttributeIDs | <empty> | Additional attributes to be transferred to AEM specified as a comma separated list of IDs, e.g., longDescription,MaxOrderQuantity |
Product attributes that have a data type are converted into property values with a data type in AEM. The IS7 specific data types Money and Quantity are exported and imported as decimal value only. The currency mnemonic and unit is not kept. IS7 Integer attributes are transferred as Long.
Native product attributes that can also be specified in the customAttributeIDs list:
Native Product Attribute Name | Description | DataType (AEM) |
---|---|---|
MinOrderQuantity | Minimum Order Quantity | Decimal |
MaxOrderQuantity | Maximum Order Quantity | Decimal |
StepQuantity | Order Step Quantity | Decimal |
Unit | unit | String |
Image | Image (deprecated) | String |
Thumbnail | Thumbnail (deprecated) | String |
Taxclass | Tax Class | String |
Online | The online flag of the product. | Boolean |
Available | The in-stock flag of the product. | Boolean |
LastModified | The last modified date | Date |
LastOrderDate | last order date | Date |
EndOfLifeDate | end of life date | Date |
TypeCode | type code | Long |
Template | template (unused) | String |
Which products have to be exported is determined using the standard functionality of product data feeds to select products. In the data feed details:
The express update product data feed 'AdobeProductCSVExpressUpdate' is pre-configured to export the products that have been marked for express update since the last run of this data feed. Products can be marked for express update on the product details page.
As said before products can be marked for express update on the product details page. Only these product are processed by the feed. The configuration of the feed is identical to the Product Data Feed. The difference is that the Commerce Management application user has no UI to configure the assigned products.
After the export the express update flag will be reset. If the feed runs twice in a sequence the second run produces an empty CSV.
The incremental data feed 'AdobeProductDeltaCSV' is pre-configured to export the products that have changed since the last run of this data feed. The resulting CSV data can be used to update the product data at AEM side. In addition to the properties of the Product Data Feed exists an additional property that switches this data feed into the 'lastModified'-Mode to select the products that have been modified.
Property | Default Value | Description |
---|---|---|
lastModifiedProducts | undefined | If the lastModifiedProducts is set at the data feed and LastModifiedFromDate is set as search criterion in the advanced search for the selected products only 'touched' products are exported by this feed. |
To enable the selection of last modified products you have to select the products with the Advanced Search and set a arbitrary Last Modified From Date. This Last Modified From Date will be automatically replaced by the execution date and time of the last execution of this feed.
Note
This feed shows only changed and new products in the product tab. If there are no changed or new products the list shows 'No products assigned'.
Deleted products are not handled by this feed yet. If there are deleted products you need to execute a full import or delete it manually in AEM.
The product image zip data feed produces an image zip-file of product images for a specified type.
Property | Default Value | Description |
---|---|---|
imageTypeID | 3XL | The image view (optional) ID and the image type ID that is used to create an image reference for the product. Image View ID and Image Type ID are separated by the colon (:), e.g., front:1XL . |
imageTargetBasePath | /content/dam/geometrixx-outdoors/products/import | The image target path determines the location where images are stored in the AEM. |
Which product images have to be exported is determined using the standard functionality of product data feeds to select products. In the data feed details:
The catalog data feed exports category data. The data feed might be configured to export all categories of a given catalog into a CSV file. The configured data feed currently exports the following data:
The values of the properties in the next table are exported on the second line of the resulting CSV data feed. There default values are given in the table. If non-defaults are required the properties can be changed using the feed configuration file.
Property | Default Value | Description |
---|---|---|
basePath | /etc/commerce/products/+"baseCatalogID" | This is the path in the content repository that points to root node where the products are stored/imported. |
catalogTemplate | /content/catalogs/ish-geometrixx-outdoors/template-pages/catalog-page-template-intershop | The path to an AEM catalog template to be used at the intershop base catalog |
sectionTemplate | /content/catalogs/geometrixx-outdoors/template-pages/section-page-template | The path to an AEM section template to be used at the intershop base catalog |
productTemplate | /content/catalogs/geometrixx-outdoors/template-pages/product-page-template | The path to an AEM product template to be used at the intershop base catalog |
design | /etc/designs/geometrixx-outdoors | The path to an AEM design that is used at the intershop base catalog |
baseCatalogID | The ID of the exported catalog in lower case. | The base catalog ID (all IS7 catalogs are imported into that base catalog) |
baseCatalogName | The ID of the exported catalog in lower case. | A descriptive name for the base catalog |
Which catalog has to be exported is determined using the 'Catalog' tab in the feed configuration. The user may select only one catalog per feed. To configure a catalog data feed do the following:
The import supports both, full import and incremental import. A full import assumes an import of complete product or catalog data. Therefore, the full import deletes all existing data in the selected area and re-creates all the products or catalogs from the given input data file. The incremental import keeps the existing product or catalog data and updates this data with the contents in the given input data file.
There is a product import job that can import product data automatically into AEM. The job is disabled per default. To enable the job you need to configure it in the AEM Web Console Configuration http://localhost:4502/system/console/configMgr Look for the name 'Intershop Product Import Job' and click on the name to change the configuration. Edit the 'Product CSV Path' to point to the location of the export files of the intershop location and check the 'Job Enabled' checkbox to enable the job.
The other default values will match the default feed configuration and must only be changed if you have set up different feeds or a different store. By default the job runs every 30 seconds to check if one of the given files in the list is changed. The schedule expression uses a quartz cron expression. See Quarz Scheduler Documentation for more information. If a changed file is detected the product import is started immediately. The first file in the list is assumed to be a full import file. If this file changes the import runs as a full import. Other files in the list of 'Product CSV File Names' are assumed to contain incremental product data and an incremental import is run if one of these files are changed.
Currently only product data and no catalog import CSVs are supported for automated import.
There is an additional importer that calls the importer of version 1.1 for product and image import via REST interface.
To make changes in the catalog structure and product assignments to categories visible to the site it is necessary to roll-out these changes from the blueprint into the actual site.
Click Rollout Changes.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.