Skip to main content

SDL Tridion: How to publish using SSHFTP publishing protocol?


I have had the chance to setup my SDL Tridion 2011 environment to use SSHFTP publishing protocol.

Such experience didn't come without its challenges and now that I got it working, I would like to share it in case someone needs to set this up in the future.

First of all, I had to setup the SSHFTP server and then the SSHFTP client to test if I can establish the connection successfully.

In this case, I have chosen coreftp server that I found fairly easy to configure. After installing this tool, setup a new SSHFTP server, as demonstrated below:



Ensure to specify the hostname and the port number, as well as, the certificate and the path to the directory to your incoming folder.

As a second step, add a user that can access the incoming folder, as shown in the image below:



The next step will be to ensure that your Deployer (running as a Windows Service) has its incoming folder configured to the same folder as the SSH FTP server. Navigate to your TRIDION_HOME\config\cd_deployer_conf.xml and change the incoming folder to the same as where your SSH FTP is listening, in my case:

 <Queue>
        <Location Path="c:\tridion\incoming" WindowSize="20" Workers="10" Cleanup="true" Interval="2s"/>
    </Queue>


This will allow that once the package arrives in the incoming folder, the deployer will start processing its contents. After applying this change, restart your Deployer.

Now you can use a client to test if you are able to connect successfully. Any SSH FTP client can be used, in my case I have used Filezilla.

You are now ready to configure your publication target on the CME, as the Transport Service needs to know where it should place the package for the SSHFTP and Deployer. In this case, I have configured the publication target as follows:



You should now be all set to publish using SSHFTP protocol!

Comments

RobertC said…
Nice article Rute. I'd also like to add that if publishing is failing to an SSHFTP target, confirm is there were any recent updates to the SSH on the server being published to. Recently a customer patched a UNIX system with an SSH update that broke our publishing.
Rute said…
Hi Robert,

Thank you for your post!
I wasn't aware that an update to the SSH could have such impact - so thank you for sharing this information, I will keep it in mind! Kind regards, Rute

Popular posts from this blog

SDL Tridion: Tips to troubleshoot and resolve the 'Throttling' status

The throttling status should be a temporary state, so although you might see some items in the Publishing Queue with that state, it should resolve itself once the deployer has available threads to pick up more packages. In case the items stay 'stuck' in this status, there are a few things you can check that I enumerate below:
·As mentioned in the documentation, ensure that the window size is equal to or larger than the total number of Transport Service threads configured on the Content Manager side. This settings can be found in the cd_transport_conf.xml, as follows:
<Workers NormalPriorityPoolSize="5" HighPriorityPoolSize="5" TransportPriorityPoolSize="5"/>
By default, this section is commented out and these are the default values. If the deployer’s window size is lower than 5 then you need to change it to ensure that it is set to 5 or higher.
·Check if the database maintenance tasks for the broker database are in place and the frequency tha…

SDL Tridion: How to enable Profiling and Personalization in 2013 using Tracking Keys

When attempting to setup Profiling and Personalization in Tridion, I have faced some challenges and once I was able to get it to work, I have made a small list of steps that were essential to finish this setup.

Here you can find the steps I have followed to be able to enable P&P in my SDL Tridion 2013 environment using Tracking Keys:

Add the cd_wai.jar to your deployer and website's lib folder;

Add the cd_wai_conf.xml to your deployer and website's config folder;

Update the cd_wai_conf.xml to include a reference to the host name, in other words, the location of your website. In my case, I have changed it to the following:

<Host Domain="localhost" Port="83" Protocol="http" Path="/"/>

In the same configuration file, ensure to enable Personalization, as follows:

<Personalization Enabled="true" Persistence="cookies">

Now in your CME, create your target groups, by selecting your publication folder where yo…

Tips for configuring the SDL Tridion Cache Channel Service

When installing and configuring cache, you may have one of these two scenarios below:
Scenario 1: The deployer, CCS and websites all reside in the same server
When the deployer, CCS and websites are running on the same server, open the cd_storage_conf.xml of one of these components and make the following changes: ·Enable caching by setting the following flag to true: <ObjectCache Enabled=“true"> ·Leave the RMI section commented out:
<!-- RMI CacheChannel Connector example <RemoteSynchronization Queuesize="128" ServiceMonitorInterval="10000" FlushCacheDuringDisconnectInterval="20000"> <Connector Class="com.tridion.cache.RMICacheChannelConnector" Host="127.0.0.1" Port="1099" /> </RemoteSynchronization>--> ·Enable the item types that you would like to cache, by explicitly adding the cached element and setting it to true:
<Item typeMapping="Metadata" cached="true"(..)/> <Item ty…