1

I am trying to query odata service in SDL Web 8.1. While querying I am getting special characters as result in the browser. Please let me know if anything going incorrect in the configuration.

Regards

  • Please edit your question and provide bit more detail about your issues like input and output screenshots may help to understand your issue better to help you – Velmurugan Sep 24 '18 at 7:53
  • Hi, We have recently upgraded one of our CMS environment from SDL Tridion 2011 SP1 to SDL Web 8.1. We were using OData service for content querying in SDL Tridion 2011 SP1. After upgrade to SDL web 8.1, I am trying to query same OData service, I am getting results but the Presentation Content is not showing the actual content instead its showing special characters. Please let me know if this clarifies. – user2166 Sep 24 '18 at 8:04
  • @Velmurugan, as of now I am not able to capture the screenshots as required by you, I'll try to add ASAP. – user2166 Sep 24 '18 at 8:23
  • Maybe you have not configured encoding on either on odata service or webapp, could you please double check? – Velmurugan Sep 24 '18 at 8:57
  • Hi, I am accessing the OData service in Browser and as of now not consuming in any web application. I have checked the encoding for OData web service and its UTF-8. Further can you please suggest me where else I need to check the encoding configuration values. – user2166 Sep 24 '18 at 9:14
1

To enable encoding to use the jvm.xml in your Content Delivery services config folder something like:

<!--
This file can be used to send application specific JVM arguments.
-->
<VirtualMachine>
  <Options>
    <!--
    Add the Option tag to define specific JVM options.
    The Option tag can define the MaximumHeapSizeInMB (-Xmx), the InitialHeapSizeInMB (-Xms) and other JVM properties(-D).
    -->
    <!-- 
    <Option Name="-Xmx" Value="400m"/>
    <Option Name="-Xms" Value="50m"/>
    -->
    <Option Name="-Dfile.encoding" Value="UTF-8"/>
  </Options>
</VirtualMachine>
| improve this answer | |
  • I tried your suggestions but seems no luck. Any suggestions further? – user2166 Sep 25 '18 at 13:07
1

As I was not able to find any direct fix for OData.svc itself, I tried the suggested solution provided in the SDL Web 8 documentation SDL Web 8. I created a reverse proxy url rewrite module which directed all requests coming to Odata.svc to Content.svc microservice. This seems to solve the problem.

| 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.