Thursday, November 03, 2011

Pimping out the Tridion 2011 Service Pack 1

We're getting ready to launch Service Pack 1 in the coming weeks, so I thought it would be a good time to start pimping it out.

What's new with Service Pack 1
New & improved installer (with flashy images while installing :))
User Generated Content (aka Community Builder) is integrated into the platform
Translation Manager is also integrated into the platform, and now includes support for both World Server and Translation Management System

Content Manager Changes
Grouping of items in CM calls - You can now read multiple items from the database with a single TOM.NET or CoreService call, instead of having to retrieve them individually.
Description fields are now included in GetItems and GetListItems calls, not requiring you to load the full objects before reading this property.
New "Ancestors" calls: You can get the whole hierarchy of "parent" items with one simple call: GetAncestors or GetListAncestors

Content Delivery Changes
The Content Delivery layout is much simplified, so you don't have to pick-and-mix files from here and there. Instead there are 7 roles for Content Delivery that are pre-defined for you:
  • API
  • Cache Channel Service
  • Content Deployer
  • Monitoring
  • User Generated Content
  • HTTP Upload
  • Content Delivery Web Service
Just add water, and your soup is ready. Speaking of Content Delivery Web Service, there is also a native .NET oData Web Service that runs on top of IIS in this release.

There are a gazillion little changes more though, like showing breadcrumbs on items in Tridion, consistency of RTF behaviors across browsers, and quite a few fixes to other issues that have been fixed before.

Interested in knowing more? Check it out here.


Andrey Marchuk said...

You can't read items in bunches.
What you can do is to call GetList on an array of IDs and get all the properties you could normally get in a list.

Another addition is that you now have a precompiled CoreService client assembly that you could (should) use instaed of service reference.

Nuno said...

Thanks Andrey, looks like I either misread the Release notes, or it's wrongly worded there.

Now that I have it installed I'll be able to find some other new stuff and I'll update this post.


Richard said...

Hi Nuno,

I am having trouble with the HTTP Upload (tomcat web server) writing to a database. The HTTP Upload keeps writing to a file. In my cd_storage_conf.xml file, I have the configuration to use a MSSQL as my storage and to use the MSSQL as my item type. I don't see any errors in the error log of invalid database connection. For some reason, it keeps writing to a file.


Nuno said...

When I get that one it's typically because I forgot to point my config to a correct license file.

If Tridion can't find a license file it will revert to "Default Bindings", meaning that everything goes on the file system.

Richard said...

Thanks Nuno, I still am struggling with this as it seems to always go to the Default Bindings. I have support looking into this matter now.

I have another question concerning architecture. Our company actually goes through 3000 to 4000 publishing changes a day. Our current architecture uses the content delivery file storage system and the web site is usually very slow and/or times out a lot due to cached memory objects being locked or files being overwritten and being locked. So we want to move to a database storage system instead of the file storage system to allow for better performance. The question that I have, is the Tridion deployer (tomcat application server) using the database storage a viable data warehouse solution where updates are done a record by record in the database? Or would it be better to have an existing database being updated by the Tridion deployer and have another separate database be updated through a data services ETL.


Nuno said...


This scenario (all in database) is used by some of our busiest clients without issues on performance.

It is also the model used by DD4T