Tridion 2013 vs 2011 SP1 architecture

16

Are there any specific changes under the hood in 2013 vs 2011 SP1 that are noteworthy from an architectural and installation point of view - for example I've heard COM+ has now been dropped for the CM?

mpaton

Posted 2013-03-14T13:15:58.297

Reputation: 767

Martin, perhaps check through these notes made by John winter, or even better the seminary provided by Nuno http://www.tridiondeveloper.com/sdl-tridion-2013-whats-new https://sdl.dist.sdlmedia.com/vms/distribution/?o=A437E6D1-FC2C-4A6C-AEAA-FCC2C1E89D78

– Dylan .. Mark Saunders – 2013-03-19T17:13:25.563

Answers

15

From an installation point of view, there is no more Database Manager tool, to install or upgrade the databases, you use PowerShell scripts.

Another thing to note for upgrades is that there is no Logging database for 2013 anymore, so on a fresh install you don't create one and for an upgrade you can drop that database.

COM+ is not installed by default, it has become optional in 2013 (its currently still there for backwards compatibility, but you have to specifically add it)

Bart Koopman

Posted 2013-03-14T13:15:58.297

Reputation: 29 724

15

One of the big things to note is that the Content Manager will only be supported on the following operating systems:

  • Windows Server 2012
  • Windows Server 2008 R2 SP1

This will mean that only 64bit operating systems are supported!

On top of this, it is worth noting that .NET version 2.0 will be deprecated on the Content Delivery side (from a .NET perspective), with only .NET v4 and v4.5 supported.

On the client side IE7 & IE8 will no longer be supported.

Jonathan Williams

Posted 2013-03-14T13:15:58.297

Reputation: 12 464

5

Architecturally - not much to see on the surface, but in the content manager server, most of the remaining COM+ libraries have been replaced by .NET implementations.

From an installation point of view, the most obvious thing I noticed was the disappearance of the logging database.

Dominic Cronin

Posted 2013-03-14T13:15:58.297

Reputation: 14 997

2

From a DB standpoint, the Items_states table is now merged into the Publish_states table

One of the biggest change is that the component_presentation table has been updated from ntext to nvarchar(MAX) type for the Content column.

2013 deployer now publish encoded or even strange Asian character into the broker database so you cannot query the component_presentation table directly. Fetching it via the new 2013 CD API will work fine though

Robert Jin

Posted 2013-03-14T13:15:58.297

Reputation: 802