Known issues in staged-upgrade setups
If you perform a staged upgrade, some issues are known to arise, depending on the version from which you upgrade, and depending on which part (Content Manager or Content Delivery) you upgrade first.
All older versions with SDL Web 8.5 Content Delivery
- OAuth authentication cannot be used in conjunction with the Ambient Data Framework in Content Deployer
-
You need to disable OAuth in the Ambient Data Framework configuration file, cd_ambient_conf.xml, that you include with Content Deployer.
- OAuth authentication cannot be used in conjunction with User Generated Content
-
You need to disable OAuth in the User Generated Content (UGC) feature.
- Experience Manager functionality requires workaround
-
This problem is the result of a change in the name of the endpoint, from odata.svc to preview.svc. You can work around this problem in two ways.
First, you could set up a reverse proxy that forwards all requests aimed at odata.svc to preview.svc. To create a reverse proxy, in IIS Manager, create an empty Web site with the following Web.config file:<?xml version="1.0" encoding="UTF-8"?> <configuration> <system.webServer> <directoryBrowse enabled="true", showFlags="Date, Time, Size, Extension, LongDate" /> <handlers> <remove name="svc-ISAPI-4.0_32bit" /> <remove name="svc-ISAPI-4.0_64bit" /> <remove name="svc-Integrated" /> <remove name="svc-ISAPI-2.0" /> <remove name="svc-Integrated-4.0" /> <remove name="svc-ISAPI-2.0-64" /> </handlers> </system.webServer> </configuration>In the Web site, inside your Web application, create a new child Web application that points to a folder called odata.svc, and give it the following Web.config:<?xml version="1.0" encoding="UTF-8"?> <configuration> <system.webServer> <rewrite> <rules> <remove name="ReverseProxyInboundRule1" /> <rule name="ReverseProxyInboundRule1" stopProcessing="true"> <match url="(.*)" /> <action type="Rewrite" url="http://HOST:PORT/ws/preview.svc/{R:1}" logRewrittenUrl="true" /> </rule> </rules> </rewrite> </system.webServer> </configuration>where HOST and PORT identify the base URL of the Preview Service.
After you start this Web site, Experience Manager functions normally.
Alternatively, you could specify the new preview.svc in Content Manager Explorer. To do so, access the Content Manager Explorer Web site and open the Publication Target associated with your Experience Manager Web site. In the dialog that opens, select the Session Preview tab and modify the Content Delivery Endpoint URL to the URL of your Experience Manager Web service end point, that is, https://HOST:PORT/ws/preview.svc, where HOST is the host name of the machine on which the Experience Manager Web service end point runs, and PORT is its port.
- Audience Manager and Experience Optimization (formerly SmartTarget) do not work
-
These additional product features do not work while the staged upgrade is in effect.
Content Manager 2011 SP1 with SDL Web 8.5 Content Delivery
The following issues are known to arise if you use this stage-upgrade setup:
- Transaction package not removed
- If a transport package is too large for HTTP transport and leads to a publish failure, the transport package may not be removed from the location %TRIDION_HOME%\bin\transactions\. To work around this problem, ensure that your Web server is set up to handle sufficiently large packages.
- Publish Queue lists successful mass publish actions as failed
- When performing a successful mass publish (3000-4000 transactions or more), the Publish Queue may fail to show the actual successful state and instead continue to show a Waiting for deployment or a Waiting for transport state, eventually resulting in a Failed state.
- Publishing may report success of a huge publish action even though it partially failed
-
If publishing of a Structure Group containing 500 Pages partially fails (that is, not all Pages are successfully published), the transaction may still return a Success status. To work around this problem, increase your transaction timeout value.
- Scheduled publish fails if generation of publishable content and placing content online are scheduled simultaneously
-
If you schedule a publish or unpublish action using the Publish Content Later option, generating publishable content (phase 1) and placing content online (phase 2) are set to occur at the same moment. This may cause publishing or unpublishing to fail.
To work around this problem, schedule the two phases separately using the Schedule Publish Phases Separately option in the Publish or Unpublish dialog. Select the options Generate Publishable Content Later and Place Content Online Later, and set the first of these options to an earlier time than the second one.
Content Manager 2013 with SDL Web 8.5 Content Delivery
No issues are known to arise in this staged-upgrade setup.
Content Manager 2013 SP1 with SDL Web 8.5 Content Delivery
No issues are known to arise in this staged-upgrade setup.