Configuring <IndexServer>
The <IndexServer> element specifies connection details to the Fredhopper Index Server. The Index Server indexes data (for putting content into Fredhopper).
Procedure
- Open the
smarttarget_conf.xmlconfiguration file.The file is used in several locations in your installation: Where to find smarttarget_conf.xml
- In the
<IndexServer>element, define the following child elements:<Url>- The address of the machine where the Fredhopper Index Server is running.
-
The following example is for Fredhopper running on premise:
<Url>http://fredhopper.host:8180/</Url> - For an example of the URL for Fredhopper running in a hosted environment, see Installing SmartTarget in cloud.
<Authentication>-
Specify the
<username>and<password>of the user accessing the Fredhopper Index Server running in the cloud. You can encrypt the password using the SDL Tridion command line tool.Note: If Fredhopper is running on premise, the<username>and<password>is not needed. <Deployment>-
The location where the Content Deployer puts content published to Fredhopper.
<Location>-
If you installed Fredhopper on the same machine as your Content Delivery, you need to put content in the following directory (where Fredhopper picks files from up from):
<Location>BASE_DIRECTORY/INDEXER/data/fas-xml-incremental/CATALOG01</Location>Variable Description <BASE_DIRECTORY>The Fredhopper Deployment Package base directory, for example C:\fredhopper. Execute scripts in the <BASE_DIRECTORY>of the server.<INDEXER>The name of your Index Server specified in the topology.txtfile<CATALOG01>The name of your default universe. -
If you installed Fredhopper on a different machine than your Content Delivery, you need to point to the SmartTarget Deployment Web Service, for example:
<Location>http://Machine:8080/SmartTargetDeploymentWebService/SmartTargetDeploymentWebService?wsdl</Location>Note: You then need to specify the<Location>to put content in the SmartTargetDeploymentWebService_conf.xml configuration file. <InstanceName>-
The name of your Index Server instance, as defined in your Fredhopper
topology.txtfile. <KettleJobName>- The name of your kettle job on the Index Server. A Kettle job is a Fredhopper Data Manager job for enriching your data. A Kettle job has file extension .kjb.
- SmartTarget provides a default job: STJob.kjb. The job takes the package sent by the Content Deployer, verifies the format of the XML to check whether Fredhopper can handle the format, and places them in a file location where Index Server will pick up and process. The Content Deployer package provides reference information on Tridion Component Presentations in the Content Data Store.
The following is an example configuration of the<IndexServer>element:<IndexServer> <Url>http://Machine:8180/</Url> <Authentication> <Username>admin</Username> <Password>encrypted:56StnjmsTNnHdITMkL4KYw==</Password> </Authentication> <Deployment> <Location>http://Machine:8080/SmartTargetDeploymentWebService/SmartTargetDeploymentWebService?wsdl</Location> <InstanceName>INDEXER</InstanceName> <KettleJobName>STJob.kjb</KettleJobName> </Deployment> <Timeouts> <BatchActions>30000</BatchActions> <Localization>5000</Localization> <Promotions>5000</Promotions> <Triggers>5000</Triggers> <Deployment>30000</Deployment> </Timeouts> </IndexServer> - In the
<Timeouts>section, specify in the number of milliseconds SmartTarget waits before timing out in the following situations:<BatchActions>- The maximum time to take for batched actions such as the reordering of Promotions.
<Localization>- The maximum time to take retrieving the Segment titles that are displayed in the Business Manager instead of the Segment TCM URI value.
<Promotions>- The maximum time to take retrieving the list of Promotions from Fredhopper.
<Triggers>-
The maximum time to take retrieving the list of triggers from Fredhopper, as defined in the
trigger-types.xmlfile. <Deployment>- The maximum time to take deploying content to Fredhopper Access Server running in a hosted environment.
- Save and close
smarttarget_conf.xml.
Related tasks