16

I would use the token service to test the other two, thus ensuring that all 3 of them are working. To do so, though, you need to be able to create a specific HTTP request, setting the method and headers, etc. There are lots of tools out there; I typically use the Postman Chrome extension. Test the token service by getting a token you can use with the other ...


10

If you don't see any other errors, I'm guessing it is a port conflict. The default port for the Content Service is 8081; perhaps something else on your machine is already running on that port. You can check that using PowerShell: Get-NetTCPConnection | where { $_.LocalPort -eq 8081} If that returns anything, there is something running on that port. (You ...


9

The Content Interaction Library (CIL) is the public API to the REST service providing a native JAVA or .NET interface for the developers, so yes - today the recommended way to program against our REST services is to use the CIL. In the near future we will open up the REST endpoints as a public API, the reason why we chose to move first with the CIL is to ...


9

Solved it, I re-ran: Java –jar discovery-registration.jar update located in the /config folder of my discovery service :)


8

Your assumption that the first two responses are OK, but the third is not is correct. When OAuth is enabled (the default), all CD microservices (except the token service) expect an OAuth bearer token in the HTTP Authorization header (as described by Peter) and will return an invalid grant error if such a bearer token is not provided. If you get such a ...


6

You ask for code samples: the point of the CIL is that any code samples for the previous version of Content Delivery ought to work just fine. CIL is intended as a drop-in replacement. The most obvious example of its use in an open-source project is in DD4T. It's a bit of a specialised example, but perhaps interesting nonetheless: https://github.com/dd4t/...


5

I guess your CIS services run on a different machine than your web application. In that case, it is important that your CIS capabilities are not registered with localhost URLs. The web app will contact the Discovery Service to retrieve the URL of the Content Service (and other CIS Services). If those are registered with localhost URLs, the web app will ...


4

Example: using log4net; using System; using System.Collections.Generic; using Tridion.ContentDelivery.DynamicContent.Query; namespace SDL.CIL.Test { internal static class Program { private static readonly ILog Log = LogManager.GetLogger(typeof(Program)); private static void Main(string[] args) { Query query = ...


4

Hotfix CD_11.0.0.13730.zip is now available for this issue (via FTP or it can be requested from Support as well).


4

As Rick mentioned, my Deployer Storage config had these lines: <ItemTypes cached="true" defaultStorageId="reldeployerdb"> <Item cached="true" storageId="relpublishedfiles" typeMapping="Page"/> <Item cached="true" storageId="relpublishedfiles" typeMapping="Binary"/> <Publication Id="84" cached="true" defaultStorageId="...


4

The error was the symbol '-' in app.config in keys oauth‐client‐id, and oauth‐client‐secret, it's binary representation was not correct.


3

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). However, these are the things I tried and hope that might help others when having issues connecting to the odata v4 (or v2 for that matter), using the CIL ...


2

To test the Discovery service you need to get a token from the Token Service and then use the access_token to call the Discovery service (or other services you want to test). Here is how I did this with PowerShell. (you will need to add error handers) I used this method so that I can automate the service installation and testing. But Now I use Dominic's ...


2

I had the same issue. I realized that the content service has a dependency on the directory service name... in the installService.ps1, I had to modify this line $arguments += "++DependsOn=SDLWebDiscoveryServiceLive" as I had changed the default name of the discovery services.


2

I could be wrong, but I believe the v4 was never intended for public use.


2

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

After looking through all of the API calls and attempting each one of them to see the kind of results I could get, I determined that this is not possible with the content service's Odata API. Here are a few possible solutions to get around this issue: Update the component template to include the keyword inside of it (usually in an HMTL comment so that it ...


2

I get similar results in my Sites 9 setup. It could be a bug because I also cannot filter on keyword title, only on keyword key. However you can request the Keyword key to be part of the response: { categories(namespaceId: 1, publicationId: 5) { edges { cursor, node { itemId, title, itemType, children { edges { cursor, ...


2

It works for me, I'm able to reproduce this issue my side. if the graphql query used variables in parameters then always expected to send the value of the query variables to be {}. if we pass query variables value to be null then this issue occurs. Expected Request: {"query":"query myquery($uri: String = \"tcm:5-394-64\") \n{ \n page (cmUri:$uri) {\...


2

Your question is not clear to me what exactly you're trying to do and what is your expected output. For my understanding, you have upgraded your DXA web app from DXA 1.5 to DXA 1.8 with web-8.5 and your web app not getting downloaded your publish settings media system config files. eg: \BinaryData\826\system\config_all.json Try this below URL using ...


1

The error is caused by the fact that customMeta/valueType = null


1

I have seen this type of problem before. In our case the problem was due to schema changes. When a schema metadata field data type has been changed you must update all components using the schema republish items using the schema Check the metadata field type in the broker database to verify that all of the published metadata is the correct type.


1

Answer to your question, yes, Indeed It's expected and executed when a new session starts, onRequestStart at the beginning of each request, onRequestEnd at the ending of each request if ADF enabled, yes it can disable. In Java web app web.xml comment out this section to disable Ambient Data Framework if you use CIL. <filter> <filter-name>...


1

It is a bit of a lame answer perhaps, but since the DXA team is building both the DXA Java and the DXA .NET web application, yes we have some experience with sharing a design. Also looking forward with DXA 2.0, we plan to add support for Client Side JavaScript frameworks through the Model Service. But in general, it shouldn't be a very hard task to align all ...


1

Well, in my opinion the best practice mainly depends on whether you opt for CMS Baked/fried approach. Do you want to maintain the HTML Mark in component template or you just need a reference to the markup mentioned in component template(DXA way). Finding a general solution to maintain the HTML Design for both together is going to be tricky as they differ ...


1

I have also faced the similar issue when I was installing my content delivery components for single-machine installation by following this doc. I was verifying my installations after installing discovery, deployer, session-enabled content service. My discovery service was not running, whenever I was starting the service it shuts down after few seconds ...


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