Recently spoke to SDL about this issue and they didn't really give me a good answer to solve this issue.
I found that a scheduled restart of the deployer service clears out the .tmp files but keeps the items it needs to work. Clearing out the folder completely stops the deployer from working until a restart is made.
You can also move the temporary tomcat ...
The IQ Combined Services (Index and Query) are designed to work with Elastic Search present in the DXD Stack. Index service indexes the data in Elastic Search and Query Service is used to query the data out of the Elastic Search. Both the services operate on the same Elastic Search instance.
Currently, Index Service doesn't support OAuth authentication but ...
In the content service, we have info endpoint .../content.svc which would show available services deployed. But this was not intended as a customer facing URL. Now since Authentication is enabled, ping to the services deployed is not working and hence you are not seeing available services.
However, you can still use/access individual service endpoints ...
After a lot of research, we found the following.
The microservices were installed on a Linux environment, and were started using SystemD scripts.
After investigating the /var/log/messages file, which contains various stdout output messages, including the messages created by the microservices, we noticed that the microservices crashed after an ...
After playing with install scripts, I was finally able to install services with domain URL containing context path. To help others with similar requirement, I am writing the steps to install service with a custom URL:
When services are installed as a window service:
Following changes required in installService.ps1
-Add spring boot variables to pass as a ...
I dug into the code and it appears as though while it says the DestinationName is optional, I was getting a null pointer in the code on it.
DestinationName The name of this particular Capability instance (optional)
I added a DestinationName for both of the capabilities, and then tried to register all of the capabilities which was successful.
for our demos we combined multiple microservices into one, getting closer to what we used in previous versions of SDL Web, since as you say it is for an all-in-one environment.
This helps saving a considerable amount of memory.
For instance you can have the roles Deployer, Content, Context and Preview in the same microservice, just by copying the ...
The error "incorrect function" is likely due to your Java installation being questionable (perhaps corrupted).
To verify to see if indeed this was caused by Java, do the below steps:
Go to c:\windows\system32\LogFile\Apache
There should be files with name starting as
commons-daemon.yyyy-mm-dd.log, look up the latest log (or try to
restart the service so ...
Interesting that you ask this question here, while it really isn't a Tridion related question (it would belong at https://superuser.com/, https://askubuntu.com, or equivalent), but I guess that is my opinion.
The answer is depending on your Linux distribution, but in general you can add the startup script to /etc/rc.local.
You can also create a full init ...
Avoid editing the scripts unless you really run into something that cannot be set with a parameter. You should be able to pass in parameters for everything, though.
Some common parameters:
--Name lets you set the short name of the service.
--DisplayName lets you set the user-friendly name (visible in the Services list)
--Description lets you set the ...
You can set -Duser.timezone=UTC in the JVM args when running your web application (on Tomcat or other) and this will fix the problem. Note that this may affect other date based functionality in your web application so be sure to test thoroughly that any part of the application that manipulates/displays dates is working correctly.
Note also that logging ...
This is expected behaviour as you shouldn’t be able to use the same url for two sites (within Topology Manager).
You’re going to have to either:
Specify a different port
Use a different hosts name (and probably update your hosts file /DNS), or
Use the machine name / machine IP Address (e.g. http://192.168.0.22:9080)
Try to use http://127.0.0.1:9080
It looks like you are using an IBM JVM (at com.ibm.jsse2.k.a(k.java:24)).
This JVM has some specific setting that allows you to enable or disable use of TLS V1.2.
This is explained here https://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.security.component.80.doc/security-component/jsse2Docs/matchsslcontext_tls.html#matchsslcontext_tls
If you want to use XO features in the mobileApp and already using DXA, there is an OOTB option available,
Create a mobile page in Tridion and publish it to dxa webapp. Use DXA webapp to generate json response and consume it in the mobile app (eg: http://mydxawebapp.com?format=json).
In that way you can achieve all the XO features OOTB from tridion and ...
The Content Delivery microservices are currently only accessible through the CIL (as explained here http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v5/GUID-A2A47810-D27A-40CA-8C22-CCDC224AF81C), which means that you will have to use the SDL Web Content Delivery API, and thus its jars or assemblies (available via Maven or NuGet) in your mobile ...
Detailed description of Roles is documented here.
registration user is used only for registering capabilities in discovery service.
When setting up topology, you need to use cmuser Reference here
For retrieving content (CD side), you should be using cduser
Also you can check this on Roles
One of the use case of Roles is to shield certain resources (endpoints) of services from Read/Write operations. For example, when we have OAuth & Rules enabled (in cd_ambient_conf.xml), only users in CD and implementer roles can perform GET/POST requests on content service.
The provider role is used when registering capabilities with discovery service (...
In our case, port 8081 is used for something else, so it is not available for deployer service. Therefore we did not use quickinstall script. We install each service separately. Before you run installService.ps1 for each service, you can edit the script and change to your port number and run it.
Linux systems come in more or less two main flavours: those whose startup is governed by SystemV init.d scripts, and those which use the more modern SystemD
The details of getting your services to start on startup are not really a Tridion question, but a generic Unix/Linux one. So the answer is "Yes - it is possible to automate starting a script at system ...
For an official answer you probably need to go through official channels (Customer Support).
Judging by the Pre-Requisites for Content Delivery Microservices you need Java 8 and a supported OS - no word about Docker or Azure Service Fabric.
The official answer from SDL support
Case 00308815 12 October 2017 11:56
Subject: CD Micro Services Support on cloud platforms
"As long as you are building containers from our on-premise artifacts,
then we support them. In a future release, we are planning to provide
pre-built docker images of all of our services for customers wishing
Tridion XML configuration files are often manually edited. If you do this, you must always use a TEXT Only editor otherwise your file may get saved with a BOM.
The Byte Order Mark (BOM) is not handled by Java Xerces XML Parser.
So you get a Configuration Exception “Content is not allowed in prolog”
When hitting the Content service directly the response passes only through tomcat. When hitting it via the load-balancer it passes through Apache too.
In our Content service start.sh we already define:
That's why it works directly.
To fix it via the load balancer we also need to allow encoded ...
Yes you can. As Nuno mentions in his comment, you may opt not to use the CIL library in your web application and use a Web Service Reference to directly connect to the OData Content Delivery service. This means that you can rig up your own logic to determine when and where to make the connection.
Tridion's (SDL Web's) OData implementation follows the OData ...
Hotfix CD_188.8.131.5243 should resolve this issue (both file system and database deployments).
It is also possible to add the line below to the application.properties file located in the config folder and change where the files are written.
So with this change, the tmp files will be written to the specified ...