If you already installed CME and Publisher servers then try the following script to add
Enabling Add-ons Service integration with existing Content Manager servers
.\EnableAddOnService.ps1 -AddOnServiceUrl http://
localhost:83 -AccessManagementUrl http://localhost:85/access-management/connect/token -ClientId fc96aed3-b20e-4dd3-a345-
DXD loading mechanism – DXD is loading extensions on service startup. - No support of loading on the fly
After the extensions and configuration have been uploaded to the Add-on Service, the connector/extension is deployed in CM and DXD.
The CM connector will pick up the connector and deploy it on the fly, while the DXD service needs to be restarted to get ...
It seems indeed that custom resolver addons are executed BEFORE any OOTB resolvers (standard and DXA)
There is currently no way to control that custom resolver addons are executed AFTER all other (OOTB) resolvers.
There is currently no way to control the execution order of multiple custom resolver addons.
We have requested fixes/enhancements with CS.
The solution to our problem was to change the
var pubTarget = new PublicationTarget(new TcmUri(_tcmPreview), item.Session);
var pubTarget = new TargetType(new TcmUri(_tcmPreview), item.Session)
Seems that in the version 9.5 PublicationTarget is not needed anymore
Yes. It's possible to Configure Add-On Service on the Content Manager side to install the SDL Tridion Sites by scripted to install silently then it is required to pass
Indeed, The documentation it was missing, I will raise this internally to update the documentation, also left the comment in the documentation section.