0

Following the SDL Web Experience Optimization 8 documentation, installing Fredhopper, while executing:

  • Step 5 [Open a command prompt and run the following command in the target folder to start the deployment agent: bin\deployment-agent]

    • Response : No response received.
  • Step 6 [Open up another command prompt and run the following command to create your instances as specified in the topology file (in this case, ExperienceOptimization and ExperienceOptimizationLive): bin\setup-cluster]

    • Response : Finished with Errors.
  • 1
    Your Response : Finished with Errors is rather vague, can you edit your question and give some details about what errors you are exactly getting? – Bart Koopman Mar 15 '17 at 11:48
  • 1
    I think that's the actual message he's receiving – Nuno Linhares Mar 15 '17 at 11:49
  • You need to look in the Fredhopper logs to find the actual errors. It might be nothing, but usually it means that something didn't work. – Peter Kjaer Mar 15 '17 at 13:04
  • BartKoopman as Nuno Linhares stated "Finished with errors" is my actual response. @PeterKjaer : I have checked the logs but nothing was stated regarding the issues. – Riyaaz Mar 15 '17 at 13:43
  • You should check all of the logs for every instance in your cluster, as well as the agent log. There will be an error in there somewhere -- otherwise you wouldn't be getting that message. – Peter Kjaer Mar 16 '17 at 7:35
-1

In the plain text file you creating you will be mentioning as defined in the sdl docs Installing Fredhopper Step 3 given below:

The topology file defines your indexing and live servers

instance name | host | preset | indexer | comment

ExperienceOptimization|localhost|1|-|Indexer and Preview environment for demo setup
ExperienceOptimizationLive|localhost|2|ExperienceOptimization|Live Query Server for demo setup

Instead try replacing the words

ExperienceOptimization| as indexer| and
ExperienceOptimizationLive| as query1|
which works fine creating the instance folder.

  • I'm having a hard time understanding this question and answer. It looks to me like you decided to name your instances differently than what the guide suggested and it didn't work because you weren't consistent in that naming (some commands still used the ones suggested in the guide)? – Peter Kjaer Mar 24 '17 at 14:57
-1

for first step there will not be any response on command prompt. after executing step 5 navigate to any browser and try to execute url http://localhost:8177

This might take some time(5-10 min) before it actually return status on browser.

Step No 6 usual doesn't gives any error if topology file is correct. Please share your topology file. Make sure to give required permissions(r/w) to the user to make modification in file system. Give a try after making changes to permissions.

Once you are able to hit 8177 port then execute your commands to start Indexer. If everything goes fine than you will be able to access fredhopper on http://localhost:8180 if setup has been configured correctly with preset 1 and 2.

Keep you cmd windows running in background

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.