Tridion 2011 SP1 HR1 - sending content to SmartTarget/Fredhopper
We're setting up SmartTarget/Fredhopper in our Tridion 2011 SP1 HR1 environment and have hit a snag - hence the question!
- CM is configured correctly and we can see the
<SmartTarget addToFredhopper="true"/>entry in the package sent to the deployer. - Logging is configured at DEBUG level for the deployer and we can see an entry in the smarttarget log:
2013-01-23 10:46:08,148 INFO FredhopperDeployerModule - Start deploying transport package 'D:\Tridion\incoming\Zip\tcm_0-22268-66560.Content\' to Fredhopper.
- Sadly nothing appears in Fredhopper though - the publishing queue gets stuck at the Committing Deployment phase until it eventually fails with an "exceed polling error".
Fredhopper is installed on a different server so we're using the SmartTarget Web service (non-J2EE & Tomcat) and have configured this in the smarttarget_conf.xml:
Location>http://server:8080/SmartTargetDeploymentWebService/SmartTargetDeploymentWebService?wsdl</Location>
A quick check ofthis URL in a browser succesfully responds with the WSDL. We've also configured the service to a DEBUG level but no log file is ever written, suggesting the deployer never successsfully sends anything to it.
So:
- Fredhopper installed - Check
- SmartTarget Web Service (Tomcat) - Check
- Publishing - Check
- Deployer - Configured correctly, but unable to reach the Web Service by the look of it?
Can anyone advice on next steps to check or anything obvious we've missed?
UPDATE_
Additional information from the core log - there seems to be an unable to execute onSuccess in here, that looks a bit suspect!
2013-01-23 14:53:12,094 INFO FredhopperDeployerModule - Start deploying transport package 'D:\Tridion\incoming\Zip\tcm_0-22272-66560.Content\' to Fredhopper.
2013-01-23 14:53:12,109 DEBUG RMICacheChannelConnector - Broadcasting event finished for key: 67:17789:17791
2013-01-23 14:53:12,250 ERROR DeployPipelineExecutor - Unable to execute onSuccess event in phase: Deployment Commit Phase for transaction: tcm:0-22272-66560
2013-01-23 14:53:12,250 DEBUG DeployPipelineExecutor - Checking if transaction is completed: tcm:0-22272-66560 is false
2013-01-23 14:53:12,250 INFO DeployPipelineExecutor - Finished executing deployment pipeline for: tcm:0-22272-66560 in 17722 ms.
2013-01-23 14:53:12,250 INFO TransactionManager - Cleaning up Deployment package for transaction: tcm:0-22272-66560 and type: CONTENT
2013-01-23 14:53:12,265 INFO TransactionManager - Finished handling of Deployment package: tcm:0-22272-66560 with type: CONTENT
2013-01-23 14:53:12,265 DEBUG QueueLocationHandler - Removing from queue Deployment package: tcm:0-22272-66560 with type: CONTENT.
2013-01-23 14:53:12,265 DEBUG QueueLocationHandler - Removing exclusive lock on Deployment package: tcm:0-22272-66560 with type: CONTENT. 2013-01-23 14:53:12,265 DEBUG QueueLocationHandler - Removed exclusive lock on Deployment package: tcm:0-22272-66560 with type: CONTENT.
Is the SmartTarget Publisher Extension installed correctly?
In your Transport Package there should be a section in the component_presentations.xml with extra information. That information is filled by said Publisher Extension.
I would double-check the location for storing the XML files in the properties file of the deployment web service. Then make sure that it can write to that location (use a monitoring tool to check this)
It's supposed to handle errors correctly (and log them) but maybe something is going wrong there.
What happens if you change it from using the deployment web service to storing the XML files on a location on the same server? Does it create the file and does the publishing continue? This would give a clue as to where the problem lies...