Questions[tridion](server)

In a client's SDL Tridion 2009 SP1 implementation, I'm looking to publish some DCPs as HTML fragments onto the file store. This is because a current implementation uses ASCX components on the file store and we need to replace this functionality with HTML fragments as the output.

Looking in the 2009 SP1 Content Delivery Implementation Manual, there only appear to be 4 configuration settings that can be used within the Publication -> Dcp configuration node within the cd_broker_conf.xml file. These are:

• Jsp
• Asp
• Xml
• Txt

Is it possible to store DCP HTML fragments on the file store and if so, which config setting should be chosen?

I understand that I could just store these as .txt files, but I'd much prefer them to be .html files.

I am using DD4T on an SDL Tridion project and am using the following configuration in the storage config in order to publish Binaries (binaries in this case being anything store in Multimedia Components) to the filesystem but keep Pages in the Content Delivery database.

I am finding that as requirements change for what Binary files are needed e.g. the customer wants to offer Adobe Illustrator files for download, I am needing to add more types to the list by changing the config and restarting the deployer which is not ideal.

<ItemTypes defaultStorageId="defaultdb" cached="false">
    <Item typeMapping="Page" cached="false" storageId="defaultFile"/>

    <Publication Id="9" defaultStorageId="defaultdb" cached="true">
        <Item typeMapping="Binary" itemExtension=".jpg" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".gif" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".pdf" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".doc" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".docx" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".xls" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".xlsx" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".xlsm" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".jpeg" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".png" storageId="defaultFile" cached="true"/>
        <Item typeMapping="Binary" itemExtension=".ico" storageId="defaultFile" cached="true"/> 
    </Publication>
</ItemTypes>

Can anyone tell me if there is a way to change the above so that the contents of all Multimedia Components for the given publication go to the filesystem? I can't seem to find this in the documentation.

Just wanted to check as the after reading docs I'm not 100% sure but in our scenario we have a separate server with running the Deployer (HTTP Upload), a separate SQL Server with Broker on it and two presentation servers each with the API server role installed.

We want to take advantage of Tridion Object caching so

On each presentation server:

1. Installed CCS.
2. Update cd_storage_conf:
   • ObjectCache enabled = true
   • Add RemoteSynchronization entry pointing to the local Cache Channel service "localhost".
   • Set cached=true on ItemTypes I want to cache.

On Deployer server:

1. CCS not installed here.
2. Update cd_storage_conf:
   • ObjectCache enabled = true
   • Add RemoteSynchronization entry pointing to each of the Cache Channel services on the presentation servers.
   • Set cached=true on ItemTypes I want to cache.

I this correct? Basically I'm unsure if the CCS goes on each API server to be notified by the Deployer, or if it goes on the Deployer server and the API server point to it there?

Cheers

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.

Tridion 2011 centralizes all logging configuration in the logback.xml file. How do I configure the verbose logging of link resolving in Tridion 2011?

I do not think this is it, since it uses the DeployerLog. Am I missing something?

   <logger name="com.tridion.tcdl">
        <appender-ref ref="rollingDeployerLog"/>
   </logger>