7
votes
Accepted
What is the Tridion.TopologyManager.Client endpoint
The easiest way to find out the endpoint URL is to check the Windows environment variable on the CM server using the following PowerShell command: get-item env:tridion_ttm_serviceurl
This should give ...
6
votes
Accepted
Publishing Component Template so it's queryable by oData
You could create a (dummy) Page based on a Page Template which collects and renders the required CT metadata of all CTs (in JSON or XML format).
Publishing the metadata of all CTs can be achieved by ...
5
votes
Can we use same OData Webservice instance to serve content from different Brokers
In short: no.
You can only bind one database to each service. May I ask why you're using 3 different brokers?
5
votes
Optimal way to expose Tridion content to external systems?
Whether creating a REST API over OData is a good option for you, nobody can answer but you I would say. Simply using a REST service is commonly accepted as one of the easier ways for external systems ...
4
votes
Why OData is missing some components with Filter criteria whereas it works fine if also provide the component Id in Query?
Maybe the problem is the number of results of the query.
By default the number of results are limited to 25, as it is configured in the cd_webservice_conf.xml
<OData>
<DefaultTop>25&...
4
votes
Accepted
Web service that queries Broker Database outside of SDL Web 8.5?
You need to connect to Content svc via CIL. Here are a couple links:
https://shahideqamuddin.blogspot.com/2017/11/getting-started-with-tridion-cil.html
https://community.sdl.com/product-groups/sdl-...
3
votes
Accepted
How can I successfully query the Content Service using its v4 odata endpoint?
So I finally figured it out... It was a combination of several things, but long story short, it had to do with my settings having the wrong encoding (assuming you had the rest of the setup correctly). ...
3
votes
Optimal way to expose Tridion content to external systems?
Update:
I see @Bart updated his answer. Here's my update in case someone is looking for info about that specific integration.
The Salesforce CMS Connect basic integration expect HTML from whatever ...
2
votes
WebApp Unable to retrieve OAuthToken in DXA 2.0
I figured out the answer to the problem I was having. Actually I had the problem in my /token.svc token expiration time. For example I had expiry time of 3 minutes and when a new call was invoked to ...
2
votes
Accepted
DXA 1.7 Experience Manager: Update Preview OData 403 Forbidden error
My first guess would be that your Preview Service (or Session-enabled Content Service) is not be correctly installed/configured, please note that it has a different cd_ambient_conf.xml than the DXA ...
2
votes
Publishing Component Template so it's queryable by oData
I am posting this as answer, and not as comment to your question because its easier this way. What we did is used TOM.NET API during rendering to extract all meta we need about component templates. ...
2
votes
Accepted
Update Preview is not working with XPM and DXA
The bindings in my web.xml was what was causing the issue with the ODATA service (a combination of how SSL termination happens in our load balancer and ODATA server). Thanks to Brandon (from SDL ...
2
votes
How can I successfully query the Content Service using its v4 odata endpoint?
I could be wrong, but I believe the v4 was never intended for public use.
2
votes
How can I successfully query the Content Service using its v4 odata endpoint?
I'm not sure if it's supported to directly use the v2 or v4 service endpoints. I always thought the CIL libraries know internally which service to use for a specific query.
2
votes
profiling and personalisation using microservice
As far as I know, the (legacy) Personalization & Profiling functionality is not exposed through SDL Web 8 CIL APIs, but only in the (deprecated) in-process APIs.
Note that Experience Optimization ...
1
vote
Accepted
Junk characters shown in Broker Database DCP publishing in SDL Web 8
I would like to point that content in Broker database is always encoded and it's correctly set as such. Since your Content.svc is returning properly decoded data, it means that problem is not in ...
1
vote
Accepted
Odata service querying results in special characters
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 ...
1
vote
Odata service querying results in special characters
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.
-->
<...
1
vote
Accepted
OData WebService (java) giving Error Result - Tridion 2013 SP1
Issue Solved:
only change in the url.
Below are the correct complete urls that works as expected:
http://myserver:11090/cd_webservice/odata.svc/ComponentPresentationshttp://myserver:11090/...
1
vote
ODATA : Query attributes in OData WebService
AFAIK, there is no baseline performance define for odata as it varies based on situation and amount of data odata service serves.So giving some generic guidelines:
The main parameters affecting ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
odata × 89content-delivery × 31
2013 × 14
2013-sp1 × 14
2011 × 13
web8 × 9
experience-manager × 9
broker × 9
java × 6
web8.5 × 5
ambient-data-framework × 5
dxa × 4
dd4t × 4
ugc × 4
sites-9 × 3
microservices × 3
dxa-2.0 × 2
configuration × 2
c# × 2
api × 2
session-preview × 2
content-service × 2
httpupload × 2
webservice × 2
core-service × 1