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 ...


15

Most likely your Dynamic Component Template output type is set to HTML Fragment. This instructs Tridion to not do anything with the rendered output as it is plain static HTML. Change your template output type to REL when storing DCPs in the database, or JSP Scripting if storing them on the filesystem.


14

As @Likhan is mentioning in his answer, it seems that the information is saved in Unicode/UTF16 so it needs to be decoded using other Encoding like iso-8859-1. I developed a workaround for it developing a SQL CLR Stored Procedure SQL CLR STORED PROCEDURE public partial class StoredProcedures { [SqlProcedure] public static void ...


14

Chris hits a few of the main differences between the CWA and DD4T project. My view is a bit simpler, so I'll share it too. In a Tridion implementation your content lives (at least) three places: in the Content Manager database as XML in the Content Delivery broker in the visitor's browser as HTML Tridion systems architecture +----------+ +---...


13

The problem here is that it is an unpublish operation and no templates are executed and we cannot use the AddInstructions method available in the RenderedItem class. As an alternative there is a non documented extension point called a TransportHandler, you need to implement the ITransportHandler interface that is located in a GAC assmebly Tridion....


13

As far as I know since Tridion 2013 the encoding in database for content field has changed for mssql. You no longer will be able to do select on database to see the content anymore. I have seen around floating somewhere a query which can decode it for human readable view. Will try to look it up. However, even if the content cannot be seen properly in ...


13

You can get readable content from the COMPONENT_PRESENTATION table directly in sql by double converting the content field like this: SELECT CONVERT(varchar(max),CONVERT(varbinary(max),content)) FROM COMPONENT_PRESENTATIONS WHERE <where_clause>


13

Yes you can re-use the Broker database for the discovery-service. The reason why we provide it separately is so in the future we can have different options. You can imagine you can register different capabilities in the discovery-service that perhaps do not require a broker db in the future. Also putting this in a different database offers different ...


13

The short answer is "Follow the documentation". I would say 95% of implementations are distributed between CM and CD machines (and often more with dedicated GUI, Search, Publishing and DB on the CM side), normally with a firewall between them and the CD side (which is built for even more distribution between caching, deploying, rendering and presenting ...


12

From your description, I suspect you may have cache enabled on your app servers, but not using (or not correctly configured) the Cache Channel Service. There's some info on the Tridion object Cache on Tridion World and also on SDL Live Content (login required) Update The configuration seems OK as far as I can remember the 2009 config... can you double ...


12

Tridion supports any MQ product that adheres to the JMS specification. Keep in mind that JMS has two modes: MDB (Message Drive Bean) Simple Messaging Tridion supports both, but your specific MQ product may not support both modes (last I saw, Websphere only supported MDB by default).


12

No, it is not OK - unless they use the exact same configuration files, including storage locations. I've done this before by mistake, and only noticed what happened when I saw XPM tags in the live website. Basically, whichever deployer starts first will load the configuration into memory, and this stays on. If you have different configurations - which you ...


11

You can use the ComponentMetaFactory class to interrogate the metadata of your component. Criteria c1 = new ItemTitleCriteria("MC%", Criteria.Like); //Create query Query myQuery = new Query(c1); String[] itemURIs = myQuery.ExecuteQuery(); ComponentPresentationAssembler cpAssembler = new ComponentPresentationAssembler(); ComponentMetaFactory cmFactory = ...


11

Check your storage configuration (cd_storage_conf.xml or cd_broker_conf.xml for older systems), specifically the storage location for ComponentPresentation items with item extension ".ascx" You need to ensure that you are publishing your ASCX web controls to the file system and to somewhere within your web application in order that .Net will execute them. ...


11

It sounds to me like you are trying to rewrite functionality which already exists in Tridion, namely dynamic linking. If you use the Default Finish Actions TBB your published page or component presentation output will contain TCDL tags, which on deployment get transformed into JSP code for the standard Tridion dynamic linking taglib (which does exactly what ...


11

The problem was caused by the single dll file: xmogrt.dll The problem was that somehow my application had the 32 bit version, when I needed to add the 64 bit. Note: The file size of the 64 version is 1,123kb, the 32bit version is less.


10

The protocol of deployment is setup in the Publication Target on the CMS, this is done under Destinations in the General tab of the Publication Target. The configuration of the Deployer is just specifying where to pick the transport packages up from, unless it is a HTTP/HTTPS Deployer, then the protocol is depending on the setup of the website (either HTTP ...


10

You can try this to enable debug level log at Hibernate. <logger name="org.hibernate" level=”debug”> <appender-ref ref="rollingHibernateLog"/> </logger> rollingHibernateLog –must be also defined in logback.xml


10

By changing the settings in cd_storage_conf.xml so that the default storage area my local file store I found an ascx file corresponding to my component presentation. Once this was present my page was correctly rendered. <Storage Type="filesystem" Class="com.tridion.storage.filesystem.FSDAOFactory" Id="defaultFile" defaultFilesystem="false"...


10

This is where the complexity of Content Modeling really comes around the corner. There are several approaches to a certain problem, and each one of those will have pros and cons. It is well accepted to place things like a page title, description and keywords in Page Metadata. For a multi language BluePrint it is unwanted to have a need to localize Pages for ...


10

Functionally there are some differences: KeywordCriteria allows string arrays (several keywords to be queried at once). So in one query, you can retrieve all items that are tagged with any of those keywords; TaxonomyKeywordNameCriteria allows query on branches of a keyword. So in one query, you can retrieve all items that are tagged with the keyword you ...


10

Not sure why do you want to get this information from the Tridion Config file but you may follow below steps to get the versions - For Content Manager: you can check the "About SDL Tridion" tab in the Dashboard as shown below Alternatively, you may click on the top-right corner SDL | Tridion text to open a pop-up and see the version as shown below: For ...


10

This problem can be resolved by simply checking the cd_deployer_conf.xml file within the deploying application, the incorrect property <TCDLEngine> <Properties> <property Name="aspnet.tagprefix" Value="smarttarget" /> Should become: <TCDLEngine> <Properties> <property Name="aspnet.tagprefix" Value="tridion" /> ...


10

Apart from Pankaj's reasons, also consider the following: In a production (live) environment, you wouldn't want the CM database running on the front end for security reasons. The usual setup is that the back end system, in this case the Tridion CM is running completely behind a firewall and in a different network than your front end servers, which need the ...


10

There's no reason why you still can't use the TBB's. I'd recommend using them in the event you wish to move away from the DD4T mvc framework in the future. Simply output your content as REL and transform the TCDL tags yourself when you return your content from the broker.


10

Something like this should work: using (var ctTypeCriteria = new ItemTypeCriteria(32)) { using (var idCriteria = new ItemReferenceCriteria(3148)) { var ctAndIdCriteria = new AndCriteria(ctTypeCriteria, idCriteria); var outputFormat = ((ITemplateMeta)new Tridion.ContentDelivery.DynamicContent.Query.Query(andCrit)....


10

For anyone else stuck with this, here's the solution. Oracle 12c introduces multitenancy. With this architecture the Tridion Content Delivery database must be set up in the pluggable database rather than the container database that is the default when you first connect via sqlplus. To switch to the pluggable database you will need to log in "sys as sysdba" ...


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 ...


10

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 ...


10

Yes, it turns out we were indeed missing a Content Delivery hotfix. We installed the latest cumulative CD hotfix (CD_8.5.0.9057), which solved our issue. The specific hotfix that originally caught our attention was CD_8.5.0.3300, as its problem description was exactly the issue we were seeing.


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