Table of Contents |
---|
Introduction
...
Repository | Description | Usage |
---|---|---|
exporter-shopware6 | a standard Shopware6 plugin responsible to export Shopware data to Boxalino | To be replaced with the Data Integration repository |
a Shopware6 plugin responsible to export the Shopware data following the Boxalino Data Integration Data Structures | Install and update when Boxalino provides a new version | |
a standard Shopware6 plugin responsible to manage all the calls to Boxalino API for your front-end | Install and update when Boxalino provides a new version | |
a sample (tutorial) Shopware6 plugin provided to examplified how to integrate Boxalino (you can either build your own from scratch or download (and rename namespace) it to have all default features active directly, but do not copy or clone, as it is your environment and should not be updated from our repo) | Use as inspiration or download (and rename namespace) to bootstrap all features (but do not copy or clone!) and then develop, maintain and extend by yourself |
...
Make sure that if you export your data in dev (vs prod), that you access the API with dev=true (vs false)
Make sure that you download (and rename namespace) but do not copy or clone the rtux-integration-shopware repository, even if you chose the approach “All-at-Once”. The integration layer needs to be your environment that you extend / modify and maintain.
Make sure that you do not call the API before you have configured the following aspects in the Boxalino Admin and have pressed test or publish:
Widgets (in the main view, even if you leave the configuration of the widget strategy empty), otherwise, the system will throw an error because you are calling a non-existing widget
Layout Blocks (that all the template you need have been configured in the Layout blocks, otherwise, you cannot create your Narratives (point c))
Narratives connected to Widgets of point a, as without narratives configured for the widget, your API response will be empty
Click Test (or Save&Test) and wait at least 5 minutes before using the API with the parameter test=true
Publish and wait at least 5 minutes before using the API with the parameter test=false
...
Add the plugin to your project via composer
composer require boxalino/data-integration-shopware6
Activate the plugin (Shopware6 default)
./bin/console plugin:refresh
./bin/console plugin:install --activate --clearCache BoxalinoDataIntegration
Log in your Shopware admin and configure the plugin with the configurations provided for your setup
Shopware Admin >> Settings >> System >> Plugins >> Boxalino Data Integration
If the plugin configurations are not displayed, they can be accessed via direct link:
admin#/sw/plugin/settings/BoxalinoDataIntegration
Set configuration per Sales Channel and disable the plugin where it is not in use. The Headless channel must have the plugin disabled.
Use the ? icon to get information on the configurations options or check https://github.com/boxalino/data-integration-shopware6/wiki/Configurations
More information on the available data indexes available in the wiki https://github.com/boxalino/data-integration-shopware6/wiki/Data-Indexes
Add the generic services to your Integration Layer
You can skip this step if you chose the approach “All-at-Once” and want to keep the default services.the doc_product handler is the service responsible for the export of product information (as seen on https://github.com/boxalino/rtux-integration-shopware/blob/3.0.0/src/Resources/config/services/di/product.xml )
has configured a series of property handlers for different data structure export (ex: categories, stock, price, translation properties, options, image, link etc)
the doc_language handler will export the existing languages for the given sales channel (https://github.com/boxalino/rtux-integration-shopware/blob/3.0.0/src/Resources/config/services/di/language.xml )
the doc_attribute handler will export information on your product attributes (https://github.com/boxalino/rtux-integration-shopware/blob/3.0.0/src/Resources/config/services/di/attribute.xml )
the doc_attribute_value handler will export the facet options for the product attributes (https://github.com/boxalino/rtux-integration-shopware/blob/3.0.0/src/Resources/config/services/di/attribute_value.xml )
the doc_order handler is the service responsible for exporting your order information (as seen on https://github.com/boxalino/rtux-integration-shopware/blob/3.0.0/src/Resources/config/services/di/order.xml )
the doc_user handler will handle the SW6 logic for exporting user information (https://github.com/boxalino/rtux-integration-shopware/blob/3.0.2/src/Resources/config/services/di/user.xml )
Integrate the Product Export Console Command service (as seen on https://github.com/boxalino/rtux-integration-shopware/blob/3.0.0/src/Resources/config/services/di/product-console.xml )
Trigger a full data index
./bin/console boxalino:di:full:product
More options for the full data index :https://github.com/boxalino/data-integration-shopware6/wiki/Integration:-Full
You can review the status of the sync process https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/394559761/Sync+Request#Request-REVIEW
Tip |
---|
A full data export has started. The data integration will log it's process in a dedicated log ./var/log/boxalino-di-product-env.log |
...
In this section, we present the building process of the integration layer with the approach described above as “All-At-Once”. This strategy is being described in the video tutorial https://www.youtube.com/watch?v=Fl8d0MO0ub0
...
Create an empty Shopware6 plugin skeleton in your project codebase by following your project practices: in custom/plugins or vendor path
From a project level, require & activate the Data Integration Layer and the Framework Layer
composer require boxalino/rtux-shopware
composer require boxalino/data-integration-shopware6
./bin/console plugin:refresh
./bin/console plugin:install --activate --clearCache BoxalinoDataIntegration BoxalinoRealTimeUserExperience
Download the Boxalino Guidelines for the Integration Layer from the public repository
we recommend to download the latest available tag
Review the downloaded version composer.json
From the downloaded archive, extract the src folder
From the src folder, delete the Shopware Plugin Class
this file is specific to every plugin and your default/base Shopware6 Integration Layer Plugin already has one
Copy the src folder in your project`s Integration Layer
by doing so, you are merging the content of the Integration Guidelines in your own code-base
if your project does not require the extended features (ex: Instant Update ) - disable it`s load by commenting this imported XML
(optional) replace the /src/Resources/config/plugin.png with your agency`s icon or remove it
Change the namespace by:
replacing Boxalino\RealTimeUserExperienceIntegration with your own project`s Integration Layer namespace
Install and Activate your project`s Integration Layer plugin (Shopware6 command)
Re-compile the theme (administration and frontend)
./bin/build-administration.sh
./bin/build-storefront.sh
Configure the Data Integration Layer and Framework Layer in Shopware 6 admin
check out the Data Integration Layer Configurations wiki https://github.com/boxalino/data-integration-shopware6/wiki/Configurations
set the DI configuration per Sales Channel and disable the plugin where it is not in use
the Headless channel must have the plugins disabled
check out the Framework Layer Configurations wiki https://github.com/boxalino/rtux-shopware/wiki/Configurations
Run the data exporter command in order to initialize your account`s data index
./bin/console boxalino:di:full:product
each repository has it`s own individual logger handler; the logs are saved in boxalino-di-<type>-<env>.log files
read more on the available data indexes on the SOLR data indexes wiki page https://github.com/boxalino/data-integration-shopware6/wiki/Data-Indexes
you can review the status of the SOLR sync with the use of our open API https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/394559761/Sync+Request#Request-REVIEW
Load the Narrative JSON Guidelines in Boxalino Intelligence Admin
ask Boxalino on the setup channel to assist
provide your project`s Integration Layer namespace
do it yourself
check out the JSON Guidelines page https://github.com/boxalino/rtux-integration-shopware/wiki/JSON-Guidelines-(Complete)
copy each JSON content in the required path from Boxalino Intelligence Admin
Menu: Advanced >> Template Resources
copy and load as they are
Menu: Merchandising >> Facets
copy and load as they are
Menu: Marketing >> Layout Block
copy the JSON structure
replace the @BoxalinoRealTimeUserExperienceIntegration namespace with your project`s Integration Layer namespace
load in Boxalino Intelligence Admin
Menu: Marketing >> Narratives
copy and load as they are
Menu: Strategies >> Touch Point Optimizers >> Search block >> click on the search widget
copy, import and save&test as they are
Per Shopware6 layout-strategy, the category uses the Shopping Experiences layouts. In order to enable navigation and edit the home page - new layouts with the narrative CMS block must be created.
check out CMS Element (for Shopping Experiences) Configurations and Practices
...