Hot answers tagged

5

It seems you're asking two questions. Do we need to apply the cumulative update Yes. It clearly states (on the link provide by Atila) that you can upgrade from SDL Web 8 "with Cumulative Update 1 applied". I'd suggest it probably makes sense to apply the cumulative update anyway - it's likely you're simply working around a few problems (or even unaware ...


4

Rolling upgrades are only supported and tested from the previous point release. In this case it means that a rolling upgrade from 9.0 > 9.1 is supported and everything else isn’t. So, in total, supported: 8.5 -> 9.0 9.0->9.1 9.1->9.5 From 8.5 to 9.1 you'll have to be creative and press on with the upgrade. The most viable route might be a staged upgrade ...


3

If you are provisioning new app servers from scratch, then upgrade of the app servers is obviously not applicable. However, you will have to upgrade your DBs to 8.1.1 first to ensure your uograde to 9.0 is supported (the direct upgrade path has simply not been tested by SDL). Furthermore, it makes sense to upgrade at least one app server to 8.1.1 too, to ...


3

After some debugging, we finally found that the database server was provisioned in a different datacenter, causing some latency. Since the discovery service is making a lot of database calls for one request (especially if you have a lot of publication mappings/websites), this latency (even very small latency) adds up and causes a long wait time. Moving the ...


2

Watch this space Mr Williams. I checked this very question out at he Benelux user group and the answer was that it would ‘PROBABLY’ work for 8.5 to 9.1. I expressed my concern should it be minor versions for the simple fact that most clients (and of course I’m excluding cloud clients here) are reluctant to upgrade to the first version of a new major (and ...


2

Remembering the Sites 9 Technical Readiness webinar, it was said that rolling upgrades will only be possible 1 "version" at a time. They didn't specify major or minor, but it makes sense that that "limitation" will apply to both. In other words, you won't be able to directly upgrade to 9.1 (using the rolling approach), but instead will have to do 2 rolling ...


2

The recommended way is to autowire the databinder into your controller using Spring, using the @Autowired annotation.


2

Looking at the error, it seems that there is a blueprint conflict. The error actually tells you which items is the conflicting one: tcm:373-156169-1024. It seems that such keyword exists at a lower level (or higher) level in the blueprint from where the script is attempting to create it. Make sure that the level of the blueprint you are importing items ...


2

From a high-level perspective, here are the main areas you would need to consider. First, look at the Windows Server and Software pre-requisites. If you are considering using the SDL Cloud, you would not need to worry about the CMS pre-requisites, and possibly CD, depending on the Cloud option you choose. However, if you still will host everything on-...


1

Welcome to stackexchange. docs.sdl.com is obviously a starting point :). However 2011 SP1 to Sites 9 is a major upgrade (skipping 2013, 2013 SP1, Web 8, Web 8.5). There are numerous strategies to choose from with the newer software. I strongly recommend that you get an upgrade report or assessment performed by SDL in your environment to come up with a high-...


1

It is my understanding that you can upgrade from 8.1 See the list of available version from which you can upgrade to Sites 9 here. What you cannot do from that version is a "direct" rolling upgrade to Sites 9. Those are supported starting Web 8.5. But if you have any doubts, you can always check with SDL support.


Only top voted, non community-wiki answers of a minimum length are eligible