Installation
Global‑e offers two installation scripts:
Global‑e Accelerator Recipe Installation: Run the automatic Global‑e Accelerator Recipe on your Hybris Test Site when installing the Global‑e Add-on for the first time. This allows Global‑e to identify potential overlaps with your current customization.
Manual Installation: Run the manual installation to start the integration with an existing Hybris project: Pull the Global‑e extensions, include them in the project repository, and then configure the Global‑e Add-on.
Prerequisites
The Global‑e add-on setup requires a Global‑e merchant account.
Supported Versions: Supported SAP Hybris version: 2211.3.
Global‑e Accelerator Recipe Installation
The Global‑e accelerator lets you discover the functionality of the platform.
Recipe automates the platform code build and initializes the accelerator sites.
The Recipe installation procedure is only performed when installing the add-on the first time (generally, in the testing environment).
To install the Global-e Add-on with Recipe:
Configure the database, user, and permissions:
mysql> create database globale; mysql> create user 'globale'; mysql> grant all on globale.* to 'globale'@'%' identified by 'globale';
Unzip the SAP Commerce distribution ZIP archive.
Copy the mysql db driver to:
/hybris/bin/platform/lib/dbdriver
Copy
globale recipe
to the SAP Commerce installer:cp -r ${PATH_TO_GLOBALE_REPO}/y-config/installer/recipes/* ${PATH_TO_HYBRIS_UNPACKED}/installer/recipes"
Create symlinks:
ln -sfn ${PATH_TO_GLOBALE_REPO}/y-ext ${PATH_TO_HYBRIS_UNPACKED}/hybris/bin/globale"
Now, the source code is linked to the SAP commerce suite ready to build.
Build and initialize:
cd ${PATH_TO_HYBRIS_UNPACKED}/hybris/bin/platform ./setantenv.sh ant clean -Dinput.template=develop ${PATH_TO_HYBRIS_UNPACKED}/installer/install.sh -r globale initialize
Configure the Global‑e Add-on. See Configure the Global‑e Add-on.
Manual Installation
For an existing Hybris integration, use the manual Global‑e Add-on installation.
To place a call manually (without a recipe):
Open the
localextensions.xml
file and add the following Global‑e extensions:<extension name='globalecore' /> <extension name='globalefacades' /> <extension name='globaleaddon' /> <extension name='globaleendpoint' /> <extension name='globalepromotions' /> <extension name='globalebackoffice' />
Install the
globaleaddon
:ant addoninstall -Daddonnames=globaleaddon - DaddonStorefront.yacceleratorstorefront=STOREFRONTNAME
Configure the Global‑e Add-on. See Configure the Global‑e Add-on.
Configure the Global‑e Add-on
The Global‑e Add-on deploys these main configuration files.
hybris/config/local.properties
- the file containing all the configuration properties (UID, GUID, feature toggles)hybris/config/localextensions.xml
- the file containing the list of modules and extensions (globalecore
,globalefacades
,globaleaddon
, and so on).
To configure the Global-e Add-on:
Open the
local.properties
configuration file.Add your Global‑e Merchant credentials:
| Your Global-e Merchant ID. Template:
Example: |
| Your Global-e Merchant GUID. Note that you receive a different GUID for staging and production. Make sure to use the correct GUID. Template:
Example: |
Additional Settings
Client
globale.client.js.domain = 'https://www2.bglobale.com' globale.client.js.path = '/scripts/merchants/globale.merchant.client.js'
Global‑e Enabled
globale.enabled = true globale.enabled.initial.product.call = false
Global‑e Cookie
globale.cookie.name = 'GlobalE_Data' globale.cookie.expiration = '259200'
API Call Timeout
globale.api.call.timeout = '6000'
API Connections
globale.api.connect.timeout = '1000' globale.api.call.max.connections.host = '100' globale.api.call.max.total.connections = '200'
Send Products
globale.send.products.batch.size = '10'
Country Code
globale.default.country.code = 'GB'
Language
globale.store.multilanguage = 'true' globale.store.english = 'en'