8

You should be able to add a pipeline element after the "Tridion-Commit-TX" pipeline and before the Cleanup Step, which then should act as a PostCommit. In XO, the same happens: <!-- Add the following pipelines after the existing "Tridion-Commit-TX" pipelines --> <Pipeline Id="Tridion-Process-PostCommit" Action="Deploy" Verb="Process"> <...


8

I was able to fix the problem making this change on tcdl-conf.xml Old value: <Property Name="tcdl.target.language" Value="dotnet"/> New value (this fixed the problem) <Property Name="tcdl.page.target.language" Value="dotnet"/>


5

The bottom of your error states Placeholder value is found. Please specify valid configuration for State Store database. This means that the state configuration (which you can find in the cd_deployer_conf.xml contains some placeholder value (${...}) instead of an actual value. This is the state store configuration block : <State> <Storage ...


4

https://docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20Sites-v1/GUID-93347DFB-D6EB-4398-A78D-220B7FD685E3 Go to your Content Deployer's config\ folder, and open deployer-conf.xml for editing. Find the last Pipeline section in the file, and add the following two Pipeline sections below the last Pipeline section in the file: <Pipeline Id="Tridion-...


4

As far as I know, the state store DB contains the state of a publish transaction during that transaction, and this data is/can be removed once that transaction has successfully finished. This means that indeed, you can disable publishing, make sure all publish transactions are finished, set up a new state store db and reconfigure your microservices to point ...


4

As per DXA documentation , yes it is mandatory to publish it to database, SDL Docs Not valid, as it is not possible to publish to file system with out of the box DXA Topology manager maintains a link between CM and CD using a new Microservice called discovery.svc where we configure the deployer capabilities You can see the Topology Manager's CDEnvironment ...


4

In DXA implementation is it mandatory to publish everything to Broker DB? Yes, this is required. You could change DXA code to work around this, but it's probably going to be a lot of trouble. If we want to publish to file system where exactly we have to change it, cd_deployer_config? cd_storage_conf for the deployer. As said above, this will very likely ...


4

You are looking at the wrong documentation. Experience Optimization is part of Web 8.5 now and as such has been merged into the same documentation publication. You'll notice that there isn't a separate link for it anymore when 8.5 is selected in the drop-down list. The correct documentation page is therefore here: Adding Experience Optimization to Content ...


4

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. https://en.wikipedia.org/wiki/Byte_order_mark 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” I ...


3

Issue resolved after using JMSUri value below in the deployer-conf.xml files, where port 61616 is used instead of incorrect admin port 8161. tcp://localhost:61616 In hindsight, the FileSystem Adapter log entry was a red herring... Adapter was found, but was not the cause of error.


2

The XSD was updated where the second complexType above (PipelinesType) was actually PipelineType which conflicted from the first. We have no record of it being updated but it was. Having changed it (or re-copied the install version over it) and restarting the services we thought it would have been up to speed. Seems a Linux reboot did the trick!


2

The action TridionBootstrap from the original deployer-conf.xml file is missing. It should be between the initial <Pipelines> and <Pipeline Id="Tridion-Process-Deploy"... tags: <Pipeline Id="Tridion-Bootstrap" Action="TridionBootstrap" Verb="Content,Prepare,Commit"> <Steps> <Step Id="TridionUnzipStep"/> </Steps&...


1

Does the content publish eventually, if you wait long enough? The above could be just a warning, although not the most elegant way to put it. Otherwise it could still be masking a different reason this is happening.. I would try extending the transaction polling timeout for the transport service, here is how (referenced from this SDL Community article): ...


1

The problem here was that if one of the property value (for example password) contains $, then there is a problem resolving the value which results in this exception. Fixing this should resolve the error with loading State store configuration.


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