10

We Can achieve this using the following option in the FH/ST server : http://[host]:[port]/fredhopper/sysadmin/reload-config.jsp?select=trigger-types although, the person who taught me that, told me that we need to be very careful with that administration console, we can mess up the entire environment Thanks Marc!


9

The attributes (fields) in Fredhopper have a maximum size which you probably exeeded. An attribute cannot exceed the max character length of 32K. Most likely you have hit this limit. Logs Check the Fredhopper logs on the indexer instance and the xmlloader log in particular. You can expect an error message like this: 2015-01-09 14:59:55,963 ERROR [XML-...


8

Claim to trigger mapping The first problem is in the mapping. You should map the "group" instead of the claim. So you want to map the "group" taf:claim:usertype to the prefix user. Try this mapping: <taf_claim_usertype>user</taf_claim_usertype> This way the claim taf:claim:usertype:prof will be mapped to the trigger url-param user_prof. ...


7

Apart from the approach Stephan202 mentioned: If you're using the deployment agent, you can use it's "capture" functionality to capture the complete configuration, and restore that when needed.


7

Your JAVA website will use the SmartTaget tag library, or if you like the SmartTarget API, to get the content for a specific SmartTarget region. SmartTarget will also take care of the SmartTarget markup for Experience Manager. In a JSP page you could add some JSP tags to define the SmartTarget region on the page. SmartTarget will do the rest. See a minimal ...


7

Fredhopper: SDL Fredhopper is a Customer Experience Management tool which provides a seamless, targeted and fully personalized website experience to the end users. The SDL Fredhopper enables the marketing team to target a specific segment of customer with all the right products or content which suits them best. SmartTarget: SmartTarget is an add-on for SDL ...


7

I have contacted Fredhopper customer support and they have provided me with the scripts: log-analyzer.pl and log-analyzer.py. If you have the similar request, please feel free to contact them and they should provide it to you.


6

I currently do not have access to the LiveContent documentation page, so the following information is from the top of my head: SmartTarget 2014 installations that use an on-premise installation of Fredhopper are advised to use FAS 7.5.0.16, which is contained in fredhopper-7.5-revision-13 (i.e., not fredhopper-7.5-revision-14, which contains FAS 7.5.1.0). ...


6

The capture-import command (and pretty much all other commands!) should be run from the fredhopper installation directory, not from the bin directory.


6

Although not part of the official public API, I would recommend using the TriggerTypesHelper class to create/update the triggers - as well as the LocalizationHelper class if you need to use different labels than the raw values (for instance, we use the URI of Segments as the trigger values but show the title to users when editing Promotions). You should not ...


6

SmartTarget promotions are stored in Fredhopper, as "campaigns". Unless SmartTarget stores additional meta-data outside of FH (something I'm not aware of), it should be enough to simply extract the campaigns from Fredhopper using their configuration REST API. You can do this using e.g. curl. The full campaign configuration for a single FH universe and locale ...


6

You will get the Please wait The Business Manager will be available when the indices are loaded. message as long as Fredhopper indices are not built. You could say, the problem is that the Fredhopper system has no data. To initialize Fredhopper you can either Copy the SmartTarget 2014\Fredhopper extensions\data\metadata.xml file from the installation ...


6

SmartTarget tcdl tags are transformed by the Tridion Deployer. The SmartTarget module needs to be added to the cd_deployer_conf.xml. add the following to the <Processors> element <Processor Action="Deploy" Class="com.tridion.deployer.Processor" Phase="post-transaction"> <Module Type="SmartTargetDeploy" Class="com.tridion.smarttarget....


6

This is not so much an error but rather an indication that Fredhopper is empty. If you follow the steps outlined in the SmartTarget documentation, you will load a metadata XML file into Fredhopper to avoid exactly this situation. Since you did not yet put any data into it, Fredhopper displays this message until such a time that you add some data. If you are ...


6

It is considered bad security practice to install and run processes as the root user on linux. Each service should run under it's own user in order that it can be isolated from other areas of the system and secured appropriately. See https://askubuntu.com/a/207481 for a more comprehensive answer.


6

java.net.BindException: Address already in use This means that you are trying to bind to a port which is already in use by another process Try using lsof -i:<port> to determine which process is already bound to the ports that fredhopper is trying to use FredHopper typically uses ports starting from 8180 and rising by 1000 each time, e.g. 8180, 9180, ...


6

It is possible to provide labels for trigger values that are different from the actual values (e.g. title instead of ID). But it requires you to use the API to set it up and it's kind of complicated. In this case, you already have the Title available as the 'templatetitle' attribute so you can indeed just use that instead.


6

Export the configuration For Unix: bin/capture-export INSTANCE-NAME path/to/output.zip -c -i -x -l For windows: bin\capture-export INSTANCE-NAME path/to/output.zip -c -i -x -l [Edit] Use the -O switch to define the output file name. Use any of the options to specify what should be included in the capture: -c - config data; -i - indices; -l - log ...


5

If it was running before and not anymore now, and you didn't change anything in the configuration just before it stopped working, then the configuration is fine. My guess is something happened to the ability of the CMS connecting to the service end point address. Which could be several things: connection issues somewhere between the CMS and the service ...


5

As mentioned on the documentation page you linked, your attribute needs to be live for you to use it as a facet, sort by it, or filter by it. The example you gave would be a facet. So yes, you'll need to make it live and re-index. While you're at it, you should think about other attributes that you might want to use for these things in the future :)


5

You can use the Fredhopper preview page for this. The preview URL is something like this: http://localhost:8180/preview/?preview_seo=false&fh_location=//catalog01/en_US Just replace the fh_location parameter with the one from the log.


5

Complementary to oic's answer, there are two ways to run a query: The SmartTarget API runs the query against the REST API at http://localhost:8180/fredhopper/query (assuming the query server is on http://localhost:8180) So in your case the REST URL is http://localhost:8180/fredhopper/query?fh_location=//catalog01/en_US/categories<{catalog01_tcm_0_19_1}&...


5

Typically this means that the component tcm_54-14212-16 combined with its Component Template (CT) tcm_54-44540-32 is not present in the Fredhopper index. This can happen if you're missing the Add To SmartTarget TBB in your CT, or if your CT is not dynamic, or if the Component is not published. If you are using specific IDs in the Handpicked list in the ...


5

As David mentioned, one or more of the ports are already in use by some other process. So you can try to find out what that is and change its port. Or you could just use a different "preset" for your instances in topology.txt. The presets define all of the ports for the different Fredhopper services. So for instance, the Query Server for preset 1 uses port ...


5

In Linux the slashes have to be the other way around. In the root of your Fredhopper installation, type: ./bin/deployment-agent-client remove INSTANCE_NAME Be sure to stop the instance before that, using the same path separator.


5

There could be few things which you can check for the reason why your query is returning result while executing directly in fredhopper and not returning result in your application: Check the log of your application if your query is getting timed out. You default promotion with title containing "Do not remove" is present in fredhopper. Check your application ...


5

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 ...


5

You can start the sync client through the deployment agent: bin/deployment-agent-client invoke [instanceName] syncclient start Same goes for every other process (qserver, xmlloader, etc.). They can all be managed through the deployment agent.


5

The field is a remnant from earlier versions of SmartTarget where you were still using the Business Manager interface. It's basically there to give you an actual preview of the CP in the preview section of Fredhopper. It is no longer included by default in new installations, but if you upgraded from an older version it continues to do so for backwards-...


5

Yes, you can create a Scheduled Task (in the Windows Task Scheduler Library in Computer Management) which is configured to trigger on system startup and which doesn't require a logged in user. Let the Task execute a batch/command file which contains those statements.


Only top voted, non community-wiki answers of a minimum length are eligible