Hot answers tagged

16

Actually there is a better and far safer solution than the one @Nuno proposes. What you can do is "mock unpublish process". You can capture undeploy transport package on CD side of some other page, then change it to have id of your page (change XML that contains inpublish instructions), and copy it into incoming folder of deployer. Deployer will pick it up ...


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


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

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


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

You need two DB Broker DB - It is configured in httpUpload and your Delivery website Session Preview DB - it will be used by Session preview service and this service is consumed by XPM. No separate db for XPM. This db will also configured in storage config of your website. HttpUpload and Odata.svc would be separate websites


12

The setup is correct, and the rendered output is correct as well. However, you will need to create some code to handle images stored in the DB by your webserver. Your webserver is not able to do this by default, and Tridion also doesn't have something like that out of the box. I'm not sure if you are using DD4T or not. DD4T does have a module that takes ...


12

When you use the broker API, you can add all sorts of criteria to filter One of the available criteria is the CustomMetaValueCriteria class, which allows filtering for a custom metadata string value. It takes a couple of parameters the key of the custom metadata field the value it should filter on an operator like greater than, equal, not equal,... I ...


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


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


9

As hinted at by Nick, the Criteria.AddCriteria method doesn't return a Criteria object, so you can't assign it as you're trying to. What you probably want is something like this: searchCriteria.AddCriteria(finalCriteria); myCriteria = searchCriteria; Note that if you do this, searchCriteria and myCriteria will be the same object instance, so changes to one ...


9

Tridion uses the Hibernate framework for it's database persistence, so Hibernate's logging is what needs to be set up. In logback.xml define the following: 1) Define an appender to put the DB log statements into a separate file. Simply paste this into your logback.xml: <appender name="rollingHibernateLog" class="ch.qos.logback.core.rolling....


9

Doesn't Content Service become bottleneck on SDL Web 8.5? Yes and no. You're indeed in fact moving the processes, libraries and dependencies which fetch data from the Broker DB from the web app to a separate server or service. The effect of this is, that processes surrounding requests are spread across different JVMs, which in total bring a more scalable ...


9

Changing (or adding) an index may not seem like a big deal (and I would agree with this view) except that it will very likely break the database upgrade scripts whenever you decide to move to a future version. I have had this exact scenario recently where we had to remove the extra indices that were added before being able to successfully run the upgrade. ...


8

It looks like cd_dynamic.jar is missing in the lib folder. Update: Needs to remember that cd_dynamic.jar and cd_dynamic_conf.xml are dependent on each other. Hence, cd_dynamic.jar should be placed in lib folder cd_dynamic_conf.xml should be placed in config folder


8

There is no dependency between your CM and CD database other than the version of SDL Tridion, so provided you are using a supported database and client version, you are good to go. The only differences between using Oracle and MS SQL server I have seen in the past was ordering of characters. I remember once that on a production server we were using Oracle ...


7

Have you considered using a Redundancy of data for instance SQL Server Database Cluster or Oracle RAC? SQL Cluster or Oracle RAC will keep your data redundant and in sync for possible failures. Now I have noticed in previous projects that an Active / Active configuration is not supported by Tridion and we had to move to an Active / Passive model.


7

You should not run into any issues. SDL will always recommend installing these two databases on different machines. It is a fully supported scenario. If you are moving your Broker DB to the new machine, all you should need to do is edit your cd_broker_conf.xml (for 2009) or cd_storage_conf.xml (for 2011 or 2013). NOTE: Most implementations have more than ...


7

Transforming a broker configuration file to a storage configuration file is something that should only take place during an upgrade. In normal running, current versions of Tridion use only the storage configuration. If you don't have one, the correct way to get one is to create one with a text editor. Generally it's a good idea to begin with the sample ...


7

I would be suspicious of DFS. If it is copying the files too often, you will trigger unnecessary recompiles, and therefore application restarts. You can investigate this by using perfmon and adding some ASP.NET counters, specifically CompilationsTotal and ApplicationRestarts. Then just check if the results correlate with your performance dropouts.


7

I would suggest setting your ASP.NET MVC (DD4T) app to use UTF-8 encoding. http://msdn.microsoft.com/en-us/library/hy4kkhe0%28v=vs.71%29.aspx


7

You question may be more related cache channel service rather the Tridion CDA or it is little unclear as the question is mixing up on the functionality of Object Cache and CCS. Before I answer your question, Few Important Notes on Tridion Object Caching and Cache Channel Service(CCS): Tridion Object Caching on your CDA is memory based and stand alone to ...


7

I don't like quoting myself, but... who are we kidding: I love quoting myself. From over on StackOverflow: Tridion 5.3 was the first version where you got the option to store pages and binaries into the database. But the only way to retrieve them would then be through the API; so there wasn't a web site integration layer yet (unless you were already ...


7

Regular component fields cannot be queried in the content delivery system, as only system metadata, component metadata fields and taxonomy fields are stored there with the templates output. If you're only dealing with a few components you could load them all and check the Component Presentation content, but this is inefficient. You could move your content ...


7

TCDBroker, TCDLink and TCDWAI are Windows services which serve Tridion Content Delivery capability to your web applications. Your issue is probably got to do with that no valid JDK runtime is installed. Tridion 2013 requires a 32 and 64 bit JDK version 7 installed on your machine.


7

The best way forward is to contact SDL Customer Support, propose the changes and see what their thoughts are. Indices are not changing the structure of the data, but you don't want future product upgrades to be blocked either if your indices are in the way of database changes. So to be on the safe side: check with Customer Support or evaluate if the change ...


6

The short answer is 'yes' and 'yes'. The long answer: in your cd_storage_conf.xml you can specify the item type mapping DynamicLinkInfo to use a Content Delivery Database (FKA the Broker DB). While keeping all your other mappings to file system, this ensues that only your linking (i.e. Component, Binary and Page) info will end up in the CD DB. Regarding ...


6

in cd_broker_conf.xml you have section like following. <Storage> <Database Type="sql"> <Pool Type="jdbc" Size="5" MonitorInterval="60" IdleTimeout="120" CheckoutTimeout="120" /> <DataSource Class="com.microsoft.sqlserver.jdbc.SQLServerDataSource"> <Property Name="serverName" Value="db"/> ...


6

If you do not need to manage the product data as content in anyway (edit it, translate it, link to it, put it through workflow etc.) there is no reason to put it in a Content Management System like Tridion at all - particularly if it runs to thousands of items. Tridion just becomes a middleman sitting between your web application and Product Information ...


6

There are quite a few things that can be checked. Its clear that there is a difference in the servers themselves or the way they are operating. Assuming they are just the same specs then I would look at: The deployed application; are all the files the right versions The configuration; caching on in all places? Is the config the same? Is the network on the ...


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