1

I'm in the process of upgrading my services from 8.1.1 to 8.5, and I have discovered that when attempting to register my capabilities, I get an ODataUnmarshelling exception with the following:

Caused by: com.sdl.odata.api.unmarshaller.ODataUnmarshallingException: The request body contains a property that does not exist in the structured type: Tridion.WebDelivery.Platform.DeployerCapability, property: strategy

In my storage config, the deployer capability is configured as follows: 

<Role Name="DeployerCapability" Url="http://localhost:9084/httpupload">
    <Property Name="encoding" Value="UTF-8"/>
</Role>

So where is the strategy coming from and why doesn't the discovery-registration tool understand it? I had a poke around in the discovery database, but couldn't find anything likely in there.

Improve this question
2
  • 1
    Is the discovery-registration tool is also 8.5 ? strategy is new config option added for deployer capability config.
    – vinayknl
    Mar 3, 2017 at 20:32
  • You nailed it. Another victim of the unfortunate "xcopy upgrade" strategy. I copied the jar over from the release zip and it's working fine again. Still puzzled about where the property was coming from though. Anyway - if you add that as an answer, I'll accept it. Thanks
    – Dominic Cronin ♦
    Mar 3, 2017 at 21:27

1 Answer 1

Reset to default
2

We need to use 8.5 discovery registration tool against 8.5 discovery service.

In 8.5, Deployer capability entity has additional configuration point (strategy) which is used to configure multiple deployer end point. Due to this change in entity data model, 8.5 registration tool is required.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.