The requested added pipelines in the deployer-conf.xml have a spelling mistake in the documentation
The first error shows you are supplying the parameters in the incorrect format.
Hope below steps should work for you -
Make sure you have installed elastic search 5.5 or 5.6 version running.
For windows environment use single hyphen (-). It should be like
.\installElasticSearchIndexes.ps1 -es-host "localhost" -es-port "9200" -es-scheme "http"
In this ...
No - it is not possible to randomize the results returned by out-of-the-box usage of SmartTarget (I guess what you are looking for is a 'random' option in the sorting dropdown). See this answer and question for more.
As mentioned there, what we did on our implementation was implement the randomness as a post processing step on the results returned from the ...
Issue was due to a campaign directly being created in the Fredhopper Business Manager (FBM), and labeled SmartTarget (ST). Issue no longer reproducible when the label is removed from campaign.
Just as recap, even though for troubleshooting purposes it is possible to make SDL Web promotions visible in the FBM, and the default FH admin user is able to ...
The error indicates that something went wrong when loading your configuration file (e.g. it is invalid).
To resolve it, make sure your smarttarget_conf.xml file has a value for the DefaultUniverse setting. The default value is 'catalog01'.
While you are there, you should take a look at the other settings and make sure they are correct as well.
The fact that you get a 404 indicates that the API extension isn't working. Coupled with the error in the Business Manager, I'm certain you are running into a known issue that has been fixed in the newer cloud releases.
The smarttarget_api_extension.jar file mistakenly included some javax.servlet classes (from transient dependencies) and they can interfere ...
The first four are added by Fredhopper, the other four by XO.
The former cannot be hidden and the latter are always hidden (as they are defined on the other tabs instead).
Actually, you could probably filter out the ones you don't want in a data extender, but I doubt it would be worth the effort.
Ok apparently we need claims to be declared both in the <ForwardedClaims> and <GloballyAcceptedClaims> in the staging site's cd_ambient_conf.xml.
Here is a working config file:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<Configuration Version="8.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:...
To quote from the prerequisites section of the documentation:
SDL Web Experience Optimization 8 requires version 7.5.x of Fredhopper Access Server.
You cannot use version 8 as there are breaking changes (it's a new major version, after all).
You can use Java 8 with the later versions of Fredhopper. I recommend you use version 184.108.40.206 or higher.
The XO installer doesn't add XO TBBs to existing Publications. It does add the XO TBBs to the set of templates to create for new Publications (BluePrint roots).
If you want to get the XO TBBs in an existing BluePrint, you have to use the SDL Template Builder to Create/update Default Templates in your BluePrint root Publication.
As @Ankon says, if you use different user during installation process (for example root for make some directories and Fredhopper for running) you probably have not rights on some directories.
Try to change the owner of $FREDHOPPER_HOME to fredhopper user with recursive options.
You should always use fredhopper user for running and maintenance.
I hope this ...
The Experience Optimization Management and Query service url seems to be incomplete in the out of the box provided cd_storage_conf.xml file as below:
<Role Name="SmartTargetManagementCapability" Url="http://localhost:8093/"></Role>
<Role Name="SmartTargetQueryCapability" Url="http://localhost:8094/"></Role>
You are looking at the wrong documentation. Experience Optimization is part of Web 8.5 now and as such has been merged into the same documentation publication. You'll notice that there isn't a separate link for it anymore when 8.5 is selected in the drop-down list.
The correct documentation page is therefore here:
Adding Experience Optimization to Content ...
For such URL to resolve, you have to ensure you have a Publication which maps to the Website root (you don't have to actually publish anything in that Publication, but just have a mapping in Topology Manager so a Localization can be resolved).
Alternatively, you can change the redirect URL prefix in smarttarget_conf.xml so it matches the URL path of one of ...
The Content Delivery microservices are currently only accessible through the CIL (as explained here http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v5/GUID-A2A47810-D27A-40CA-8C22-CCDC224AF81C), which means that you will have to use the SDL Web Content Delivery API, and thus its jars or assemblies (available via Maven or NuGet) in your mobile ...
If you want to use XO features in the mobileApp and already using DXA, there is an OOTB option available,
Create a mobile page in Tridion and publish it to dxa webapp. Use DXA webapp to generate json response and consume it in the mobile app (eg: http://mydxawebapp.com?format=json).
In that way you can achieve all the XO features OOTB from tridion and ...
In the installation media of your Experience Optimization release, you will find the following folder:
In there are 10 more jars, the last one named smarttarget_google-analytics.jar, which is the one that contains your missing class.
Following the documentation, you should:
From the installation ...
I noticed in your installation error logs you have wrongly installed SDL Tridion Docs search functionality elasticsearch indexes installation script instead of XO elasticsearch installation script.
Documentation is indeed and it's correct but you have wrongly referred to the installation media folder for the script.
XO Installation script media ...
If I remember correctly, the XO TBBs aren’t created using Template Builder. Instead, they are created when XO is installed as a feature.
By default, the XO TBBs are created (by the installer) in /Building Blocks/Default Templates/Experience Optimization
It sounds like you installed the previous version of Experience Optimization on top of 8.5 (especially considering this other question you asked). However, XO is just a feature in the suite installer now. You don't install it separately.
You'll need to uninstall the old one and modify your SDL Web 8.5 installation to include Experience Optimization.
According to the error message, you don't have Experience Optimization TBBs in your CMS.
You must ensure that the Experience Optimization feature is installed on your CMS before running the DXA XO Module's cms-import.ps1.
If the Experience Optimization feature is installed, it should create XO TBBs in /Building Blocks/Default Templates/Experience ...
When using Keywords, it currently matches by an escaped value of the TCM URI -- not the title of the Keyword.
So your claim should have the URI of the Keyword, URL encoded, with the dashes replaced by underscores (Fredhopper doesn't allow those in identifiers). For example, if your Keyword has a URI of "tcm:5-1111-1024" - the claim value should be "tcm%...
A 406 Unacceptable response is most unusual in this case. It suggests that the type of content being returned is not supported by the client (i.e. it wants to return content that is gzipped but the client hasn't indicated that it supports that in the 'Accept-Encoding' request header).
I would first check if you are actually talking to the right service. ...
Actually, the correct ordering in which it is returning items is based on the way the items get published to fredhopper, not their name. This we found out the hard way. :(
So basically, if you publish components X and Y with template A and B in FH, you will get the following:
but if you republish template B, new items will be XB and YB
so you ...
You should check that your Page Template has the right values in the "Add Promotions" Template Building Block. There is a mandatory parameter field for Maximum items to display, and that should have the total number of items you expect to return.
You will also need to make sure that when you create the promotion, in the section where you select the folder ...
You can do A/B testing using a Smart Target functionality called Experiments. This allows you to define two or more variants of content, which will be shown randomly to visitors (visitor A will see variant A, visitor B will see variant B, etc...)
Using the Experiments gui, you are able to see the number of times each variant is shown, and how many ...