Configuring jCustomer features

This topic shows you how to configure the main features in jCustomer.

Changing the default configuration

Before perform other modifications, ensure that you set your own cluster name. For more information, see Installing jCustomer in Installing Elasticsearch, jCustomer, and jExperience.

If you want to change the default configuration, you can perform any modification you want in the <jcustomer-install-dir>/etc directory by creating your own custom configuration in the unomi.custom.system.properties configuration file. You can find default values for the properties in the custom.system.properties file.

For example, you defines the addresses and ports where jCustomer can be found:

org.apache.unomi.cluster.group=${env:UNOMI_CLUSTER_GROUP:-default}
# To simplify testing we set the public address to use HTTP, but for production environments it is highly recommended
# to switch to using HTTPS with a proper SSL certificate installed.
org.apache.unomi.cluster.public.address=${env:UNOMI_CLUSTER_PUBLIC_ADDRESS:-http://localhost:8181}
org.apache.unomi.cluster.internal.address=${env:UNOMI_CLUSTER_INTERNAL_ADDRESS:-https://localhost:9443}

Installing the MaxMind GeoIPLite2 IP lookup database

jCustomer requires an IP database to resolve IP addresses to user location. The GeoLite2 database can be downloaded at MaxMind from the following location:

http://dev.maxmind.com/geoip/geoip2/geolite2/

Simply download the GeoLite2-City.mmdb file and copy it into the <jcustomer-install-dir>/etc directory.

Installing Geonames database

jCustomer includes a geocoding service based on the geonames database (http://www.geonames.org/). You can use it to create conditions based on countries or cities. To use it, you need to install the Geonames database. Get the "allCountries.zip" database from here:

http://download.geonames.org/export/dump/

Download it and put it in the <jcustomer-install-dir>/etc directory, without unzipping it.

Edit the <jcustomer-install-dir>/etc/unomi.custom.system.properties file and set the org.apache.unomi.geonames.forceImport property to true. The data import should start right away. Otherwise, the import should start at the next startup. The import runs in background, but can take about 15 minutes.

At the end, you should have about 4 million entries in the "geonames" ElasticSearch index.

jExperience and remote publication

jExperience is fully compatible with a remote publishing architecture. Though a precise method must be applied. Here are the steps:

1. Start ElasticSearch.
2. Start jCustomer.
3. Start Jahia (ensure that contribution server operating mode is defined as "production" and remote server operating mode is defined as "distantPublicationServer", using jahia.properties).
4. On the contribution server:
   Note: The remote site must have the same name/sitekey as original site, as all goals/conditions are based on node paths. Different site names are not supported for now.
   1. Create the desired site (for example, ACME SPORT).
   2. Install and enable the jExperience-modules.
   3. Configure jExperience in Site Settings.
5. On the remote server:
   1. Create a new site with the same template set and same name/sitekey.
   2. Install jExperience-modules.
      Note: Do not activate jExperience-modules for this site.
6. Then set up the remote publication on the contribution node and execute the remote publication (check logs and UI, details about remote publication setup can be found here).
   1. Open the remote site in a new private window and browse the page.
   2. On the contribution server, check that the corresponding visitor profile was added in jExperience > Global > Audience > Profiles

Configuring the email action

In jExperience Rules, an action is available to send email. Emails are sent using an SMTP server that needs to be configured in the following jCustomer file: /etc/unomi.custom.system.properties 

org.apache.unomi.mail.server.hostname=<smtp server host name>
org.apache.unomi.mail.server.port=<smtp server port>
org.apache.unomi.mail.server.username=<smtp server username>
org.apache.unomi.mail.server.password=<smtp server password>
org.apache.unomi.mail.server.sslOnConnect=<use ssl>

In the email template, you can use the following pattern to display any profile property value in the email that will be sent: $profile.properties.("propertyId")$